Skip to main content

Service Binding Mapping for DNS Servers

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: Andrew.Campling@419.Consulting, The IESG <>,,,,,
Subject: Protocol Action: 'Service Binding Mapping for DNS Servers' to Proposed Standard (draft-ietf-add-svcb-dns-08.txt)

The IESG has approved the following document:
- 'Service Binding Mapping for DNS Servers'
  (draft-ietf-add-svcb-dns-08.txt) as Proposed Standard

This document is the product of the Adaptive DNS Discovery Working Group.

The IESG contact persons are Erik Kline and Éric Vyncke.

A URL of this Internet-Draft is:

Ballot Text

Technical Summary

   The SVCB DNS resource 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
   encrypted transport protocols.

Working Group Summary

There has been extensive discussion amongst a variety of individuals.  The shepherd and the responsible AD believe that the document represents the consensus view of the working group as a whole.

Document Quality

The document was written to harmonise several different drafts that all
proposed to use the SVCB format to convey information about a DNS server that
supports encrypted transport.  This document specifies a minimal SVCB mapping
for DNS URIs without addressing any particular use case.  Draft-ietf-add-ddr
and draft-ietf-add-dnr have both followed the approach outlined in this

The document has had detailed reviews by working group members, with replies to
the mailing list by the author indicating how the comments have been addressed.
 All issues and pull requests on GitHub are closed.


The doc shepherd is Andrew Campling.
The responsible AD is Éric Vyncke.


There was a very vague IPR disclosure by Verisign shortly after the ADD working
group was formed that may pertain in some way to ADD.  It involved unpublished
filings and did not include any detail other than that Verisign had filed a
patent with the USPTO.

For reference, the following link is to the relevant posts on the ADD mailing


 Section 9 of the document contains the IANA considerations, identifying the
need for additions to the SVCB Service Parameters and DNS Underscore Global
Scoped Entry Registries.  Specifically, IANA is requested to add the following

- SVCB Service Parameters Registry
Number – 7; Name – dohpath; Meaning - DNS over HTTPS path template

- DNS Underscore Global Scoped Entry Registry
RR Type – SVCB; _Node Name - _dns; Meaning – DNS SVCB Info

RFC Editor Note

RFC Editor Note

Please assign consecutive RFC numbers to:

* draft-ietf-add-svcb-dns
* draft-ietf-add-ddr
* draft-ietf-add-dnr

Thank you,