Internet Engineering Task Force (IETF) L. Camara Internet-Draft June 14, 2017 Updates: 2026, 5657, 7997 (if approved) Intended Status: Best Current Practice Expires: December 16, 2017 Allow non-ASCII characters in Internet-Drafts draft-luis140219-id-nonascii-02 Abstract RFC 7997 allowed non-ASCII characters in RFCs. This document updates RFC 2026, removing from it the requirement that Internet-Drafts be fully in ASCII. This document also updates RFC 5657 and RFC 7997 to note the allowance of non-ASCII characters in Internet-Drafts. [[RFC-Editor: please replace the second character of my surname by U+00E2 when publishing as RFC in the header and in all pages. Non-ASCII characters are allowed in RFCs as per RFC 7997.]] Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on December 16, 2017. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents Camara Expires December 16, 2017 [Page 1] Internet-Draft Non-ASCII Characters in Internet-Drafts June 2017 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Removal of the ASCII requirement for Internet-Drafts . . . . . 2 2.1. Updates to RFC 2026 . . . . . . . . . . . . . . . . . . . . . 2 2.2. Updates to RFC 5657 . . . . . . . . . . . . . . . . . . . . . 2 2.3. Updates to RFC 7997 . . . . . . . . . . . . . . . . . . . . . 3 2.4. Action to be taken . . . . . . . . . . . . . . . . . . . . . 3 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. Normative References . . . . . . . . . . . . . . . . . . . . . 4 6. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction RFC 7997 allows international characters in RFCs. This document allows non-ASCII characters in Internet-Drafts. [[RFC-Editor: This document, with an intended status of Best Current Practice, normatively references RFC 7997, an Informational RFC, being that reference a downref. This document needs to be a Best Current Practice because it updates BCP 9/RFC 2026, and the downref makes sense because RFC 7997 describes the rules for using non-ASCII characters and therefore is effectively part of this document because of the requirement in the second paragraph of Section 2. Please refer to BCP 97 (RFC 3967, RFC 4897, RFC 8067) for the downref guidelines.]] The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119, RFC8174]. 2. Removal of the ASCII requirement for Internet-Drafts Internet-Drafts posted after dd mmmm yyyy [[RFC-Editor: please put here the date when this document is published as RFC]] use UTF-8 [RFC3629] as their character encoding. The use of non-ASCII characters in Internet-Drafts MUST follow the rules of [RFC7997]. 2.1. Updates to RFC 2026 RFC 7997 does not update RFC 2026 and is Informational. This document makes the action of RFC 7997 normative, by replacing "ASCII" with "UTF-8" and by replacing the reference to the ASCII standard (X3.4-1986, reference [2] in RFC 2026) with a reference to the UTF-8 standard (RFC 3629). 2.2. Updates to RFC 5657 The first paragraph of Section 3 of RFC 5657 currently reads: Camara Expires December 16, 2017 [Page 2] Internet-Draft Non-ASCII Characters in Internet-Drafts June 2017 """ The format of implementation and interoperability reports MUST be ASCII text with line breaks for readability. As with Internet- Drafts, no 8-bit characters are currently allowed. It is acceptable, but not necessary, for a report to be formatted as an Internet-Draft. """ It should read: """ The format of implementation and interoperability reports MUST be UTF-8 [RFC3629] text with line breaks for readability. It is acceptable, but not necessary, for a report to be formatted as an Internet-Draft. """ The normative references section of RFC 5657 should have a reference to RFC 3629. 2.3. Updates to RFC 7997 RFC 7997 is updated to note that non-ASCII characters are now allowed in Internet-Drafts. 2.4. Action to be taken The draft submission tool (https://datatracker.ietf.org/submit/) must be updated to allow non-ASCII characters and [IDGUIDE] must be updated. The penultimate paragraph of Section 6 of [IDGUIDE] currently reads: """ I-Ds must be in ASCII. No 8-bit characters are allowed. If you need to include code points, one suggestion is to use the Unicode convention: U+XXXX, where X is a hexadecimal digit. """ It must be replaced by the phrase "I-Ds must be in UTF-8 [RFC3629].". The remaining occurrences of "ASCII" in [IDGUIDE] are to be replaced with "UTF-8". A reference to [RFC3629] must be added to Section 11 of [IDGUIDE]. The references to RFC 3979 and RFC 4879 must be replaced with a reference to RFC 8179, as RFC 3979 and RFC 4879 are obsoleted by RFC 8179. 3. Security Considerations The security considerations of this document are only those of [RFC7997]. Camara Expires December 16, 2017 [Page 3] Internet-Draft Non-ASCII Characters in Internet-Drafts June 2017 4. IANA Considerations [[RFC-Editor: please remove this section when publishing.]] This document has no actions for IANA. 5. Normative References [IDGUIDE] Housley, R., "Guidelines to Authors of Internet-Drafts", , 7 December 2010. (Permalink to 2010 version: ) [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [RFC2119] Bradner, S., "Key Words for Use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003. [RFC5657] Dusseault, L., and R. Sparks, "Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard", BCP 9, RFC 5657, September 2009. [RFC7997] Flanagan, H., Ed., "The Use of Non-ASCII Characters in RFCs", RFC 7997, December 2016. [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", RFC 8174, May 2017. [[RFC-Editor: please replace the 'i' in my name by U+00ED and the first 'a' in the surname by U+00E2, as non-ASCII characters are allowed as per RFC 7997]] 6. Author's Address Luis Camara EMail: Camara Expires December 16, 2017 [Page 4]