Hello DPRIVE!

in the last two draft revisions of our protocol for unauthenticated
encryption from resolvers to authoritatives, we adopted the SVCB
discovery mechanism from draft-rescorla-dprive-adox-latest-00. This
means that the two documents overlap somewhat, and there would be
effort needed to keep the mechanisms in sync.

To avoid that problem, instead we present here a separate document that
contains the parts that the two protocols have in common. Our draft is
adopted; we understand the authors of the authenticated draft intend to
ask for adoption soon, as well. If the WG adopts this separate
document, we will not have to keep the discovery bits in sync between
the two, and we can hammer out the details of discovery once, in a
single place.

We imagine this would be much more efficient.

- Paul & Peter


-------- Forwarded Message --------
From: internet-dra...@ietf.org
To: Paul Hoffman <paul.hoff...@icann.org>, Peter van Dijk <
peter.van.d...@powerdns.com>
Subject: [EXT] New Version Notification for draft-pp-dprive-common-
features-00.txt
Date: Sun, 02 May 2021 09:51:09 -0700

A new version of I-D, draft-pp-dprive-common-features-00.txt
has been successfully submitted by Peter van Dijk and posted to the
IETF repository.

Name:           draft-pp-dprive-common-features
Revision:       00
Title:          Common Features for Encrypted Recursive to Authoritative DNS
Document date:  2021-05-02
Group:          Individual Submission
Pages:          7
URL:            
https://www.ietf.org/archive/id/draft-pp-dprive-common-features-00.txt
Status:         
https://datatracker.ietf.org/doc/draft-pp-dprive-common-features/
Htmlized:       
https://datatracker.ietf.org/doc/html/draft-pp-dprive-common-features
Htmlized:       https://tools.ietf.org/html/draft-pp-dprive-common-features-00


Abstract:
   Encryption between recursive and authoritative DNS servers is
   currently being defined in two modes: unauthenticated and fully-
   authenticated.  These two modes have some features in common, and
   this document defines those common features so that the documents
   defining the modes do not need to point to each other.

                                                                                
  


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




_______________________________________________
dns-privacy mailing list
dns-privacy@ietf.org
https://www.ietf.org/mailman/listinfo/dns-privacy

Reply via email to