[Ietf-not43] Comments on CRISP Requirements draft-06 and CRIS P Internet Resour ce Number Requirements draft-00

[Rick Wesson]

IMHO, It is not the IETF that should deal with how data is verified. In fact 
since ICANN has initiated processes to define such we definately MUST NOT 
attempt to define such in the IETF.

see http://www.icann.org/announcements/announcement-18sep03.htm

-rick

On Wednesday 12 November 2003 9:02 am, Ryan Lehning wrote:
> Andy,
>
> Thanks for pointing me to this.  Yes, it looks like dreg contains an
> element for last verified date.  However, there doesn't appear to be any
> indication of how the data was verified.  I'm not sure that users can
> reasonably rely on the accuracy of data without some indication of how that
> data was verified.
>
> thanks,
> Ryan
>
> -----Original Message-----
> From: Andrew Newton [mailto:anewton at ecotroph.net]
> Sent: Wednesday, November 12, 2003 10:08 AM
> To: Ryan Lehning
> Cc: 'Rick Wesson'; 'ietf-not43 at lists.verisignlabs.com'
> Subject: Re: [Ietf-not43] Comments on CRISP Requirements draft-06 and
> CRIS P Internet Resour ce Number Requirements draft-00
>
> Ryan Lehning wrote:
> > Rick,
> >
> > If a "Last Verified Date" would be valuable, why isn't it included in the
> > Requirements document?  Do others have comments on whether there are
>
> better
>
> > ways of implementing the SECSAC recommendations than my proposal?
> >
> > Thanks,
> >
> > Ryan
>
> Yes.  Look at dreg.  I believe this covers the SECSAC recommendation (as
> described by Rick).
>
> -andy
>
> _______________________________________________
> Ietf-not43 mailing list
> Ietf-not43 at lists.verisignlabs.com
> https://lists.verisignlabs.com/mailman/listinfo/ietf-not43