[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rfci-discuss
Subject:    [RFCI-Discuss] Re: what public database operatros can and cannot do
From:       Bruce Campbell <bruce.campbell () ripe ! net>
Date:       2002-02-08 23:02:16
Message-ID: Pine.LNX.4.44.0202082347030.17272-100000 () x22 ! ripe ! net
[Download RAW message or body]

On Fri, 8 Feb 2002, Bruce Campbell wrote:

> [ on data ownership and private contacts ]
> > > Circumstances such as ownership of the data may not permit us to update
> > > the database ourselves.
> >
> > Then perhaps you should list contact addresses of who _is_ responsible
> > for said data? For instance, if RIPE does not have the ability to
> [snippery]
> > > or update our private file in order to get the information
> > > updated the next time they come calling (which may be some time).
> >
> > Private file?
>
> See our policies.  As a RIR, a _lot_ of information is required seperately
> to what is seen in the public database, as part of the requirement to
> justify the address space requested.  In general, whats in that file and
> not in the database (including private contacts) is confidential to the
> business (ISP etc) in question and may not be legally released.

Allen has pointed out that I hadn't replied to a private mail of his on
last month's '.NL whois' thread ( I mistakenly sent him a rather
long-winded reply privately instead of to the list, clumsy fingers during
conference stress unfortunately ).

As that thread is over, I won't resurrect it at this time, save to pull a
relevant paragraph concerning the current thread:

: the RIPE NCC is obligated to provide certain data, in this case the
: relevant contact data.  The NCC does not provide to you (as an ad-hoc
: whois querier) and is not obligated to provide to you, all of the data
: that the NCC has collected in the course of making an allocation.
:
: The basic 'whims' that the NCC has to follow are recorded in RFC2050.
: The RIPE documents further document such 'whims'.

The other main aspects of that mail are concerning properly defining the
'WHOIS' protocol (as a protocol, not as the current mishmash between
protocol and required data).  Astute observers will note that the
referred-to draft (draft-campbell-whois-00.txt) has been announced via
ietf-announce in its original form in the last few days, and
private/public comments on that will be accepted.

Regards,

-- 
                             Bruce Campbell                            RIPE
                   Systems/Network Engineer                             NCC
                 www.ripe.net - PGP562C8B1B                      Operations


[prev in list] [next in list] [prev in thread] [next in thread]