Verio renamed NTTCOM in RIPE Database
Dear Colleagues, On 31 March 2007, the Verio routing registry database was renamed NTTCOM. This change of name has been incorporated in the RIPE Database server which mirrors a number of public databases including the NTTCOM routing registry. More information about the NTTCOM routing registry is available at: http://www.us.ntt.net/about/policy/rr.cfm The list of databases mirrored by the RIPE Database server is available at: http://www.ripe.net/db/mirrored.html -- Katie Petrusha RIPE Database administration RIPE NCC
On 31 March 2007, the Verio routing registry database was renamed NTTCOM. This change of name has been incorporated in the RIPE Database server which mirrors a number of public databases including the NTTCOM routing registry.
More information about the NTTCOM routing registry is available at: http://www.us.ntt.net/about/policy/rr.cfm
how/when will that affect us poor peval() users? `/usr/local/bin/peval -s $IRR $OBJ do we just change $IRR from VERIO to NTTCOM and it will all work? randy
On 31 March 2007, the Verio routing registry database was renamed NTTCOM. This change of name has been incorporated in the RIPE Database server which mirrors a number of public databases including the NTTCOM routing registry.
More information about the NTTCOM routing registry is available at: http://www.us.ntt.net/about/policy/rr.cfm
how/when will that affect us poor peval() users?
`/usr/local/bin/peval -s $IRR $OBJ
do we just change $IRR from VERIO to NTTCOM and it will all work?
yes Assuming that defaults/environment/additional flags in appropriate position for the database host and access protocol (radb ./. ripe) are right that should do it - and I can report success using peval/RtConfig derivatives for a couple of days.
randy
Cheers, Ruediger
participants (3)
-
Katie Petrusha -
Randy Bush -
Ruediger Volk, Deutsche Telekom T-Com - TE141-P1