Re: Summary RE: DNSEXT WGLC: DNSSEC Opt-in

[Brian Wellington <Brian.Wellington@nominum.com>]

On Thu, 13 Feb 2003, Hallam-Baker, Phillip wrote:

> There were 27 messages in this thread from 10 distinct individuals.

I can't speak for anyone else, but I have problems with your analysis.
> 
> Q: Does this document satisfy people as being implement able and
> testable
> specification ?
> 
> Answers:
> 	Kosters - Yes  [detailed response]
> 	Loomis - I believe that the specification can be implemented and
> tested.
> 	Wellington - i believe that the current version of the
> specification 
> 		is complete.

I'm pretty sure I never said that.  I have implemented opt-in, but am most 
definitely not sure of its correctness and whether I missed any corner 
cases.

> Q: Are there implementations of opt-in and have there been any tests ?
> 
> Answers:
> 	Kosters - Yes [detailed response]
> 	Austein - asked about resolver side implementations
> 	Arends - Yes, Verisignlabs and ISC have auth.server
> implementations, 
> 		ISC has a resolver implementation.
> 	Nordmark - Does this mean that there is a caching resolver 
> 		implementation that has been tested? 
> 	Arends - I don't have material on how thorough the caching
> resolver 
> 		implementation has been tested.
> 	Wellington - yes.

There are two questions here, and 'yes' implies yes to both.  Yes, there 
are implementations.  No, I have never tested them and do not know the 
results of any tests that have been performed.

> In addition there were responses on the question of advancement
> 
> 	Hallam-Baker - It should advance
> 	Vixie - dunno.  but in any case i am strongly in favour of it
> 	Conrad - To be perfectly honest, I no longer care 
> 	Wellington - yes.  (notes to be posted here shortly, so they
> tell me.)

You've got to be kidding me.  I have never supported the advancement of 
opt-in.  I don't know what notes these are, since I haven't publicly said 
anything about opt-in in the last 6 months.

Check your facts before putting words in other people's mouths.

Brian

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