Reassignment Proposal

[Darren Loher]

Hi,

Since Level 3 uses RWHOIS for IP justification with ARIN, we already 
have the majority of information that would be required for 
reassignment in RWHOIS.  With some modifications, we could include
all the necessary template information.  This seems cleaner
than SWIP over all.

RWHOIS would be a nice method for IP reassignment/delegation if 
RWHOIS remains the prefered method for reporting IP allocations.

An IRR solution might be better in the long run.  And of course,
we run our own route registry as well, that also contains most
of the info required for delegations.  Seems reasonable to use
one of these so we're not doing so much redundant work.  Not sure
how many ISP's have real functioning route registrys as opposed
to functioning RWHOIS servers.

-Darren

-- 
Darren Loher                 Level 3 Communications
dploher at level3.net           Global Data Architecture
720-888-2847 (office)        "Sed quis custodiet ipsos custodes?"

On Thu, May 17, 2001 at 03:31:52PM -0400, ginny listman wrote:
> Tanya,
> 
> My posted message from April 27, was to survey the membership regarding
> which reassignment method they would prefer to use.  Since that time, two
> members have stated an IRR-type method, one member stated IRR or improve
> RWHOIS, and one member stated SWIP.  Four responses are not enough to draw
> any conclusion. Therefore, Engineering has continued with making internal  
> improvements in SWIP, including improved processing time, and continues
> RWHOIS analysis.  There has been no analysis on an IRR method.
> 
> Ginny Listman
> Director of Engineering
> American Registry of Internet Numbers
> 
> 
> On Thu, 17 May 2001, Tanya Hinman wrote:
> 
> > 
> > >Since this is more a question of where ARIN should invest resources in
> > >developing, and less a policy issue, I would like to move the discussion
> > >to the dbwg list.
> > 
> > So is it ok to say we are moving forward with this option since it is not a
> > policy issue? Can we start developing our own WHOIS database within our
> > Routing Registry and stop using the SWIP option once it is completed? If
> > ARIN sets the guidelines for what needs to be included in the WHOIS, then we
> > can start our development based on those guidelines. Including that same
> > information that SWIP contains should be sufficient, with the ability to
> > block personal information from the public if the customer wishes.
> > 
> > 
> > Tanya Hinman