From duerst@it.aoyama.ac.jp Mon Oct 1 01:25:46 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CFD221F85C7 for ; Mon, 1 Oct 2012 01:25:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.118 X-Spam-Level: X-Spam-Status: No, score=-103.118 tagged_above=-999 required=5 tests=[AWL=0.672, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NudUXZMhzAQ2 for ; Mon, 1 Oct 2012 01:25:45 -0700 (PDT) Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id DCC3721F84D1 for ; Mon, 1 Oct 2012 01:25:43 -0700 (PDT) Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q918PRKj023101 for ; Mon, 1 Oct 2012 17:25:29 +0900 Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 3a40_dca1_8e27eb64_0ba1_11e2_a884_001d096c5782; Mon, 01 Oct 2012 17:25:27 +0900 Received: from [IPv6:::1] ([133.2.210.1]:50008) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id for from ; Mon, 1 Oct 2012 17:25:28 +0900 Message-ID: <5069536D.3060006@it.aoyama.ac.jp> Date: Mon, 01 Oct 2012 17:25:17 +0900 From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= Organization: Aoyama Gakuin University User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4 MIME-Version: 1.0 To: Peter Saint-Andre References: <505B6F19.109@stpeter.im> <505D9BA9.7010505@it.aoyama.ac.jp> <5064E44E.8080305@stpeter.im> In-Reply-To: <5064E44E.8080305@stpeter.im> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "precis@ietf.org" Subject: Re: [precis] width mapping in draft-yoneya-precis-mappings X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2012 08:25:46 -0000 Hello Peter, On 2012/09/28 8:42, Peter Saint-Andre wrote: >>> I don't think there will be false positives. Saying that e.g. IBM >>> and ＩＢＭ are should be two different things is simply crazy. So it >>> should be either width mapping, or the less basic forms (i.e. >>> full-width for Latin and half-width for Kana,...) should be >>> prohibited. > > That all makes sense. It sounds as if we'll want to advise PRECIS > usages and subclasses to strongly consider performing width mapping. > Do you think it is so important that we ought to think about adding it > to the framework alongside casemapping and the other "first-class" > PRECIS rules? I have to admit that I'm not very familiar with the details of PRECIS, but I think yes, that would make sense. Regards, Martin. From duerst@it.aoyama.ac.jp Tue Oct 2 03:06:30 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 100E321F89C3 for ; Tue, 2 Oct 2012 03:06:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.154 X-Spam-Level: X-Spam-Status: No, score=-103.154 tagged_above=-999 required=5 tests=[AWL=0.636, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qDXBt7wj4jzr for ; Tue, 2 Oct 2012 03:06:28 -0700 (PDT) Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id ACB1A21F88B6 for ; Tue, 2 Oct 2012 03:06:27 -0700 (PDT) Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q92A6GaS008245 for ; Tue, 2 Oct 2012 19:06:16 +0900 Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 7f41_d77c_cdf29514_0c78_11e2_a61d_001d096c566a; Tue, 02 Oct 2012 19:06:15 +0900 Received: from [IPv6:::1] ([133.2.210.1]:47869) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id for from ; Tue, 2 Oct 2012 19:06:16 +0900 Message-ID: <506ABC8D.9000109@it.aoyama.ac.jp> Date: Tue, 02 Oct 2012 19:06:05 +0900 From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= Organization: Aoyama Gakuin University User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4 MIME-Version: 1.0 To: Peter Saint-Andre References: <5059D4CF.30206@stpeter.im> <505A2025.1000608@stpeter.im> <505A6682.9040304@it.aoyama.ac.jp> <505C7D56.9010106@stpeter.im> <505CA5C4.1050904@stpeter.im> <505CB79A.1010202@stpeter.im> <505D9C23.1090307@it.aoyama.ac.jp> <505F4245.7040708@stpeter.im> <5060065A.6050108@it.aoyama.ac.jp> <5060711D.8010200@stpeter.im> In-Reply-To: <5060711D.8010200@stpeter.im> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "precis@ietf.org" Subject: Re: [precis] registration policy for subclasses X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2012 10:06:30 -0000 Hello Peter, On 2012/09/24 23:41, Peter Saint-Andre wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > You're probably right. Those "in the know" who actually read the > relevant specs are well aware of these historical relationships. > Tracking which PRECIS usages replace which Stringprep profiles might > be something that is better left to a wiki, not an IANA registry. Just to be clear, my suggestion was that this information (maybe in a somewhat more concise form than my example below) go into the actual template, not into a separate wiki. Regards, Martin. > On 9/24/12 1:06 AM, "Martin J. Dürst" wrote: >> Given that there are quite a lot of ways in which this "obsoletion" >> can happen, I think an entry of the form >> >> Obsoletes: foo >> >> is totally inappropriate. It should be replaced by some more >> detailled description, such as (just an example): >> >> Historical Relationship: This registration is intended to replace >> the "foo" stringprep profile wherever possible. It the data has >> been carefully checked to avoid any changes from the "foo" profile, >> with the exception that this profile is no longer based on a fixed >> version of Unicode and therefore includes more characters. Also, >> the two characters BAR and BAZ were excluded because they lead to >> heavy ... in practice. Specifications are recommended to update >> their references to this registration after a careful analysis of >> the consequences. >> >> As I said, this is just an example, but I hope it shows the idea. >> >> Regards, Martin. >> >> On 2012/09/24 2:09, Peter Saint-Andre wrote: On 9/22/12 5:08 AM, >> "Martin J. Dürst" wrote: >>>>> On 2012/09/22 3:53, Peter Saint-Andre wrote: One further >>>>> thought: would it make sense to capture the fact that some >>>>> new precis usages obsolete a old stringprep profiles? >>>>> >>>>>> What does "obsoletes" mean here? Is the result still the >>>>>> same (just a different framework), or are changes to the >>>>>> definition allowed? >> >> Good question. I mean "replaces" or "supersedes", where going >> forward the new Precis usage is intended to be used instead of the >> old Stringprep profile when handling the relevant protocol >> elements. For example, the Precis profiles we're defining in >> draft-ietf-xmpp-6122bis for XMPP localparts and resourceparts are >> intended to be used in the future instead of the Nodeprep and >> Resourceprep profiles of Stringprep first defined in RFC 3920. >> Although in the XMPP community we are working to make sure that the >> new Precis profiles have very similar output to the old Stringprep >> profiles (i.e., the same result using a different framework), I >> think any changes to the definition are a matter for the >> application protocol and not the Precis framework. >> >> Another way to handle this matter is to make sure that the >> application protocol specs contain an IANA action to change the >> status of the relevant Stringprep profile(s): >> >> http://www.iana.org/assignments/stringprep-profiles/stringprep-profiles.xml >> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.18 (Darwin) > Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ > > iEYEARECAAYFAlBgcR0ACgkQNL8k5A2w/vyJFwCgpalBsopDctr2HxMtTiI2Sn68 > u3wAoJL5N45YgkHDBranX7O2t1Cy/3mJ > =qQQ/ > -----END PGP SIGNATURE----- > From t.nemo10@kmd.keio.ac.jp Tue Oct 2 20:28:46 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8ADE21F8489 for ; Tue, 2 Oct 2012 20:28:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.598 X-Spam-Level: X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UXd7Vs2NGRuT for ; Tue, 2 Oct 2012 20:28:46 -0700 (PDT) Received: from mail.kmd.keio.ac.jp (mail.kmd.keio.ac.jp [IPv6:2001:200:167:2e90::164]) by ietfa.amsl.com (Postfix) with ESMTP id 968FA21F847C for ; Tue, 2 Oct 2012 20:28:45 -0700 (PDT) Received: from dh209.jprs.co.jp (dh209.jprs.co.jp [202.11.17.209]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.kmd.keio.ac.jp (Postfix) with ESMTPSA id 283B17FBD3 for ; Wed, 3 Oct 2012 12:28:40 +0900 (JST) From: Takahiro Nemoto Content-Type: multipart/alternative; boundary="Apple-Mail=_C3F689A3-B16C-4041-AADA-A5910E904CAF" Message-Id: <4BEAC091-F304-4BA2-B00C-59042BE272DB@kmd.keio.ac.jp> Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\)) Date: Wed, 3 Oct 2012 12:28:39 +0900 References: <505F4D08.70205@stpeter.im> To: "precis@ietf.org" In-Reply-To: <505F4D08.70205@stpeter.im> X-Mailer: Apple Mail (2.1498) Subject: Re: [precis] order of mapping in draft-yoneya-precis-mappings X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2012 03:28:47 -0000 --Apple-Mail=_C3F689A3-B16C-4041-AADA-A5910E904CAF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, Peter-san, thank you for comments. Draft-yoneya-precis-mappings defines mappings that must be considered=20 between receiving user input and passing permitted code points to = internationalized protocols as a guideline for authors of protocol profiles of precis = framework. Yoneya-san and I think we described about mappings that are undescribed in precis framework and it's preferable to perform before precis = framework like RFC5895. So, this document don't mention processing order of precis framework. But, I made sure that draft-ietf-precis-framework-06 defines Additional=20= Mappings. I don't necessarily want to perform mappings before precis = framework. But I think it's preferable to perform Additional Mappings then = Casemapping if Additional Mapping may include local case mapping is in section 4.3. = of=20 draft-yoneya-precis-mappings. Because local case mapping makes no sense to perform after casemapping. For example, U+0049(LATIN CAPITAL LETTER I) in Turkish should be mapped=20= to U+0131(LATIN CAPITAL LETTER I). I investigated Unicode characters that need local case mapping with=20 the Specialcasing.txt in section 3.13 of The Unicode Standerd after=20 I received comments during at Vancouver meeting. And I found the = characters=20 in a few language. And then I checked whether the characters are = affected=20 by order of local case mapping and normal casemapping that=20 the Casefolding.txt of The Unicode Standerd defines. I'm writing about this characters in next draft-yoneya-precis-mappings and I'm going to submit it shortly. Any comment would be greatly appreciated when the draft was submitted. Nemo -- Takahiro Nemoto t.nemo10@kmd.keio.ac.jp On 2012/09/24, at 2:55, Peter Saint-Andre wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Section 5 of draft-yoneya-precis-mappings states that the additional > mappings are to be performed before applying the rules from > draft-ietf-precis-framework. This seems to imply that these additional > mappings will be applied before Unicode normalization. In Vancouver, I > thought we concluded that we want to perform normalization before > applying other mappings (as is done in IDNA2008). It would be good for > us to be completely clear about the order here, in the framework spec, > and in the specs for application protocols that reuse PRECIS. >=20 > Peter >=20 > - --=20 > Peter Saint-Andre > https://stpeter.im/ >=20 >=20 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.18 (Darwin) > Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ >=20 > iEYEARECAAYFAlBfTQgACgkQNL8k5A2w/vy7OACg1RXn1DY4aGioUJPBV/WnhUe7 > bHsAnjoO8/md8c97YQyQed3+tAv4vCDN > =3DfMhi > -----END PGP SIGNATURE----- > _______________________________________________ > precis mailing list > precis@ietf.org > https://www.ietf.org/mailman/listinfo/precis --Apple-Mail=_C3F689A3-B16C-4041-AADA-A5910E904CAF Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi, Peter-san, = thank you for comments.

between receiving user input and passing permitted code points to = internationalized
protocols as a guideline for authors of protocol profiles of = precis framework.
Yoneya-san and I think we described about mappings that = are undescribed
in precis framework and it's preferable = to perform before precis framework like = RFC5895.
So, = this document don't mention processing order of precis = framework.

But, I made sure that draft-ietf-precis-framework-06 = defines Additional 
Mappings. I don't necessarily want to perform = mappings before precis framework.
But I think it's preferable = to perform Additional Mappings = then Casemapping
if Additional Mapping may include local case = mapping is in section 4.3. of 
draft-yoneya-precis-mappings. Because = local case mapping makes no sense
to perform after = casemapping.

For = example, U+0049(LATIN CAPITAL LETTER I) in Turkish should be = mapped 
to U+0131(LATIN CAPITAL LETTER I).

I investigated Unicode characters = that need local case mapping with 
the Specialcasing.txt in section 3.13 = of The Unicode Standerd after 
I received comments during = at Vancouver meeting. And I found = the characters 
in a few language. And then I checked whether the = characters are affected 
by order of local case mapping and = normal casemapping that 
the Casefolding.txt of = The Unicode Standerd defines.
I'm writing about this characters in = next draft-yoneya-precis-mappings
and I'm going to submit = it shortly.

Any = comment would be greatly appreciated when the draft was = submitted.

Nemo

--
Takahiro = Nemoto
<= /div>


On 2012/09/24, at 2:55, Peter = Saint-Andre <stpeter@stpeter.im> = wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: = SHA1

Section 5 of draft-yoneya-precis-mappings states that the = additional
mappings are to be performed before applying the rules = from
draft-ietf-precis-framework. This seems to imply that these = additional
mappings will be applied before Unicode normalization. In = Vancouver, I
thought we concluded that we want to perform = normalization before
applying other mappings (as is done in = IDNA2008). It would be good for
us to be completely clear about the = order here, in the framework spec,
and in the specs for application = protocols that reuse PRECIS.

Peter

- --
Peter = Saint-Andre
https://stpeter.im/


-----BEGIN= PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 = (Darwin)
Comment: Using GnuPG with Mozilla - = http://www.enigmail.net/

iEYEARECAAYFAlBfTQgACgkQNL8k5A2w/vy7OACg1R= Xn1DY4aGioUJPBV/WnhUe7
bHsAnjoO8/md8c97YQyQed3+tAv4vCDN
=3DfMhi
-= ----END PGP = SIGNATURE-----
_______________________________________________
preci= s mailing = list
precis@ietf.org
https://www.ietf.org/mailman/listinfo/precis

= --Apple-Mail=_C3F689A3-B16C-4041-AADA-A5910E904CAF-- From Marc.Blanchet@viagenie.ca Thu Oct 4 15:59:01 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8390F21F8650 for ; Thu, 4 Oct 2012 15:59:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jwiN+kPFT9Yr for ; Thu, 4 Oct 2012 15:58:59 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id E80FC21F864D for ; Thu, 4 Oct 2012 15:58:58 -0700 (PDT) Received: from [10.104.0.108] (unknown [75.98.19.134]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B4A5345D2E for ; Thu, 4 Oct 2012 18:58:57 -0400 (EDT) From: Marc Blanchet Content-Type: multipart/alternative; boundary="Apple-Mail=_94EDFB48-19B1-475C-936E-E2A1B2D423A8" Date: Thu, 4 Oct 2012 18:58:53 -0400 References: <20121004191313.4079.23127.idtracker@ietfa.amsl.com> To: precis@ietf.org Message-Id: <0BD15DD5-82E5-471A-A519-4ABB479832F5@viagenie.ca> Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) Subject: [precis] Fwd: precis - Requested session has been scheduled for IETF 85 X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2012 22:59:01 -0000 --Apple-Mail=_94EDFB48-19B1-475C-936E-E2A1B2D423A8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 FYI. as usual, scheduling may change. Marc. D=E9but du message r=E9exp=E9di=E9 : > De : "\"IETF Secretariat\"" > Objet : precis - Requested session has been scheduled for IETF 85 > Date : 4 octobre 2012 15:13:13 HAE > =C0 : yoshiro.yoneya@jprs.co.jp > Cc : precis-ads@tools.ietf.org, Marc.Blanchet@viagenie.ca, = yoshiro.yoneya@jprs.co.jp, wlo@amsl.com >=20 > Dear Yoshiro Yoneya, >=20 > The session(s) that you have requested have been scheduled. > Below is the scheduled session information followed by > the original request.=20 >=20 > precis Session 1 (2:00:00) > Tuesday, Afternoon Session I 1300-1500 > Room Name: Room 209 > --------------------------------------------- >=20 >=20 >=20 > Request Information: >=20 >=20 > --------------------------------------------------------- > Working Group Name:=20 > Area Name:=20 > Session Requester:=20 >=20 > Number of Sessions: 1 > Length of Session(s): 2 Hours > Number of Attendees: 35 > Conflicts to Avoid:=20 > First Priority: appsawg apparea eai iri saag storm xmpp sunset4 > Second Priority: websec >=20 >=20 >=20 > Special Requests: >=20 > --------------------------------------------------------- --Apple-Mail=_94EDFB48-19B1-475C-936E-E2A1B2D423A8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 FYI. = as usual, scheduling may change. Marc.

D=E9but du = message r=E9exp=E9di=E9 :

De : "\"IETF = Secretariat\"" <agenda@ietf.org>
Objet : precis - = Requested session has been scheduled for IETF = 85
Date : 4 octobre 2012 15:13:13 HAE

Dea= r Yoshiro Yoneya,

The session(s) that you have requested have = been scheduled.
Below is the scheduled session information followed = by
the original request.

precis Session 1 (2:00:00)
=    Tuesday, Afternoon Session I 1300-1500
=    Room Name: Room 209
=    ---------------------------------------------


Request = Information:


--------------------------------------------------= -------
Working Group Name:
Area Name:
Session Requester: =

Number of Sessions: 1
Length of Session(s):  2 = Hours
Number of Attendees: 35
Conflicts to Avoid:
First = Priority: appsawg apparea eai iri saag storm xmpp sunset4
Second = Priority: websec



Special = Requests:

---------------------------------------------------------=

= --Apple-Mail=_94EDFB48-19B1-475C-936E-E2A1B2D423A8-- From t.nemo10@kmd.keio.ac.jp Thu Oct 4 23:44:15 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34DAE21F849B for ; Thu, 4 Oct 2012 23:44:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.74 X-Spam-Level: X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uzq7oRi64Jcc for ; Thu, 4 Oct 2012 23:44:14 -0700 (PDT) Received: from mail.kmd.keio.ac.jp (mail.kmd.keio.ac.jp [IPv6:2001:200:167:2e90::164]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD0021F8555 for ; Thu, 4 Oct 2012 23:44:13 -0700 (PDT) Received: from [IPv6:2001:200:167:2ec1:4506:a095:3e44:19ce] (unknown [IPv6:2001:200:167:2ec1:4506:a095:3e44:19ce]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.kmd.keio.ac.jp (Postfix) with ESMTPSA id 769D67FBE9 for ; Fri, 5 Oct 2012 15:44:11 +0900 (JST) From: Takahiro Nemoto Content-Type: multipart/alternative; boundary="Apple-Mail=_F6BE022A-4EAD-4A05-A7D6-F3DDDEE408F7" Date: Fri, 5 Oct 2012 15:44:11 +0900 References: <20121004171120.5223.62906.idtracker@ietfa.amsl.com> To: "precis@ietf.org" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\)) X-Mailer: Apple Mail (2.1498) Subject: [precis] Fwd: New Version Notification for draft-yoneya-precis-mappings-03.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2012 06:44:15 -0000 --Apple-Mail=_F6BE022A-4EAD-4A05-A7D6-F3DDDEE408F7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-2022-jp Dear all, Yoneya-san and I submitted new version of precis mappings=20 document. we reflected comments during at last Meeting in this version, but didn't reflect comments from the mailing list yet. Please read and give your comments/suggestions. Regards, Nemo Begin forwarded message: > =1B$B:9=3DP?M=1B(B: internet-drafts@ietf.org > =1B$B7oL>=1B(B: New Version Notification for = draft-yoneya-precis-mappings-03.txt > =1B$BF|;~=1B(B: 2012=1B$BG/=1B(B10=1B$B7n=1B(B5=1B$BF|=1B(B 2:11:20 = JST > =1B$B08@h=1B(B: t.nemo10@kmd.keio.ac.jp > Cc: yoshiro.yoneya@jprs.co.jp >=20 >=20 > A new version of I-D, draft-yoneya-precis-mappings-03.txt > has been successfully submitted by Takahiro NEMOTO and posted to the > IETF repository. >=20 > Filename: draft-yoneya-precis-mappings > Revision: 03 > Title: Mapping characters for precis classes > Creation date: 2012-10-03 > WG ID: Individual Submission > Number of pages: 20 > URL: = http://www.ietf.org/internet-drafts/draft-yoneya-precis-mappings-03.txt > Status: = http://datatracker.ietf.org/doc/draft-yoneya-precis-mappings > Htmlized: = http://tools.ietf.org/html/draft-yoneya-precis-mappings-03 > Diff: = http://www.ietf.org/rfcdiff?url2=3Ddraft-yoneya-precis-mappings-03 >=20 > Abstract: > Preparation and comparison of internationalized strings ("precis") > framework [I-D.ietf-precis-framework] is defining several classes of > strings for preparation and comparison. In the document, case > mapping is defined because many of protocols handle case sensitive = or > case insensitive string comparison and therefore preparation of > string is mandatory. As described in IDNA mapping [RFC5895] and > precis problem statement [I-D.ietf-precis-problem-statement], > mappings in internationalized strings are not limited to case, but > also width, delimiters and/or other specials are taken into > consideration. This document is a guideline for authors of protocol > profiles of precis framework and describes the mappings that must be > considered between receiving user input and passing permitted code > points to internationalized protocols. >=20 >=20 >=20 >=20 > The IETF Secretariat >=20 --Apple-Mail=_F6BE022A-4EAD-4A05-A7D6-F3DDDEE408F7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-2022-jp
=1B$B:9=3DP?M=1B(B: = internet-drafts@ietf.org
<= /span>
=1B$B7oL>=1B(B: New Version = Notification for = draft-yoneya-precis-mappings-03.txt
=1B$BF|;~=1B(B: = 2012=1B$BG/=1B(B10=1B$B7n=1B(B5=1B$BF|=1B(B 2:11:20 = JST
=1B$B08@h=1B(B: t.nemo10@kmd.keio.ac.jp


A new version of I-D, = draft-yoneya-precis-mappings-03.txt
has been successfully submitted = by Takahiro NEMOTO and posted to the
IETF = repository.

Filename: = draft-yoneya-precis-mappings
Revision: 03
Title: Mapping = characters for precis classes
Creation date: = 2012-10-03
WG ID: Individual Submission
Number = of pages: 20
URL: =             http://www.ietf.org/internet-drafts/draft-yoneya-precis-mappings-03= .txt
Status: =          http= ://datatracker.ietf.org/doc/draft-yoneya-precis-mappings
Htmlized: =        http:/= /tools.ietf.org/html/draft-yoneya-precis-mappings-03
Diff: =            http://www.ietf.org/rfcdiff?url2=3Ddraft-yoneya-precis-mappings-03
Abstract:
  Preparation and comparison of = internationalized strings ("precis")
  framework = [I-D.ietf-precis-framework] is defining several classes of
=   strings for preparation and comparison.  In the = document, case
  mapping is defined because many of = protocols handle case sensitive or
  case insensitive = string comparison and therefore preparation of
  string is = mandatory.  As described in IDNA mapping [RFC5895] and
=   precis problem statement = [I-D.ietf-precis-problem-statement],
  mappings in = internationalized strings are not limited to case, but
=   also width, delimiters and/or other specials are taken = into
  consideration.  This document is a guideline = for authors of protocol
  profiles of precis framework and = describes the mappings that must be
  considered between = receiving user input and passing permitted code
  points = to internationalized protocols.




The IETF = Secretariat


= --Apple-Mail=_F6BE022A-4EAD-4A05-A7D6-F3DDDEE408F7-- From internet-drafts@ietf.org Mon Oct 8 11:43:00 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6DBA21F8847; Mon, 8 Oct 2012 11:43:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.507 X-Spam-Level: X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8mxt4OQvLL5P; Mon, 8 Oct 2012 11:43:00 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB31721F8841; Mon, 8 Oct 2012 11:42:59 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.34 Message-ID: <20121008184259.15700.27748.idtracker@ietfa.amsl.com> Date: Mon, 08 Oct 2012 11:42:59 -0700 Cc: precis@ietf.org Subject: [precis] I-D Action: draft-ietf-precis-nickname-03.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Oct 2012 18:43:01 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Preparation and Comparison of Internation= alized Strings Working Group of the IETF. Title : Preparation and Comparison of Nicknames Author(s) : Peter Saint-Andre Filename : draft-ietf-precis-nickname-03.txt Pages : 7 Date : 2012-10-08 Abstract: This document describes how to prepare and compare Unicode strings representing nicknames, primarily as used within textual chatrooms. This profile is intended to be used by messaging and text conferencing technologies such as the Extensible Messaging and Presence Protocol (XMPP), the Message Session Relay Protocol (MSRP), and Centralized Conferencing (XCON). 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: http://tools.ietf.org/html/draft-ietf-precis-nickname-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-precis-nickname-03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From stpeter@stpeter.im Mon Oct 8 11:44:34 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05BF721F87B0 for ; Mon, 8 Oct 2012 11:44:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.575 X-Spam-Level: X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cVrFP4DdfZkL for ; Mon, 8 Oct 2012 11:44:30 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 12C0221F852A for ; Mon, 8 Oct 2012 11:44:30 -0700 (PDT) Received: from [64.101.72.58] (unknown [64.101.72.58]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0A2334009B for ; Mon, 8 Oct 2012 12:46:37 -0600 (MDT) Message-ID: <50731F22.9040406@stpeter.im> Date: Mon, 08 Oct 2012 12:44:50 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: precis@ietf.org References: <20121008184259.15700.27748.idtracker@ietfa.amsl.com> In-Reply-To: <20121008184259.15700.27748.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [precis] I-D Action: draft-ietf-precis-nickname-03.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Oct 2012 18:44:34 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just some small adjustments to incorporate feedback from reviewers in the SIMPLE WG. I will continue to ping people for reviews in this WG and in SIMPLE. On 10/8/12 12:42 PM, 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 and Comparison of Nicknames Author(s) > : Peter Saint-Andre Filename : > draft-ietf-precis-nickname-03.txt Pages : 7 Date > : 2012-10-08 > > Abstract: This document describes how to prepare and compare > Unicode strings representing nicknames, primarily as used within > textual chatrooms. This profile is intended to be used by messaging > and text conferencing technologies such as the Extensible Messaging > and Presence Protocol (XMPP), the Message Session Relay Protocol > (MSRP), and Centralized Conferencing (XCON). > > > 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: > http://tools.ietf.org/html/draft-ietf-precis-nickname-03 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-precis-nickname-03 > > > 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 > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBzHyIACgkQNL8k5A2w/vzFbQCbBfkNJ0mB4cVrlVLU8eP9AHJh hnYAoLlhIeYnm3iYCWzHRuPQjhKrAcjJ =QsHX -----END PGP SIGNATURE----- From presnick@qti.qualcomm.com Mon Oct 8 21:16:38 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A25511E80CC for ; Mon, 8 Oct 2012 21:16:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.588 X-Spam-Level: X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tir0007X3afr for ; Mon, 8 Oct 2012 21:16:37 -0700 (PDT) Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id D069D1F0420 for ; Mon, 8 Oct 2012 21:16:36 -0700 (PDT) X-IronPort-AV: E=McAfee;i="5400,1158,6859"; a="247472634" Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 08 Oct 2012 21:16:36 -0700 X-IronPort-AV: E=Sophos;i="4.80,557,1344236400"; d="scan'208";a="342092850" Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 08 Oct 2012 21:16:36 -0700 Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.1; Mon, 8 Oct 2012 21:16:35 -0700 Message-ID: <5073A521.6030507@qti.qualcomm.com> Date: Mon, 8 Oct 2012 23:16:33 -0500 From: Pete Resnick User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4 MIME-Version: 1.0 To: Peter Saint-Andre References: <505B5F32.3020604@stpeter.im> In-Reply-To: <505B5F32.3020604@stpeter.im> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [172.30.39.5] Cc: "precis@ietf.org" Subject: Re: [precis] Document Shepherd Write-Up for draft-ietf-precis-problem-statement-08 X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2012 04:16:38 -0000 On 9/20/12 1:23 PM, Peter Saint-Andre wrote: > In accordance with RFC 4858, here is the Document Shepherd Write-Up for > "Stringprep Revision and PRECIS Problem Statement" > (draft-ietf-precis-problem-statement-08). > I only had one AD Evaluation comment. Please handle it as a Last Call comment. Comment: Please strike section 2. There are no 2119 terms in this document. All else looks ready for Last Call. (I have already requested Last Call; it will be issued as soon as the secretariat gets a chance). pr -- Pete Resnick Qualcomm Technologies, Inc. - +1 (858)651-4478 From iesg-secretary@ietf.org Tue Oct 9 06:44:59 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D15E21F865B; Tue, 9 Oct 2012 06:44:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.488 X-Spam-Level: X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvhCdFw5pme0; Tue, 9 Oct 2012 06:44:58 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9374C21F84F1; Tue, 9 Oct 2012 06:44:58 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.34 Message-ID: <20121009134458.18784.49285.idtracker@ietfa.amsl.com> Date: Tue, 09 Oct 2012 06:44:58 -0700 Cc: precis@ietf.org Subject: [precis] Last Call: (Stringprep Revision and PRECIS Problem Statement) to Informational RFC X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ietf@ietf.org List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2012 13:44:59 -0000 The IESG has received a request from the Preparation and Comparison of Internationalized Strings WG (precis) to consider the following document: - 'Stringprep Revision and PRECIS Problem Statement' as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2012-10-23. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract If a protocol expects to compare two strings and is prepared only for those strings to be ASCII, then using Unicode codepoints in those strings requires they be prepared somehow. Internationalizing Domain Names in Applications (here called IDNA2003) defined and used Stringprep and Nameprep. Other protocols subsequently defined Stringprep profiles. A new approach different from Stringprep and Nameprep is used for a revision of IDNA2003 (called IDNA2008). Other Stringprep profiles need to be similarly updated or a replacement of Stringprep needs to be designed. This document outlines the issues to be faced by those designing a Stringprep replacement. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-precis-problem-statement/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-precis-problem-statement/ballot/ No IPR declarations have been submitted directly on this I-D. From stpeter@stpeter.im Tue Oct 9 07:36:52 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C498611E80D1 for ; Tue, 9 Oct 2012 07:36:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.532 X-Spam-Level: X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKPK2KLZbOpH for ; Tue, 9 Oct 2012 07:36:52 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 095EE11E8101 for ; Tue, 9 Oct 2012 07:36:52 -0700 (PDT) Received: from [192.168.1.2] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A221A400F9; Tue, 9 Oct 2012 08:39:02 -0600 (MDT) Message-ID: <5074369B.2060207@stpeter.im> Date: Tue, 09 Oct 2012 08:37:15 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Pete Resnick References: <505B5F32.3020604@stpeter.im> <5073A521.6030507@qti.qualcomm.com> In-Reply-To: <5073A521.6030507@qti.qualcomm.com> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "precis@ietf.org" Subject: Re: [precis] Document Shepherd Write-Up for draft-ietf-precis-problem-statement-08 X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2012 14:36:52 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/8/12 10:16 PM, Pete Resnick wrote: > On 9/20/12 1:23 PM, Peter Saint-Andre wrote: >> In accordance with RFC 4858, here is the Document Shepherd >> Write-Up for "Stringprep Revision and PRECIS Problem Statement" >> (draft-ietf-precis-problem-statement-08). >> > > I only had one AD Evaluation comment. Please handle it as a Last > Call comment. > > Comment: Please strike section 2. There are no 2119 terms in this > document. Actually, there are some of those terms in the appendices, which it seems have copied some text from the relevant RFCs. I would encourage the authors to modify that text so that it no longer contains any of the conformance keywords, because the "background information" subsections of several appendices don't seem normative to me... Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB0NpsACgkQNL8k5A2w/vxiYQCgy+RBVt8mdeLCwJwu0gGdySsR TKwAoIEe2IuOo71j5yBcguEEqnqFp67F =njCu -----END PGP SIGNATURE----- From stpeter@stpeter.im Tue Oct 9 09:25:16 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4A621F87BC; Tue, 9 Oct 2012 09:25:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.535 X-Spam-Level: X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3opR9aSkCBjx; Tue, 9 Oct 2012 09:25:15 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B7E3021F87B9; Tue, 9 Oct 2012 09:25:13 -0700 (PDT) Received: from [192.168.1.2] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B3F80400F9; Tue, 9 Oct 2012 10:27:24 -0600 (MDT) Message-ID: <50745001.9080308@stpeter.im> Date: Tue, 09 Oct 2012 10:25:37 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: SM References: <20121009134458.18784.49285.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121009070956.0ac31c90@resistor.net> In-Reply-To: <6.2.5.6.2.20121009070956.0ac31c90@resistor.net> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: ietf@ietf.org, "precis@ietf.org" Subject: Re: [precis] Last Call: (Stringprep Revision and PRECIS Problem Statement) to Informational RFC X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2012 16:25:16 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/9/12 9:25 AM, SM wrote: > At 06:44 09-10-2012, The IESG wrote: >> The IESG has received a request from the Preparation and >> Comparison of Internationalized Strings WG (precis) to consider >> the following document: - 'Stringprep Revision and PRECIS Problem >> Statement' as >> Informational RFC >> >> The IESG plans to make a decision in the next few weeks, and >> solicits final comments on this action. Please send substantive >> comments to the ietf@ietf.org mailing lists by 2012-10-23. >> Exceptionally, comments may be > > Section 2 could be dropped as it isn't that important to have RFC > 2119 in a problem statement. In Section 4: > > "For example, Stringprep is based on and profiles may use NFKC > [UAX15], while IDNA2008 mostly uses NFC [UAX15]." > > I suggest reviewing the references to see what background > information is required for the reader to understand "NFKC". At the least, spelling out these acronyms on first use would be helpful (e.g., "Unicode Normalization Form KC"). > In Section 6: > > "The above suggests the following guidance for replacing > Stringprep: o A stringprep replacement should be defined." > > That sounds obvious. > > The appendix is more informative than the rest of the draft. The > text in the Appendix B comes out as rough notes though. Indeed, that appendix consists of notes copied from a wiki page that the PRECIS WG used to collect the information. > In Section 5.3.3.2: > > "It is important to identify the willingness of the protocol-using > community to accept backwards-incompatible changes." > > The "tolerance for change" for several "protocol-using communities" > is rated as "not sure". I understand that it is difficult to get > definitive answers for these questions. It's doubtful that people > will choose "better support for different linguistic environments > against the potential side effects of backward incompatibility". > It seems that the WG has taken on an intractable problem. Your conclusion does not follow. Yes, it is true that we're not sure how willing some developer communities are to upgrade from Stringprep (based on Unicode 3.2) to PRECIS (version-agile, currently Unicode 6.1). However, we know that some developer communities are in fact willing to upgrade, and they have been more involved in the PRECIS WG. Furthermore, in general applications don't have a choice about what Unicode version is installed on the underlying system, so as time goes by Stringprep will become more and more problematic. There was strong agreement at the NEWPREP BoF to work on a common solution that all Stringprep-using protocols could re-use. The approach taken in the PRECIS framework specification is closely modelled on IDNA2008 and follows the recommendations from RFC 4690. If you are going to maintain that the PRECIS WG has taken on an intractable problem, then I think you're also arguing that the IDNABIS WG took on an intractable problem and that IDNA2008 failed to provide a viable solution to the shortcomings of IDNA2003 and the Nameprep profile of Stringprep. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB0UAEACgkQNL8k5A2w/vwxggCfY5oXnRgP3UhOkZY3cu+1A/QX gK4AoN5kxFk+5T19loPFsXup5YhzimWy =LRQY -----END PGP SIGNATURE----- From sm@resistor.net Tue Oct 9 13:28:41 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D525121F8587; Tue, 9 Oct 2012 13:28:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.594 X-Spam-Level: X-Spam-Status: No, score=-102.594 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G45-gB4oJBt9; Tue, 9 Oct 2012 13:28:41 -0700 (PDT) Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 078A721F853E; Tue, 9 Oct 2012 13:28:33 -0700 (PDT) Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q99KSPEV018461; Tue, 9 Oct 2012 13:28:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1349814512; bh=gk4POarhZqMgri8OaaE5niIm6KZtNsah0VPVgkB1grc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=igMorl0HugmFHzRZiPSAz93Sw37hm+vgLuCrX3GxrgVzjiHjv8Ogz+N0wvXxDs+RH MTRhWi7ULWd0cmrTrbtYJCwhks8j53yUQzDDpebFjZ5tBN8YJquBe2hDR4+yPXbL0A A8LrWb+c7shEU8RpP6qpLqiY8ahc58nxin0DSzFc= DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1349814512; i=@resistor.net; bh=gk4POarhZqMgri8OaaE5niIm6KZtNsah0VPVgkB1grc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3/VnMiNXJoZYwge2pIbqxiNRhW/FnhkLnppwK5ZVFNmhRiVYICFe9KJKBT08cxFLJ 0v5oYV3iuQoAh96HqcMpA3JZLpDEBMHi45cnnPennLkOJ47QW6cCZBVchhoaqgJYnj ctGKdMxsPEeEffWxVGs0LFVMvx+9AhR5B94QmtRc= Message-Id: <6.2.5.6.2.20121009103254.0ac57808@resistor.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Tue, 09 Oct 2012 13:16:03 -0700 To: Peter Saint-Andre From: SM In-Reply-To: <50745001.9080308@stpeter.im> References: <20121009134458.18784.49285.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121009070956.0ac31c90@resistor.net> <50745001.9080308@stpeter.im> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: ietf@ietf.org, precis@ietf.org Subject: Re: [precis] Last Call: (Stringprep Revision and PRECIS Problem Statement) to Informational RFC X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2012 20:28:42 -0000 Hi Peter, At 09:25 09-10-2012, Peter Saint-Andre wrote: >At the least, spelling out these acronyms on first use would be >helpful (e.g., "Unicode Normalization Form KC"). Yes. >Indeed, that appendix consists of notes copied from a wiki page that >the PRECIS WG used to collect the information. Ok. >follows the recommendations from RFC 4690. If you are going to >maintain that the PRECIS WG has taken on an intractable problem, then >I think you're also arguing that the IDNABIS WG took on an intractable >problem and that IDNA2008 failed to provide a viable solution to the >shortcomings of IDNA2003 and the Nameprep profile of Stringprep. My view is that the IDNABIS took on a difficult and politically-sensitive problem. There's an open source implementation of the specification . IDNABIS had the advantage of being related to domain names. I'll take back the comment as you did a good write-up. :-) Regards, -sm From salvatore.loreto@ericsson.com Sat Oct 13 09:17:33 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96B0821F854E for ; Sat, 13 Oct 2012 09:17:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.419 X-Spam-Level: X-Spam-Status: No, score=-106.419 tagged_above=-999 required=5 tests=[AWL=-0.170, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id khGGmhoWpYMr for ; Sat, 13 Oct 2012 09:17:32 -0700 (PDT) Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 4364521F8575 for ; Sat, 13 Oct 2012 09:17:31 -0700 (PDT) X-AuditID: c1b4fb25-b7f956d0000011c3-3a-50799417338c Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 3E.00.04547.71499705; Sat, 13 Oct 2012 18:17:27 +0200 (CEST) Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.279.1; Sat, 13 Oct 2012 18:17:26 +0200 Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 8DDCF2AC9; Sat, 13 Oct 2012 19:17:24 +0300 (EEST) Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 31DC6538FB; Sat, 13 Oct 2012 19:17:24 +0300 (EEST) Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id DAF1C53655; Sat, 13 Oct 2012 19:17:23 +0300 (EEST) Message-ID: <50799413.7000407@ericsson.com> Date: Sat, 13 Oct 2012 19:17:23 +0300 From: Salvatore Loreto User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: precis@ietf.org Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFLMWRmVeSWpSXmKPExsUyM+Jvra74lMoAg+kPNS12ff/DanFsTz+z A5PHkiU/mTzm7nnBHMAUxWWTkpqTWZZapG+XwJXx/9kL1oLL7BWn18k0MPaxdTFyckgImEgc m3+cEcIWk7hwbz1QnItDSOAUo8TznZeZIZwNjBI/7vQxQji7GSW6f3UzQTjrGCV2zL0J5Wxn lJj4ezEzyDBeAW2JixPeAtkcHCwCqhIb/pWAhNkEzCSeP9wCViIqkCzRO38nI0S5oMTJmU9Y QGwRAWGJW7cXsoLYzAJaErPfbgSrERbQlfi7pY8ZIm4rcWHOdRYIW15i+9s5zBA/qElcPbcJ zBYC6u0928k0gVF4FpIVs5C0z0LSvoCReRWjcG5iZk56uZFealFmcnFxfp5eceomRmB4H9zy W3UH451zIocYpTlYlMR5rbfu8RcSSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAGLf31uJrimm3 DssXv1umzLDcNuoDz9tzj4QYbrAb521K4UpouNESq3r07+OTNp2CBU805mx/a7Lot/st7oKf G3jWenwU/7hINHBB7K8zu6wFxXi9LBZ9TJW44Pu4/98N+y83d52+KzJbNWSumEtm4znVizt+ /e3PTWhQCAwxEfcIznysKDKnXomlOCPRUIu5qDgRAGJXbxk9AgAA Subject: [precis] comments on draft-precis-nickname-03 X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2012 16:17:33 -0000 I have reviewed the draft-ietf-precis-nickname-03 the only concern I have is on the last sentence of Section 3. Use in Application Protocols: Application protocols are also allowed to define application-specific rules governing use of nicknames in the relevant protocol slots (e.g., rules regarding the length of nicknames). I am not sure "use" is the term here. The responsibilities of the specific application protocol, that are of interest of this draft, are those that would eventually extending the string conformation constraints (e.g., rules regarding the length of nicknames) , and that must not contradict the rules specified in Section 2. However an application will also specify other rules governing use of nicknames (e.g. some names are reserved, prohibit to use etc.) but those are not of interest for this draft as far as the string name conform to Section2. cheers /Sal -- Salvatore Loreto, PhD www.sloreto.com From yoshiro.yoneya@jprs.co.jp Tue Oct 16 05:23:14 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3AB821F8818 for ; Tue, 16 Oct 2012 05:23:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UVBc-n+iZOXd for ; Tue, 16 Oct 2012 05:23:09 -0700 (PDT) Received: from off-send02.tyo.jprs.co.jp (off-send02.tyo.jprs.co.jp [IPv6:2001:df0:8:17::20]) by ietfa.amsl.com (Postfix) with ESMTP id 792CC21F87B5 for ; Tue, 16 Oct 2012 05:23:09 -0700 (PDT) Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send02.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id q9GCN7nQ026795 for ; Tue, 16 Oct 2012 21:23:08 +0900 X-AuditID: ac120820-b7fd46d0000058b8-57-507d51a7f07b Received: from NOTE345 (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id F0.5C.22712.7A15D705; Tue, 16 Oct 2012 21:23:07 +0900 (JST) Date: Tue, 16 Oct 2012 21:22:44 +0900 From: Yoshiro YONEYA To: precis@ietf.org Message-Id: <20121016212244.76c5c5970fad66a6c4750157@jprs.co.jp> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCIsWRmVeSWpSXmKPExsWyRoiFT3d1YG2Awa7Zaha7vv9hdWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxqRLAgXXWSuWXOJuYDzD0sXIySEhYCKxvv8eM4QtJnHh3nq2 LkYuDiGB44wSd3a8YwNJsAioSsyZthesiE3AQOLXst9MILaIgLDErdsLWUFsYQEViSV777CD 2LwCDhLHZ26AWmAh8ffud6B6DqC4oMTfHcIgYWYBLYmHv26xQNjyEtvfzmGewMgzC6FqFpKq WUiqFjAyr2KUyU9L0y1OzUspzk03MNQrqczXyyooKtZLBtGbGMGBwqGwg3HGKYNDjAIcjEo8 vJ5FNQFCrIllxZW5hxglOZiURHmLvWoDhPiS8lMqMxKLM+KLSnNSiw8xSnAwK4nwqtoC5XhT EiurUovyYVLSHCxK4rzHz+7wExJITyxJzU5NLUgtgsnKcHAoSfB+9QNqFCxKTU+tSMvMKUFI M3FwggznARq+HKSGt7ggMbc4Mx0if4pRUkqcV9wfKCEAksgozYPrfcUoDvSCMG8tSJYHGPVw Xa+ABjIBDezaXQ0ysCQRISXVwLhClCt73/eGt6nn5Ox+3LlgYua+cPWF1iMna1WvJu4+XJvi ns4/qVQxzHnVOdbWF8EJdfo71uxWf/K50fCmBGd/cq5B/BRt+1lfrTznzX7F8W1zkqzNbiG5 54+1VvFvklL+H5glmrwkld96hrNc4RP3ee+mTlOaw9t235b/r/auhTXnJM+/26nEUpyRaKjF XFScCADiOrZbtwIAAA== Subject: [precis] IETF85 Atlanta draft agenda X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2012 12:23:14 -0000 Dear all, Following is draft agenda for IETF 85 Atlanta. Please send comments/additions/changes to the chairs. 1. Administrativia 2. Document updates / Discussion 2.1 WG I-Ds (1) Framework https://datatracker.ietf.org/doc/draft-ietf-precis-framework/ 2.2 Individual Documents (1) Mapping characters for PRECIS classes https://datatracker.ietf.org/doc/draft-yoneya-precis-mappings/ (2) Username and Password Preparation Algorithms https://datatracker.ietf.org/doc/draft-melnikov-precis-saslprepbis/ (3) Preparation and Comparison of Nicknames https://datatracker.ietf.org/doc/draft-saintandre-precis-nickname/ 3. Next steps Marc & Yoneya, co-chairs From yoshiro.yoneya@jprs.co.jp Tue Oct 16 05:28:27 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF5BF21F895D for ; Tue, 16 Oct 2012 05:28:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D69dSsH7Yz5Q for ; Tue, 16 Oct 2012 05:28:27 -0700 (PDT) Received: from off-send02.tyo.jprs.co.jp (off-send02.tyo.jprs.co.jp [IPv6:2001:df0:8:17::20]) by ietfa.amsl.com (Postfix) with ESMTP id 277A721F895C for ; Tue, 16 Oct 2012 05:28:27 -0700 (PDT) Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send02.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id q9GCSP5l027056 for ; Tue, 16 Oct 2012 21:28:26 +0900 X-AuditID: ac120820-b7fd46d0000058b8-6f-507d52e7a2c6 Received: from NOTE345 (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id A3.5C.22712.7E25D705; Tue, 16 Oct 2012 21:28:24 +0900 (JST) Date: Tue, 16 Oct 2012 21:28:14 +0900 From: Yoshiro YONEYA To: precis@ietf.org Message-Id: <20121016212814.7685289c12c83ab8e82c3d5b@jprs.co.jp> In-Reply-To: <20121016212244.76c5c5970fad66a6c4750157@jprs.co.jp> References: <20121016212244.76c5c5970fad66a6c4750157@jprs.co.jp> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBIsWRmVeSWpSXmKPExsWyRoiFT/dFUG2Awe45Wha7vv9htehq28zi wOSxZMlPJo+/99+xBjBFcdmkpOZklqUW6dslcGWcubSPrWABe0X7vQaWBsYXrF2MnBwSAiYS V599ZYawxSQu3FvP1sXIxSEkcJxRYsbZ2YwgCRYBVYmPEz6BFbEJGEj8WvabCcQWERCWuHV7 IdggYQFDibm7T4PZvAIOEt+/zgGr4RRwlDi1+hnYHCGgeOO1M1CLLST+3v0OVMMBVC8o8XeH MEiYWUBL4uGvWywQtrzE9rdzmCcw8s1CqJqFpGoWkqoFjMyrGGXy09J0i1PzUopz0w0M9Uoq 8/WyCoqK9ZJB9CZGcMBxKOxgnHHK4BCjAAejEg+vZ1FNgBBrYllxZe4hRkkOJiVR3mKv2gAh vqT8lMqMxOKM+KLSnNTiQ4wSHMxKIryqtkA53pTEyqrUonyYlDQHi5I47/GzO/yEBNITS1Kz U1MLUotgsjIcHEoSvPyBQI2CRanpqRVpmTklCGkmDk6Q4TxAw61BaniLCxJzizPTIfKnGCWl xHmzQRICIImM0jy43leM4kAvCPNOBsnyAJMHXNcroIFMQAO7dleDDCxJREhJNTBGztnU/+v4 S6nnLEH/Tn0UvvuswZ4latNX4Yn9Iuybpz4zWHnCuVfmFZOzQ63itcadcqmW6cnPTh8pvOWz s9x8VfK8Uy7XPZJPCBzQ3Zfln5We7Ra6zuDGEaV311ea/3E5ocnnKiF9t/PvzIbvT2JUJSan Sz7p57jizSEyQ3mJ/S37SbPfzLFQYinOSDTUYi4qTgQArMt57NsCAAA= Subject: Re: [precis] IETF85 Atlanta draft agenda X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2012 12:28:28 -0000 Dear all, Oops, I'm sorry I had a big mistake. Please review following agenda instead of previous one. On Tue, 16 Oct 2012 21:22:44 +0900 Yoshiro YONEYA wrote: > Dear all, > > Following is draft agenda for IETF 85 Atlanta. > Please send comments/additions/changes to the chairs. 1. Administrativia 2. Document updates / Discussion 2.1 WG I-Ds (1) Framework https://datatracker.ietf.org/doc/draft-ietf-precis-framework/ (2) Preparation and Comparison of Nicknames https://datatracker.ietf.org/doc/draft-ietf-precis-nickname 2.2 Individual Documents (1) Mapping characters for PRECIS classes https://datatracker.ietf.org/doc/draft-yoneya-precis-mappings/ (2) Username and Password Preparation Algorithms https://datatracker.ietf.org/doc/draft-melnikov-precis-saslprepbis/ 3. Next steps Marc & Yoneya, co-chairs From stpeter@stpeter.im Tue Oct 16 07:01:20 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A212C21F887B for ; Tue, 16 Oct 2012 07:01:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.64 X-Spam-Level: X-Spam-Status: No, score=-102.64 tagged_above=-999 required=5 tests=[AWL=-0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6U9TBxoTgN3e for ; Tue, 16 Oct 2012 07:01:19 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 6D93221F886F for ; Tue, 16 Oct 2012 07:01:19 -0700 (PDT) Received: from [192.168.1.5] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 00E114011B; Tue, 16 Oct 2012 08:03:52 -0600 (MDT) Message-ID: <507D68AD.4040404@stpeter.im> Date: Tue, 16 Oct 2012 08:01:17 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Salvatore Loreto References: <50799413.7000407@ericsson.com> In-Reply-To: <50799413.7000407@ericsson.com> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: precis@ietf.org Subject: Re: [precis] comments on draft-precis-nickname-03 X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2012 14:01:20 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/13/12 10:17 AM, Salvatore Loreto wrote: > I have reviewed the draft-ietf-precis-nickname-03 Hi Sal, thanks for the review! > the only concern I have is on the last sentence of Section 3. Use > in Application Protocols: > > Application protocols are also allowed to define > application-specific rules governing use of nicknames in the > relevant protocol slots (e.g., rules regarding the length of > nicknames). > > I am not sure "use" is the term here. The responsibilities of the > specific application protocol, that are of interest of this draft, > are those that would eventually extending the string conformation > constraints (e.g., rules regarding the length of nicknames) , and > that must not contradict the rules specified in Section 2. However > an application will also specify other rules governing use of > nicknames (e.g. some names are reserved, prohibit to use etc.) but > those are not of interest for this draft as far as the string name > conform to Section2. Let me see if I understand your point: there are rules about the nickname strings themselves (e.g., length, allowable characters, further restrictions to mitigate confusion about visually similar characters), and then there are rules about how nickname strings are employed in an application protocol (e.g., reserved nicknames, prohibited nicknames). How about rephrasing the sentence as follows... OLD This specification defines only the PRECIS-based rules for handling of nicknames. It is the responsibility of application protocols such as MSRP, XCON, and XMPP to specify which entities are expected to enforce these rules (e.g., chat servers, chat clients, or both). Application protocols are also allowed to define application-specific rules governing use of nicknames in the relevant protocol slots (e.g., rules regarding the length of nicknames). NEW This specification defines only the PRECIS-based rules for handling of nickname strings. It is the responsibility of an application protocol (e.g., MSRP, XCON, or XMPP) to specify the protocol slots in which nickname strings can appear, as well as the entities that are expected to enforce the rules governing nickname strings in that protocol (e.g., chat servers, chat clients, or both). Above and beyond the PRECIS-based rules specified here, application protocols can also define application-specific rules governing nickname strings (rules regarding the minimum or maximum length of nicknames, further restrictions on allowable characters or character ranges, safeguards to mitigate the effects of visually similar characters, etc.). Naturally, application protocols can also specify rules governing the actual use of nicknames in applications (reserved nicknames, authorization requirements for using nicknames, whether certain nicknames can be prohibited, handling of duplicates, the relationship between nicknames and underlying identifiers such as SIP URIs or JabberIDs, etc.). Better? Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB9aK0ACgkQNL8k5A2w/vxesACggUfScJphwk40beaXI8k4AMsd psYAoOQLIpjgoVR8lfBSE7WX1SEpNZuw =iQLH -----END PGP SIGNATURE----- From stpeter@stpeter.im Tue Oct 16 07:37:18 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D91BD21F878A for ; Tue, 16 Oct 2012 07:37:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.639 X-Spam-Level: X-Spam-Status: No, score=-102.639 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W-MzdcM2Xju4 for ; Tue, 16 Oct 2012 07:37:18 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id EBA6C21F8739 for ; Tue, 16 Oct 2012 07:37:17 -0700 (PDT) Received: from [192.168.1.5] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id D92B84011B; Tue, 16 Oct 2012 08:39:51 -0600 (MDT) Message-ID: <507D711C.6090200@stpeter.im> Date: Tue, 16 Oct 2012 08:37:16 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Yoshiro YONEYA References: <20121016212244.76c5c5970fad66a6c4750157@jprs.co.jp> <20121016212814.7685289c12c83ab8e82c3d5b@jprs.co.jp> In-Reply-To: <20121016212814.7685289c12c83ab8e82c3d5b@jprs.co.jp> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: precis@ietf.org Subject: Re: [precis] IETF85 Atlanta draft agenda X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2012 14:37:19 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Yoneya-san, that agenda looks good. Here is a bit of agenda-bashing and my thoughts on the various documents... On 10/16/12 6:28 AM, Yoshiro YONEYA wrote: > > On Tue, 16 Oct 2012 21:22:44 +0900 Yoshiro YONEYA > wrote: > >> Dear all, >> >> Following is draft agenda for IETF 85 Atlanta. Please send >> comments/additions/changes to the chairs. > > 1. Administrativia > > 2. Document updates / Discussion 2.1 WG I-Ds (1) Framework > https://datatracker.ietf.org/doc/draft-ietf-precis-framework/ In Atlanta I hope that we can have some discussion about whether to make width mapping a "full-class citizen" similar to casemapping and normalization (i.e., every class and subclass would need to specify if width mapping is required, recommended, or left up to the application protocol). Feedback would also be good on the IANA considerations. And of course we still need to do some testing. > (2) Preparation and Comparison of Nicknames > https://datatracker.ietf.org/doc/draft-ietf-precis-nickname This is very close to done. I've pinged a number of people in the SIP and XMPP communities for feedback. As a result, I expect to publish a small update before the cut-off date next Monday. I think it will be ready for WGLC at that point. > 2.2 Individual Documents (1) Mapping characters for PRECIS classes > https://datatracker.ietf.org/doc/draft-yoneya-precis-mappings/ I think it would be appropriate for the WG to adopt this item. Also see above about width mapping. > (2) Username and Password Preparation Algorithms > https://datatracker.ietf.org/doc/draft-melnikov-precis-saslprepbis/ I > think it would be appropriate for the WG to adopt this item (as I recall, we had agreement about that in Vancouver but Alexey and I wanted to clean up a few aspects of the spec before publishing it as a WG item). We still need to get more feedback about this spec from the security community and various application communities that use SASL (IMAP, XMPP, etc.). (3) XMPP Address Format https://datatracker.ietf.org/doc/draft-ietf-xmpp-6122bis/ This has been updated to align with the framework. This too is very close to done, and IMHO would be ready for WGLC in the XMPP WG (with cross-review from the PRECIS WG) soon after the Atlanta meeting (practically, we might want to run this LC after the LC on the nickname spec, but I leave that up to the PRECIS WG and XMPP WG chairs). (4) any updates to draft-nemoto-precis-framework-implement-report? > 3. Next steps Great reviews from lots of WG participants, widespread implementation, and universal deployment. ;-) Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB9cRwACgkQNL8k5A2w/vxU6QCdGp6fWk4SPlHraRloC37I3NTw 27AAoOKPdDfSdqt9hexBXd02KsG8UYFp =YWMH -----END PGP SIGNATURE----- From salvatore.loreto@ericsson.com Wed Oct 17 05:50:47 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6150321F8793 for ; Wed, 17 Oct 2012 05:50:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.393 X-Spam-Level: X-Spam-Status: No, score=-106.393 tagged_above=-999 required=5 tests=[AWL=-0.144, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mu7CkVQIwgll for ; Wed, 17 Oct 2012 05:50:46 -0700 (PDT) Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id B072C21F8781 for ; Wed, 17 Oct 2012 05:50:45 -0700 (PDT) X-AuditID: c1b4fb2d-b7fea6d000002ccb-65-507ea9a3a0ff Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 17.66.11467.3A9AE705; Wed, 17 Oct 2012 14:50:44 +0200 (CEST) Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Wed, 17 Oct 2012 14:50:43 +0200 Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 891A12AFE; Wed, 17 Oct 2012 15:50:43 +0300 (EEST) Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 3844C539E5; Wed, 17 Oct 2012 15:50:43 +0300 (EEST) Received: from n106.nomadiclab.com (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id DB1FE5361E; Wed, 17 Oct 2012 15:50:42 +0300 (EEST) Message-ID: <507EA9A2.8030300@ericsson.com> Date: Wed, 17 Oct 2012 15:50:42 +0300 From: Salvatore Loreto User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Peter Saint-Andre References: <50799413.7000407@ericsson.com> <507D68AD.4040404@stpeter.im> In-Reply-To: <507D68AD.4040404@stpeter.im> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyM+Jvre6SlXUBBo8P8Fns+v6H1eLYnn5m ByaPJUt+MnnM3fOCOYApissmJTUnsyy1SN8ugStj0fRDjAXHpSpOv/vE2sA4SbSLkZNDQsBE Yu6PZlYIW0ziwr31bF2MXBxCAqcYJY72LmWFcDYwSrxva2OHcHYzSvztvc0E0iIksI5RoqnN HCKxnFHi1LULYAleAW2J23tmMXcxcnCwCKhKXFsbDRJmEzCTeP5wCzOILSqQLDFvw1VmiHJB iZMzn7CA2CICWhKXrvWxg9jMAsIS67Z9YgQZIyxgKHHodjiIKSTgKXFrjgpIBSdQdeutrSwQ 1RYSi98chOqUl9j+dg4zxGNqElfPbWKGuFhLovdsJ9MERtFZSBbPQtI+C0n7AkbmVYzCuYmZ OenlhnqpRZnJxcX5eXrFqZsYgbFwcMtv3R2Mp86JHGKU5mBREuflStrvLySQnliSmp2aWpBa FF9UmpNafIiRiYNTqoExK/O3/59HnDfeqHMszM9YL1amd2TSsY9v5X/YvIl2urK74GDS1IMl 9tNKVmqab/UzsVr+yeJiRoByoti83/bNy1c+kGeQrVTN/bvs9j/24oqpBlxPCtuS/kS6xxyu XrKX1yVls2N+h9SHPaLye7wXbF2yMldaOOWsw7Ji4SMG84wqZzceM7+sxFKckWioxVxUnAgA FSm4clMCAAA= Cc: precis@ietf.org Subject: Re: [precis] comments on draft-precis-nickname-03 X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Oct 2012 12:50:47 -0000 On 10/16/12 5:01 PM, Peter Saint-Andre wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 10/13/12 10:17 AM, Salvatore Loreto wrote: >> I have reviewed the draft-ietf-precis-nickname-03 > Hi Sal, thanks for the review! > >> the only concern I have is on the last sentence of Section 3. Use >> in Application Protocols: >> >> Application protocols are also allowed to define >> application-specific rules governing use of nicknames in the >> relevant protocol slots (e.g., rules regarding the length of >> nicknames). >> >> I am not sure "use" is the term here. The responsibilities of the >> specific application protocol, that are of interest of this draft, >> are those that would eventually extending the string conformation >> constraints (e.g., rules regarding the length of nicknames) , and >> that must not contradict the rules specified in Section 2. However >> an application will also specify other rules governing use of >> nicknames (e.g. some names are reserved, prohibit to use etc.) but >> those are not of interest for this draft as far as the string name >> conform to Section2. > Let me see if I understand your point: there are rules about the > nickname strings themselves (e.g., length, allowable characters, > further restrictions to mitigate confusion about visually similar > characters), and then there are rules about how nickname strings are > employed in an application protocol (e.g., reserved nicknames, > prohibited nicknames). > > How about rephrasing the sentence as follows... > > OLD > This specification defines only the PRECIS-based rules for handling > of nicknames. It is the responsibility of application protocols such > as MSRP, XCON, and XMPP to specify which entities are expected to > enforce these rules (e.g., chat servers, chat clients, or both). > Application protocols are also allowed to define application-specific > rules governing use of nicknames in the relevant protocol slots > (e.g., rules regarding the length of nicknames). > > NEW > This specification defines only the PRECIS-based rules for handling > of nickname strings. It is the responsibility of an application > protocol (e.g., MSRP, XCON, or XMPP) to specify the protocol slots in > which nickname strings can appear, as well as the entities that are > expected to enforce the rules governing nickname strings in that > protocol (e.g., chat servers, chat clients, or both). Above and > beyond the PRECIS-based rules specified here, application protocols > can also define application-specific rules governing nickname strings > (rules regarding the minimum or maximum length of nicknames, further > restrictions on allowable characters or character ranges, safeguards > to mitigate the effects of visually similar characters, etc.). > Naturally, application protocols can also specify rules governing the > actual use of nicknames in applications (reserved nicknames, > authorization requirements for using nicknames, whether certain > nicknames can be prohibited, handling of duplicates, the relationship > between nicknames and underlying identifiers such as SIP URIs or > JabberIDs, etc.). > > Better? yes, it works for me thanks a lot Salvatore -- Salvatore Loreto, PhD www.sloreto.com From stpeter@stpeter.im Wed Oct 17 08:03:48 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2117521F8496 for ; Wed, 17 Oct 2012 08:03:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.579 X-Spam-Level: X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 600xGf6cU8cu for ; Wed, 17 Oct 2012 08:03:47 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 3687921F8493 for ; Wed, 17 Oct 2012 08:03:47 -0700 (PDT) Received: from [64.101.72.58] (unknown [64.101.72.58]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0474B4010C; Wed, 17 Oct 2012 09:06:23 -0600 (MDT) Message-ID: <507EBEA7.7020901@stpeter.im> Date: Wed, 17 Oct 2012 08:20:23 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Salvatore Loreto References: <50799413.7000407@ericsson.com> <507D68AD.4040404@stpeter.im> <507EA9A2.8030300@ericsson.com> In-Reply-To: <507EA9A2.8030300@ericsson.com> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: precis@ietf.org Subject: Re: [precis] comments on draft-precis-nickname-03 X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Oct 2012 15:03:48 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/17/12 6:50 AM, Salvatore Loreto wrote: > On 10/16/12 5:01 PM, Peter Saint-Andre wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 10/13/12 10:17 AM, Salvatore Loreto wrote: >>> I have reviewed the draft-ietf-precis-nickname-03 >> Hi Sal, thanks for the review! >> >>> the only concern I have is on the last sentence of Section 3. >>> Use in Application Protocols: >>> >>> Application protocols are also allowed to define >>> application-specific rules governing use of nicknames in the >>> relevant protocol slots (e.g., rules regarding the length of >>> nicknames). >>> >>> I am not sure "use" is the term here. The responsibilities of >>> the specific application protocol, that are of interest of this >>> draft, are those that would eventually extending the string >>> conformation constraints (e.g., rules regarding the length of >>> nicknames) , and that must not contradict the rules specified >>> in Section 2. However an application will also specify other >>> rules governing use of nicknames (e.g. some names are reserved, >>> prohibit to use etc.) but those are not of interest for this >>> draft as far as the string name conform to Section2. >> Let me see if I understand your point: there are rules about the >> nickname strings themselves (e.g., length, allowable characters, >> further restrictions to mitigate confusion about visually >> similar characters), and then there are rules about how nickname >> strings are employed in an application protocol (e.g., reserved >> nicknames, prohibited nicknames). >> >> How about rephrasing the sentence as follows... >> >> OLD This specification defines only the PRECIS-based rules for >> handling of nicknames. It is the responsibility of application >> protocols such as MSRP, XCON, and XMPP to specify which entities >> are expected to enforce these rules (e.g., chat servers, chat >> clients, or both). Application protocols are also allowed to >> define application-specific rules governing use of nicknames in >> the relevant protocol slots (e.g., rules regarding the length of >> nicknames). >> >> NEW This specification defines only the PRECIS-based rules for >> handling of nickname strings. It is the responsibility of an >> application protocol (e.g., MSRP, XCON, or XMPP) to specify the >> protocol slots in which nickname strings can appear, as well as >> the entities that are expected to enforce the rules governing >> nickname strings in that protocol (e.g., chat servers, chat >> clients, or both). Above and beyond the PRECIS-based rules >> specified here, application protocols can also define >> application-specific rules governing nickname strings (rules >> regarding the minimum or maximum length of nicknames, further >> restrictions on allowable characters or character ranges, >> safeguards to mitigate the effects of visually similar >> characters, etc.). Naturally, application protocols can also >> specify rules governing the actual use of nicknames in >> applications (reserved nicknames, authorization requirements for >> using nicknames, whether certain nicknames can be prohibited, >> handling of duplicates, the relationship between nicknames and >> underlying identifiers such as SIP URIs or JabberIDs, etc.). >> >> Better? > yes, it works for me Excellent. I'll publish a revised I-D before the cut-off on Monday, with this new text and perhaps a few other small fixes (if I receive more feedback). > thanks a lot We aim to please! Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB+vqcACgkQNL8k5A2w/vzrbgCfdDO4NAvek2Fp2/jtUg0UY2Xb x8IAn37mObwQKjImUizQAv/durAXAU3G =Fjbv -----END PGP SIGNATURE----- From internet-drafts@ietf.org Fri Oct 19 20:14:07 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C80121F882A; Fri, 19 Oct 2012 20:14:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.525 X-Spam-Level: X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xKIdsVUwiUsk; Fri, 19 Oct 2012 20:14:06 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A213021F8834; Fri, 19 Oct 2012 20:14:06 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.34 Message-ID: <20121020031406.30668.55437.idtracker@ietfa.amsl.com> Date: Fri, 19 Oct 2012 20:14:06 -0700 Cc: precis@ietf.org Subject: [precis] I-D Action: draft-ietf-precis-nickname-04.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Oct 2012 03:14:07 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Preparation and Comparison of Internation= alized Strings Working Group of the IETF. Title : Preparation and Comparison of Nicknames Author(s) : Peter Saint-Andre Filename : draft-ietf-precis-nickname-04.txt Pages : 7 Date : 2012-10-19 Abstract: This document describes how to prepare and compare Unicode strings representing nicknames, primarily for use within textual chatrooms. This profile is intended to be used by messaging and text conferencing technologies such as the Extensible Messaging and Presence Protocol (XMPP), the Message Session Relay Protocol (MSRP), and Centralized Conferencing (XCON). 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: http://tools.ietf.org/html/draft-ietf-precis-nickname-04 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-precis-nickname-04 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From stpeter@stpeter.im Mon Oct 22 09:08:30 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F0FD21F89E9 for ; Mon, 22 Oct 2012 09:08:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.613 X-Spam-Level: X-Spam-Status: No, score=-102.613 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sKLUCqv9gh48 for ; Mon, 22 Oct 2012 09:08:29 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 2E0B621F8417 for ; Mon, 22 Oct 2012 09:08:28 -0700 (PDT) Received: from [192.168.1.5] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E02F24010C for ; Mon, 22 Oct 2012 10:11:22 -0600 (MDT) Message-ID: <50856F8B.7040104@stpeter.im> Date: Mon, 22 Oct 2012 10:08:43 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: "precis@ietf.org" References: In-Reply-To: X-Enigmail-Version: 1.4.5 X-Forwarded-Message-Id: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [precis] Fwd: [saag] Fwd: I-D Action: draft-iab-identifier-comparison-05.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 16:08:30 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 FYI. - -------- Original Message -------- Subject: [saag] Fwd: I-D Action: draft-iab-identifier-comparison-05.txt Date: Sun, 21 Oct 2012 10:37:39 -0400 From: Russ Housley To: IETF SAAG This document is in the final stages. If you have last minute comments, please send them to iab@iab.org very soon. Russ > From: internet-drafts@ietf.org Date: October 20, 2012 7:19:31 PM > EDT To: i-d-announce@ietf.org Cc: iab@iab.org Subject: [IAB] I-D > Action: draft-iab-identifier-comparison-05.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. This draft is a work item of the Internet Architecture > Board Working Group of the IETF. > > Title : Issues in Identifier Comparison for Security > Purposes Author(s) : Dave Thaler Filename : > draft-iab-identifier-comparison-05.txt Pages : 23 Date > : 2012-10-20 > > Abstract: Identifiers such as hostnames, URIs, and email addresses > are often used in security contexts to identify security principals > and resources. In such contexts, an identifier supplied via some > protocol is often compared against some policy to make security > decisions such as whether the principal may access the resource, > what level of authentication or encryption is required, etc. If > the parties involved in a security decision use different > algorithms to compare identifiers, then failure scenarios ranging > from denial of service to elevation of privilege can result. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-iab-identifier-comparison > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-iab-identifier-comparison-05 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-iab-identifier-comparison-05 > > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > _______________________________________________ saag mailing list saag@ietf.org https://www.ietf.org/mailman/listinfo/saag -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCFb4sACgkQNL8k5A2w/vyXSACfZ59P2s1AtnRdZYDcxiMvSB74 N3UAoLonz2HHlK4obwdjLOwcxxaIyFfH =PuHU -----END PGP SIGNATURE----- From t.nemo10@kmd.keio.ac.jp Wed Oct 24 00:15:33 2012 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34F7F21F8D12 for ; Wed, 24 Oct 2012 00:15:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.999, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O7FYgWL+99m7 for ; Wed, 24 Oct 2012 00:15:31 -0700 (PDT) Received: from mail.kmd.keio.ac.jp (mail.kmd.keio.ac.jp [IPv6:2001:200:167:2e90::164]) by ietfa.amsl.com (Postfix) with ESMTP id B23CD21F8D0E for ; Wed, 24 Oct 2012 00:15:31 -0700 (PDT) Received: from dh202.jprs.co.jp (dh202.jprs.co.jp [202.11.17.202]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.kmd.keio.ac.jp (Postfix) with ESMTPSA id C84747FBE2; Wed, 24 Oct 2012 16:15:27 +0900 (JST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Takahiro Nemoto In-Reply-To: <507D711C.6090200@stpeter.im> Date: Wed, 24 Oct 2012 16:15:27 +0900 Content-Transfer-Encoding: 7bit Message-Id: <0F38518B-7DF8-4F9D-AAED-863A7EF755CC@kmd.keio.ac.jp> References: <20121016212244.76c5c5970fad66a6c4750157@jprs.co.jp> <20121016212814.7685289c12c83ab8e82c3d5b@jprs.co.jp> <507D711C.6090200@stpeter.im> To: Peter Saint-Andre X-Mailer: Apple Mail (2.1499) Cc: precis@ietf.org Subject: Re: [precis] IETF85 Atlanta draft agenda X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2012 07:15:33 -0000 Hello, Peter-san Thank you for adding my I-D in the agenda. But sorry, I don't have my update I-D yet... But I've made an experimental implementation for precis nickname that is one of precis framework. So I would like to briefly report and comment for precis framework in the (1)Framework session. :) Nemo On 2012/10/16, at 23:37, Peter Saint-Andre wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello Yoneya-san, that agenda looks good. Here is a bit of > agenda-bashing and my thoughts on the various documents... > > On 10/16/12 6:28 AM, Yoshiro YONEYA wrote: >> >> On Tue, 16 Oct 2012 21:22:44 +0900 Yoshiro YONEYA >> wrote: >> >>> Dear all, >>> >>> Following is draft agenda for IETF 85 Atlanta. Please send >>> comments/additions/changes to the chairs. >> >> 1. Administrativia >> >> 2. Document updates / Discussion 2.1 WG I-Ds (1) Framework >> https://datatracker.ietf.org/doc/draft-ietf-precis-framework/ > > In Atlanta I hope that we can have some discussion about whether to > make width mapping a "full-class citizen" similar to casemapping and > normalization (i.e., every class and subclass would need to specify if > width mapping is required, recommended, or left up to the application > protocol). Feedback would also be good on the IANA considerations. And > of course we still need to do some testing. > >> (2) Preparation and Comparison of Nicknames >> https://datatracker.ietf.org/doc/draft-ietf-precis-nickname > > This is very close to done. I've pinged a number of people in the SIP > and XMPP communities for feedback. As a result, I expect to publish a > small update before the cut-off date next Monday. I think it will be > ready for WGLC at that point. > >> 2.2 Individual Documents (1) Mapping characters for PRECIS classes >> https://datatracker.ietf.org/doc/draft-yoneya-precis-mappings/ > > I think it would be appropriate for the WG to adopt this item. Also > see above about width mapping. > >> (2) Username and Password Preparation Algorithms >> https://datatracker.ietf.org/doc/draft-melnikov-precis-saslprepbis/ > > I >> > think it would be appropriate for the WG to adopt this item (as I > recall, we had agreement about that in Vancouver but Alexey and I > wanted to clean up a few aspects of the spec before publishing it as a > WG item). We still need to get more feedback about this spec from the > security community and various application communities that use SASL > (IMAP, XMPP, etc.). > > (3) XMPP Address Format > https://datatracker.ietf.org/doc/draft-ietf-xmpp-6122bis/ > > This has been updated to align with the framework. This too is very > close to done, and IMHO would be ready for WGLC in the XMPP WG (with > cross-review from the PRECIS WG) soon after the Atlanta meeting > (practically, we might want to run this LC after the LC on the > nickname spec, but I leave that up to the PRECIS WG and XMPP WG chairs). > > (4) any updates to draft-nemoto-precis-framework-implement-report? > >> 3. Next steps > > Great reviews from lots of WG participants, widespread implementation, > and universal deployment. ;-) > > Peter > > - -- > Peter Saint-Andre > https://stpeter.im/ > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.18 (Darwin) > Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ > > iEYEARECAAYFAlB9cRwACgkQNL8k5A2w/vxU6QCdGp6fWk4SPlHraRloC37I3NTw > 27AAoOKPdDfSdqt9hexBXd02KsG8UYFp > =YWMH > -----END PGP SIGNATURE----- > _______________________________________________ > precis mailing list > precis@ietf.org > https://www.ietf.org/mailman/listinfo/precis