Service Binding Mapping for DNS Servers
draft-schwartz-svcb-dns-01
add B. Schwartz
Internet-Draft Google LLC
Intended status: Standards Track 10 August 2020
Expires: 11 February 2021
Service Binding Mapping for DNS Servers
draft-schwartz-svcb-dns-01
Abstract
The SVCB DNS record type expresses a bound collection of endpoint
metadata, for use when establishing a connection to a named service.
DNS itself can be such a service, when the server is identified by a
domain name. This document provides the SVCB mapping for named DNS
servers, allowing them to indicate support for new transport
protocols.
Discussion Venues
This note is to be removed before publishing as an RFC.
Discussion of this document takes place on the ADD Working Group
mailing list (add@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/browse/add/.
Source for this draft and an issue tracker can be found at
https://github.com/bemasc/svcb-dns.
Status of This Memo
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 11 February 2021.
Schwartz Expires 11 February 2021 [Page 1]
Internet-Draft SVCB for DNS August 2020
Copyright Notice
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3
3. Name form . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Applicable existing SvcParamKeys . . . . . . . . . . . . . . 3
4.1. port . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.2. alpn and no-default-alpn . . . . . . . . . . . . . . . . 3
4.3. Other applicable SvcParamKeys . . . . . . . . . . . . . . 4
5. New SvcParamKeys . . . . . . . . . . . . . . . . . . . . . . 4
5.1. dohpath . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 4
7. Relationship to DNS URIs . . . . . . . . . . . . . . . . . . 4
8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 5
9. Security Considerations . . . . . . . . . . . . . . . . . . . 5
9.1. Adversary on the query path . . . . . . . . . . . . . . . 5
9.2. Adversary on the transport path . . . . . . . . . . . . . 6
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
11.1. Normative References . . . . . . . . . . . . . . . . . . 7
11.2. Informative References . . . . . . . . . . . . . . . . . 7
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
The SVCB record type [SVCB] provides clients with information about
how to reach alternative endpoints for a service, which may have
improved performance or privacy properties. The service is
identified by a "scheme" indicating the service type, a hostname, and
optionally other information such as a port number. A DNS server is
often identified only by its IP address (e.g. in DHCP), but in some
contexts it can also be identified by a hostname (e.g. "NS" records,
manual resolver configuration).
Schwartz Expires 11 February 2021 [Page 2]
Internet-Draft SVCB for DNS August 2020
Use of the SVCB record type requires a mapping document for each
service type, indicating how a client for that service can interpret
Show full document text