RFC 6950

Architectural Considerations on Application Features in the DNS, October 2013

Canonical URL:
https://www.rfc-editor.org/rfc/rfc6950.txt
File formats:
Plain TextPDF
Status:
INFORMATIONAL
Authors:
J. Peterson
O. Kolkman
H. Tschofenig
B. Aboba
Stream:
IAB

Cite this RFC: TXT  |  XML

DOI:  http://dx.doi.org/10.17487/RFC6950

Discuss this RFC: Send questions or comments to iab@iab.org

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader



Search RFCs
Advanced Search
×