Re: [DNSOP] additional section, was Over on the dbound list: draft-dcrocker-dns-perimeter-00

2019-04-14 Thread John R Levine
On Thu, 3 Apr 2019, John Levine wrote: The part of interest to DNSOP would be section 7 on pages 12 and 13 where it discusses tree walks and potential new additional section processing to find the closest perimeter record above a name being checked. This draft proposes to publish TXT records to

Re: [DNSOP] additional section, was Over on the dbound list: draft-dcrocker-dns-perimeter-00

2019-04-14 Thread Ted Lemon
On Apr 14, 2019, at 11:13 AM, John R Levine wrote: > Although it is legal to put an additional section in an NXDOMAIN response, > it's uncommon and I don't know how the bailiwick checks would work. We already do something like this when looking for the zone apex, and it potentially has the same

Re: [DNSOP] [Ext] Re: draft-ietf-dnsop-algorithm-update

2019-04-14 Thread Mark Andrews
And as DNS is loosely coherent a validator cannot check this rule even when getting answers from a single IP address as there may be a anycast server behind that address. This loose coherence allows for servers to incrementally sign a zone when introducing a new algorithm. A incrementally signe