MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other modern Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
IETF · RFCОфициальная английская аннотация
MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other modern Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
{
"id": "RFC2278",
"number": 2278,
"title_en": "IANA Charset Registration Procedures",
"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": "MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other modern Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.",
"authors": [
"N. Freed",
"J. Postel"
],
"organizations": [],
"publication_date": "1998-01-01",
"current_status": "INFORMATIONAL",
"current_status_ru": "Информационный",
"publication_status": "BEST CURRENT PRACTICE",
"publication_status_ru": "Лучшая современная практика",
"lifecycle": "superseded",
"lifecycle_ru": "Заменён",
"stream": "Legacy",
"stream_ru": "Исторический поток",
"area": "",
"area_ru": "",
"working_group": "",
"source_draft": "draft-freed-charset-reg-03",
"page_count": 10,
"doi": "10.17487/RFC2278",
"keywords": [
"character",
"set",
"mime",
"multipurpose",
"internet",
"mail",
"extensions"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [
"RFC2978"
],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc2278/",
"html": "https://www.rfc-editor.org/rfc/rfc2278.html",
"txt": "https://www.rfc-editor.org/rfc/rfc2278.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc2278/"
}
}