[25572] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: RPSL Transition

daemon@ATHENA.MIT.EDU (Gerald Andrew Winters)
Wed Oct 20 11:08:14 1999

From: Gerald Andrew Winters <gerald@merit.edu>
Message-Id: <199910201506.LAA08581@home.merit.edu>
To: markb@infi.net (Mark Borchers)
Date: Wed, 20 Oct 1999 11:06:41 -0400 (EDT)
Cc: nanog@merit.edu
In-Reply-To: <199910201439.KAA00097@ns2.harpweek.com> from "Mark Borchers" at Oct 20, 99 09:39:42 am
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu



> Some recent correspondence with the RA folks seems to indicate that 
> the RIPE-181 database and the RPSL database are not being merged.  
> Thus, when transitioning to RPSL, all objects for an AS (Maintainer, 
> AS, and the rest) will need to be re-registered.  

Yes, this topic was covered at NANOG.  The integration between
the ripe181 db and the rpsl db will occur at short intervals so
that an update in the ripe181 db will show up in the rpsl db
(possibly overwriting a corresponding rpsl object).  This 
integration will commence early next week until full transtion is 
complete on 1/00.  When the initial integration takes place the latest 
rpsl objects will take precedence over corresponding ripe181 objects.

--jerry



home help back first fref pref prev next nref lref last post