EDNS Version 1 (EDNS(1))
draft-andrews-edns1-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark P. Andrews | ||
| Last updated | 2014-10-17 (Latest revision 2014-04-15) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
It is impracticable to deploy new EDNS options, with EDNS version 0, on a global scale due to inconsistent server behaviour in deployed servers when a EDNS option is present in the query. Most existing EDNS option deployment has been small scale between essentially consenting implementations. When EDNS options were added to every outgoing recursive query made it became clear that trial and error to discover the level of EDNS version 0 support was not practicable. This document request that EDNS version 1 be assigned so that consistent well defined behaviour can be seen when a EDNS option is present.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)