Reassignment Proposal

[Lee Howard]

I've been thinking along similar lines for a while.  Presumable, eveyone
has a database of their IP allocations (for some people, this database
is a spreadsheet or spiral-bound notebook).  Trying to keep that database
in sync with the IRR (whether ARIN, RADB, or internal) and SWIP is 
difficult, and distributing data queries to the database of record makes
a lot of sense to me.  Much like DNS, come to think of it.

Would you provide responses in RPSL? 

I seem to recall ARIN announcing the publication of RWHOIS output
requirements, but I can't find them (or anything about RWHOIS) on the
ARIN site map.  RWHOIS is on the agenda for 4/4/2000 Public Policy
Meeting, but my meeting notes don't have anything more specific.  In
fact, there are no meeting minutes on ARIN's site for that meeting.

I'm all in favor of a combined RWHOIS/IRR responder.

Lee Howard


On Tue, 24 Apr 2001, Tanya Hinman wrote:

> Date: Tue, 24 Apr 2001 13:44:32 -0400
> From: Tanya Hinman <thinman at clp.cw.net>
> To: ppml at arin.net
> Subject: Reassignment Proposal
> 
> 
> We would like to propose the creation of a third reassignment option in
> conjunction with the current SWIP and RWHOIS options. As companies expand
> globally, it would be much simpler for them to update WHOIS data in their
> own one Registry rather than the three RIRs. We would like to create our own
> WHOIS database within our Routing Registry. This would be similar to the way
> RIPE represents WHOIS information along with their Routing Registry, and it
> would be in place of a stand alone RWHOIS database which some of the other
> ISP's are currently using.
> 
> 1)If this is accepted by all three RIRs it would be very efficient and it
> may help to relieve some of the load from the RIR's.
> 2)If the RIRs were to Mirror the WHOIS data from ours/other ISPs'
> Registries, it would also allow queries from the RIRs registries rather than
> referencing the customer's URL like the current RWHOIS reference.
> 3)It would be much easier to update and keep data accurate if all the data
> is managed using the same database.
> 4)Guidelines for the format of this WHOIS option will need to be set in
> order to implement a standard.
> 
> Thank you,
> Tanya Hinman
> Cable & Wireless
>