
From nobody Tue Sep  1 10:56:40 2015
Return-Path: <peter@andyet.net>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6685F1B64AA for <precis@ietfa.amsl.com>; Tue,  1 Sep 2015 10:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Id0UZgIP9S33 for <precis@ietfa.amsl.com>; Tue,  1 Sep 2015 10:56:38 -0700 (PDT)
Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com [209.85.213.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A6481B6345 for <precis@ietf.org>; Tue,  1 Sep 2015 10:56:36 -0700 (PDT)
Received: by igcpb10 with SMTP id pb10so7193863igc.1 for <precis@ietf.org>; Tue, 01 Sep 2015 10:56:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=k8P3yni/5omMHeUIieL6PRqU7ytx85EgPYtZI4/8LY8=; b=MlDU4CmIN2BGeXklEUEnEK8igvv3TYyWlSRmYvfPUH7XIvUKLsiefzf9Gi20fJR/g0 GBtVDcs5a/q+EYFRIDM8QhwV2i7QfDTJXtvvbhLYKJSvY9frDgl4OHh9MngXsHp1llD4 N16NRtHcH7eTPT3Xxp+G8J60XdkdJPtygOAqUfn3+TcNkuQytBwIepUK5iS+kzdjFNHQ THOiy7WyIJi6gk7Zc5gfViba3yjCGDEQNO8a9nYkSUwvV479wLJqk6Drcyirx++dUtkE 7Dt2cwg3TBXKDnVIy0ceN0sZD/ZDlRfNY+P0tZFhRwpjvftRkwC8KyfDVUlffKBYU286 drrQ==
X-Gm-Message-State: ALoCoQmAm8xdNCEYba9lco9jvBdlqySTBImiA8jwpu4VgmWBTIv9Dpf43/luxvbVtAXRzilX/ySV
X-Received: by 10.50.138.137 with SMTP id qq9mr3904359igb.47.1441130195810; Tue, 01 Sep 2015 10:56:35 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:90fe:6b6b:a4b9:ca9b]) by smtp.googlemail.com with ESMTPSA id au6sm2235988igc.0.2015.09.01.10.56.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Sep 2015 10:56:35 -0700 (PDT)
To: Ben Campbell <ben@nostrum.com>, The IESG <iesg@ietf.org>
References: <20150901045033.18104.5426.idtracker@ietfa.amsl.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E5E6D0.1000307@andyet.net>
Date: Tue, 1 Sep 2015 11:56:32 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <20150901045033.18104.5426.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/6_0arLC0VUvqFvSrnwhH8JddnEY>
Cc: draft-ietf-precis-nickname@ietf.org, draft-ietf-precis-nickname.ad@ietf.org, precis@ietf.org, precis-chairs@ietf.org, draft-ietf-precis-nickname.shepherd@ietf.org, joe-ietf@cursive.net
Subject: Re: [precis] Ben Campbell's Yes on draft-ietf-precis-nickname-18: (with COMMENT)
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 17:56:39 -0000

On 8/31/15 10:50 PM, Ben Campbell wrote:
> Ben Campbell has entered the following ballot position for
> draft-ietf-precis-nickname-18: Yes
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-precis-nickname/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Yay! Just a few nits:
>
> -- Abstract:
> The abstract could be beefed up against? Maybe say what a nickname is in
> this context?
> [Edit: "Against"?  I meant "a bit".]

Good idea.

> -- 1.1, first paragraph: "...participants to specify a nickname ..."
> Plural agreement mismatch.

Noted.

> -- 1.1, 2nd paragraph:
> People really use "petname" for this? Who knew?

Yes. Perhaps a pointer to 
http://www.skyhunter.com/marcs/petnames/IntroPetNames.html would be helpful?

Peter



-- 
Peter Saint-Andre
https://andyet.com/


From nobody Tue Sep  1 12:44:55 2015
Return-Path: <peter@andyet.net>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A02521B35C8 for <precis@ietfa.amsl.com>; Tue,  1 Sep 2015 12:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M3ruHNJ5NfNJ for <precis@ietfa.amsl.com>; Tue,  1 Sep 2015 12:44:52 -0700 (PDT)
Received: from mail-ig0-f177.google.com (mail-ig0-f177.google.com [209.85.213.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 950111B3568 for <precis@ietf.org>; Tue,  1 Sep 2015 12:44:50 -0700 (PDT)
Received: by igcrk20 with SMTP id rk20so9409880igc.1 for <precis@ietf.org>; Tue, 01 Sep 2015 12:44:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=VFOQTprt1bXSfzjZuS+et057zgHZSP0QyXemRZkZsG0=; b=FVPoNAYtG9s4fv13HtfggzUC9IYxTT3LjTbTsMfuKmVVjs3G2UEzoGkuGhQ9Z+Qcrq DYjJxC2DpCIJyhG4eWGqP8cND3uxBBAlUSQDpISXLM4zf16p3U6evunhjn0ovTH9kd/f YqovMTdcg1R1anDmwJd7BYZjvF+HfGykQleRjitOASZSBuqycY7VoZyn/ahs/iwlHqG+ y22g40z0RDtXNejMquoXCmIRVgDYs7jF3BlUs/tVfzbJyZ+p5E4YTJXw2Iy9e+O9OE5w dncLmAwCp3WpvRQvpyg8Gpw3c2/pZbQNV1S/JJpELGsz6MjEhrFUyMrTxfM5jOA8/AGa 233g==
X-Gm-Message-State: ALoCoQk/jW2ePPZNvzhhJVFPw1v50PPq2SPmsGf6mmbYpQ6z4fEqy1lVztYlhRgFdtFCrejmIrjC
X-Received: by 10.50.142.98 with SMTP id rv2mr3834669igb.41.1441136689807; Tue, 01 Sep 2015 12:44:49 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:90fe:6b6b:a4b9:ca9b]) by smtp.googlemail.com with ESMTPSA id o19sm2478171igs.18.2015.09.01.12.44.48 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Sep 2015 12:44:48 -0700 (PDT)
To: Ben Campbell <ben@nostrum.com>, The IESG <iesg@ietf.org>
References: <20150901045033.18104.5426.idtracker@ietfa.amsl.com> <55E5E6D0.1000307@andyet.net>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E6002F.8050408@andyet.net>
Date: Tue, 1 Sep 2015 13:44:47 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <55E5E6D0.1000307@andyet.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/2ASOfg2Lkg6OXptDk9dly4cmFI0>
Cc: draft-ietf-precis-nickname@ietf.org, draft-ietf-precis-nickname.ad@ietf.org, precis@ietf.org, precis-chairs@ietf.org, draft-ietf-precis-nickname.shepherd@ietf.org, joe-ietf@cursive.net
Subject: Re: [precis] Ben Campbell's Yes on draft-ietf-precis-nickname-18: (with COMMENT)
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 19:44:53 -0000

On 9/1/15 11:56 AM, Peter Saint-Andre - &yet wrote:
> On 8/31/15 10:50 PM, Ben Campbell wrote:
>> Ben Campbell has entered the following ballot position for
>> draft-ietf-precis-nickname-18: Yes
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-precis-nickname/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Yay! Just a few nits:
>>
>> -- Abstract:
>> The abstract could be beefed up against? Maybe say what a nickname is in
>> this context?
>> [Edit: "Against"?  I meant "a bit".]
>
> Good idea.

I suggest:

    This document describes methods for handling Unicode strings
    representing memorable, human-friendly names (variously called
    "nicknames", "display names", or "petnames") for people, devices,
    accounts, websites, and other entities.

>> -- 1.1, first paragraph: "...participants to specify a nickname ..."
>> Plural agreement mismatch.
>
> Noted.
>
>> -- 1.1, 2nd paragraph:
>> People really use "petname" for this? Who knew?
>
> Yes. Perhaps a pointer to
> http://www.skyhunter.com/marcs/petnames/IntroPetNames.html would be
> helpful?

I think Section 1.1 could use a bit of clarification through regarding 
terminology, something like the following...

