Re: NSEC-13 conclusion

[Edward Lewis <Ed.Lewis@neustar.biz>]

I have to ask, now that I have time to read the 
document, is there a reason opt-out is optional 
wrt to NSEC3?

Yes I know I'm late in asking, but as things wind 
down I get to catch up on my reading pile.

The reason I'm asking this question is that I am 
concerned (meaning unable to come up with a 
concrete reason) about altering parameters in an 
operating zone.  If there are few NSEC3 records 
to update, I think it is okay.  But if there are 
millions of records, I am not so sure.

Did we consider adding text to encourage liberal use of opt-out?

At 11:26 -0500 12/11/07, Ólafur Guðmundsson /DNSEXT
 chair wrote:
> Namedroppers,
> There seems to be consensus that the change is acceptable.
> The working group is done with NSEC3.
>
> Mark,
> please forward this version to the RFC-editor, for publication.
>
>         Olafur
>
>
> --
> 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/>

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                +1-571-434-5468
NeuStar

Think glocally.  Act confused.

--
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/>