From nobody Mon Jun 1 11:22:23 2015 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ECEB1B30AA; Mon, 1 Jun 2015 11:22:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S-R_cMtiXSlP; Mon, 1 Jun 2015 11:22:20 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 41FA21B30BC; Mon, 1 Jun 2015 11:22:03 -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: 6.0.3.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150601182203.14097.82911.idtracker@ietfa.amsl.com> Date: Mon, 01 Jun 2015 11:22:03 -0700 Archived-At: Cc: precis chair , precis mailing list , RFC Editor Subject: [precis] Protocol Action: 'Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords' to Proposed Standard (draft-ietf-precis-saslprepbis-18.txt) X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2015 18:22:22 -0000 The IESG has approved the following document: - 'Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords' (draft-ietf-precis-saslprepbis-18.txt) as Proposed Standard This document is the product of the Preparation and Comparison of Internationalized Strings Working Group. The IESG contact persons are Ben Campbell, Barry Leiba and Alissa Cooper. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-precis-saslprepbis/ Technical Summary This document describes methods for handling internationalized usernames and passwords. It provides for a more sustainable approach than SASLprep (RFC 4013) by leveraging the PRECIS framework; this includes better adaptability to future versions of Unicode. While oriented toward SASL authentication schemes, the methods in this document can be applied to other schemes, such as HTTP-based authentication. Review and Consensus This document received wide review, including input from individuals in the KITTEN and HTTP-AUTH Working Groups, and spanned at least two Working Group Last Calls. The consensus in the PRECIS Working Group is to publish this document. One of the major points of concern was how to handle case mapping in usernames. In some protocols the case is significant, others it is not. To address this concern, the consensus was to define two profiles for usernames that protocols and applications are expected to choose exactly one of: UsernameCaseMapped for when case is not significant, and UsernameCasePreserved for when case is significant. The other major point of concern was how to deal with changes to the Unicode specifications (e.g., draft-klensin-idna-5892upd-unicode70). This concern is not specific to this document -- or even to the PRECIS Working Group -- but is relevant to all IETF technologies dealing with internationalized text (e.g., IDNA2008 and PRECIS). The issues are complex and the IETF has not yet developed mitigations. The rough consensus of the Working Group was to proceed with the PRECIS work as it stands since it is considered a significant improvement over the Stringprep-based approach, and to address these issues more comprehensively once future mitigations have been developed. Personnel Matthew Miller is the document shepherd, and Barry Leiba is the responsible AD. From nobody Thu Jun 11 16:04:51 2015 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22D631B3453 for ; Thu, 11 Jun 2015 16:04:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.702 X-Spam-Level: X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KUbgWF3Eg8ys for ; Thu, 11 Jun 2015 16:04:47 -0700 (PDT) Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A8911B3451 for ; Thu, 11 Jun 2015 16:04:47 -0700 (PDT) Received: by iebgx4 with SMTP id gx4so13818814ieb.0 for ; Thu, 11 Jun 2015 16:04:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=GsP6expTBcpx6DgY7cPSmQ0NaldSjgIocLNQ4VNmJJ4=; b=BzMXAtJ+xpGwStEDtPJbCuvpAK7WagVQyOWJzZiSYOlak8shcWnSJL1Uz66fDXmCm6 NAg0JnppBd2VsDESTbANf9t/B2NQ0YFgjC0PLNCZPN9YgwwyqCmxdM3PL0pfs3ago4cy Qvc4FmVLXoqD6IpNAxImJmBJW6bwEqUf/ogiyDX+4QDKY8kPVvFlWLU3fnAPtgIxllaY uRFJ/AIGzWSGsIunhcjFmABOy+71WmwIqTdiES96DZepeWy+80RnStq2EjVtHMRSppR+ vuV37s1nWQ0QjYCwGIM/GNi3+/djPsU0bv8pe0bw1IhWm91SpngsMFgJxtQx2xmTdQl2 xE7w== X-Gm-Message-State: ALoCoQk5/BcGD43FBOVRoEMoQi4g5MdPlWVZvriNUgnrGBM5lPPZ/+2sRl4vKyMMVDTgLagbnZ8L X-Received: by 10.43.148.72 with SMTP id kf8mr13810680icc.76.1434063886803; Thu, 11 Jun 2015 16:04:46 -0700 (PDT) Received: from aither.local ([2601:1:8200:3a60:d89f:1b2f:6531:1568]) by mx.google.com with ESMTPSA id g23sm1347207iod.37.2015.06.11.16.04.44 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jun 2015 16:04:45 -0700 (PDT) Message-ID: <557A140B.9060203@andyet.net> Date: Thu, 11 Jun 2015 17:04:43 -0600 From: Peter Saint-Andre - &yet User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: "precis@ietf.org" Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [precis] shepherd review of draft-ietf-precis-mappings X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 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, 11 Jun 2015 23:04:49 -0000 With my document shepherd hat on, I just reviewed draft-ietf-precis-mappings. I have sent some editorial comments to the authors. I also found two more substantive issues... 1. The "local case mapping" method specified in Section 2.3 talks about locale and context. However, the example in the second paragraph is a matter of language, not locale: As an example of locale and context-dependent mapping, LATIN CAPITAL LETTER I ("I", U+0049) is normally mapped to LATIN SMALL LETTER I ("i", U+0069); however, if the case of Turkish (or one of several other languages), unless an I is before a dot_above, the character should be mapped to LATIN SMALL LETTER DOTLESS I (U+0131). As I understand it, locale (see Section 8 of RFC 6365) would refer to a particular region within a language-speaking community, such as Switzerland within the German-speaking areas. The SpecialCasing.txt file in the Unicode standard talks about language-sensitive mappings for the Lithuanian, Turkish, and Azeri languages. (It also talks about a language-insensitive mapping, i.e., context-dependent mapping, for Greek final sigma.) It does not talk about locale-dependent mappings for particular regions within any language-speaking communities. Therefore, I wonder if all mentions of locale in draft-ietf-precis-mappings really ought to be mentions of language. On reading the text in the document right now, I provisionally concluded that this switch would make sense, but I haven't thought carefully about every instance. And I would be curious to hear from the authors and working group about this issue. 2. Appendix B purports to describe why local case mapping needs to be an alternative to Unicode Default Case Mapping instead of being applied sequentially (the text mentions the possibility of applying local case mapping before Unicode Default Case Mapping - is that the only option, or should we say something about applying it after?). However, Appendix B only mentions eszett (U+00DF) and to my mind does not provide a complete argument for why local case mapping needs to be an alternative to Unicode Default Case Mapping. At the least, it might be valuable to mention the handling of characters other than eszett. I suppose the basic argument is already in Section 2.3, but if so then I think that Appendix B might have a misleading title. Other than these two issues, I think the document is in good shape (modulo some editorial adjustments). Peter -- Peter Saint-Andre https://andyet.com/ From nobody Fri Jun 12 02:25:25 2015 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE25D1A8A72 for ; Fri, 12 Jun 2015 02:25:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.261 X-Spam-Level: X-Spam-Status: No, score=-3.261 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9kECokNhihXz for ; Fri, 12 Jun 2015 02:25:18 -0700 (PDT) Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D13401A8A7D for ; Fri, 12 Jun 2015 02:25:17 -0700 (PDT) Received: from [77.72.226.113] (dyn-fg113.sth.netnod.se [77.72.226.113]) by mail.frobbit.se (Postfix) with ESMTPSA id 52FA61FFC5; Fri, 12 Jun 2015 11:25:14 +0200 (CEST) From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" To: "Peter Saint-Andre - &yet" Date: Fri, 12 Jun 2015 11:25:13 +0200 Message-ID: In-Reply-To: <557A140B.9060203@andyet.net> References: <557A140B.9060203@andyet.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_MailMate_FA1996EB-BD6D-420C-A991-3AEC9CE39ABC_="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Mailer: MailMate (1.9.1r5095) Archived-At: Cc: precis@ietf.org Subject: Re: [precis] shepherd review of draft-ietf-precis-mappings X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 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, 12 Jun 2015 09:25:24 -0000 This is an OpenPGP/MIME signed message (RFC 3156 and 4880). --=_MailMate_FA1996EB-BD6D-420C-A991-3AEC9CE39ABC_= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable There might be geographical issues as well, and not only language. Or rat= her, if the language also have a geographic tag (that I do not remember w= hat its name is) then it might be complete. Example, in French, one do not have accents on the capital letters (well,= one have if it is needed due to distinguish between words, if it is a na= me etc -- so it is optional), but do in Canada. Of course, one can say ma= ybe that French in France is one language and French in Qu=C3=A9b=C3=A9c = is another, but... You get the point. So, I agree with you that one should probably treat the word "language" a= s only one example of a parameter in the "locale" definition that changes= the behaviour of the function. Patrik On 12 Jun 2015, at 1:04, Peter Saint-Andre - &yet wrote: > With my document shepherd hat on, I just reviewed draft-ietf-precis-map= pings. I have sent some editorial comments to the authors. I also found t= wo more substantive issues... > > 1. The "local case mapping" method specified in Section 2.3 talks about= locale and context. However, the example in the second paragraph is a ma= tter of language, not locale: > > As an example of locale and context-dependent mapping, LATIN CAPITAL > LETTER I ("I", U+0049) is normally mapped to LATIN SMALL LETTER I > ("i", U+0069); however, if the case of Turkish (or one of several > other languages), unless an I is before a dot_above, the character > should be mapped to LATIN SMALL LETTER DOTLESS I (U+0131). > > As I understand it, locale (see Section 8 of RFC 6365) would refer to a= particular region within a language-speaking community, such as Switzerl= and within the German-speaking areas. > > The SpecialCasing.txt file in the Unicode standard talks about language= -sensitive mappings for the Lithuanian, Turkish, and Azeri languages. (It= also talks about a language-insensitive mapping, i.e., context-dependent= mapping, for Greek final sigma.) It does not talk about locale-dependent= mappings for particular regions within any language-speaking communities= =2E > > Therefore, I wonder if all mentions of locale in draft-ietf-precis-mapp= ings really ought to be mentions of language. On reading the text in the = document right now, I provisionally concluded that this switch would make= sense, but I haven't thought carefully about every instance. And I would= be curious to hear from the authors and working group about this issue. > > 2. Appendix B purports to describe why local case mapping needs to be a= n alternative to Unicode Default Case Mapping instead of being applied se= quentially (the text mentions the possibility of applying local case mapp= ing before Unicode Default Case Mapping - is that the only option, or sho= uld we say something about applying it after?). > > However, Appendix B only mentions eszett (U+00DF) and to my mind does n= ot provide a complete argument for why local case mapping needs to be an = alternative to Unicode Default Case Mapping. At the least, it might be va= luable to mention the handling of characters other than eszett. I suppose= the basic argument is already in Section 2.3, but if so then I think tha= t Appendix B might have a misleading title. > > Other than these two issues, I think the document is in good shape (mod= ulo some editorial adjustments). > > Peter > > -- = > Peter Saint-Andre > https://andyet.com/ > > _______________________________________________ > precis mailing list > precis@ietf.org > https://www.ietf.org/mailman/listinfo/precis --=_MailMate_FA1996EB-BD6D-420C-A991-3AEC9CE39ABC_= Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlV6pXkACgkQrMabGguI182MCQCdFU+zwZCfOhoNj9tTM9qImyCB 8rYAoJDLFSalftsJ97P806DYpMYijHC1 =SHF4 -----END PGP SIGNATURE----- --=_MailMate_FA1996EB-BD6D-420C-A991-3AEC9CE39ABC_=-- From nobody Fri Jun 12 09:50:09 2015 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 960AE1A88C3 for ; Fri, 12 Jun 2015 09:50:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.301 X-Spam-Level: X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U55IiKiY4rFK for ; Fri, 12 Jun 2015 09:50:05 -0700 (PDT) Received: from mail-ig0-f180.google.com (mail-ig0-f180.google.com [209.85.213.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D3B11ABD3B for ; Fri, 12 Jun 2015 09:49:51 -0700 (PDT) Received: by igbhj9 with SMTP id hj9so16286929igb.1 for ; Fri, 12 Jun 2015 09:49:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=pYsvuoggsWkTmTTwaG6GqfsYbnf8fG6vzzodFXk5Dqk=; b=dS+BkDoYxJzO8/SdT39+9Z0XGI2NMMuC3KUXLnkUxskx1+PVM+JEngz4bgbU4EcMX1 xOoNd8zmIe06IxHuISq5yGxj8hU0GhMyFACIbP6TI6P7Kr+f7sVbW8v5QVZ+NBUf8WJP 3JCYHlvCeTdOsJ7lJEhJTi+s6rS/UbM++AQJgHdFj5KrzkQ7vZcdPCJAcJrup7XZE18d 4XQWSA6KQX0VaaKa4vq/R2EEoI43UGNqmmablLZT2CARzTPLNa27AdasmcCMov9FTQXp quJpOOLIYMC75+zAkHIW/lWgREvZQpYTP0hQRUSAYCY7g8YrCemx/XVHht+gDGLrKWLZ jZ0A== X-Gm-Message-State: ALoCoQlrr+lsqow7+bQslSVZ+NdkJrtJX5r1/uhCcuZzkNOBUUhGAhDZLKovgyNBDCOSZQsqOefn X-Received: by 10.107.130.218 with SMTP id m87mr18761720ioi.62.1434127790409; Fri, 12 Jun 2015 09:49:50 -0700 (PDT) Received: from aither.local ([2601:1:8200:3a60:c4ad:ae21:45d1:bb19]) by mx.google.com with ESMTPSA id n14sm2809197ion.5.2015.06.12.09.49.48 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Jun 2015 09:49:48 -0700 (PDT) Message-ID: <557B0DA9.1010800@andyet.net> Date: Fri, 12 Jun 2015 10:49:45 -0600 From: Peter Saint-Andre - &yet User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= References: <557A140B.9060203@andyet.net> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Cc: precis@ietf.org Subject: Re: [precis] shepherd review of draft-ietf-precis-mappings X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 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, 12 Jun 2015 16:50:07 -0000 Hi Patrik, On 6/12/15 3:25 AM, Patrik Fältström wrote: > There might be geographical issues as well, and not only language. Or > rather, if the language also have a geographic tag (that I do not > remember what its name is) then it might be complete. > > Example, in French, one do not have accents on the capital letters > (well, one have if it is needed due to distinguish between words, if > it is a name etc -- so it is optional), but do in Canada. Of course, > one can say maybe that French in France is one language and French in > Québéc is another, but... > > You get the point. Yes, I see your point, and fr-fr vs. fr-ca is a good example that Marc could tell us all about. :-) > So, I agree with you that one should probably treat the word > "language" as only one example of a parameter in the "locale" > definition that changes the behaviour of the function. Agreed. However, it's important to note that right now the alternative case mapping method defined in this document doesn't cover modifications based on geographic location or political jurisdiction, only language (see my previous note) and in one case context (Greek final sigma). By the way, the more I think about it, the less I like the term "local case mapping" because "local" sounds like "locale" and also could be confused with localization. I suggest that we might want to change it to "alternative case mapping" (as opposed to "default case mapping" as in Unicode Default Case Folding). Peter > Patrik > > On 12 Jun 2015, at 1:04, Peter Saint-Andre - &yet wrote: > >> With my document shepherd hat on, I just reviewed >> draft-ietf-precis-mappings. I have sent some editorial comments to >> the authors. I also found two more substantive issues... >> >> 1. The "local case mapping" method specified in Section 2.3 talks >> about locale and context. However, the example in the second >> paragraph is a matter of language, not locale: >> >> As an example of locale and context-dependent mapping, LATIN >> CAPITAL LETTER I ("I", U+0049) is normally mapped to LATIN SMALL >> LETTER I ("i", U+0069); however, if the case of Turkish (or one of >> several other languages), unless an I is before a dot_above, the >> character should be mapped to LATIN SMALL LETTER DOTLESS I >> (U+0131). >> >> As I understand it, locale (see Section 8 of RFC 6365) would refer >> to a particular region within a language-speaking community, such >> as Switzerland within the German-speaking areas. >> >> The SpecialCasing.txt file in the Unicode standard talks about >> language-sensitive mappings for the Lithuanian, Turkish, and Azeri >> languages. (It also talks about a language-insensitive mapping, >> i.e., context-dependent mapping, for Greek final sigma.) It does >> not talk about locale-dependent mappings for particular regions >> within any language-speaking communities. >> >> Therefore, I wonder if all mentions of locale in >> draft-ietf-precis-mappings really ought to be mentions of language. >> On reading the text in the document right now, I provisionally >> concluded that this switch would make sense, but I haven't thought >> carefully about every instance. And I would be curious to hear from >> the authors and working group about this issue. >> >> 2. Appendix B purports to describe why local case mapping needs to >> be an alternative to Unicode Default Case Mapping instead of being >> applied sequentially (the text mentions the possibility of applying >> local case mapping before Unicode Default Case Mapping - is that >> the only option, or should we say something about applying it >> after?). >> >> However, Appendix B only mentions eszett (U+00DF) and to my mind >> does not provide a complete argument for why local case mapping >> needs to be an alternative to Unicode Default Case Mapping. At the >> least, it might be valuable to mention the handling of characters >> other than eszett. I suppose the basic argument is already in >> Section 2.3, but if so then I think that Appendix B might have a >> misleading title. >> >> Other than these two issues, I think the document is in good shape >> (modulo some editorial adjustments). >> >> Peter >> >> -- Peter Saint-Andre https://andyet.com/ >> >> _______________________________________________ precis mailing >> list precis@ietf.org https://www.ietf.org/mailman/listinfo/precis From nobody Fri Jun 12 09:57:31 2015 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEFA41AC442 for ; Fri, 12 Jun 2015 09:57:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.261 X-Spam-Level: X-Spam-Status: No, score=-1.261 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oX2QP_LJfZod for ; Fri, 12 Jun 2015 09:57:29 -0700 (PDT) Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A4F01AC444 for ; Fri, 12 Jun 2015 09:57:29 -0700 (PDT) Received: from [172.20.10.6] (2.66.6.99.mobile.tre.se [2.66.6.99]) by mail.frobbit.se (Postfix) with ESMTPSA id C3FB8200C7; Fri, 12 Jun 2015 18:57:27 +0200 (CEST) From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" To: "Peter Saint-Andre - &yet" Date: Fri, 12 Jun 2015 18:57:27 +0200 Message-ID: <2834BF80-8AF0-4C28-85E5-CDB11C4E870C@frobbit.se> In-Reply-To: <557B0DA9.1010800@andyet.net> References: <557A140B.9060203@andyet.net> <557B0DA9.1010800@andyet.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_MailMate_7923EECB-6141-4FDE-B88F-E5FADFCE84D0_="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Mailer: MailMate (1.9.1r5095) Archived-At: Cc: precis@ietf.org Subject: Re: [precis] shepherd review of draft-ietf-precis-mappings X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 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, 12 Jun 2015 16:57:30 -0000 This is an OpenPGP/MIME signed message (RFC 3156 and 4880). --=_MailMate_7923EECB-6141-4FDE-B88F-E5FADFCE84D0_= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On 12 Jun 2015, at 18:49, Peter Saint-Andre - &yet wrote: > I suggest that we might want to change it to "alternative case mapping"= (as opposed to "default case mapping" as in Unicode Default Case Folding= ). Sounds like a good plan to me. Patrik --=_MailMate_7923EECB-6141-4FDE-B88F-E5FADFCE84D0_= Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlV7D3cACgkQrMabGguI181lggCeMuoH9rlPu8SujDnq45+neSoA bMoAn3jreEmMl+VYKmflSJXggcRBNiix =y8ZU -----END PGP SIGNATURE----- --=_MailMate_7923EECB-6141-4FDE-B88F-E5FADFCE84D0_=-- From nobody Mon Jun 15 12:20:37 2015 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 651831A8880 for ; Mon, 15 Jun 2015 12:20:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.911 X-Spam-Level: X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nTWVadTrVXNz for ; Mon, 15 Jun 2015 12:20:34 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7480F1A8895 for ; Mon, 15 Jun 2015 12:20:28 -0700 (PDT) Received: from [206.123.31.98] (kuwa.viagenie.ca [206.123.31.98]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 5D713475A4 for ; Mon, 15 Jun 2015 15:20:30 -0400 (EDT) From: "Marc Blanchet" To: precis@ietf.org Date: Mon, 15 Jun 2015 15:20:27 -0400 Message-ID: <383C9DA6-9B92-49EF-9EBA-176AD83E063B@viagenie.ca> References: <20150615191756.32261.18236.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (1.9.1r5084) Archived-At: Subject: [precis] Fwd: Protocol Action: 'Extensible Messaging and Presence Protocol (XMPP): Address Format' to Proposed Standard (draft-ietf-xmpp-6122bis-24.txt) X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 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, 15 Jun 2015 19:20:35 -0000 XMPP using precis! congratulations! Marc. Forwarded message: > From: The IESG > To: IETF-Announce > Cc: xmpp chair , xmpp mailing list > , RFC Editor > Subject: Protocol Action: 'Extensible Messaging and Presence Protocol > (XMPP): Address Format' to Proposed Standard > (draft-ietf-xmpp-6122bis-24.txt) > Date: Mon, 15 Jun 2015 12:17:56 -0700 > > The IESG has approved the following document: > - 'Extensible Messaging and Presence Protocol (XMPP): Address Format' > (draft-ietf-xmpp-6122bis-24.txt) as Proposed Standard > > This document is the product of the Extensible Messaging and Presence > Protocol Working Group. > > The IESG contact persons are Barry Leiba, Ben Campbell and Alissa > Cooper. > > A URL of this Internet Draft is: > https://datatracker.ietf.org/doc/draft-ietf-xmpp-6122bis/ > > > > > > Technical Summary > > This document defines the address format for the Extensible Messaging > and Presence Protocol (XMPP), including support for code points > outside the ASCII range. This document obsoletes RFC 6122 to move > from using stringprep to using precis profiles. > > Working Group Summary > > This document received review from a small but active number of > individuals from the Working Group and the XMPP Community. There is > consensus to publish this document. > > The XMPP Community did raise the concern that some addresses which are > valid using RFC 6122 are no longer valid using this document. > However, > the consensus of the XMPP Community and the Working Group is that: > this > document adequately describes the concerns and potential ways to > resolve such issues; and that such JIDs are exceedingly rare, if they > have ever been encountered. > > Document Quality > > XMPP has a number of interoperable implementations, and a vibrant > development community. Several implementers have reviewed various > versions of this document. > > Personnel > > The Document Shepherd is Matthew Miller > The responsible AD is Ben Campbell. From nobody Wed Jun 24 12:25:35 2015 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 868C01A8AEA for ; Wed, 24 Jun 2015 12:25:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.911 X-Spam-Level: X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FPSguiiXlu9r for ; Wed, 24 Jun 2015 12:25:32 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7347B1B2D04 for ; Wed, 24 Jun 2015 12:25:32 -0700 (PDT) Received: from [10.196.201.172] (41-193.icannmeeting.org [199.91.193.41]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 0A9F146912 for ; Wed, 24 Jun 2015 15:25:33 -0400 (EDT) From: "Marc Blanchet" To: precis@ietf.org Date: Wed, 24 Jun 2015 16:25:30 -0300 Message-ID: <975F9730-9A50-4A30-A4B0-F47F36B5BB65@viagenie.ca> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailer: MailMate (1.9.1r5084) Archived-At: Subject: Re: [precis] meeting in Prague? X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 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 Jun 2015 19:25:33 -0000 followup: - we haven’t requested a slot for precis. - there was a request to wg chairs to request the minimum they need because the schedule was overbooked. Therefore, there will be no precis meeting in Prague. Regards, Marc. On 28 May 2015, at 13:10, Marc Blanchet wrote: > The co-chairs do not currently plan to request a meeting slot for next > IETF in Prague. Do people have any topic to discuss that requires f2f > time in Prague? > > Regards, Marc. > > _______________________________________________ > precis mailing list > precis@ietf.org > https://www.ietf.org/mailman/listinfo/precis From nobody Fri Jun 26 08:29:22 2015 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D4711A1BB3; Fri, 26 Jun 2015 08:29:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id njMjsMslI1eY; Fri, 26 Jun 2015 08:29:19 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 35E091A1B78; Fri, 26 Jun 2015 08:29:19 -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: 6.0.4.p1 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <20150626152919.24519.62010.idtracker@ietfa.amsl.com> Date: Fri, 26 Jun 2015 08:29:19 -0700 Archived-At: Cc: precis@ietf.org Subject: [precis] Last Call: (Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames) to Proposed Standard X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 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: Fri, 26 Jun 2015 15:29:20 -0000 The IESG has received a request from the Preparation and Comparison of Internationalized Strings WG (precis) to consider the following document: - 'Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames' as Proposed Standard 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 2015-07-10. 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 This document describes methods for handling Unicode strings representing nicknames. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-precis-nickname/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-precis-nickname/ballot/ No IPR declarations have been submitted directly on this I-D. From nobody Fri Jun 26 09:24:18 2015 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C74C21A00E2; Fri, 26 Jun 2015 09:24:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EtjIB4GEaK9T; Fri, 26 Jun 2015 09:24:14 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C7E3B1A0373; Fri, 26 Jun 2015 09:24:13 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.0.4.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150626162413.8547.73423.idtracker@ietfa.amsl.com> Date: Fri, 26 Jun 2015 09:24:13 -0700 Archived-At: Cc: precis@ietf.org Subject: [precis] I-D Action: draft-ietf-precis-nickname-18.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2015 16:24:15 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Preparation and Comparison of Internationalized Strings Working Group of the IETF. Title : Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames Author : Peter Saint-Andre Filename : draft-ietf-precis-nickname-18.txt Pages : 9 Date : 2015-06-26 Abstract: This document describes methods for handling Unicode strings representing nicknames. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-precis-nickname/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-precis-nickname-18 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-precis-nickname-18 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Jun 26 09:30:02 2015 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E18711A1A76 for ; Fri, 26 Jun 2015 09:30:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MvYC2a3iFZPL for ; Fri, 26 Jun 2015 09:29:59 -0700 (PDT) Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com [209.85.213.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7189D1A1A73 for ; Fri, 26 Jun 2015 09:29:59 -0700 (PDT) Received: by igrv9 with SMTP id v9so4621524igr.1 for ; Fri, 26 Jun 2015 09:29:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Hfea+FnrNX6H1oCfHtEhRFJqeP8iTZIr8riRy5g9iHM=; b=GpTYKj3DqLL8LOrdryE5kg4WRSl8koDvxC6n70O35xN093D7e+EFgIMfc0ZiT5Mgco fpdtrkKtKOIWi7lXxaig1Nf84CqSChMnEY55Uu/V9L8bY/NvyWFjPvATTWuhcyELF//5 AKV4M9R2T7ulbkjyZtrI5uHcihcYlhtTLRfMie5GzbqHq1Zsmnx+pIWko5xGeHRoRyl7 b+Asr+krN3ymrLcoJVYcuM75ZIBmRXwI1DTPbT4n+NkW7rnTic+CzFHKErqqv3ESbpXb SjHnbJ3o3/NboP7JxUhy9llcTaTJ8ZNnmTnLrl2RnVMZKK+kXVrPuqEFn+RWLHTgRUrF F4gw== X-Gm-Message-State: ALoCoQmrehlPyM8EKLalJuho7sctd+CiiVfem31MpCrXi6hbyUW+yp+SIkOxwYhLweERNUjD6Gp9 X-Received: by 10.50.30.197 with SMTP id u5mr4714439igh.9.1435336198886; Fri, 26 Jun 2015 09:29:58 -0700 (PDT) Received: from aither.local ([2601:282:4201:ef5b:e0dd:a498:af68:ea6f]) by mx.google.com with ESMTPSA id 77sm21926587ioi.20.2015.06.26.09.29.56 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 Jun 2015 09:29:57 -0700 (PDT) Message-ID: <558D7E02.6010102@andyet.net> Date: Fri, 26 Jun 2015 10:29:54 -0600 From: Peter Saint-Andre - &yet User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: precis@ietf.org References: <20150626162413.8547.73423.idtracker@ietfa.amsl.com> In-Reply-To: <20150626162413.8547.73423.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [precis] I-D Action: draft-ietf-precis-nickname-18.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 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, 26 Jun 2015 16:30:01 -0000 A few small fixes to address feedback from the document shepherd. Thanks, Matt! On 6/26/15 10:24 AM, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Preparation and Comparison of Internationalized Strings Working Group of the IETF. > > Title : Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames > Author : Peter Saint-Andre > Filename : draft-ietf-precis-nickname-18.txt > Pages : 9 > Date : 2015-06-26 > > Abstract: > This document describes methods for handling Unicode strings > representing nicknames. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-precis-nickname/ > > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-precis-nickname-18 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-precis-nickname-18 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > precis mailing list > precis@ietf.org > https://www.ietf.org/mailman/listinfo/precis > -- Peter Saint-Andre https://andyet.com/