RFC8553 · DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names
DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names
Using an underscore for a prefix creates a space for constrained interoperation of resource records. Original uses of an underscore character as a domain node name prefix were specified without the benefit of an IANA registry. This produced an entirely uncoordinated set of name-creation activities, all drawing from the same namespace. A registry for these names has now been defined by RFC 8552. However, the existing specifications that use underscored naming need to be modified in order to be in line with the new registry. This document specifies those changes. The changes preserve existing software and operational practice, while adapting the specifications for those practices to the newer underscore registry model.
IETF · RFCОфициальная английская аннотация
Using an underscore for a prefix creates a space for constrained interoperation of resource records. Original uses of an underscore character as a domain node name prefix were specified without the benefit of an IANA registry. This produced an entirely uncoordinated set of name-creation activities, all drawing from the same namespace. A registry for these names has now been defined by RFC 8552. However, the existing specifications that use underscored naming need to be modified in order to be in line with the new registry. This document specifies those changes. The changes preserve existing software and operational practice, while adapting the specifications for those practices to the newer underscore registry model.
{
"id": "RFC8553",
"number": 8553,
"title_en": "DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names",
"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": "Using an underscore for a prefix creates a space for constrained interoperation of resource records. Original uses of an underscore character as a domain node name prefix were specified without the benefit of an IANA registry. This produced an entirely uncoordinated set of name-creation activities, all drawing from the same namespace. A registry for these names has now been defined by RFC 8552. However, the existing specifications that use underscored naming need to be modified in order to be in line with the new registry. This document specifies those changes. The changes preserve existing software and operational practice, while adapting the specifications for those practices to the newer underscore registry model.",
"authors": [
"D. Crocker"
],
"organizations": [],
"publication_date": "2019-03-01",
"current_status": "BEST CURRENT PRACTICE",
"current_status_ru": "Лучшая современная практика",
"publication_status": "BEST CURRENT PRACTICE",
"publication_status_ru": "Лучшая современная практика",
"lifecycle": "active",
"lifecycle_ru": "Действующий",
"stream": "IETF",
"stream_ru": "IETF",
"area": "ops",
"area_ru": "Эксплуатация и управление",
"working_group": "dnsop",
"source_draft": "draft-ietf-dnsop-attrleaf-fix-07",
"page_count": 15,
"doi": "10.17487/RFC8553",
"keywords": [
"DNS",
"Domain Name System"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [
"RFC2782",
"RFC3263",
"RFC3529",
"RFC3620",
"RFC3832",
"RFC3887",
"RFC3958",
"RFC4120",
"RFC4227",
"RFC4386",
"RFC4387",
"RFC4976",
"RFC5026",
"RFC5328",
"RFC5389",
"RFC5415",
"RFC5518",
"RFC5555",
"RFC5617",
"RFC5679",
"RFC5766",
"RFC5780",
"RFC5804",
"RFC5864",
"RFC5928",
"RFC6120",
"RFC6186",
"RFC6376",
"RFC6733",
"RFC6763",
"RFC7208",
"RFC7489",
"RFC8145"
],
"updated_by": [],
"is_also": [
"BCP222"
],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc8553/",
"html": "https://www.rfc-editor.org/rfc/rfc8553.html",
"txt": "https://www.rfc-editor.org/rfc/rfc8553.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc8553/"
}
}