###

    A number of technologies and applications provide the ability for a
    person to choose a memorable, human-friendly name in a communications
    context, or to set such a name for another entity entity such as a
    device, account, contact, or website.  Such names are variously
    called "nicknames" (e.g., in chatroom applications), "display names"
    (e.g., in Internet mail), or "petnames" (see [1]); for consistency,
    these are all called "nicknames" in this document.

    Nicknames are commonly supported in technologies for textual
    chatrooms, e.g., Internet Relay Chat [RFC2811] and multi-party chat
    technologies based on the Extensible Messaging and Presence Protocol
    (XMPP) [RFC6120] [XEP-0045], the Message Session Relay Protocol
    (MSRP) [RFC4975] [I-D.ietf-simple-chat], and Centralized Conferencing
    (XCON) [RFC5239] [I-D.boulton-xcon-session-chat].  Recent chatroom
    technologies also allow internationalized nicknames because they
    support characters from outside the ASCII range [RFC20], typically by
    means of the Unicode character set [Unicode].  Although such
    nicknames tend to be used primarily for display purposes, they are
    sometimes used for programmatic purposes as well (e.g., kicking users
    or avoiding nickname conflicts).

    A similar usage enables a person to set their own preferred display
    name or to set a preferred display name for another user (e.g., the
    "display-name" construct in the Internet message format [RFC5322] and
    [XEP-0172] in XMPP).

    Memorable, human-friendly names are also used in contexts other than
    personal messaging, such as names for devices (e.g., in a network
    visualization application), websites (e.g., for bookmarks in a web
    browser), accounts (e.g., in a web interface for a list of payees in
    a bank account), people (e.g., in a contact list application), and
    the like.

    The rules specified in this document can be applied in all of the
    foregoing contexts.

    To increase the likelihood that memorable, human-friendly names will
    work in ways that make sense for typical users throughout the world,
    this document defines rules for preparing, enforcing, and comparing
    internationalized nicknames.

...

[1] http://www.skyhunter.com/marcs/petnames/IntroPetNames.html

###

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Tue Sep  1 13:22:38 2015
Return-Path: <ben@nostrum.com>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 520311B4234 for <precis@ietfa.amsl.com>; Tue,  1 Sep 2015 13:22:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vk6DA1UOvKYe for <precis@ietfa.amsl.com>; Tue,  1 Sep 2015 13:22:35 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDB7D1B2E91 for <precis@ietf.org>; Tue,  1 Sep 2015 13:22:35 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t81KMNZV078272 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 1 Sep 2015 15:22:34 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: "Ben Campbell" <ben@nostrum.com>
To: "Peter Saint-Andre - &yet" <peter@andyet.net>
Date: Tue, 01 Sep 2015 15:22:23 -0500
Message-ID: <DB798CF6-C9E7-4DC4-9184-1CEE4EF9534B@nostrum.com>
In-Reply-To: <55E6002F.8050408@andyet.net>
References: <20150901045033.18104.5426.idtracker@ietfa.amsl.com> <55E5E6D0.1000307@andyet.net> <55E6002F.8050408@andyet.net>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/bkKYXPl8Y1bDhiGCdSA4iPbIcFg>
Cc: draft-ietf-precis-nickname@ietf.org, draft-ietf-precis-nickname.ad@ietf.org, precis@ietf.org, draft-ietf-precis-nickname.shepherd@ietf.org, The IESG <iesg@ietf.org>, joe-ietf@cursive.net, precis-chairs@ietf.org
Subject: Re: [precis] Ben Campbell's Yes on draft-ietf-precis-nickname-18: (with COMMENT)
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 20:22:37 -0000

On 1 Sep 2015, at 14:44, Peter Saint-Andre - &yet wrote:

[...]

>>>
>>> -- Abstract:
>>> The abstract could be beefed up against? Maybe say what a nickname 
>>> is in
>>> this context?
>>> [Edit: "Against"?  I meant "a bit".]
>>
>> Good idea.
>
> I suggest:
>
> This document describes methods for handling Unicode strings
> representing memorable, human-friendly names (variously called
> "nicknames", "display names", or "petnames") for people, devices,
> accounts, websites, and other entities.
>

That WFM.

[...]
>>
>>> -- 1.1, 2nd paragraph:
>>> People really use "petname" for this? Who knew?
>>
>> Yes. Perhaps a pointer to
>> http://www.skyhunter.com/marcs/petnames/IntroPetNames.html would be
>> helpful?
>
> I think Section 1.1 could use a bit of clarification through regarding 
> terminology, something like the following...
>
> ###
>
> A number of technologies and applications provide the ability for a
> person to choose a memorable, human-friendly name in a communications
> context, or to set such a name for another entity entity such as a
> device, account, contact, or website.  Such names are variously
> called "nicknames" (e.g., in chatroom applications), "display names"
> (e.g., in Internet mail), or "petnames" (see [1]); for consistency,
> these are all called "nicknames" in this document.
>
> Nicknames are commonly supported in technologies for textual
> chatrooms, e.g., Internet Relay Chat [RFC2811] and multi-party chat
> technologies based on the Extensible Messaging and Presence Protocol
> (XMPP) [RFC6120] [XEP-0045], the Message Session Relay Protocol
> (MSRP) [RFC4975] [I-D.ietf-simple-chat], and Centralized Conferencing
> (XCON) [RFC5239] [I-D.boulton-xcon-session-chat].  Recent chatroom
> technologies also allow internationalized nicknames because they
> support characters from outside the ASCII range [RFC20], typically by
> means of the Unicode character set [Unicode].  Although such
> nicknames tend to be used primarily for display purposes, they are
> sometimes used for programmatic purposes as well (e.g., kicking users
> or avoiding nickname conflicts).
>
> A similar usage enables a person to set their own preferred display
> name or to set a preferred display name for another user (e.g., the
> "display-name" construct in the Internet message format [RFC5322] and
> [XEP-0172] in XMPP).
>
> Memorable, human-friendly names are also used in contexts other than
> personal messaging, such as names for devices (e.g., in a network
> visualization application), websites (e.g., for bookmarks in a web
> browser), accounts (e.g., in a web interface for a list of payees in
> a bank account), people (e.g., in a contact list application), and
> the like.
>
> The rules specified in this document can be applied in all of the
> foregoing contexts.
>
> To increase the likelihood that memorable, human-friendly names will
> work in ways that make sense for typical users throughout the world,
> this document defines rules for preparing, enforcing, and comparing
> internationalized nicknames.

That also WFM. (And for the record, I really didn't expect my "petname" 
observation to be actionable. But I like the proposed text.)


>
> ...
>
> [1] http://www.skyhunter.com/marcs/petnames/IntroPetNames.html
>
> ###
>
> Peter
>
> -- 
> Peter Saint-Andre
> https://andyet.com/


From nobody Wed Sep  2 15:04:49 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B85C1B37C2; Wed,  2 Sep 2015 15:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9wbXeB8uCo-1; Wed,  2 Sep 2015 15:04:43 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C1BCD1B3E22; Wed,  2 Sep 2015 15:04:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150902220443.12714.44152.idtracker@ietfa.amsl.com>
Date: Wed, 02 Sep 2015 15:04:43 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/hHTpYdCHHZxiVfpd5QEXZK_auFU>
Cc: draft-ietf-precis-mappings.ad@ietf.org, precis@ietf.org, draft-ietf-precis-mappings.shepherd@ietf.org, stpeter@jabber.org, draft-ietf-precis-mappings@ietf.org, precis-chairs@ietf.org
Subject: [precis] Stephen Farrell's No Objection on draft-ietf-precis-mappings-11: (with COMMENT)
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2015 22:04:45 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-precis-mappings-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-precis-mappings/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


- The write-up didn't tell me if this is likely to be
considered as neutral by the Unicode folks, or as
something non-neutral. I'm curious about that, but not
concerned much. I do think the IESG should be aware
though if this is something that might cause e.g.
liaison fun for the IAB later on.  (I'm not saying I
think it does/would btw, just that I'd like to know if
it might.)

- The secdir review [1] raised an issue and some
changes were proposed for a -12 version that hasn't
yet popped out (which is fine). This is just to note
that to decrease the probability we forget:-)

   [1] https://www.ietf.org/mail-archive/web/secdir/current/msg05900.html



