Eric Orth wrote:
> On Tue, Nov 17, 2020 at 4:46 PM Tony Finch wrote:
> >
> > There's also a privacy leak: if you assign a unique subdomain then when a
> > device roams and leaks queries for the private domain, the device can be
> > tracked and correlated with other devices that use the same
I support the resolver IP range discovery function. I don't think it will
be hard to come up with a reasonable format for that. An APL record with
standard address families would seem fine. A URI record pointed at a JSON
blob or a flat text file would be fine too.
I do not support the
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.
Title : Interoperable Domain Name System (DNS) Server Cookies
Authors : Ondrej Sury
The IESG has approved the following document:
- 'Message Digest for DNS Zones'
(draft-ietf-dnsop-dns-zone-digest-14.txt) as Proposed Standard
This document is the product of the Domain Name System Operations Working
Group.
The IESG contact persons are Warren Kumari, Robert Wilton and Barry
On Tue, Nov 17, 2020 at 4:46 PM Tony Finch wrote:
> Brian Dickson wrote:
>
> > One potential approach is to say (in the RFC) that one of the two-letter
> > reserved codes should avoid name collision by putting a
> collision-resistant
> > second-level label, below .zz and above the private use
