RFC 5507: Design Choices When Expanding the DNS
In plain English — editorial summary, not part of the RFC
This note discusses how to extend the DNS with new data for a new application. DNS extension discussions too often focus on reuse of the TXT Resource Record Type. This document lists different mechanisms to extend the DNS, and concludes that the use of a new DNS Resource Record Type is the best solution. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5507
- Published
- April 2009
- Authors
- IAB; P. Faltstrom; R. Austein; P. Koch
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4367What's in a Name: False Assumptions about DNS NamesCurrent
February 2006
- RFC 5205Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionsObsoleted
April 2008
- RFC 51586to4 Reverse DNS Delegation SpecificationUpdated
March 2008
- RFC 5155DNS Security (DNSSEC) Hashed Authenticated Denial of ExistenceUpdated
March 2008
- RFC 5864DNS SRV Resource Records for AFSUpdated
April 2010
- RFC 6117IANA Registration of Enumservices: Guide, Template, and IANA ConsiderationsCurrent
March 2011
- RFC 6118Update of Legacy IANA Registrations of EnumservicesCurrent
March 2011
- RFC 6168Requirements for Management of Name Servers for the DNSCurrent
May 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?