draft-ietf-dnsop-terminology-ter-00.txt   draft-ietf-dnsop-terminology-ter-01.txt 
Network Working Group P. Hoffman Network Working Group P. Hoffman
Internet-Draft ICANN Internet-Draft ICANN
Updates: RFC 8499 (if approved) August 15, 2019 Updates: RFC 8499 (if approved) February 11, 2020
Intended status: Standards Track Intended status: Standards Track
Expires: February 16, 2020 Expires: August 14, 2020
Terminology for DNS Transports and Location Terminology for DNS Transports and Location
draft-ietf-dnsop-terminology-ter-00 draft-ietf-dnsop-terminology-ter-01
Abstract Abstract
This document adds terms and abbreviations to "DNS Terminology" (RFC This document adds terms and abbreviations to "DNS Terminology" (RFC
8499) that relate to DNS running over various transports, as well as 8499) that relate to DNS running over various transports, as well as
terms and abbreviations for DNS resolution at traditional and non- terms and abbreviations for DNS resolution at traditional and non-
traditional locations. traditional locations.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 February 16, 2020. This Internet-Draft will expire on August 14, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 26 skipping to change at page 2, line 26
DNS-over-TLS (DoT): DNS over TLS as defined in [RFC7858] and its DNS-over-TLS (DoT): DNS over TLS as defined in [RFC7858] and its
successors. successors.
DNS-over-HTTPS (DoH): DNS over HTTPS as defined in [RFC8484] and its DNS-over-HTTPS (DoH): DNS over HTTPS as defined in [RFC8484] and its
successors. successors.
Classic DNS: DNS over UDP or TCP as defined in [RFC1035] and its Classic DNS: DNS over UDP or TCP as defined in [RFC1035] and its
successors. Classic DNS applies to DNS communication between stub successors. Classic DNS applies to DNS communication between stub
resolvers and recursive resolvers, and between recursive resolvers resolvers and recursive resolvers, and between recursive resolvers
and authoritative servers.' Classic DNS is not encrypted. and authoritative servers. This has sometimes been called "Do53".
Classic DNS is not encrypted.
Recursive DoT (RDoT): RDoT specifically means DNS-over-TLS for Recursive DoT (RDoT): RDoT specifically means DNS-over-TLS for
transport between a stub resolver and a recursive resolver, or transport between a stub resolver and a recursive resolver, or
between a recursive resolver and another recursive resolver. This between a recursive resolver and another recursive resolver. This
term is necessary because it is expected that DNS-over-TLS will term is necessary because it is expected that DNS-over-TLS will
later be defined as a transport between recursive resolvers and later be defined as a transport between recursive resolvers and
authoritative servers, authoritative servers,
Authoritative DoT (ADoT): If DNS-over-TLS is later defined as the Authoritative DoT (ADoT): If DNS-over-TLS is later defined as the
transport between recursive resolvers and authoritative servers, transport between recursive resolvers and authoritative servers,
 End of changes. 6 change blocks. 
6 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/