[Add] Protocol Action: 'DHCP and Router Advertisement Options for the Discovery of Network-designated Resolvers (DNR)' to Proposed Standard (draft-ietf-add-dnr-13.txt)

[The IESG <[e-mail]>]

The IESG has approved the following document:
- 'DHCP and Router Advertisement Options for the Discovery of Network-
   designated Resolvers (DNR)'
  (draft-ietf-add-dnr-13.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:
https://datatracker.ietf.org/doc/draft-ietf-add-dnr/





Technical Summary

   The document specifies new DHCP and IPv6 Router Advertisement options
   to discover encrypted DNS resolvers (e.g., DNS-over-HTTPS, DNS-over-
   TLS, DNS-over-QUIC).  Particularly, it allows a host to learn an
   authentication domain name together with a list of IP addresses and a
   set of service parameters to reach such encrypted DNS resolvers.

Working Group Summary

There has been discussion amongst a variety of individuals, with ten people
mentioned in the acknowledgements section of the document.  The shepherd believes that the
document represents the consensus view of the working group as a whole and that
it addresses a significant need that was identified during previous working
group discussions.


Document Quality

It has been reviewed by working group members, hence the number of iterations
of the draft to date.  A total of 128 mailing list posts reference the various
DDR drafts, complemented by closed issues and closed pull requests on GitHub. 
The authors have also given updates on progress during working group sessions
at IETF meetings to highlight the draft to a broader audience.

Looking outside of the ADD working group, there has been consultation with the
DHC working Group on the DHCP content in this draft.

The document has also received more reviews during the IETF Last Call.

Personnel

   Shepherd is Andrew Campling.
   Responsible AD is Éric Vyncke.

IESG Note

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
list.

        https://mailarchive.ietf.org/arch/msg/add/lB8c9COt5jyqgHhWjW9TFH_V4Nk/

IANA Note

Section 8 of the document contains the IANA considerations, identifying the
need for two option codes and one option type within existing registries. 
Specifically, IANA is requested to:

- assign a new DHCPv6 Option Code in the registry maintained in “DHCPv6 Option
Codes”
(https://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xhtml#dhcpv6-parameters-2)

- assign a new DHCP Option Code in the registry maintained in "BOOTP Vendor
Extensions and DHCP Options"
(https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml#options)

- assign a new IPv6 Neighbor Discovery Option type in the "IPv6 Neighbor
Discovery Option Formats" sub-registry under the "Internet Control Message
Protocol version 6 (ICMPv6) Parameters" registry
(http://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#icmpv6-parameters-5)



RFC Editor Note

Please assign consecutive RFC numbers to:

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

Thank you,
-éric