Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-21 Thread Stephane Bortzmeyer
On Wed, Dec 21, 2016 at 11:34:52AM -0800, 神明達哉 wrote a message of 143 lines which said: > - Title: "Aggressive use of NSEC/NSEC3" > > I think this should now be e.g., "Aggressive use of DNSSEC-validated > cache" because of the equal weight given to the aggressive use

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-21 Thread Stephane Bortzmeyer
On Tue, Dec 20, 2016 at 07:38:08PM +, Warren Kumari wrote a message of 72 lines which said: > > * synthesis of NXDOMAIN from NSEC (obviously; that's the minimum) > > * synthesis of NXDOMAIN from NSEC3 (if no opt-out) > > * synthesis of NODATA from NSEC/NSEC3 > > *

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-21 Thread 神明達哉
At Tue, 13 Dec 2016 14:13:27 -0500, tjw ietf wrote: > We felt another formal Working Group Last call was needed, though hopefully > shorter. > > This starts a Working Group Last Call for: > "Aggressive use of NSEC/NSEC3" > draft-ietf-dnsop-nsec-aggressiveuse > >

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-20 Thread Warren Kumari
On Tue, Dec 20, 2016 at 5:59 AM Stephane Bortzmeyer wrote: > On Tue, Dec 13, 2016 at 07:16:37PM +, > Warren Kumari wrote > a message of 132 lines which said: > > > The authors think that they have captured / addressed everyone's > > comments - if we

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-20 Thread Paul Wouters
On Tue, 20 Dec 2016, Stephane Bortzmeyer wrote: One of my comments was not addressed. I would like, in section 10, see some details about what exactly is implemented by Unbound and Google Public DNS: * synthesis of NXDOMAIN from NSEC (obviously; that's the minimum) * synthesis of NXDOMAIN from

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-20 Thread Stephane Bortzmeyer
On Tue, Dec 20, 2016 at 10:14:16AM -0500, Paul Wouters wrote a message of 16 lines which said: > > One of my comments was not addressed. I would like, in section 10, see > > some details about what exactly is implemented by Unbound and Google > > Public DNS: > > > > *

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-20 Thread Paul Wouters
On Tue, 20 Dec 2016, Stephane Bortzmeyer wrote: One of my comments was not addressed. I would like, in section 10, see some details about what exactly is implemented by Unbound and Google Public DNS: * synthesis of NXDOMAIN from NSEC (obviously; that's the minimum) * synthesis of NXDOMAIN from

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-20 Thread Stephane Bortzmeyer
On Tue, Dec 13, 2016 at 07:16:37PM +, Warren Kumari wrote a message of 132 lines which said: > The authors think that they have captured / addressed everyone's > comments - if we missed (or misunderstood) anything, it was > unintentional. One of my comments was not

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-15 Thread Bob Harold
On Wed, Dec 14, 2016 at 8:53 AM, Stephane Bortzmeyer wrote: > On Tue, Dec 13, 2016 at 02:13:27PM -0500, > tjw ietf wrote > a message of 94 lines which said: > > > This starts a Working Group Last Call for: > > "Aggressive use of NSEC/NSEC3" > >

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-14 Thread Stephane Bortzmeyer
On Tue, Dec 13, 2016 at 02:13:27PM -0500, tjw ietf wrote a message of 94 lines which said: > This starts a Working Group Last Call for: > "Aggressive use of NSEC/NSEC3" > draft-ietf-dnsop-nsec-aggressiveuse I've read -07 and I believe it is OK and ready for

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-14 Thread tjw ietf
Sigh, I did. Thank you Matthijs for keeping me honest. tim On Wed, Dec 14, 2016 at 7:46 AM, Matthijs Mekking wrote: > Tim, > > On 13-12-16 20:13, tjw ietf wrote: > >> All >> >> The process of WGLC for this document engaged the working group and >> there was much

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-14 Thread Matthijs Mekking
Tim, On 13-12-16 20:13, tjw ietf wrote: All The process of WGLC for this document engaged the working group and there was much discussion and several different versions. It seems that the authors have addressed everything that has been brought up. We felt another formal Working Group Last

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

2016-12-13 Thread Warren Kumari
The authors think that they have captured / addressed everyone's comments - if we missed (or misunderstood) anything, it was unintentional. W On Tue, Dec 13, 2016, 2:13 PM tjw ietf wrote: > All > > The process of WGLC for this document engaged the working group and there >