idnits 2.17.1 draft-ietf-dnsop-terminology-ter-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. -- The draft header indicates that this document updates RFC8499, but the abstract doesn't seem to directly say this. It does mention RFC8499 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 03, 2020) is 1362 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'RFC8499' on line 109 looks like a reference -- Missing reference section? 'RFC7858' on line 100 looks like a reference -- Missing reference section? 'RFC8484' on line 105 looks like a reference -- Missing reference section? 'I-D.ietf-dprive-dnsoquic' on line 91 looks like a reference -- Missing reference section? 'RFC1035' on line 96 looks like a reference Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Hoffman 3 Internet-Draft ICANN 4 Updates: RFC 8499 (if approved) August 03, 2020 5 Intended status: Standards Track 6 Expires: February 4, 2021 8 Terminology for DNS Transports and Location 9 draft-ietf-dnsop-terminology-ter-02 11 Abstract 13 This document adds terms and abbreviations to "DNS Terminology" (RFC 14 8499) that relate to DNS running over various transports, as well as 15 terms and abbreviations for DNS resolution at traditional and non- 16 traditional locations. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on February 4, 2021. 35 Copyright Notice 37 Copyright (c) 2020 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. New Terms and Abbreviations . . . . . . . . . . . . . . . . . 2 53 2. Normative References . . . . . . . . . . . . . . . . . . . . 2 54 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 57 1. New Terms and Abbreviations 59 The following terms and abbreviations are added to Section 6 of 60 [RFC8499]. 62 DNS-over-TLS (DoT): DNS over TLS as defined in [RFC7858] and its 63 successors. 65 DNS-over-HTTPS (DoH): DNS over HTTPS as defined in [RFC8484] and its 66 successors. 68 DNS-over-QUIC (DoQ): DNS over QUIC as defined in 69 [I-D.ietf-dprive-dnsoquic] 71 Classic DNS: DNS over UDP or TCP as defined in [RFC1035] and its 72 successors. Classic DNS applies to DNS communication between stub 73 resolvers and recursive resolvers, and between recursive resolvers 74 and authoritative servers. This has sometimes been called "Do53". 75 Classic DNS is not encrypted. 77 Recursive DoT (RDoT): RDoT specifically means DNS-over-TLS for 78 transport between a stub resolver and a recursive resolver, or 79 between a recursive resolver and another recursive resolver. This 80 term is necessary because it is expected that DNS-over-TLS will 81 later be defined as a transport between recursive resolvers and 82 authoritative servers, 84 Authoritative DoT (ADoT): If DNS-over-TLS is later defined as a 85 transport between recursive resolvers and authoritative servers, 86 ADoT specifically means DNS-over-TLS for transport between 87 recursive resolvers and authoritative servers. 89 2. Normative References 91 [I-D.ietf-dprive-dnsoquic] 92 Huitema, C., Mankin, A., and S. Dickinson, "Specification 93 of DNS over Dedicated QUIC Connections", draft-ietf- 94 dprive-dnsoquic-00 (work in progress), April 2020. 96 [RFC1035] Mockapetris, P., "Domain names - implementation and 97 specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, 98 November 1987, . 100 [RFC7858] Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D., 101 and P. Hoffman, "Specification for DNS over Transport 102 Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, May 103 2016, . 105 [RFC8484] Hoffman, P. and P. McManus, "DNS Queries over HTTPS 106 (DoH)", RFC 8484, DOI 10.17487/RFC8484, October 2018, 107 . 109 [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS 110 Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, 111 January 2019, . 113 Acknowledgments 115 Sara Dickinson contributed ideas before the first draft was 116 published. Warren Kumari contributed the idea for "Applications 117 Doing DNS" as a term. Many people contributed the idea that it is 118 better to define terms rather than just acronyms. 120 Author's Address 122 Paul Hoffman 123 ICANN 125 Email: paul.hoffman@icann.org