rfc-8553
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.
updates
- rfc-2782 — A DNS RR for specifying the location of services (DNS SRV)
- rfc-3263 — Session Initiation Protocol (SIP): Locating SIP Servers
- rfc-3529 — Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP)
- rfc-3620 — The TUNNEL Profile
- rfc-3832 — Remote Service Discovery in the Service Location Protocol (SLP) via DNS SRV
- rfc-3887 — Message Tracking Query Protocol
- rfc-3958 — Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)
- rfc-4120 — The Kerberos Network Authentication Service (V5)
- rfc-4227 — Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
- rfc-4386 — Internet X.509 Public Key Infrastructure Repository Locator Service
- rfc-4387 — Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access via HTTP
- rfc-4976 — Relay Extensions for the Message Sessions Relay Protocol (MSRP)
- rfc-5026 — Mobile IPv6 Bootstrapping in Split Scenario
- rfc-5328 — A Uniform Resource Name (URN) Namespace for the Digital Video Broadcasting Project (DVB)
- rfc-5389 — Session Traversal Utilities for NAT (STUN)
- rfc-5415 — Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification
- rfc-5518 — Vouch By Reference
- rfc-5555 — Mobile IPv6 Support for Dual Stack Hosts and Routers
- rfc-5617 — DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)
- rfc-5679 — Locating IEEE 802.21 Mobility Services Using DNS
- rfc-5766 — Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
- rfc-5780 — NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN)
- rfc-5804 — A Protocol for Remotely Managing Sieve Scripts
- rfc-5864 — DNS SRV Resource Records for AFS
- rfc-5928 — Traversal Using Relays around NAT (TURN) Resolution Mechanism
- rfc-6120 — Extensible Messaging and Presence Protocol (XMPP): Core
- rfc-6186 — Use of SRV Records for Locating Email Submission/Access Services
- rfc-6376 — DomainKeys Identified Mail (DKIM) Signatures
- rfc-6733 — Diameter Base Protocol
- rfc-6763 — DNS-Based Service Discovery
- rfc-7208 — Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1
- rfc-7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC)
- rfc-8145 — Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)
also
- bcp-222