Architectural Considerations on Application Features in the DNS
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 31
- 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.
- Publication Date
- 2013-10-01
- Status Note
- Informational
- DOI
10.17487/RFC6950- Link
- https://doi.org/10.17487/RFC6950
- Author(s)
- Jon PetersonOlaf KolkmanHannes TschofenigDr. Bernard D. Aboba
Latest version of IETF RFC 6950
Document Versions — IETF RFC 6950
-
▶ IETF RFC 6950 (2013-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- Barnes, R. and P. Saint-Andre, "High Assurance Re-Direction (HARD) Problem Statement", Work in Progress, July 2010. EXTERNAL
- Stastny, R., Conroy, L., and J. Reid, "IANA Registration for Enumservice UNUSED", Work in Progress, March 2008. EXTERNAL
- Faltstrom, P. and O. Kolkman, "The Uniform Resource Identifier (URI) DNS Resource Record", Work in Progress, July 2013. EXTERNAL
- Contavalli, C., van der Gaast, W., Leach, S., and D. Rodden, "Client IP information in DNS requests", Work in Progress, May 2010. EXTERNAL
- Lindsay, G., "DNSSEC and DNS Amplification Attacks", April 2012. EXTERNAL
- Kaplan, H., Walter, R., Gorman, P., and M. Maharishi, "EDNS Option Code for SIP and PSTN Source Reference Info", Work in Progress, October 2011. EXTERNAL
- Bellis, R., "IANA Registrations for the 'Send-N' Enumservice", Work in Progress, June 2008. EXTERNAL
- Creighton, T., Griffiths, C., Livingood, J., and R. Weber, "DNS Redirect Use by Service Providers", Work in Progress, October 2010. EXTERNAL
- IETF RFC 882 [Superseded*]
- IETF RFC 883 [Superseded*]
- IETF RFC 974 [Superseded*]
- IETF RFC 1034 [Active*]
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 1464 [Active*]
- IETF RFC 1530 [Active*]
- IETF RFC 1794 [Active*]
- IETF RFC 1918 [Active*]
- IETF RFC 1995 [Active*]
- IETF RFC 2052 [Superseded*]
- IETF RFC 2168 [Superseded*]
- IETF RFC 2181 [Active*]
- IETF RFC 2397 [Active*]
- IETF RFC 2671 [Superseded*]
- IETF RFC 2818 [Superseded*]
- IETF RFC 2826 [Active*]
- IETF RFC 2845 [Superseded*]
- IETF RFC 2915 [Superseded*]
- IETF RFC 2916 [Superseded*]
- IETF RFC 3007 [Active*]
- IETF RFC 3261 [Active*]
- IETF RFC 3263 [Active*]
- IETF RFC 3401 [Active*]
- IETF RFC 3402 [Active*]
- IETF RFC 3403 [Active*]
- IETF RFC 3596 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 4033 [Active*]
- RFC4367 — RFC4367 EXTERNAL
- IETF RFC 4398 [Active*]
- IETF RFC 4732 [Active*]
- IETF RFC 4985 [Active*]
- RFC5486 — RFC5486 EXTERNAL
- IETF RFC 5507 [Active*]
- IETF RFC 5922 [Active*]
- IETF RFC 6055 [Active*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 6269 [Active*]
- IETF RFC 6376 [Active*]
- IETF RFC 6394 [Active*]
- IETF RFC 6763 [Active*]
- IETF RFC 6891 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6950.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 6950, Architectural Considerations on Application Features in the DNS. Available at https://doi.org/10.17487/RFC6950
Snippet:
IETF RFC 6950, Architectural Considerations on Application Features in the DNS. Available at https://doi.org/10.17487/RFC6950
HTML (ISO 690 compliant)
Preview:
IETF RFC 6950, Architectural Considerations on Application Features in the DNS. Available at https://doi.org/10.17487/RFC6950
Snippet:
<span class="citation"><cite>IETF RFC 6950</cite>, Architectural Considerations on Application Features in the DNS. Available at <a href="https://doi.org/10.17487/RFC6950" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6950</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6950, Architectural Considerations on Application Features in the DNS
doi: 10.17487/RFC6950
url: https://doi.org/10.17487/RFC6950
doi: 10.17487/RFC6950
url: https://doi.org/10.17487/RFC6950
Snippet:
<li> <cite id="bib-rfc6950">IETF RFC 6950</cite>, Architectural Considerations on Application Features in the DNS <span class="doi">10.17487/RFC6950</span> </li>
Referenced By
- IETF RFC 7368 [Active*]
- IETF RFC 9210 [Active*]