[Add] Fwd: New Version Notification for draft-pauly-add-resolver-discovery-01.txt

[Tommy Pauly <[e-mail]>]

Hello ADD,

We’ve published a revision of draft-pauly-add-resolver-discovery. This revision incorporates various pieces of feedback we’ve received. Specifically, the changes include:

- Aligning with the current version of SCVB/HTTPS records
- Improvements to how to upgrade a local resolver to a DoH resolver 
- Clarification of expiration and TTL of resolver designation
- An appendix describing the choice of using SVCB records for designation, as opposed to other record types or approaches that only provide hints in HTTP responses

We can share details on these changes at the upcoming IETF 108 meeting. We’d like to also start considering how this work can progress as an item for the working group.

Best,
Tommy


> Begin forwarded message:
> 
> From: [e-mail]
> Subject: New Version Notification for draft-pauly-add-resolver-discovery-01.txt
> Date: July 13, 2020 at 1:21:32 PM PDT
> To: "Christopher A. Wood" <[e-mail]>, Christopher Wood <[e-mail]>, Tommy Jensen <[e-mail]>, Tommy Pauly <[e-mail]>, Eric Kinnear <[e-mail]>, Patrick McManus <[e-mail]>
> 
> 
> A new version of I-D, draft-pauly-add-resolver-discovery-01.txt
> has been successfully submitted by Tommy Pauly and posted to the
> IETF repository.
> 
> Name:		draft-pauly-add-resolver-discovery
> Revision:	01
> Title:		Adaptive DNS Resolver Discovery
> Document date:	2020-07-13
> Group:		Individual Submission
> Pages:		17
> URL:            https://www.ietf.org/internet-drafts/draft-pauly-add-resolver-discovery-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-pauly-add-resolver-discovery/
> Htmlized:       https://tools.ietf.org/html/draft-pauly-add-resolver-discovery-01
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-pauly-add-resolver-discovery
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-pauly-add-resolver-discovery-01
> 
> Abstract:
>   This document defines a method for dynamically discovering resolvers
>   that support encrypted transports, and introduces the concept of
>   designating a resolver to be used for a subset of client queries
>   based on domain.  This method is intended to work both for locally-
>   hosted resolvers and resolvers accessible over the broader Internet.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
>