Re: Whoisfix BOF 51st IETF / Minutes

Engin and all,

  Not to worry, Dave often makes these types of mistakes.

Engin Gunduz wrote:

> Hi,
>
> On Mon, 13 Aug 2001, Dave Crocker wrote:
> >
> > Folks,
> >
> > Here are the excellent notes that Ted took, unchanged.  The polling cited
> > at the end of the notes includes the list of possible task items suggested
> > by attendees.
> >
> > If there are no objections to these notes by this Friday, I'll post them to
> > the IETF secretariat.
> >
> > d/
> >
> [....]
> > With that background Marjann presented how they use whois and noted that
>                        ^^^^^^^
> Mirjam Kuehne
>
> > APNIC uses a version of the RIPE NCC code for similar purposes, to whit:
> > track IP and ASN allocation, maintain contact info, and maintain both
> > reverse and forward domain name data.  Data are populated both by the RIPE
> > NCC and the domain holders.  In addition, RIPE uses whois as part of its
> [....]
> >
> > Randy then gave a presentation of NIC handle info in the whois data at ARIN
> > and RIPE, which notes that different registries have different identities
> > attached to the same identifier, despite a hack that tries to use
> > REGISTRY-handle method for associating data to the original handle.  This
> > is partly because of RIPE's method of doing referential integrity (dumping
> > the other database into their own).
>
> This is not the case: the other DBs are not dumped into our own. We just
> allow users to create person objects with non-RIPE NIC handles.
>
> Thanks for the  minutes,
> -engin
>
> Engin Gunduz
> RIPE NCC Database Group

Regards,
--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 118k members strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail [email protected]
Contact Number:  972-447-1800 x1894 or 214-244-4827
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208