RFC 2671: Extension Mechanisms for DNS (EDNS0)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6891.
Current document in this lineage: RFC 6891 — Extension Mechanisms for DNS (EDNS(0))
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC2671
- Published
- August 1999
- Authors
- P. Vixie
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 6891
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2671 (1999)
- RFC 2673 (1999)
- RFC 6891 (2013) ✓
Read the full history of Extension Mechanisms for DNS (EDNS(0)) →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2672Non-Terminal DNS Name RedirectionObsoleted
August 1999
- RFC 2782A DNS RR for specifying the location of services (DNS SRV)Updated
February 2000
- RFC 3110RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)Updated
May 2001
- RFC 3123A DNS RR Type for Lists of Address Prefixes (APL RR)Current
June 2001
- RFC 3597Handling of Unknown DNS Resource Record (RR) TypesUpdated
September 2003
- RFC 7830The EDNS(0) Padding OptionCurrent
May 2016
- RFC 2915The Naming Authority Pointer (NAPTR) DNS Resource RecordObsoleted
September 2000
- RFC 3401Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDSCurrent
October 2002
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?