| < draft-spacek-edns-camel-diet-00.txt | draft-spacek-edns-camel-diet-01.txt > | |||
|---|---|---|---|---|
| Network Working Group P. Spacek | Network Working Group P. Spacek | |||
| Internet-Draft CZ.NIC | Internet-Draft CZ.NIC | |||
| Intended status: Standards Track O. Gudmundsson | Intended status: Standards Track O. Gudmundsson | |||
| Expires: September 20, 2018 Cloudflare | Expires: November 30, 2018 Cloudflare | |||
| O. Sury | O. Sury | |||
| ISC | ISC | |||
| March 19, 2018 | May 29, 2018 | |||
| Minimal EDNS compliance requirements | Minimal EDNS compliance requirements | |||
| draft-spacek-edns-camel-diet-00 | draft-spacek-edns-camel-diet-01 | |||
| Abstract | Abstract | |||
| DNS responders must either follow RFC 6891 by implementing EDNS or | DNS responders must either follow RFC 6891 by fully implementing EDNS | |||
| respond with RCODE=FORMERR to queries containing OPT record. Non- | or at least respond to queries containing OPT record according to | |||
| compliant implementations are not worth talking to. | older specifications. Non-compliant implementations which do not | |||
| respond at all are not worth talking to. | ||||
| Status of This Memo | Status of This Memo | |||
| This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on September 20, 2018. | This Internet-Draft will expire on November 30, 2018. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 2, line 20 ¶ | skipping to change at page 2, line 20 ¶ | |||
| 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 | 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 2. The Protocol . . . . . . . . . . . . . . . . . . . . . . . . 2 | 2. The Protocol . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 | 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 | |||
| 4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 2 | 4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 2 | |||
| 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 | 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 6. Normative References . . . . . . . . . . . . . . . . . . . . 3 | 6. Normative References . . . . . . . . . . . . . . . . . . . . 3 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 1. Introduction | 1. Introduction | |||
| EDNS version 0 was standardized in 1999, but non-RFC 1035 compliant | Neither the original DNS standard RFC 1035 nor its extensions RFC | |||
| implementations still exist and cause lot of extra queries and | 2671 and RFC 6891 allow not to respond to a DNS query. Many years | |||
| complicated logic in recursive resolvers. RFC 6891 clearly states | later non-compliant implementations which drop queries still exist | |||
| that FORMERR is the only acceptable answer for implementations | and cause lot of extra queries, latency, and complicated logic in | |||
| without support for EDNS. The cost of supporting these non-compliant | recursive resolvers. The cost of supporting these non-compliant | |||
| implementations keeps increasing. | implementations keeps increasing. | |||
| 1.1. Terminology | 1.1. Terminology | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | |||
| document are to be interpreted as described in RFC 2119. | document are to be interpreted as described in RFC 2119. | |||
| 2. The Protocol | 2. The Protocol | |||
| No DNS response message to a repeated DNS query containing EDNS | No DNS response message to a repeated DNS query containing EDNS | |||
| extension means that the other side is not a DNS responder and the | extension implies that the other side is not a DNS responder. The | |||
| querier MUST NOT retry its query without EDNS. | querier MUST NOT retry its query without EDNS. | |||
| 3. Security Considerations | 3. Security Considerations | |||
| Instruction to follow EDNS standard does not change security | Instruction to follow EDNS standard does not change security | |||
| properties beyond what is written in RFC 6891. | properties beyond what is written in RFC 6891. | |||
| 4. Privacy Considerations | 4. Privacy Considerations | |||
| This has no effect on privacy of DNS. | This has no effect on privacy of DNS. | |||
| End of changes. 7 change blocks. | ||||
| 13 lines changed or deleted | 14 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||