Extension Mechanisms for DNS (EDNS0)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 7
- Abstract
- The Domain Name System's wire protocol includes a number of fixed fields whose range has been or soon will be exhausted and does not allow clients to advertise their capabilities to servers. This document describes backward compatible mechanisms for allowing the protocol to grow. [STANDARDS-TRACK]
- Publication Date
- 1999-08-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2671- Link
- https://doi.org/10.17487/RFC2671
- Author(s)
- Paul A. Vixie
- Keyword(s)
- EDNS0, DNS, Resource Records
Latest version of IETF RFC 2671
Document Versions — IETF RFC 2671
-
▶ IETF RFC 2671 (1999-08-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Superseded by:
- RFC6891 — RFC6891 EXTERNAL
Bibliographic Reference(s)
- IETF RFC 1035 [Active, Amended*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2671.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 2671, Extension Mechanisms for DNS (EDNS0). Available at https://doi.org/10.17487/RFC2671
Snippet:
IETF RFC 2671, Extension Mechanisms for DNS (EDNS0). Available at https://doi.org/10.17487/RFC2671
HTML (ISO 690 compliant)
Preview:
IETF RFC 2671, Extension Mechanisms for DNS (EDNS0). Available at https://doi.org/10.17487/RFC2671
Snippet:
<span class="citation"><cite>IETF RFC 2671</cite>, Extension Mechanisms for DNS (EDNS0). Available at <a href="https://doi.org/10.17487/RFC2671" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2671</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 2671, Extension Mechanisms for DNS (EDNS0)
doi: 10.17487/RFC2671
url: https://doi.org/10.17487/RFC2671
doi: 10.17487/RFC2671
url: https://doi.org/10.17487/RFC2671
Snippet:
<li> <cite id="bib-rfc2671">IETF RFC 2671</cite>, Extension Mechanisms for DNS (EDNS0) <span class="doi">10.17487/RFC2671</span> </li>
Referenced By
- IETF RFC 2672 [Superseded*]
- IETF RFC 2673 [Superseded*]
- IETF RFC 2929 [Superseded*]
- IETF RFC 3110 [Active*]
- IETF RFC 3225 [Active*]
- IETF RFC 3226 [Active*]
- IETF RFC 3467 [Active*]
- IETF RFC 3755 [Superseded*]
- IETF RFC 3833 [Active*]
- IETF RFC 4033 [Active*]
- IETF RFC 4035 [Active*]
- IETF RFC 4343 [Active*]
- IETF RFC 4472 [Active*]
- IETF RFC 5358 [Active*]
- IETF RFC 5891 [Active*]
- IETF RFC 5894 [Active*]
- IETF RFC 6709 [Active*]
- IETF RFC 6762 [Active*]