From nobody Wed Sep  2 16:02:13 2015
Return-Path: <peter@andyet.net>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09B141B2C42 for <precis@ietfa.amsl.com>; Wed,  2 Sep 2015 16:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LS4MXqXRZ-GM for <precis@ietfa.amsl.com>; Wed,  2 Sep 2015 16:02:11 -0700 (PDT)
Received: from mail-ig0-f170.google.com (mail-ig0-f170.google.com [209.85.213.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AD991B53D3 for <precis@ietf.org>; Wed,  2 Sep 2015 16:02:10 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so1676614igb.0 for <precis@ietf.org>; Wed, 02 Sep 2015 16:02:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=mO2KltHxFRIjSGWnuWSDL1QZBBkau3Bc1IX6Sizl8kI=; b=ElbW13P32Sxvr9LHefTnE3q2NDZHF4mYz9CX/UIO2+WCUy23yUnpW/xJXpgs2OB010 9CRnBToD6CM8nCqIzDHIrdOpLsrRJtp7zIig8aFgHLF9t21M5tKqqqVJq1hG5vtmbrcN xnRCJn+lpKU7f1YJfDW/8wtuDBt0taYz3fqYDUIw4vpSCG+6yS5JVjfdT9+hyGt93z3W eB5PerVIoc4dSwsvnkkpDyJCAVOViypGz6xWxfuGM3Fo1KFKVJRq1qAScGgibrN+FEkU sBlwA2me24psRd9BESOTKULdZ64hoR4IL3jEH9pM3bCd3yhSgEMIgbxL9ebbbWU32Z1F CHEA==
X-Gm-Message-State: ALoCoQmdZHfzqT5cnoasUJrNxdLhbsfB/Z4ZaSzW+QjrKaFglvT+QRO4i1D2hcLhYxyA5vwGN3td
X-Received: by 10.50.77.110 with SMTP id r14mr5537318igw.69.1441234929803; Wed, 02 Sep 2015 16:02:09 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:95e9:2445:47d:81c6]) by smtp.googlemail.com with ESMTPSA id l14sm20245241ioe.35.2015.09.02.16.02.07 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 Sep 2015 16:02:08 -0700 (PDT)
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
References: <20150902220443.12714.44152.idtracker@ietfa.amsl.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E77FEE.8050209@andyet.net>
Date: Wed, 2 Sep 2015 17:02:06 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <20150902220443.12714.44152.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/a8fDm8lNUMelcNC75AtItlX6WqI>
Cc: draft-ietf-precis-mappings.ad@ietf.org, precis@ietf.org, draft-ietf-precis-mappings.shepherd@ietf.org, stpeter@jabber.org, draft-ietf-precis-mappings@ietf.org, precis-chairs@ietf.org
Subject: Re: [precis] Stephen Farrell's No Objection on draft-ietf-precis-mappings-11: (with COMMENT)
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2015 23:02:13 -0000

<hat type='shepherd'/>

On 9/2/15 4:04 PM, Stephen Farrell wrote:
> Stephen Farrell has entered the following ballot position for
> draft-ietf-precis-mappings-11: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-precis-mappings/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
>
> - The write-up didn't tell me if this is likely to be
> considered as neutral by the Unicode folks, or as
> something non-neutral. I'm curious about that, but not
> concerned much. I do think the IESG should be aware
> though if this is something that might cause e.g.
> liaison fun for the IAB later on.  (I'm not saying I
> think it does/would btw, just that I'd like to know if
> it might.)

What do you mean by "neutral"?

> - The secdir review [1] raised an issue and some
> changes were proposed for a -12 version that hasn't
> yet popped out (which is fine). This is just to note
> that to decrease the probability we forget:-)
>
>     [1] https://www.ietf.org/mail-archive/web/secdir/current/msg05900.html

I do think that a pointer to RFC 7564 (especially §12.5) would be helpful.

Peter


From nobody Wed Sep  2 16:06:19 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70EC01B34A6; Wed,  2 Sep 2015 16:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lu2b84iI6JZG; Wed,  2 Sep 2015 16:06:13 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B43A91B39F9; Wed,  2 Sep 2015 16:06:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 5C717BDCC; Thu,  3 Sep 2015 00:06:11 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0sWp_TBPJ8by; Thu,  3 Sep 2015 00:06:10 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.42.21.56]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8725FBDD0; Thu,  3 Sep 2015 00:06:06 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1441235166; bh=eg9GkzOjk32UBt2w3rygRUlm38zJrHqkw79Ws9wTvp4=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=TV1YljX/OxU2OLAJV35XmexFPkU18TTcv6FqVmOE0zEFf+Us4bxIGchvsdWG2kxxc +9AsreC+q4jCsIrw31gLhACdWr5nmqkpnMHakhmKiG9XGSwqjSBsvFIF1DrIf8o1HO mv8g3f6N5rL80y1juiUk11yqKMqndBZz09F8p3KE=
To: Peter Saint-Andre - &yet <peter@andyet.net>, The IESG <iesg@ietf.org>
References: <20150902220443.12714.44152.idtracker@ietfa.amsl.com> <55E77FEE.8050209@andyet.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <55E780DE.6060402@cs.tcd.ie>
Date: Thu, 3 Sep 2015 00:06:06 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55E77FEE.8050209@andyet.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/LXyyat_Qzic2Oi5P9fJlN0IhtE4>
Cc: draft-ietf-precis-mappings.ad@ietf.org, precis@ietf.org, draft-ietf-precis-mappings.shepherd@ietf.org, stpeter@jabber.org, draft-ietf-precis-mappings@ietf.org, precis-chairs@ietf.org
Subject: Re: [precis] Stephen Farrell's No Objection on draft-ietf-precis-mappings-11: (with COMMENT)
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2015 23:06:15 -0000

Hiya,

On 03/09/15 00:02, Peter Saint-Andre - &yet wrote:
>>
>> - The write-up didn't tell me if this is likely to be
>> considered as neutral by the Unicode folks, or as
>> something non-neutral. I'm curious about that, but not
>> concerned much. I do think the IESG should be aware
>> though if this is something that might cause e.g.
>> liaison fun for the IAB later on.  (I'm not saying I
>> think it does/would btw, just that I'd like to know if
>> it might.)
> 
> What do you mean by "neutral"?

So I was being too oblique eh:-) Not something I'm good at
I guess.

I'm wondering if this contains anything about which they'd
go ballistic.

S.


From nobody Wed Sep  2 16:43:18 2015
Return-Path: <peter@andyet.net>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85D001B4994 for <precis@ietfa.amsl.com>; Wed,  2 Sep 2015 16:43:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3vZKBtzmJRQR for <precis@ietfa.amsl.com>; Wed,  2 Sep 2015 16:43:15 -0700 (PDT)
Received: from mail-ig0-f174.google.com (mail-ig0-f174.google.com [209.85.213.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DF201B4967 for <precis@ietf.org>; Wed,  2 Sep 2015 16:43:14 -0700 (PDT)
Received: by igcpb10 with SMTP id pb10so2193818igc.1 for <precis@ietf.org>; Wed, 02 Sep 2015 16:43:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=UYYCLOXH4CNIqVPJLUtRMeYXZKOfvQs9v2pSF88oQ3Y=; b=G+zyEuGvOrtElH+hY5dr0bnPuBr1nh5F/T3DBtdL53JIf1wdN9lC+ltWCYORRErgek x6Pm9ex29VlDokTOIS5LgDtZvejWJzJSUW/mcJNyTeHrJ4/fRIYUrdJqSTB4aknHXqmo EtFCQG237hs2fL7IBkK33m5xwVfL3mvnaVOJczf+ygp3T2Cqw7krqOrngp6bs0+YJV7A Nv/sCNlLtAddM9vQFodsqYjgh7g4mJ+B85Sjl7YAYIyEMYtztu/9TLBtmB895f7AUznJ 5npiuTyvNjPWAjIJiWDcZnMd5o5dO0/ShP6yskLSmi0BO15agIuaIFygK4s4c5NIiWti SkAA==
X-Gm-Message-State: ALoCoQlxsYIi3y8pxqTemFbxSIPHtTGCwS3Q2XPBIbUaYYialaJ+sToKfl+QH/KfyZ4hL9b79q/J
X-Received: by 10.50.18.40 with SMTP id t8mr7599959igd.57.1441237393894; Wed, 02 Sep 2015 16:43:13 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:95e9:2445:47d:81c6]) by smtp.googlemail.com with ESMTPSA id 10sm3554730igt.2.2015.09.02.16.43.12 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 Sep 2015 16:43:13 -0700 (PDT)
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
References: <20150902220443.12714.44152.idtracker@ietfa.amsl.com> <55E77FEE.8050209@andyet.net> <55E780DE.6060402@cs.tcd.ie>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E7898F.4070405@andyet.net>
Date: Wed, 2 Sep 2015 17:43:11 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <55E780DE.6060402@cs.tcd.ie>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/9HQM_PS5nWLMfCvPWyFeza1bWJM>
Cc: draft-ietf-precis-mappings.ad@ietf.org, precis@ietf.org, draft-ietf-precis-mappings.shepherd@ietf.org, stpeter@jabber.org, draft-ietf-precis-mappings@ietf.org, precis-chairs@ietf.org
Subject: Re: [precis] Stephen Farrell's No Objection on draft-ietf-precis-mappings-11: (with COMMENT)
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2015 23:43:16 -0000

On 9/2/15 5:06 PM, Stephen Farrell wrote:
>
> Hiya,
>
> On 03/09/15 00:02, Peter Saint-Andre - &yet wrote:
>>>
>>> - The write-up didn't tell me if this is likely to be
>>> considered as neutral by the Unicode folks, or as
>>> something non-neutral. I'm curious about that, but not
>>> concerned much. I do think the IESG should be aware
>>> though if this is something that might cause e.g.
>>> liaison fun for the IAB later on.  (I'm not saying I
>>> think it does/would btw, just that I'd like to know if
>>> it might.)
>>
>> What do you mean by "neutral"?
>
> So I was being too oblique eh:-) Not something I'm good at
> I guess.
>
> I'm wondering if this contains anything about which they'd
> go ballistic.

