< draft-luis140219-id-nonascii-02.txt   draft-luis140219-id-nonascii-03.txt >
Internet Engineering Task Force (IETF) L. Camara Internet Engineering Task Force (IETF) L. Camara
Internet-Draft June 14, 2017 Internet-Draft June 18, 2017
Updates: 2026, 5657, 7997 (if approved) Updates: 2026, 5657, 7997 (if approved)
Intended Status: Best Current Practice Intended Status: Best Current Practice
Expires: December 16, 2017 Expires: December 20, 2017
Allow non-ASCII characters in Internet-Drafts Allow non-ASCII characters in Internet-Drafts
draft-luis140219-id-nonascii-02 draft-luis140219-id-nonascii-03
Abstract Abstract
RFC 7997 allowed non-ASCII characters in RFCs. This document updates RFC 7997 allowed non-ASCII characters in RFCs. This document updates
RFC 2026, removing from it the requirement that Internet-Drafts be RFC 2026, removing from it the requirement that Internet-Drafts be
fully in ASCII. This document also updates RFC 5657 and RFC 7997 to fully in ASCII. This document also updates RFC 5657 and RFC 7997 to
note the allowance of non-ASCII characters in Internet-Drafts. note the allowance of non-ASCII characters in Internet-Drafts.
[[RFC-Editor: please replace the second character of my surname by [[RFC-Editor: please replace the second character of my surname by
U+00E2 when publishing as RFC in the header and in all pages. U+00E2 when publishing as RFC in the header and in all pages.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 16, 2017. This Internet-Draft will expire on December 20, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Removal of the ASCII requirement for Internet-Drafts . . . . . 2 2. Removal of the ASCII requirement for Internet-Drafts . . . . . 2
2.1. Updates to RFC 2026 . . . . . . . . . . . . . . . . . . . . . 2 2.1. Updates to RFC 2026 . . . . . . . . . . . . . . . . . . . . . 2
2.2. Updates to RFC 5657 . . . . . . . . . . . . . . . . . . . . . 2 2.2. Updates to RFC 5657 . . . . . . . . . . . . . . . . . . . . . 3
2.3. Updates to RFC 7997 . . . . . . . . . . . . . . . . . . . . . 3 2.3. Updates to RFC 7997 . . . . . . . . . . . . . . . . . . . . . 3
2.4. Action to be taken . . . . . . . . . . . . . . . . . . . . . 3 2.4. Action to be taken . . . . . . . . . . . . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5. Normative References . . . . . . . . . . . . . . . . . . . . . 4 5. Normative References . . . . . . . . . . . . . . . . . . . . . 4
6. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 4 6. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
RFC 7997 allows international characters in RFCs. This document RFC 7997 allows international characters in RFCs. This document
allows non-ASCII characters in Internet-Drafts. allows non-ASCII characters in Internet-Drafts, and updates RFC 2026,
RFC 5657 and RFC 7997 to make the action of
[[RFC-Editor: This document, with an intended status of Best Current [[RFC-Editor: This document, with an intended status of Best Current
Practice, normatively references RFC 7997, an Informational RFC, Practice, normatively references RFC 7997, an Informational RFC,
being that reference a downref. This document needs to be a Best being that reference a downref. This document needs to be a Best
Current Practice because it updates BCP 9/RFC 2026, and the downref Current Practice because it updates BCP 9/RFC 2026, and the downref
makes sense because RFC 7997 describes the rules for using non-ASCII makes sense because RFC 7997 describes the rules for using non-ASCII
characters and therefore is effectively part of this document because characters and therefore is effectively part of this document because
of the requirement in the second paragraph of Section 2. Please refer of the requirement in the second paragraph of Section 2. Please refer
to BCP 97 (RFC 3967, RFC 4897, RFC 8067) for the downref to BCP 97 (RFC 3967, RFC 4897, RFC 8067) for the downref
guidelines.]] guidelines.]]
skipping to change at page 2, line 49 skipping to change at page 2, line 50
UTF-8 [RFC3629] as their character encoding. UTF-8 [RFC3629] as their character encoding.
The use of non-ASCII characters in Internet-Drafts MUST follow the The use of non-ASCII characters in Internet-Drafts MUST follow the
rules of [RFC7997]. rules of [RFC7997].
2.1. Updates to RFC 2026 2.1. Updates to RFC 2026
RFC 7997 does not update RFC 2026 and is Informational. This RFC 7997 does not update RFC 2026 and is Informational. This
document makes the action of RFC 7997 normative, by replacing "ASCII" document makes the action of RFC 7997 normative, by replacing "ASCII"
with "UTF-8" and by replacing the reference to the ASCII standard 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 (X3.4-1986, reference [2] in [RFC2026]) with a reference to the UTF-8
standard (RFC 3629). standard (RFC 3629).
2.2. Updates to RFC 5657 2.2. Updates to RFC 5657
The first paragraph of Section 3 of RFC 5657 currently reads: The first paragraph of Section 3 of [RFC5657] currently reads:
""" """
The format of implementation and interoperability reports MUST be The format of implementation and interoperability reports MUST be
ASCII text with line breaks for readability. As with Internet- ASCII text with line breaks for readability. As with Internet-
Drafts, no 8-bit characters are currently allowed. It is acceptable, Drafts, no 8-bit characters are currently allowed. It is acceptable,
but not necessary, for a report to be formatted as an Internet-Draft. but not necessary, for a report to be formatted as an Internet-Draft.
""" """
It should read: It should read:
""" """
skipping to change at page 3, line 50 skipping to change at page 3, line 53
""" """
It must be replaced by the phrase "I-Ds must be in UTF-8 [RFC3629].". 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 The remaining occurrences of "ASCII" in [IDGUIDE] are to be replaced
with "UTF-8". A reference to [RFC3629] must be added to with "UTF-8". A reference to [RFC3629] must be added to
Section 11 of [IDGUIDE]. The references to RFC 3979 and RFC 4879 must 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 be replaced with a reference to RFC 8179, as RFC 3979 and RFC 4879
are obsoleted by RFC 8179. are obsoleted by RFC 8179.
All other documents stating that RFCs and/or I-Ds must be in ASCII
and/or that 8-bit characters are not allowed must be updated to
replace references to ASCII with references to "UTF-8" or
"UTF-8 [RFC3629]" and to remove statements that no 8-bit characters
are allowed.
3. Security Considerations 3. Security Considerations
The security considerations of this document are only those of The security considerations of this document are only those
[RFC7997]. of [RFC7997].
4. IANA Considerations 4. IANA Considerations
[[RFC-Editor: please remove this section when publishing.]] [[RFC-Editor: please remove this section when publishing.]]
This document has no actions for IANA. This document has no actions for IANA.
5. Normative References 5. Normative References
[IDGUIDE] Housley, R., "Guidelines to Authors of Internet-Drafts", [IDGUIDE] Housley, R., "Guidelines to Authors of Internet-Drafts",
 End of changes. 11 change blocks. 
12 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/