| dprive | D. Migault |
| Internet-Draft | Ericsson |
| Intended status: Informational | March 18, 2020 |
| Expires: September 19, 2020 |
Domain Name System Uniform Resource Identifiers for DNS over HTTPS and DNS over TLS
draft-mglt-dprive-dns-uri-00
Today DNS resources may also be accessed using multiple transport which includes DNS over UDP/TCP port 53 [RFC1034],[RFC1035]. DNS over TLS [RFC7858] or DNS over HTTPS [RFC8484]. This document describes URIs that describes the DNS resource as well as indicate the transport to access the resource.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 19, 2020.
Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
[RFC4501] defines an URI [RFC7553] for DNS resources accessed but does not specify the transport used to access the DNS resource.
Today DNS resources may also be accessed using multiple transport layers which includes DNS over UDP/TCP port 53 [RFC1034],[RFC1035]. DNS over TLS [RFC7858] or DNS over HTTPS [RFC8484]. This document describes URIs that describes the DNS resource as well as indicate the transport to access the resource.
This section describes the URI template for the registration of the URI as described in [RFC7595] to describe DNS resources being accessed using DNS over TLS.
URL scheme name: "dns53".
URL scheme syntax: A DNS URI designates a DNS resource record set,
referenced by domain name, class, type, and, optionally, the
authority. The DNS URI follows the generic syntax from {{RFC3986}}
and is described using ABNF {{RFC5234}}. Strings are not case
sensitive, and free insertion of linear-white-space is not permitted.
dnsurl = "dns53:" [ "//" dnsauthority "/" ]
dnsname ["?" dnsquery]
dnsauthority = host [ ":" port ]
; See RFC 3986 for the
; definition of "host" and "port".
dnsname = *pchar
; See RFC 3986 for the
; definition of "pchar".
; The "dnsname" field may be a
; "relative" or "absolute" name,
; as per RFC 1034, section 3.1.
; Note further that an empty
; "dnsname" value is to be
; interpreted as the root itself.
; See below on relative dnsnames.
dnsquery = dnsqueryelement [";" dnsquery]
dnsqueryelement = ( "CLASS=" dnsclassval ) / ( "TYPE=" dnstypeval )
; Each clause MUST NOT be used more
; than once.
dnsclassval = 1*digit / "IN" / "CH" /
<Any IANA registered DNS class mnemonic>
dnstypeval = 1*digit / "A" / "NS" / "MD" /
<Any IANA registered DNS type mnemonic>
The DNS resource follows [RFC4501] but indicates the DNS resource MUST be accessed using UDP or TCP as described in [RFC1034] or [RFC1035].
This section describes the URI template for the registration of the URI as described in [RFC7595] to describe DNS resources being accessed using DNS over TLS.
URL scheme name: "dot".
URL scheme syntax: A DNS URI designates a DNS resource record set,
referenced by domain name, class, type, and, optionally, the
authority. The DNS URI follows the generic syntax from {{RFC3986}}
and is described using ABNF {{RFC5234}}. Strings are not case
sensitive, and free insertion of linear-white-space is not permitted.
dnsurl = "dot:" [ "//" dnsauthority "/" ]
dnsname ["?" dnsquery]
dnsauthority = host [ ":" port ]
; See RFC 3986 for the
; definition of "host" and "port".
dnsname = *pchar
; See RFC 3986 for the
; definition of "pchar".
; The "dnsname" field may be a
; "relative" or "absolute" name,
; as per RFC 1034, section 3.1.
; Note further that an empty
; "dnsname" value is to be
; interpreted as the root itself.
; See below on relative dnsnames.
dnsquery = dnsqueryelement [";" dnsquery]
dnsqueryelement = ( "CLASS=" dnsclassval ) / ( "TYPE=" dnstypeval )
; Each clause MUST NOT be used more
; than once.
dnsclassval = 1*digit / "IN" / "CH" /
<Any IANA registered DNS class mnemonic>
dnstypeval = 1*digit / "A" / "NS" / "MD" /
<Any IANA registered DNS type mnemonic>
The DNS resource follows [RFC4501] but indicates the DNS resource MUST be accessed using TCP over TLS as described in [RFC7858].
This section describes the URI template for the registration of the URI as described in [RFC8484] to describe DNS resources being accessed using DNS over HTTPS.
URL scheme name: "doh".
URL scheme syntax: A DNS URI designates a DNS resource record set,
referenced by domain name, class, type, and, optionally, the
authority. The DNS URI follows the generic syntax from {{RFC3986}}
and is described using ABNF {{RFC5234}}. Strings are not case
sensitive, and free insertion of linear-white-space is not permitted.
dnsurl = "doh:" [ "//" dnsauthority "/" ]
dnsname ["?" dnsquery]
dnsauthority = host [ ":" port ] [ "/" abs_path ]
; See RFC 3986 for the
; definition of "host" and "port"
; "abs_path"
dnsname = *pchar
; See RFC 3986 for the
; definition of "pchar".
; The "dnsname" field may be a
; "relative" or "absolute" name,
; as per RFC 1034, section 3.1.
; Note further that an empty
; "dnsname" value is to be
; interpreted as the root itself.
; See below on relative dnsnames.
dnsquery = dnsqueryelement [";" dnsquery]
dnsqueryelement = ( "CLASS=" dnsclassval ) / ( "TYPE=" dnstypeval )
; Each clause MUST NOT be used more
; than once.
dnsclassval = 1*digit / "IN" / "CH" /
<Any IANA registered DNS class mnemonic>
dnstypeval = 1*digit / "A" / "NS" / "MD" /
<Any IANA registered DNS type mnemonic>
The DNS resource follows [RFC4501] but indicates the DNS resource MUST be accessed using HTTPS as described in [RFC8484].
The URI template are largly inspired from [RFC4501].