I'm just a lowly shepherd, but I don't think so...



From nobody Thu Sep  3 10:48:54 2015
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 577F31B3823 for <precis@ietfa.amsl.com>; Thu,  3 Sep 2015 10:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.588
X-Spam-Level: 
X-Spam-Status: No, score=0.588 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, J_CHICKENPOX_46=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mKvPJc6ocBaB for <precis@ietfa.amsl.com>; Thu,  3 Sep 2015 10:48:47 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id D33941B3936 for <precis@ietf.org>; Thu,  3 Sep 2015 10:48:34 -0700 (PDT)
Received: from [206.123.31.98] (kuwa.viagenie.ca [206.123.31.98]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 5FA054757C for <precis@ietf.org>; Thu,  3 Sep 2015 13:48:34 -0400 (EDT)
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: precis@ietf.org
Date: Thu, 03 Sep 2015 13:48:23 -0400
Message-ID: <5D7EF0E6-0CDF-4C8C-A43A-9D756050CFC9@viagenie.ca>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.1r5084)
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/YlaI3P2HPm5R8nAzAwF_M2V69k4>
Subject: [precis] yokohama: no meeting
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 17:48:48 -0000

Hello,
  co-chairs think there is no need for a precis meeting at the next 
IETF. Unless someone disagrees, we are not planning to request time slot 
for Yokohama.

Regards, Marc&Alexey


From nobody Thu Sep  3 10:52:03 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A04E1B324B; Thu,  3 Sep 2015 10:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z62TJiiz5_4r; Thu,  3 Sep 2015 10:51:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 379381B3490; Thu,  3 Sep 2015 10:51:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150903175158.13649.98921.idtracker@ietfa.amsl.com>
Date: Thu, 03 Sep 2015 10:51:58 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/pAqrNTbymIWb7u78gHvgbW82GHo>
Cc: precis@ietf.org
Subject: [precis] I-D Action: draft-ietf-precis-nickname-19.txt
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 17:52:00 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Preparation and Comparison of Internationalized Strings Working Group of the IETF.

        Title           : Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames
        Author          : Peter Saint-Andre
	Filename        : draft-ietf-precis-nickname-19.txt
	Pages           : 10
	Date            : 2015-09-03

Abstract:
   This document describes methods for handling Unicode strings
   representing memorable, human-friendly names (variously called
   "nicknames", "display names", or "petnames") for people, devices,
   accounts, websites, and other entities.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-precis-nickname/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-precis-nickname-19

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-precis-nickname-19


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Sep  3 10:53:58 2015
Return-Path: <peter@andyet.net>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE5F1B38A9 for <precis@ietfa.amsl.com>; Thu,  3 Sep 2015 10:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bW3jhpzORBWY for <precis@ietfa.amsl.com>; Thu,  3 Sep 2015 10:53:54 -0700 (PDT)
Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com [209.85.213.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CFCF1B32A8 for <precis@ietf.org>; Thu,  3 Sep 2015 10:53:54 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so54954662igb.0 for <precis@ietf.org>; Thu, 03 Sep 2015 10:53:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=OnAoYIChwMxMvYc7Kd2uj2i4GAVbpA8aK7y8/kbxC4w=; b=lv9t6W58CWwoNTaw7xaVHnDMkY1IK3GtTdpO+h8k5jd9vg4vwK0QOVgDLDZqgkgPIM WXjGTNLOF32RTb4JbhaMygRVKXoEa9gqZ0bstfjfaKMqngNZFao6VTPYtuwQW6wkTCdI rXNMvcXKML7qVVwCdYA167suFNr/dH3SOKCRuhWJDtsKl/2IiJaEfhDRPujIeoM2Hmz7 4yN1KAikoOqlCunqV1TPs9jX1cdh41/mbioIOq0kdGL3GfZQMLvaslslH/wp5Fhf6xa/ kc6E0fHLFfQU1l/wMBhRsZkaj4WYYX4n3fSVbAfQ99y+Ot1XiVodlTJVak0uJhSYD7Og wf9Q==
X-Gm-Message-State: ALoCoQmjZR34om2DWd31gg/rzkezP+nfNwBA+cqWbgOD3lFovl52WkBT5SjjISAeawwI7Xb9GVpw
X-Received: by 10.50.30.106 with SMTP id r10mr15776441igh.69.1441302833111; Thu, 03 Sep 2015 10:53:53 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:49b:c7f4:b326:4d42]) by smtp.googlemail.com with ESMTPSA id p65sm93039ioe.26.2015.09.03.10.53.51 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Sep 2015 10:53:52 -0700 (PDT)
To: precis@ietf.org
References: <20150903175158.13649.98921.idtracker@ietfa.amsl.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E8892E.4050101@andyet.net>
Date: Thu, 3 Sep 2015 11:53:50 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <20150903175158.13649.98921.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/oEBbi_620SNzslOssl1oI23tEY8>
Subject: Re: [precis] I-D Action: draft-ietf-precis-nickname-19.txt
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 17:53:56 -0000

Some adjustments to address IESG and designated expert feedback...

On 9/3/15 11:51 AM, internet-drafts@ietf.org wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Preparation and Comparison of Internationalized Strings Working Group of the IETF.
>
>          Title           : Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames
>          Author          : Peter Saint-Andre
> 	Filename        : draft-ietf-precis-nickname-19.txt
> 	Pages           : 10
> 	Date            : 2015-09-03
>
> Abstract:
>     This document describes methods for handling Unicode strings
>     representing memorable, human-friendly names (variously called
>     "nicknames", "display names", or "petnames") for people, devices,
>     accounts, websites, and other entities.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-precis-nickname/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-precis-nickname-19
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-precis-nickname-19
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> precis mailing list
> precis@ietf.org
> https://www.ietf.org/mailman/listinfo/precis
>


