CurrentBEST CURRENT PRACTICEIETF streamBCP222

RFC 8553: DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names

In plain English — editorial summary, not part of the 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.

Document record

Document ID
RFC8553
Published
March 2019
Authors
D. Crocker
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
ops
Pages
15
Also known as
BCP222

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8553-dns-attrleaf-changes-fixing-specifications-that-use-underscored-node-names