A Proposed Enhancement to the EDNS0 Version Mechanism
draft-ietf-dnsext-edns0dot5-02

Document Type Expired Internet-Draft (dnsext WG)
Last updated 2000-11-17
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-dnsext-edns0dot5-02.txt

Abstract

EDNS0 [EDNS0] specifies a general framework for extending the packet format used by the Domain Name System protocols. The framework includes a simple version numbering scheme to allow the parties in a DNS protocol exchange to determine which extension features the other party understands. While having the advantage of simplicity, the version numbering scheme as specified has drawbacks: - It provides no way to deprecate a protocol feature; - It provides no way to deploy experimental protocol features. This note proposes to replace the monolithic version numbering mechanism with a mechanism for listing an explicit set of protocol features that a particular implementation supports. We retain version numbering as a way of abbreviating the feature sets that we expect to see in common use.

Authors

Rob Austein (sra@hactrn.net)
Harald Alvestrand (harald@alvestrand.no)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)