The Use of Non-ASCII Characters in RFCs
RFC 7997
Revision differences
Document history
| Date | Rev. | By | Action |
|---|---|---|---|
|
2020-10-28
|
02 | (System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2020-03-30
|
02 | (System) | Received changes through RFC Editor sync (added Errata tag) |
|
2018-12-20
|
02 | (System) | Received changes through RFC Editor sync (changed abstract to 'In order to support the internationalization of protocols and a more diverse Internet community, the RFC … Received changes through RFC Editor sync (changed abstract to 'In order to support the internationalization of protocols and a more diverse Internet community, the RFC Series must evolve to allow for the use of non-ASCII characters in RFCs. While English remains the required language of the Series, the encoding of future RFCs will be in UTF-8, allowing for a broader range of characters than typically used in the English language. This document describes the RFC Editor requirements and gives guidance regarding the use of non-ASCII characters in RFCs. This document updates RFC 7322. Please view this document in PDF form to see the full text.') |
|
2016-12-16
|
02 | (System) | Received changes through RFC Editor sync (created alias RFC 7997, changed abstract to 'In order to support the internationalization of protocols and a more … Received changes through RFC Editor sync (created alias RFC 7997, changed abstract to 'In order to support the internationalization of protocols and a more diverse Internet community, the RFC Series must evolve to allow for the use of non-ASCII characters in RFCs. While English remains the required language of the Series, the encoding of future RFCs will be in UTF-8, allowing for a broader range of characters than typically used in the English language. This document describes the RFC Editor requirements and gives guidance regarding the use of non-ASCII characters in RFCs.', changed pages to 15, changed standardization level to Informational, changed state to RFC, added RFC published event at 2016-12-16, changed IAB state to Published RFC, created updates relation between draft-iab-rfc-nonascii and RFC 7322) |
|
2016-12-16
|
02 | (System) | RFC published |
|
2016-11-03
|
02 | (System) | RFC Editor state changed to AUTH48-DONE from AUTH48 |
|
2016-10-18
|
02 | (System) | RFC Editor state changed to AUTH48 from RFC-EDITOR |
|
2016-09-28
|
02 | (System) | RFC Editor state changed to RFC-EDITOR from REF |
|
2016-09-16
|
02 | (System) | RFC Editor state changed to REF from AUTH |
|
2016-09-15
|
02 | (System) | RFC Editor state changed to AUTH from EDIT |
|
2016-08-04
|
02 | (System) | IANA Action state changed to No IC from In Progress |
|
2016-08-04
|
02 | (System) | IANA Action state changed to In Progress |
|
2016-08-04
|
02 | (System) | RFC Editor state changed to EDIT |
|
2016-08-03
|
02 | Cindy Morgan | IAB state changed to Sent to the RFC Editor from Community Review |
|
2016-08-03
|
02 | Cindy Morgan | Sent request for publication to the RFC Editor |
|
2016-08-03
|
01 | Cindy Morgan | Changed consensus to Yes from Unknown |
|
2016-04-27
|
02 | Heather Flanagan | New version available: draft-iab-rfc-nonascii-02.txt |
|
2016-02-29
|
01 | Heather Flanagan | New version available: draft-iab-rfc-nonascii-01.txt |
|
2016-02-23
|
00 | Cindy Morgan | This document now replaces draft-flanagan-nonascii instead of None |
|
2016-02-11
|
00 | Cindy Morgan | IAB state changed to Community Review |
|
2016-02-11
|
00 | Cindy Morgan | Intended Status changed to Informational from None |
|
2016-01-13
|
00 | Naveen Khan | New revision available |