Architectural Considerations on Application Features in the DNS
RFC 6950, “Architectural Considerations on Application Features in the DNS”, is an Informational document published in October 2013 by J. Peterson, O. Kolkman, H. Tschofenig, B. Aboba. The canonical text is published by the RFC Editor.
Abstract
A number of Internet applications rely on the Domain Name System (DNS) to support their operations. Many applications use the DNS to locate services for a domain; some, for example, transform identifiers other than domain names into formats that the DNS can process, and then fetch application data or service location data from the DNS. Proposals incorporating sophisticated application behavior using DNS as a substrate have raised questions about the role of the DNS as an application platform. This document explores the architectural consequences of using the DNS to implement certain application features, and it provides guidance to future application designers as to the limitations of the DNS as a substrate and the situations in which alternative designs should be considered.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6950 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6949 RFC Series Format Requirements and Future Development
- RFC 6951 UDP Encapsulation of Stream Control Transmission Protocol Packets for End-Host to End-Host Communication
- RFC 6948 Some Measurements on World IPv6 Day from an End-User Perspective
- RFC 6952 Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols Design Guide
- RFC 6947 The Session Description Protocol Alternate Connectivity Attribute
- RFC 6953 Protocol to Access White-Space Databases: Use Cases and Requirements
- RFC 6946 Processing of IPv6 "Atomic" Fragments
- RFC 6954 Using the Elliptic Curve Cryptography Brainpool Curves for the Internet Key Exchange Protocol Version 2