Minimal EDNS compliance requirements
draft-spacek-edns-camel-diet-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Petr Špaček , Ólafur Guðmundsson , Ondřej Surý | ||
| Last updated | 2018-11-30 (latest revision 2018-05-29) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-spacek-edns-camel-diet-01.txt
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
(petr.spacek@nic.cz)
Ólafur Guðmundsson
(olafur+ietf@cloudflare.com)
Ondřej Surý
(ondrej@isc.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)