[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dnsext] draft-ietf-dnsext-dnssec-bis-updates and NSEC3

To: Samuel Weiler <weiler@tislabs.com>
Subject: Re: [dnsext] draft-ietf-dnsext-dnssec-bis-updates and NSEC3
From: Paul Hoffman <paul.hoffman@vpnc.org>
Date: Fri, 12 Dec 2008 10:08:23 -0800
Cc: namedroppers@ops.ietf.org
In-reply-to: <alpine.BSF.1.10.0812121111440.65532@fledge.watson.org>
References: <p06240815c5678ad257cc@[10.20.30.158]> <alpine.BSF.1.10.0812121111440.65532@fledge.watson.org>

At 11:31 AM -0500 12/12/08, Samuel Weiler wrote:
>As to whether we should including this, doc editor hat off: probably. Doc editor hat back on: rather than fold this into the existing section 2 or 3, I'm inclined to add a new section cataloging the changes made in other documents.

I'm OK with that as well, but to a naive reader, that will not feel like "NSEC3 is a full member of the DNSSEC family".

>>- Change the status of the document to say that it updates 4033 as well.
>
>Why?

Because 4033 talks about the parts of DNSSEC, and we are adding a new part. Section 8 of 4033 is inherently being updated to say "NSEC and/or NSEC3" in many places.

--Paul Hoffman, Director
--VPN Consortium

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>

References:
- [dnsext] draft-ietf-dnsext-dnssec-bis-updates and NSEC3
  - From: Paul Hoffman <paul.hoffman@vpnc.org>
- Re: [dnsext] draft-ietf-dnsext-dnssec-bis-updates and NSEC3
  - From: Samuel Weiler <weiler@tislabs.com>

Prev by Date: Re: [dnsext] one algorithm number or two
Next by Date: Re: [dnsext] one algorithm number or two
Previous by thread: Re: [dnsext] draft-ietf-dnsext-dnssec-bis-updates and NSEC3
Index(es):
- Date
- Thread