[DNSOP] Incremental zone hash - XHASH

2018-07-20 Thread Mark Andrews
Rather than having a full zone hash this can be done as a chain of hashes (XHASH). The XHASH would include all records at a signed name (where a signed name is NOT an NSEC3 name) up until the next signed name (where a signed name is NOT a NSEC3 name) in DNSSEC order similar to ZONEMD. If there is

Re: [DNSOP] QNAME minimisation on the standards track?

2018-07-20 Thread Tim Wicinski
Jonathan That's *exactly* the type of operational issues that I am interesting in documenting. (That doesn't mean the other chairs or the working group feel the same way, in fact they probably won't! Tim On Fri, Jul 20, 2018 at 9:40 AM, Jonathan Reed < jreed=40akamai@dmarc.ietf.org> wrote:

[DNSOP] The DNSOP WG has placed draft-wessels-dns-zone-digest in state "Candidate for WG Adoption"

2018-07-20 Thread IETF Secretariat
The DNSOP WG has placed draft-wessels-dns-zone-digest in state Candidate for WG Adoption (entered by Tim Wicinski) The document is available at https://datatracker.ietf.org/doc/draft-wessels-dns-zone-digest/ ___ DNSOP mailing list DNSOP@ietf.org

[DNSOP] The DNSOP WG has placed draft-kh-dnsop-7706bis in state "Candidate for WG Adoption"

2018-07-20 Thread IETF Secretariat
The DNSOP WG has placed draft-kh-dnsop-7706bis in state Candidate for WG Adoption (entered by Tim Wicinski) The document is available at https://datatracker.ietf.org/doc/draft-kh-dnsop-7706bis/ Comment: Needs some more review before we adopt. but still.

Re: [DNSOP] I-D Action: draft-ietf-dnsop-rfc5011-security-considerations-13.txt

2018-07-20 Thread Warren Kumari
[ Top-post ] Thank you to Ólafur and Dave for their comments -- I know that the discussion on the draft has been long and the draft is filled with minutia, but we'd dearly love more feedback, positive or negative. W On Thu, Jul 19, 2018 at 11:42 PM Dave Lawrence wrote: > > Warren Kumari

Re: [DNSOP] Incremental zone hash - XHASH

2018-07-20 Thread Mark Andrews
The same zone NSEC3 signed with a.example.com in OPTOUT range example.com SOA example.com NS ns.example.com example.com DNSKEY … example.com NSEC3PARAM 1 0 0 - example.com XHASH … 3QNILC4QRC2P5CRN7JGVB5S3BPG0SHUV.example.com 1 1 0 - NSEC3 1 1 0 -

[DNSOP] The DNSOP WG has placed draft-song-atr-large-resp in state "Candidate for WG Adoption"

2018-07-20 Thread IETF Secretariat
The DNSOP WG has placed draft-song-atr-large-resp in state Candidate for WG Adoption (entered by Tim Wicinski) The document is available at https://datatracker.ietf.org/doc/draft-song-atr-large-resp/ Comment: We don't know if theWG is ready to adopt this, but marking this down so the chairs do

Re: [DNSOP] QNAME minimisation on the standards track?

2018-07-20 Thread manu tman
That's a great feedback Jonathan! Thanks Manu On Fri, Jul 20, 2018 at 6:40 AM Jonathan Reed wrote: > > On Tue, 17 Jul 2018, manu tman wrote: > > > I'd like to see this standardized too. > > Side note: I would also be interested to get a return of experience from > people operating qname

[DNSOP] Publication has been requested for draft-ietf-dnsop-kskroll-sentinel-15

2018-07-20 Thread Tim Wicinski
Tim Wicinski has requested publication of draft-ietf-dnsop-kskroll-sentinel-15 as Proposed Standard on behalf of the DNSOP working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-dnsop-kskroll-sentinel/ ___

Re: [DNSOP] Call for Adoption: draft-huque-dnsop-multi-provider-dnssec

2018-07-20 Thread Tim Wicinski
All Thanks for all the comments on this draft. The Call for Adoption is ending today but it seems that there is consensus to adopt this work in DNSOP and support this work. The chairs thank everyone for the feedback. Authors should upload a new version with the

[DNSOP] IETF102 Actions and Updates

2018-07-20 Thread Tim Wicinski
All Thanks for a pretty productive week and thanks for breaking in our new chair slowly. Rough Minutes have been uploaded: https://datatracker.ietf.org/doc/minutes-102-dnsop/ And I apologize - I took notes of the last topic on Thursday but have somehow lost them. I will listen to the audio and

Re: [DNSOP] IETF102 Actions and Updates

2018-07-20 Thread Steve Crocker
I've been watching actively but quietly. Stellar work! Congratulations! Steve Crocker On Fri, Jul 20, 2018 at 2:40 PM, Tim Wicinski wrote: > > All > > Thanks for a pretty productive week and thanks for > breaking in our new chair slowly. > > Rough Minutes have been uploaded: > >

[DNSOP] I-D Action: draft-ietf-dnsop-no-response-issue-10.txt

2018-07-20 Thread internet-drafts
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 : A Common Operational Problem in DNS Servers - Failure To Respond. Authors : M. Andrews

Re: [DNSOP] Incremental zone hash - XHASH

2018-07-20 Thread Paul Vixie
perfect! Mark Andrews wrote: Rather than having a full zone hash this can be done as a chain of hashes (XHASH). The XHASH would include all records at a signed name (where a signed name is NOT an NSEC3 name) up until the next signed name (where a signed name is NOT a NSEC3 name) in DNSSEC

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-dns-capture-format

2018-07-20 Thread Tim Wicinski
All The WG Last Call for draft-ietf-dnsop-dns-capture-format and the chairs feel we have enough consensus to move this forward. HOWEVER, two things did come up with some reviews that happened in the last few days: - The packet format has a version number, but the draft does not document or

Re: [DNSOP] Incremental zone hash - XHASH

2018-07-20 Thread Wessels, Duane
Mark, Thanks for the email. My first reaction is that it adds a lot of additional records to the zone. If I understand correctly, one XHASH for every NSEC/NSEC3, plus an RRSIG for each XHASH. You didn't really say how (or if) XHASH could be used on an unsigned zone. My second reaction is