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.
IETF · RFCОфициальная английская аннотация
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.
{
"id": "RFC7997",
"number": 7997,
"title_en": "The Use of Non-ASCII Characters in RFCs",
"title_ru": "",
"summary_ru": "",
"purpose_ru": "",
"use_ru": "",
"full_translation_path": "",
"full_translation_checked_at": "",
"full_translation_source_sha256": "",
"architect_note_ru": "",
"topics_ru": [],
"translation_state": "not_prepared",
"verification_level": "not_prepared",
"verification_level_ru": "Русская выжимка не подготовлена",
"verification_note_ru": "",
"abstract_en": "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.",
"authors": [
"H. Flanagan"
],
"organizations": [],
"publication_date": "2016-12-01",
"current_status": "INFORMATIONAL",
"current_status_ru": "Информационный",
"publication_status": "INFORMATIONAL",
"publication_status_ru": "Информационный",
"lifecycle": "informational",
"lifecycle_ru": "Справочный",
"stream": "IAB",
"stream_ru": "Совет по архитектуре Интернета (IAB)",
"area": "",
"area_ru": "",
"working_group": "",
"source_draft": "draft-iab-rfc-nonascii-02",
"page_count": 15,
"doi": "10.17487/RFC7997",
"keywords": [
"RFC Series",
"UTF-8",
"ASCII",
"format",
"non-ASCII",
"v3",
"xml2rfcv3"
],
"formats": [
"TXT",
"PDF",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [
"RFC7322"
],
"updated_by": [
"RFC9920"
],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc7997/",
"html": "https://www.rfc-editor.org/rfc/rfc7997.html",
"txt": "https://www.rfc-editor.org/rfc/rfc7997.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc7997/"
}
}