From nobody Thu Sep  3 10:56:55 2015
Return-Path: <peter@andyet.net>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF56C1B3490 for <precis@ietfa.amsl.com>; Thu,  3 Sep 2015 10:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PpDhyR4N7NYe for <precis@ietfa.amsl.com>; Thu,  3 Sep 2015 10:56:50 -0700 (PDT)
Received: from mail-ig0-f177.google.com (mail-ig0-f177.google.com [209.85.213.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 483AE1B3348 for <precis@ietf.org>; Thu,  3 Sep 2015 10:56:50 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so20611686igb.0 for <precis@ietf.org>; Thu, 03 Sep 2015 10:56:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=9PL+q8+9j0OBZDHNh3K5V/QLL70QWbNw2cFsqDBdtY0=; b=gYLpoo58UwV4JWDZ7nzmOZPCZxDRtFjdc8TynDr6WlTxUko8Aa6wvCNimaaIW7sluN xNPCwbPXGaomcOr+u5AQHW5VMKpGGdOXz1JnXE6XsntVWZzY9sQ2sQC35vVE/BxKphtv DAQHHSe8jQApasuNB5Ist0R1NPgGS6wD3xI8g4N1DOF8zswTwH0cvU9znxxXZqU+iMk7 dB6TEzmobSqRwKjcShZYyynaW28MqmJzvpqppGLU0vzYaOINnRUpm5ehJfDCgrd7EIxw MRO3q0h7mWHkJBG0rBrUTkdmmWcF7blQkWcbWlFVf4n6KSLuh/AiN4GN/GNaoNdoDX8w SPDA==
X-Gm-Message-State: ALoCoQmTazejFvwH51w+7IId4GgpGWBVW2eLHHiaSVqMT6sCMv2guwcIhBsMMKoqMJrOucJkDBjX
X-Received: by 10.50.73.98 with SMTP id k2mr15399561igv.96.1441303009541; Thu, 03 Sep 2015 10:56:49 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id k70sm106118iod.11.2015.09.03.10.56.48 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Sep 2015 10:56:49 -0700 (PDT)
To: Marc Blanchet <marc.blanchet@viagenie.ca>, precis@ietf.org
References: <5D7EF0E6-0CDF-4C8C-A43A-9D756050CFC9@viagenie.ca>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E889DE.4080904@andyet.net>
Date: Thu, 3 Sep 2015 11:56:46 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <5D7EF0E6-0CDF-4C8C-A43A-9D756050CFC9@viagenie.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/WdcT5PTXqLyopRujkF_Lc8lXtzs>
Subject: Re: [precis] yokohama: no meeting
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 17:56:52 -0000

On 9/3/15 11:48 AM, Marc Blanchet wrote:
> Hello,
>   co-chairs think there is no need for a precis meeting at the next
> IETF. Unless someone disagrees, we are not planning to request time slot
> for Yokohama.
>
> Regards, Marc&Alexey
>
> _______________________________________________
> precis mailing list
> precis@ietf.org
> https://www.ietf.org/mailman/listinfo/precis

That sound right. There's the question of whether to keep the WG open at 
all once the current I-Ds are finished (perhaps both -nickname and 
-mappings were approved in the IESG meeting earlier today?), but we can 
talk about that on the list (and the decision is really up to the AD 
anyway I suppose).

Peter



From nobody Thu Sep  3 11:57:40 2015
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33F561A8ADE for <precis@ietfa.amsl.com>; Thu,  3 Sep 2015 11:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9B3buAGok1HP for <precis@ietfa.amsl.com>; Thu,  3 Sep 2015 11:57:38 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FED61A89EB for <precis@ietf.org>; Thu,  3 Sep 2015 11:57:38 -0700 (PDT)
Received: by igbni9 with SMTP id ni9so47672494igb.0 for <precis@ietf.org>; Thu, 03 Sep 2015 11:57:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=+Z73GSnLaHZDCW/bfuPgal86s1RGzKp6dfqztGtL6/Q=; b=LB/dZ6ER0g6QuQtAvEDqaARsGeFYp/ywBDFsYBR7dVlvxQYdCiuktDcCseLr7vYpiL N5q80eXsLa5nRRPftQXET56msn4o2Ju05iw7+L/ABuUhpFPqZFDs5blT1YDjIkuS+q9u 2zEG5XUkSyYQtOtf+RFmZlyibT7x6jGHlaXSGLuM+yvR8xc/SOCVZn8CFF8fMw5+tVgZ x6Xd5vqCfTDAHVRlsl2C8xZSRkRCfGsea9GQgrzMtHUUjXk/fzAO2hfeabjt/RjwKNiS Jkk2KaW28GdUoJE//baRukc4Y4EneICpIMgwWmVyDjPD41W/JpaADZiuRtE5YhXVQG1m Rb9Q==
MIME-Version: 1.0
X-Received: by 10.50.83.104 with SMTP id p8mr1211674igy.90.1441306657706; Thu, 03 Sep 2015 11:57:37 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.17.24 with HTTP; Thu, 3 Sep 2015 11:57:37 -0700 (PDT)
In-Reply-To: <55E8892E.4050101@andyet.net>
References: <20150903175158.13649.98921.idtracker@ietfa.amsl.com> <55E8892E.4050101@andyet.net>
Date: Thu, 3 Sep 2015 14:57:37 -0400
X-Google-Sender-Auth: gY6kdhu1pNvoKJX1-MvPsyvIhAw
Message-ID: <CAC4RtVDtpzzF3FN_qLTFo7Dy6uHsrKyAX8C_b8SCE0Scgn6ojw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "Peter Saint-Andre - &yet" <peter@andyet.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/fsoJukfvH9kgPWkawLXoYt0oiXg>
Cc: precis@ietf.org
Subject: Re: [precis] I-D Action: draft-ietf-precis-nickname-19.txt
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 18:57:39 -0000

> Some adjustments to address IESG and designated expert feedback...

Thanks, and I have approved this version; you should see the
announcement on Tuesday (Monday is U.S. Labor Day, when we don't labor
(go figure)).

Barry


From nobody Thu Sep  3 12:22:16 2015
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB971B3511 for <precis@ietfa.amsl.com>; Thu,  3 Sep 2015 12:22:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGU0oW2VeIgX for <precis@ietfa.amsl.com>; Thu,  3 Sep 2015 12:22:15 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D23471A8F3F for <precis@ietf.org>; Thu,  3 Sep 2015 12:22:14 -0700 (PDT)
Received: by igcrk20 with SMTP id rk20so57080931igc.1 for <precis@ietf.org>; Thu, 03 Sep 2015 12:22:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=kzkJDTmA+55qm2GAeKgoFYCI3tzfgpbOvVVZSu4VJK0=; b=mH4mHqUMRHo5Xa5/nR4rAN4wZjoeVjihp5VxV2Ux5761sBK73ble0W+/wWCQ3vegEA irlqSra2Idd63PmSkXjF72ccqASZ2IhIZbtH/1TCFLnWcirDNg4kmzcdZIl3UpuFQxVx S9fxgXpns+m+KZzleIL6JdsYB2TSawalUsJSQOEQkOuQLSr4p1ojk3kQ401sQLVXHJuN AwCI25SPMYHQqCqzzrcpwYe04znuyzoq+ZMy2pIZj8SdxBlP+RXVoaEKH+wFecfggeIa uPk6WLhftLTFGpSAA4g1RqGmpruuuDqoutTvxgcxFmaTqV8ml/7vKK4dHemr2tGK+qBk qC1Q==
MIME-Version: 1.0
X-Received: by 10.50.129.10 with SMTP id ns10mr16592030igb.90.1441308134310; Thu, 03 Sep 2015 12:22:14 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.17.24 with HTTP; Thu, 3 Sep 2015 12:22:14 -0700 (PDT)
In-Reply-To: <55E889DE.4080904@andyet.net>
References: <5D7EF0E6-0CDF-4C8C-A43A-9D756050CFC9@viagenie.ca> <55E889DE.4080904@andyet.net>
Date: Thu, 3 Sep 2015 15:22:14 -0400
X-Google-Sender-Auth: uWiUEjEOHRVSR7MQLAmXLLfhrcE
Message-ID: <CAC4RtVD2=5n7MekpMiwo9qE2V-yzW0vxqmuR=pkuoikA=_zUGw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "Peter Saint-Andre - &yet" <peter@andyet.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/rVlHz3WthNoX0aTc0AJ6Nj39oXI>
Cc: precis@ietf.org
Subject: Re: [precis] yokohama: no meeting
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 19:22:15 -0000

> That sound right. There's the question of whether to keep the WG open at all
> once the current I-Ds are finished (perhaps both -nickname and -mappings
> were approved in the IESG meeting earlier today?), but we can talk about
> that on the list (and the decision is really up to the AD anyway I suppose).

Indeed, -nickname is approved, and -mappings is awaiting a version -12
to address comments by Ben and by the SecDir review... and the need to
quote and cite the "RECOMMENDED" sentence (there should NOT be a 2119
reference there).  The shepherd should please herd the sheep on that.

The working group will remain officially open until the RFCs are
published, at which point we'll close the working group but leave the
mailing list open for any continued discussion.

Barry


From nobody Tue Sep  8 07:28:02 2015
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C47051B33B6; Tue,  8 Sep 2015 07:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SDk3ocGYt_wo; Tue,  8 Sep 2015 07:27:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DDE651B4A96; Tue,  8 Sep 2015 07:27:52 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150908142752.14925.9291.idtracker@ietfa.amsl.com>
Date: Tue, 08 Sep 2015 07:27:52 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/ehV5Bd8pnh6Ns9V3i951STDEjW8>
Cc: precis chair <precis-chairs@ietf.org>, precis mailing list <precis@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [precis] Protocol Action: 'Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames' to Proposed Standard (draft-ietf-precis-nickname-19.txt)
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Sep 2015 14:28:00 -0000

The IESG has approved the following document:
- 'Preparation, Enforcement, and Comparison of Internationalized Strings
   Representing Nicknames'
  (draft-ietf-precis-nickname-19.txt) as Proposed Standard

This document is the product of the Preparation and Comparison of
Internationalized Strings Working Group.

The IESG contact persons are Ben Campbell, Barry Leiba and Alissa Cooper.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-precis-nickname/




Technical Summary

This document describes methods for handling internationalized
nicknames (or petnames).  Such uses are common in XMPP Multi-User Chat
(MUC), Message Session Relay Protocol (MSRP), and Centralized
Conferencing (XCON), but can also be encountered in other contexts,
such as contact lists, device names, and bookmarks.  This document
provides rules for preparing strings that represent an
internationalized nickname, as well as for comparing two
internationalized nicknames.  Also provided is guidance for using these
rules in application protocols.

Review and Consensus

This document received review both from participants active in the
PRECIS Working Group as well as individuals from the XMPP and SIP
communities.  The consensus of the PRECIS Working Group is to publish
this document.

A major topic of discussion in the Working Group was in regard to
"confusables", characters that often visually appear very similar to
(if not indistinguishable from) other characters.  While there was
desire to further combat confusables (e.g., rules and/or guidelines on
incorporating a "confusables" table), ultimately the consensus of the
Working Group was to warn implementers of their existence, use NFKC
normalization to mitigate a large degree of confusables, and note there
might be more rules or guidelines implementers and deployers could
follow (UTS39).

Personnel

Matthew Miller is the document shepherd, and Barry Leiba is the
responsible AD. 


From nobody Mon Sep 14 06:24:06 2015
Return-Path: <fsb@thefsb.org>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47DC51B3426 for <precis@ietfa.amsl.com>; Mon, 14 Sep 2015 06:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.199
X-Spam-Level: 
X-Spam-Status: No, score=-1.199 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_LETTER=-2, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cm2ufE14EABC for <precis@ietfa.amsl.com>; Mon, 14 Sep 2015 06:24:04 -0700 (PDT)
Received: from smtp66.iad3a.emailsrvr.com (smtp66.iad3a.emailsrvr.com [173.203.187.66]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB74D1B3AEA for <precis@ietf.org>; Mon, 14 Sep 2015 06:24:03 -0700 (PDT)
Received: from smtp25.relay.iad3a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp25.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 0107E18045F for <precis@ietf.org>; Mon, 14 Sep 2015 09:24:02 -0400 (EDT)
Received: by smtp25.relay.iad3a.emailsrvr.com (Authenticated sender: fsb-AT-thefsb.org) with ESMTPSA id 917FE180417 for <precis@ietf.org>; Mon, 14 Sep 2015 09:24:02 -0400 (EDT)
X-Sender-Id: fsb@thefsb.org
Received: from [10.0.1.2] (c-73-4-147-142.hsd1.ma.comcast.net [73.4.147.142]) (using TLSv1 with cipher DES-CBC3-SHA) by 0.0.0.0:465 (trex/5.4.2);  Mon, 14 Sep 2015 13:24:02 GMT
User-Agent: Microsoft-MacOutlook/14.5.5.150821
Date: Mon, 14 Sep 2015 09:23:58 -0400
From: Tom Worster <fsb@thefsb.org>
To: <precis@ietf.org>
Message-ID: <D21C42AE.654C4%fsb@thefsb.org>
Thread-Topic: 2 questions from an app developer
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3525067442_72656"
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/pmzwdKH8QyeyWMC5SGhhms3Rtfo>
Subject: [precis] 2 questions from an app developer
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Sep 2015 13:24:05 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3525067442_72656
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi,

Do I understand right that an RFC 7613 password must not contain a MIDDLE
DOT (U+00B7) unless both the previous and next characters are LATIN SMALL
LETTER L (U+006C)?

Are test vectors available for either of the RFC 7564  string classes or of
the RFC 7613 ID and password profiles?

If this is not the right place for these questions, please steer me in the
right direction.

Thanks for your consideration.

Tom Worster




--B_3525067442_72656
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space;"><div style=3D"color: rgb(0, 0, 0=
); font-family: Calibri, sans-serif; font-size: 16px;">Hi,</div><div style=3D"=
color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;"><br=
></div><div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; fo=
nt-size: 16px;">Do I understand right that an&nbsp;RFC 7613 password must no=
t contain a MIDDLE DOT (U+00B7) unless both the previous and next characters=
 are LATIN SMALL LETTER L (U+006C)?</div><div style=3D"color: rgb(0, 0, 0); fo=
nt-family: Calibri, sans-serif; font-size: 16px;"><br></div><div><font face=3D=
"Calibri,sans-serif">Are test vectors available for either of the RFC 7564 &=
nbsp;string classes or of the RFC 7613 ID and password profiles?</font></div=
><div><font face=3D"Calibri,sans-serif"><br></font></div><div><font face=3D"Cali=
bri,sans-serif">If this is not the right place for these questions, please s=
teer me in the right direction.</font></div><div><font face=3D"Calibri,sans-se=
rif"><br></font></div><div><font face=3D"Calibri,sans-serif">Thanks for your c=
onsideration.</font></div><div><font face=3D"Calibri,sans-serif"><br></font></=
div><div><font face=3D"Calibri,sans-serif">Tom Worster</font></div><div><font =
face=3D"Calibri,sans-serif"><br></font></div></body></html>

--B_3525067442_72656--



From nobody Fri Sep 18 12:07:52 2015
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4A8F1B3223 for <precis@ietfa.amsl.com>; Fri, 18 Sep 2015 12:07:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P8C6bxTIhv_s for <precis@ietfa.amsl.com>; Fri, 18 Sep 2015 12:07:49 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id A19831B3163 for <precis@ietf.org>; Fri, 18 Sep 2015 12:07:49 -0700 (PDT)
Received: from [206.123.31.98] (kuwa.viagenie.ca [206.123.31.98]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 2ADCA403D7 for <precis@ietf.org>; Fri, 18 Sep 2015 15:07:49 -0400 (EDT)
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: precis@ietf.org
Date: Fri, 18 Sep 2015 15:07:38 -0400
Message-ID: <80C069A2-6B14-4368-AFE9-859836C92B06@viagenie.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.1r5084)
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/AyzOhF0i0x-1D8HPNmqkkaHlZh0>
Subject: [precis] not meeting in yokohama
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Sep 2015 19:07:50 -0000

Hello,
  I donâ€™t think we have anything that requires a meeting in Yokohama. 
Therefore, Iâ€™m planning to not request a session in Yokohama. Please 
speak up soon if you think otherwise.

Regards, Marc.


From nobody Tue Sep 29 14:28:59 2015
Return-Path: <fsb@thefsb.org>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 205D21B5129 for <precis@ietfa.amsl.com>; Tue, 29 Sep 2015 14:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.201
X-Spam-Level: 
X-Spam-Status: No, score=-1.201 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_LETTER=-2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9YIPllKZHpdM for <precis@ietfa.amsl.com>; Tue, 29 Sep 2015 14:28:56 -0700 (PDT)
Received: from smtp98.iad3a.emailsrvr.com (smtp98.iad3a.emailsrvr.com [173.203.187.98]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAE0E1B5127 for <precis@ietf.org>; Tue, 29 Sep 2015 14:28:55 -0700 (PDT)
Received: from smtp5.relay.iad3a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp5.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id E2C94803FF; Tue, 29 Sep 2015 17:28:54 -0400 (EDT)
Received: by smtp5.relay.iad3a.emailsrvr.com (Authenticated sender: fsb-AT-thefsb.org) with ESMTPSA id F03CC80133;  Tue, 29 Sep 2015 17:28:50 -0400 (EDT)
X-Sender-Id: fsb@thefsb.org
Received: from [10.0.1.2] (c-73-4-147-142.hsd1.ma.comcast.net [73.4.147.142]) (using TLSv1 with cipher DES-CBC3-SHA) by 0.0.0.0:465 (trex/5.4.2);  Tue, 29 Sep 2015 21:28:54 GMT
User-Agent: Microsoft-MacOutlook/14.5.5.150821
Date: Tue, 29 Sep 2015 17:28:45 -0400
From: Tom Worster <fsb@thefsb.org>
To: Peter Saint-Andre <peter@andyet.com>, Alexey Melnikov <Alexey.Melnikov@isode.com>
Message-ID: <D230767C.6587A%fsb@thefsb.org>
Thread-Topic: Ambiguity in specification of case mapping in RFC 7613 and draft-ietf-precis-nickname
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/7wX6-L_9HxLN2qmFp09J3MnOGLw>
Cc: precis@ietf.org
Subject: [precis] Ambiguity in specification of case mapping in RFC 7613 and draft-ietf-precis-nickname
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2015 21:28:58 -0000

Peter, Alexey,

I think there is an ambiguity in the specification of case mapping in RFC
7613 and draft-ietf-precis-nickname-19.

RFC 7613 section 3.2.2 says

   3.  Case-Mapping Rule: Uppercase and titlecase characters MUST be
       mapped to their lowercase equivalents, preferably using Unicode
       Default Case Folding as defined in the Unicode Standard [Unicode]
       (at the time of this writing, the algorithm is specified in
       Chapter 3 of [Unicode7.0], but the chapter number might change in
       a future version of the Unicode Standard); see further discussion
       in Section 3.4.

But there are 55 code points in Unicode 7.0.0 that change under default
case folding that are neither uppercase nor titlecase characters, 12 of
which are Lowercase_Letter. I suspect this stems from a confusion between
Unicode case mapping and case folding. From the Unicode Case Mapping FAQ
(http://unicode.org/faq/casemap_charprop.html):

  Q: What is the difference between case mapping and case folding?

  A: Case mapping or case conversion is a process whereby strings are
  converted to a particular form=8Buppercase, lowercase, or titlecase=8B
  possibly for display to the user. Case folding is mostly used for
  caseless comparison of text, such as identifiers in a computer program,
  rather than actual text transformation. Case folding in Unicode is
  primarily based on the lowercase mapping, but includes additional
  changes to the source text to help make it language-insensitive and
  consistent. As a result, case-folded text should be used solely for
  internal processing and generally should not be stored or displayed to
  the end user.

The purpose of the UsernameCaseMapped and Nickname PRECIS Profiles is
internal string comparison so I would expect Unicode case folding without
exception was intended. But it seems the text might be saying that we
should remove from UCD CaseFolding.txt those code points that do not have
either Uppercase_Letter or Titlecase_Letter.

Similar text in draft-ietf-precis-nickname-19 leads to similar ambiguity.

The nickname profile can be corrected or the algorithm clarified. I'm
not sure what to do with a Proposed Standard RFC. Errata? Can the case
mapping rule be changed in IANA?
https://www.iana.org/assignments/precis-parameters/profiles/UsernameCaseMap
ped.txt
e.g. to "Apply Unicode default case folding"

Tom


These are the lines in question from UCD CaseFolding.txt to which I
prefixed their General Category.

Ll; 00B5; C; 03BC; # MICRO SIGN
Ll; 017F; C; 0073; # LATIN SMALL LETTER LONG S
Mn; 0345; C; 03B9; # COMBINING GREEK YPOGEGRAMMENI
Ll; 03C2; C; 03C3; # GREEK SMALL LETTER FINAL SIGMA
Ll; 03D0; C; 03B2; # GREEK BETA SYMBOL
Ll; 03D1; C; 03B8; # GREEK THETA SYMBOL
Ll; 03D5; C; 03C6; # GREEK PHI SYMBOL
Ll; 03D6; C; 03C0; # GREEK PI SYMBOL
Ll; 03F0; C; 03BA; # GREEK KAPPA SYMBOL
Ll; 03F1; C; 03C1; # GREEK RHO SYMBOL
Ll; 03F5; C; 03B5; # GREEK LUNATE EPSILON SYMBOL
Ll; 1E9B; C; 1E61; # LATIN SMALL LETTER LONG S WITH DOT ABOVE
Ll; 1FBE; C; 03B9; # GREEK PROSGEGRAMMENI
Nl; 2160; C; 2170; # ROMAN NUMERAL ONE
Nl; 2161; C; 2171; # ROMAN NUMERAL TWO
Nl; 2162; C; 2172; # ROMAN NUMERAL THREE
Nl; 2163; C; 2173; # ROMAN NUMERAL FOUR
Nl; 2164; C; 2174; # ROMAN NUMERAL FIVE
Nl; 2165; C; 2175; # ROMAN NUMERAL SIX
Nl; 2166; C; 2176; # ROMAN NUMERAL SEVEN
Nl; 2167; C; 2177; # ROMAN NUMERAL EIGHT
Nl; 2168; C; 2178; # ROMAN NUMERAL NINE
Nl; 2169; C; 2179; # ROMAN NUMERAL TEN
Nl; 216A; C; 217A; # ROMAN NUMERAL ELEVEN
Nl; 216B; C; 217B; # ROMAN NUMERAL TWELVE
Nl; 216C; C; 217C; # ROMAN NUMERAL FIFTY
Nl; 216D; C; 217D; # ROMAN NUMERAL ONE HUNDRED
Nl; 216E; C; 217E; # ROMAN NUMERAL FIVE HUNDRED
Nl; 216F; C; 217F; # ROMAN NUMERAL ONE THOUSAND
So; 24B6; C; 24D0; # CIRCLED LATIN CAPITAL LETTER A
So; 24B7; C; 24D1; # CIRCLED LATIN CAPITAL LETTER B
So; 24B8; C; 24D2; # CIRCLED LATIN CAPITAL LETTER C
So; 24B9; C; 24D3; # CIRCLED LATIN CAPITAL LETTER D
So; 24BA; C; 24D4; # CIRCLED LATIN CAPITAL LETTER E
So; 24BB; C; 24D5; # CIRCLED LATIN CAPITAL LETTER F
So; 24BC; C; 24D6; # CIRCLED LATIN CAPITAL LETTER G
So; 24BD; C; 24D7; # CIRCLED LATIN CAPITAL LETTER H
So; 24BE; C; 24D8; # CIRCLED LATIN CAPITAL LETTER I
So; 24BF; C; 24D9; # CIRCLED LATIN CAPITAL LETTER J
So; 24C0; C; 24DA; # CIRCLED LATIN CAPITAL LETTER K
So; 24C1; C; 24DB; # CIRCLED LATIN CAPITAL LETTER L
So; 24C2; C; 24DC; # CIRCLED LATIN CAPITAL LETTER M
So; 24C3; C; 24DD; # CIRCLED LATIN CAPITAL LETTER N
So; 24C4; C; 24DE; # CIRCLED LATIN CAPITAL LETTER O
So; 24C5; C; 24DF; # CIRCLED LATIN CAPITAL LETTER P
So; 24C6; C; 24E0; # CIRCLED LATIN CAPITAL LETTER Q
So; 24C7; C; 24E1; # CIRCLED LATIN CAPITAL LETTER R
So; 24C8; C; 24E2; # CIRCLED LATIN CAPITAL LETTER S
So; 24C9; C; 24E3; # CIRCLED LATIN CAPITAL LETTER T
So; 24CA; C; 24E4; # CIRCLED LATIN CAPITAL LETTER U
So; 24CB; C; 24E5; # CIRCLED LATIN CAPITAL LETTER V
So; 24CC; C; 24E6; # CIRCLED LATIN CAPITAL LETTER W
So; 24CD; C; 24E7; # CIRCLED LATIN CAPITAL LETTER X
So; 24CE; C; 24E8; # CIRCLED LATIN CAPITAL LETTER Y
So; 24CF; C; 24E9; # CIRCLED LATIN CAPITAL LETTER Z



From nobody Wed Sep 30 14:17:10 2015
Return-Path: <peter@andyet.net>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5BA1A9096 for <precis@ietfa.amsl.com>; Wed, 30 Sep 2015 14:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level: 
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQ4O-8XmSu0G for <precis@ietfa.amsl.com>; Wed, 30 Sep 2015 14:17:05 -0700 (PDT)
Received: from mail-io0-f179.google.com (mail-io0-f179.google.com [209.85.223.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BDCE1A9094 for <precis@ietf.org>; Wed, 30 Sep 2015 14:17:01 -0700 (PDT)
Received: by iow1 with SMTP id 1so25959787iow.1 for <precis@ietf.org>; Wed, 30 Sep 2015 14:17:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=kirWqMlp83m5zqfJeYqGqFaystaxGXMVZxFlYTfz5y8=; b=a6RCARqa2qzI6TD2si9TC0pA1SBIJ52tANyVXws6qnC31qD2FJ/mAq1+nF2HuU9+Oh akakz4eDfW+txF/rlHyNZ2rvhkP15XwaHb6WVdVTFfX6JdHN0vus1NfB+dp0/SAj1LiV thh/0aSk6fWdWB64dbpj168t7cm/4xanat4U0qBHPTNI+Djcp9aSPKCEifgcmBd2CIs3 9EbsThfljZ4byV+uA5HM99y5n+4i6iDJYNXac62lvoY1hD3rug+WgqLoZq5Y5y3SSMgY MWCczo1AUtYAPWIU7KuZbFPdT4bq5jBYohOpf9vEQyqMpkgD2fTFS7ipPPyVk2Y6Einu KPNw==
X-Gm-Message-State: ALoCoQkv5d2bpnQtZChhkd6XYTkY/aq8LIFDPcnYBuvVyh6sF+SHstv9WjzO/klkpz1yRU5xY0m6
X-Received: by 10.107.132.21 with SMTP id g21mr8518207iod.175.1443647820595; Wed, 30 Sep 2015 14:17:00 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:60ed:f1b7:fac4:1f7e]) by smtp.googlemail.com with ESMTPSA id y6sm1138795igl.17.2015.09.30.14.16.58 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Sep 2015 14:16:59 -0700 (PDT)
To: Tom Worster <fsb@thefsb.org>, Alexey Melnikov <Alexey.Melnikov@isode.com>
References: <D230767C.6587A%fsb@thefsb.org>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <560C5149.5090607@andyet.net>
Date: Wed, 30 Sep 2015 15:16:57 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <D230767C.6587A%fsb@thefsb.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/k4Nep28ztBMcfgeXHsghGfopwpQ>
Cc: precis@ietf.org
Subject: Re: [precis] Ambiguity in specification of case mapping in RFC 7613 and draft-ietf-precis-nickname
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2015 21:17:07 -0000

Hi Tom, thanks for the note.

My feeling is that we phrased things in a slightly wrong way, because we 
assumed that case-mapping applies primarily or only to uppercase and 
titlecase characters. I think this was more a matter of communication 
(because people think of case mapping as something needed only with 
respect to uppercase characters), whereas it obviously applies more 
generally (i.e., applying Unicode Default Case Folding will result in 
mapping of the code points you mention here).

We could do something like this in the nickname spec...

OLD

    3.  Case Mapping Rule: Uppercase and titlecase characters MUST be
        mapped to their lowercase equivalents using Unicode Default Case
        Folding as defined in the Unicode Standard [Unicode] (at the time
        of this writing, the algorithm is specified in Chapter 3 of
        [Unicode7.0]).  In applications that prohibit conflicting
        nicknames, this rule helps to reduce the possibility of confusion
        by ensuring that nicknames differing only by case (e.g.,
        "stpeter" vs. "StPeter") would not be presented to a human user
        at the same time.

NEW

    3.  Case Mapping Rule: Unicode Default Case Folding MUST be applied,
        as defined in the Unicode Standard [Unicode] (at the time
        of this writing, the algorithm is specified in Chapter 3 of
        [Unicode7.0]).  The primary result of doing so is that uppercase
        characters are mapped to lowercase characters. In applications
        that prohibit conflicting nicknames, this rule helps to reduce
        the possibility of confusion by ensuring that nicknames
        differing only by case (e.g., "stpeter" vs. "StPeter") would not
        be presented to a human user at the same time.

Thanks for raising this issue.

Peter

On 9/29/15 3:28 PM, Tom Worster wrote:
> Peter, Alexey,
>
> I think there is an ambiguity in the specification of case mapping in RFC
> 7613 and draft-ietf-precis-nickname-19.
>
> RFC 7613 section 3.2.2 says
>
>     3.  Case-Mapping Rule: Uppercase and titlecase characters MUST be
>         mapped to their lowercase equivalents, preferably using Unicode
>         Default Case Folding as defined in the Unicode Standard [Unicode]
>         (at the time of this writing, the algorithm is specified in
>         Chapter 3 of [Unicode7.0], but the chapter number might change in
>         a future version of the Unicode Standard); see further discussion
>         in Section 3.4.
>
> But there are 55 code points in Unicode 7.0.0 that change under default
> case folding that are neither uppercase nor titlecase characters, 12 of
> which are Lowercase_Letter. I suspect this stems from a confusion between
> Unicode case mapping and case folding. From the Unicode Case Mapping FAQ
> (http://unicode.org/faq/casemap_charprop.html):
>
>    Q: What is the difference between case mapping and case folding?
>
>    A: Case mapping or case conversion is a process whereby strings are
>    converted to a particular form‹uppercase, lowercase, or titlecase‹
>    possibly for display to the user. Case folding is mostly used for
>    caseless comparison of text, such as identifiers in a computer program,
>    rather than actual text transformation. Case folding in Unicode is
>    primarily based on the lowercase mapping, but includes additional
>    changes to the source text to help make it language-insensitive and
>    consistent. As a result, case-folded text should be used solely for
>    internal processing and generally should not be stored or displayed to
>    the end user.
>
> The purpose of the UsernameCaseMapped and Nickname PRECIS Profiles is
> internal string comparison so I would expect Unicode case folding without
> exception was intended. But it seems the text might be saying that we
> should remove from UCD CaseFolding.txt those code points that do not have
> either Uppercase_Letter or Titlecase_Letter.
>
> Similar text in draft-ietf-precis-nickname-19 leads to similar ambiguity.
>
> The nickname profile can be corrected or the algorithm clarified. I'm
> not sure what to do with a Proposed Standard RFC. Errata? Can the case
> mapping rule be changed in IANA?
> https://www.iana.org/assignments/precis-parameters/profiles/UsernameCaseMap
> ped.txt
> e.g. to "Apply Unicode default case folding"
>
> Tom
>
>
> These are the lines in question from UCD CaseFolding.txt to which I
> prefixed their General Category.
>
> Ll; 00B5; C; 03BC; # MICRO SIGN
> Ll; 017F; C; 0073; # LATIN SMALL LETTER LONG S
> Mn; 0345; C; 03B9; # COMBINING GREEK YPOGEGRAMMENI
> Ll; 03C2; C; 03C3; # GREEK SMALL LETTER FINAL SIGMA
> Ll; 03D0; C; 03B2; # GREEK BETA SYMBOL
> Ll; 03D1; C; 03B8; # GREEK THETA SYMBOL
> Ll; 03D5; C; 03C6; # GREEK PHI SYMBOL
> Ll; 03D6; C; 03C0; # GREEK PI SYMBOL
> Ll; 03F0; C; 03BA; # GREEK KAPPA SYMBOL
> Ll; 03F1; C; 03C1; # GREEK RHO SYMBOL
> Ll; 03F5; C; 03B5; # GREEK LUNATE EPSILON SYMBOL
> Ll; 1E9B; C; 1E61; # LATIN SMALL LETTER LONG S WITH DOT ABOVE
> Ll; 1FBE; C; 03B9; # GREEK PROSGEGRAMMENI
> Nl; 2160; C; 2170; # ROMAN NUMERAL ONE
> Nl; 2161; C; 2171; # ROMAN NUMERAL TWO
> Nl; 2162; C; 2172; # ROMAN NUMERAL THREE
> Nl; 2163; C; 2173; # ROMAN NUMERAL FOUR
> Nl; 2164; C; 2174; # ROMAN NUMERAL FIVE
> Nl; 2165; C; 2175; # ROMAN NUMERAL SIX
> Nl; 2166; C; 2176; # ROMAN NUMERAL SEVEN
> Nl; 2167; C; 2177; # ROMAN NUMERAL EIGHT
> Nl; 2168; C; 2178; # ROMAN NUMERAL NINE
> Nl; 2169; C; 2179; # ROMAN NUMERAL TEN
> Nl; 216A; C; 217A; # ROMAN NUMERAL ELEVEN
> Nl; 216B; C; 217B; # ROMAN NUMERAL TWELVE
> Nl; 216C; C; 217C; # ROMAN NUMERAL FIFTY
> Nl; 216D; C; 217D; # ROMAN NUMERAL ONE HUNDRED
> Nl; 216E; C; 217E; # ROMAN NUMERAL FIVE HUNDRED
> Nl; 216F; C; 217F; # ROMAN NUMERAL ONE THOUSAND
> So; 24B6; C; 24D0; # CIRCLED LATIN CAPITAL LETTER A
> So; 24B7; C; 24D1; # CIRCLED LATIN CAPITAL LETTER B
> So; 24B8; C; 24D2; # CIRCLED LATIN CAPITAL LETTER C
> So; 24B9; C; 24D3; # CIRCLED LATIN CAPITAL LETTER D
> So; 24BA; C; 24D4; # CIRCLED LATIN CAPITAL LETTER E
> So; 24BB; C; 24D5; # CIRCLED LATIN CAPITAL LETTER F
> So; 24BC; C; 24D6; # CIRCLED LATIN CAPITAL LETTER G
> So; 24BD; C; 24D7; # CIRCLED LATIN CAPITAL LETTER H
> So; 24BE; C; 24D8; # CIRCLED LATIN CAPITAL LETTER I
> So; 24BF; C; 24D9; # CIRCLED LATIN CAPITAL LETTER J
> So; 24C0; C; 24DA; # CIRCLED LATIN CAPITAL LETTER K
> So; 24C1; C; 24DB; # CIRCLED LATIN CAPITAL LETTER L
> So; 24C2; C; 24DC; # CIRCLED LATIN CAPITAL LETTER M
> So; 24C3; C; 24DD; # CIRCLED LATIN CAPITAL LETTER N
> So; 24C4; C; 24DE; # CIRCLED LATIN CAPITAL LETTER O
> So; 24C5; C; 24DF; # CIRCLED LATIN CAPITAL LETTER P
> So; 24C6; C; 24E0; # CIRCLED LATIN CAPITAL LETTER Q
> So; 24C7; C; 24E1; # CIRCLED LATIN CAPITAL LETTER R
> So; 24C8; C; 24E2; # CIRCLED LATIN CAPITAL LETTER S
> So; 24C9; C; 24E3; # CIRCLED LATIN CAPITAL LETTER T
> So; 24CA; C; 24E4; # CIRCLED LATIN CAPITAL LETTER U
> So; 24CB; C; 24E5; # CIRCLED LATIN CAPITAL LETTER V
> So; 24CC; C; 24E6; # CIRCLED LATIN CAPITAL LETTER W
> So; 24CD; C; 24E7; # CIRCLED LATIN CAPITAL LETTER X
> So; 24CE; C; 24E8; # CIRCLED LATIN CAPITAL LETTER Y
> So; 24CF; C; 24E9; # CIRCLED LATIN CAPITAL LETTER Z
>
>

