DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names

Metadata

Publisher: IETF
Doc Type: Best Practice
Pages: 15
Abstract: 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.
Publication Date: 2019-03-01
Status Note: Best Current Practice
DOI: 10.17487/RFC8553
Link: https://doi.org/10.17487/RFC8553
Author(s): Dave Crocker
Keyword(s): DNS

Latest version of IETF RFC 8553

Document Versions — IETF RFC 8553

▶ IETF RFC 8553 (2019-03-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 6117 [Active*]
IETF RFC 6335 [Active*]
RFC7553 — RFC7553 EXTERNAL
RFC8145 — RFC8145 EXTERNAL
IETF RFC 8174 [Active*]
RFC8552 — RFC8552 EXTERNAL

Bibliographic Reference(s)

IANA, "Protocol Registries", < https://www.iana.org/protocols >. EXTERNAL
IETF RFC 1035 [Active, Amended*]
IETF RFC 2782 [Active*]
IETF RFC 3263 [Active*]
IETF RFC 3529 [Active*]
IETF RFC 3620 [Active*]
IETF RFC 3832 [Active*]
IETF RFC 3887 [Active*]
IETF RFC 3958 [Active*]
IETF RFC 4120 [Active*]
IETF RFC 4227 [Active*]
IETF RFC 4386 [Active*]
IETF RFC 4387 [Active*]
IETF RFC 4976 [Active*]
RFC5026 — RFC5026 EXTERNAL
RFC5328 — RFC5328 EXTERNAL
IETF RFC 5389 [Superseded*]
IETF RFC 5415 [Active*]
RFC5518 — RFC5518 EXTERNAL
RFC5555 — RFC5555 EXTERNAL
IETF RFC 5617 [Active*]
RFC5679 — RFC5679 EXTERNAL
IETF RFC 5766 [Superseded*]
RFC5780 — RFC5780 EXTERNAL
RFC5804 — RFC5804 EXTERNAL
IETF RFC 5864 [Active*]
RFC5928 — RFC5928 EXTERNAL
IETF RFC 6120 [Active*]
IETF RFC 6186 [Active*]
IETF RFC 6376 [Active*]
IETF RFC 6763 [Active*]
IETF RFC 7208 [Active*]
RFC7489 — RFC7489 EXTERNAL

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC8553.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 8553, DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names. Available at https://doi.org/10.17487/RFC8553

Snippet:

IETF RFC 8553, DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names. Available at https://doi.org/10.17487/RFC8553

HTML (ISO 690 compliant)

Preview:

IETF RFC 8553, DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names. Available at https://doi.org/10.17487/RFC8553

Snippet:

<span class="citation"><cite>IETF RFC 8553</cite>, DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names. Available at <a href="https://doi.org/10.17487/RFC8553" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8553</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 8553, DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names
doi: 10.17487/RFC8553
url: https://doi.org/10.17487/RFC8553

Snippet:

<li>
<cite id="bib-rfc8553">IETF RFC 8553</cite>, DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names
<span class="doi">10.17487/RFC8553</span>
</li>