Extension Mechanisms for DNS (EDNS(0))
RFC 6891
also known as STD 75
Revision differences
Document history
Date | By | Action |
---|---|---|
2023-12-12
|
(System) | Imported membership of rfc6891 in std75 via sync to the rfc-index |
2023-12-12
|
(System) | No history of STD75 is currently available in the datatracker before this point |
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'The Domain Name System's wire protocol includes a number of fixed fields whose range has been … Received changes through RFC Editor sync (changed abstract to '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 requestors to advertise their capabilities to responders. This document describes backward-compatible mechanisms for allowing the protocol to grow. This document updates the Extension Mechanisms for DNS (EDNS(0)) specification (and obsoletes RFC 2671) based on feedback from deployment experience in several implementations. It also obsoletes RFC 2673 ("Binary Labels in the Domain Name System") and adds considerations on the use of extended labels in the DNS.') |
2016-11-30
|
Martin Stiemerling | Closed request for Early review by TSVDIR with state 'Unknown' |
2015-10-14
|
(System) | Notify list changed from dnsext-chairs@ietf.org, draft-ietf-dnsext-rfc2671bis-edns0@ietf.org to (None) |
2013-05-02
|
(System) | IANA registries were updated to include RFC6891 |
2013-04-16
|
(System) | RFC published |