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


To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "'Edward Lewis'" <edlewis@arin.net>, <ietf-provreg@cafax.se>
Cc: <jaap@sidn.nl>
From: "Ram Mohan" <rmohan@afilias.info>
Date: Fri, 7 Mar 2003 15:35:59 -0500
Sender: owner-ietf-provreg@cafax.se
Subject: Re: [ietf-provreg] Fwd: Re: provreg milestones

agreed, both personally and for the .info registry.

-ram
----- Original Message ----- 
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Edward Lewis'" <edlewis@arin.net>; <ietf-provreg@cafax.se>
Cc: <jaap@sidn.nl>
Sent: Friday, March 07, 2003 7:23 AM
Subject: RE: [ietf-provreg] Fwd: Re: provreg milestones


> > Also to the group - as far as the privacy thing being resolved, I'm a 
> > bit hesitant to declare consensus yet to the proposal in:
> > 
> > # From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
> > # Date: Mon, 3 Mar 2003 13:02:34 -0500
> > #
> > # As far as .com is concerned, I have no doubt that an 
> > extension will be
> > # required even if we were to adopt the IESG's element 
> > tagging suggestion.
> > # That being the case, my preference would be to put _all_ of 
> > the DNP syntax
> > # and semantics into an extension (where the problem can be 
> > addressed as a
> > # whole) while making the existing DCP element mandatory if 
> > that resolves the
> > # privacy issue with the IESG.
> > 
> > (Aka - 
> > http://www.cafax.se/ietf-provreg/maillist/2003-03/msg00010.html)
> > 
> > So let me hear about that...
> 
> Ed, please note these supporting comments sent prior to your note:
> 
> http://www.cafax.se/ietf-provreg/maillist/2003-03/msg00015.html
> 
> http://www.cafax.se/ietf-provreg/maillist/2003-03/msg00023.html
> 
> -Scott-
> 

Home | Date list | Subject list