idnits 2.17.1 draft-hoffman-idna200x-topics-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 194. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 205. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 212. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 218. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 22, 2008) is 5848 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Hoffman 3 Internet-Draft VPN Consortium 4 Expires: October 24, 2008 April 22, 2008 6 Proposed High-level Changes From IDNA2003 To IDNA200x 7 draft-hoffman-idna200x-topics-03 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on October 24, 2008. 34 Copyright Notice 36 Copyright (C) The IETF Trust (2008). 38 Abstract 40 This document lists the changes that are proposed for IDNA200x. It 41 covers both the changes in the initial documents from the design team 42 and other changes proposed in the Working Group. 44 1. Introduction 46 This document lists the high-level changes that have been proposed 47 for IDNA2003 in the idnabis WG. It does not list the low-level 48 changes, such as the disposition of individual characters. 50 This is a temporary document meant for the use by the idnabis WG. 51 This work is being discussed on the mailing list at 52 idna-update@alvestrand.no. 54 2. Proposed Changes from the Design Team Documents 56 The initial set of documents for the IDNA200x effort consist of the 57 following: 59 o [IDNA200X-Protocol] - Internationalizing Domain Names in 60 Applications (IDNA): Protocol 62 o [IDNA200X-Tables] - The Unicode Codepoints and IDNA 64 o [IDNA200X-BIDI] - An updated IDNA criterion for right-to-left 65 scripts 67 o [IDNA200X-Rationale] - Internationalizing Domain Names for 68 Applications (IDNA): Issues, Explanation, and Rationale 70 At the time of this writing, these documents propose the following 71 changes to IDNA2003: 73 1. Update base character set from Unicode 3.2 to Unicode version- 74 agnostic 76 2. Separate the definitions for the "registration" and "lookup" 77 activities 79 3. Disallow symbol and punctuation characters except where special 80 exceptions are necessary 82 4. Remove the mapping and normalization steps from the protocol and 83 have them instead done by the applications themselves, possibly 84 in a local fashion, before invoking the protocol 86 5. Change the way that the protocol specifies which characters are 87 allowed in labels from "humans decide what the table of 88 codepoints contains" to "decision about codepoints are based on 89 Unicode properties plus a small exclusion list created by 90 humans" 92 6. Introduce the new concept of characters that can be used only in 93 specific contexts. 95 7. Allowing typical words and names in languages such as Dhivehi 96 and Yiddish to be expressed 98 8. Make bidirectional domain names (delimited strings of labels, 99 not just labels standing on their own) display in a non- 100 surprising fashion 102 9. Make bidirectional domain names in a paragraph display in a non- 103 surprising fashion 105 10. Remove the dot separator from the mandatory part of the protocol 107 11. Make some currently-legal, non-IDNA labels illegal 109 3. Changes Proposed by Individuals in the Working Group 111 In addition to the changes above, individuals in the Working Group 112 have proposed high-level changes. These include: 114 a. Add conversion between traditional and simplified Chinese 115 characters 117 b. Add guidelines or requirements for registration of character 118 variants, along the lines of RFC 3743 120 4. Security Considerations 122 The eventual document(s) will all have security considerations 123 sections of their own, some of which might point to the security 124 considerations in other documents. 126 5. Informative References 128 [IDNA200X-BIDI] 129 Alvestrand, H. and C. Karp, "An updated IDNA criterion for 130 right-to-left scripts", draft-alvestrand-idna-bidi (work 131 in progress). 133 [IDNA200X-Protocol] 134 Klensin, J., "Internationalizing Domain Names in 135 Applications (IDNA): Protocol", 136 draft-klensin-idnabis-protocol (work in progress). 138 [IDNA200X-Rationale] 139 Klensin, J., "Internationalizing Domain Names for 140 Applications (IDNA): Issues, Explanation, and Rationale", 141 draft-klensin-idnabis-issues (work in progress). 143 [IDNA200X-Tables] 144 Faltstrom, P., "The Unicode Codepoints and IDNA", 145 draft-faltstrom-idnabis-tables (work in progress). 147 Appendix A. Change Log 149 A.1. Differences between -00 and -01 151 Added "Remove the dot separator from the mandatory part of the 152 protocol" to the list. 154 Added "Make some currently-legal, non-IDNA labels illegal" to the 155 list. 157 A.2. Differences between -01 and -02 159 Changed the title to "Proposed...". Reworded the abstract and intro 160 to reflec this new coverage. 162 Added new section for WG-submitted changes. 164 A.3. Differences between -02 and -03 166 Clarified bullet 3. 168 Fixed the spelling of "eventual" in Section 4 and the spelling of 169 Alvestrand in the references. 171 Made the security considerations clearer and more vague. 173 Author's Address 175 Paul Hoffman 176 VPN Consortium 178 Email: paul.hoffman@vpnc.org 180 Full Copyright Statement 182 Copyright (C) The IETF Trust (2008). 184 This document is subject to the rights, licenses and restrictions 185 contained in BCP 78, and except as set forth therein, the authors 186 retain all their rights. 188 This document and the information contained herein are provided on an 189 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 190 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 191 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 192 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 193 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 194 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 196 Intellectual Property 198 The IETF takes no position regarding the validity or scope of any 199 Intellectual Property Rights or other rights that might be claimed to 200 pertain to the implementation or use of the technology described in 201 this document or the extent to which any license under such rights 202 might or might not be available; nor does it represent that it has 203 made any independent effort to identify any such rights. Information 204 on the procedures with respect to rights in RFC documents can be 205 found in BCP 78 and BCP 79. 207 Copies of IPR disclosures made to the IETF Secretariat and any 208 assurances of licenses to be made available, or the result of an 209 attempt made to obtain a general license or permission for the use of 210 such proprietary rights by implementers or users of this 211 specification can be obtained from the IETF on-line IPR repository at 212 http://www.ietf.org/ipr. 214 The IETF invites any interested party to bring to its attention any 215 copyrights, patents or patent applications, or other proprietary 216 rights that may cover technology that may be required to implement 217 this standard. Please address the information to the IETF at 218 ietf-ipr@ietf.org. 220 Acknowledgment 222 Funding for the RFC Editor function is provided by the IETF 223 Administrative Support Activity (IASA).