Minimal EDNS compliance requirements
draft-spacek-edns-camel-diet-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Petr Špaček , Ólafur Guðmundsson , Ondřej Surý | ||
| Last updated | 2018-11-30 (Latest revision 2018-05-29) | ||
| 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
DNS responders must either follow RFC 6891 by fully implementing EDNS or at least respond to queries containing OPT record according to older specifications. Non-compliant implementations which do not respond at all are not worth talking to.
Authors
Petr Špaček
Ólafur Guðmundsson
Ondřej Surý
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)