Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves
RFC 8552
part of BCP 222
Revision differences
Document history
Date | By | Action |
---|---|---|
2023-12-12
|
(System) | Imported membership of rfc8552 in bcp222 via sync to the rfc-index |
2023-12-12
|
(System) | No history of BCP222 is currently available in the datatracker before this point |
2021-04-20
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2019-08-19
|
Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events' |
2019-08-19
|
Gunter Van de Velde | Assignment of request for Last Call review by OPSDIR to Fred Baker was marked no-response |
2019-03-22
|
(System) | IANA registries were updated to include RFC8552 |
2019-03-22
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
2019-03-20
|
(System) | Received changes through RFC Editor sync (created alias RFC 8552, changed title to 'Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute … Received changes through RFC Editor sync (created alias RFC 8552, changed title to 'Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves', changed abstract to 'Formally, any DNS Resource Record (RR) may occur under any domain name. However, some services use an operational convention for defining specific interpretations of an RRset by locating the records in a DNS branch under the parent domain to which the RRset actually applies. The top of this subordinate branch is defined by a naming convention that uses a reserved node name, which begins with the underscore character (e.g., "_name"). The underscored naming construct defines a semantic scope for DNS record types that are associated with the parent domain above the underscored branch. This specification explores the nature of this DNS usage and defines the "Underscored and Globally Scoped DNS Node Names" registry with IANA. The purpose of this registry is to avoid collisions resulting from the use of the same underscored name for different services.', changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2019-03-20, changed IESG state to RFC Published, created alias BCP 222) |
2019-03-20
|
(System) | RFC published |