idnits 2.17.1 draft-hoffman-dns-terminology-ter-01.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 (April 29, 2019) is 1796 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 114 looks like a reference -- Missing reference section? 'RFC7858' on line 105 looks like a reference -- Missing reference section? 'RFC8484' on line 110 looks like a reference -- Missing reference section? 'RFC1035' on line 101 looks like a reference Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 6 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) April 29, 2019 5 Intended status: Standards Track 6 Expires: October 31, 2019 8 Terminology for DNS Transports and Location 9 draft-hoffman-dns-terminology-ter-01 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 [[ This is an early attempt at these terms. They will probably be 19 improved over time. ]] 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on October 31, 2019. 38 Copyright Notice 40 Copyright (c) 2019 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. New Terms and Abbreviations . . . . . . . . . . . . . . . . . 2 56 2. Normative References . . . . . . . . . . . . . . . . . . . . 3 57 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 60 1. New Terms and Abbreviations 62 The following terms and abbreviations are added to Section 6 of 63 [RFC8499]. 65 DNS-over-TLS (DoT): DNS over TLS as defined in [RFC7858] and its 66 successors. 68 DNS-over-HTTPS (DoH): DNS over HTTPS as defined in [RFC8484] and its 69 successors. 71 Do53: DNS over UDP or TCP as defined in [RFC1035] and its 72 successors. Do53 applies to DNS communication between stub 73 resolvers and recursive resolvers, and between recursive resolvers 74 and authoritative servers. 76 Recursive DoT (RDoT): RDoT specifically means DNS-over-TLS for 77 transport between stub resolvers and recursive resolvers. This 78 term is necessary because it is expected that DNS-over-TLS will 79 later be defined as a transport between recursive resolvers and 80 authoritative servers, 82 Authoritative DoT (ADoT): If DNS-over-TLS is later defined as the 83 transport between recursive resolvers and authoritative servers, 84 ADoT specifically means DNS-over-TLS for transport between 85 recursive resolvers and authoritative servers. 87 Applications Doing DNS (ADD): Applications that act as stub 88 resolvers. This is in contrast to the way that applications 89 traditionally have gotten DNS information, which is to use system 90 calls to the operating system on the computer, and have the 91 operating system act as the stub resolver. "Applications Doing 92 DNS" is not limited to particular transports: it applies equally 93 to DNS-over-TLS, DNS-over-HTTPS, Do53, and future DNS transports. 95 ( Temporary note, to be removed before publication as an RFC: 96 there is a mailing list discussing Applications Doing DNS at 97 https://www.ietf.org/mailman/listinfo/add ) 99 2. Normative References 101 [RFC1035] Mockapetris, P., "Domain names - implementation and 102 specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, 103 November 1987, . 105 [RFC7858] Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D., 106 and P. Hoffman, "Specification for DNS over Transport 107 Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, May 108 2016, . 110 [RFC8484] Hoffman, P. and P. McManus, "DNS Queries over HTTPS 111 (DoH)", RFC 8484, DOI 10.17487/RFC8484, October 2018, 112 . 114 [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS 115 Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, 116 January 2019, . 118 Acknowledgments 120 Sara Dickinson contributed ideas before the first draft was 121 published. Warren Kumari contributed the idea for "Applications 122 Doing DNS" as a term. Many people contributed the idea that it is 123 better to define terms rather than just acronyms. 125 Author's Address 127 Paul Hoffman 128 ICANN 130 Email: paul.hoffman@icann.org