Re: Announcement: RIPE Whois Database version 3.0 beta is out

[Heiko Blume <]

hello,

please forgive any possible ignorance on my side...


i try to use RtConfig 4.6.0 to generate a pretty simple config for testing:

   @RtConfig import AS5427 1.1.1.1 AS33333 1.1.1.1

where AS5427 contains

   import:        from AS33333
                  action pref=200;
                  accept <^AS1273+ .* AS-ECRC$>


which should request only AS-ECRC and, recursively, AS-ECRCCUSTDE from the DB.

this works just fine with whois.radb.net, but not with rpsl.ripe.net,
although both objects are identical in both databases. since both
are translated from whois.ripe.net i'm a little suprised!
am i too stupid?

regards, heiko



[69] hostmaster@localhost ~/RAToolSet-4.6.0 > RtConfig -h rpsl.ripe.net -f cache2 -T all < bla
[blah]
!
RtConfig: cisco_map_name 'AS%d-IN'
RtConfig: cisco_aspath_access_list_no '100'
Whois: Open rpsl.ripe.net:43 source= protocol=rawhoisd
Whois: SetSources -*
Whois: WriteQuery !s-*
Whois: Response % This is the RIPE Whois server v3.0 beta.

Warning: no byte count error for query !s-*.


[no output at all!]




[69] hostmaster@localhost ~/RAToolSet-4.6.0 > RtConfig -h rpsl.ripe.net -f cache2 -T all < bla
! execute
!       RtConfig -h whois.ripe.net < bla
! and see the below @RtConfig line replaced by filters
!
!
! other usual cisco command should be put around here
!
!
!@localhost networks AS5427
!
RtConfig: cisco_map_name 'AS%d-IN'
RtConfig: cisco_aspath_access_list_no '100'
Whois: Open whois.radb.net:43 source= protocol=rawhoisd
Whois: SetSources -*
Whois: WriteQuery !s-*
Whois: Response C

Whois: WriteQuery !s-lc
Whois: Response A187

Whois: Response
radb,ans,ripe,bell,mci,apnic,verio,i2,bconnex,fgc,arcstar,altdb,sinet,soundinternet,look,dodnic,panix,epoch,rgnet,area151,deru,risq,semaphore,iij,gts,csas,koren,telstra,daknet,nestegg,gw

Whois: Response C

Whois: WriteQuery !iAS-ECRC,1
Whois: Response A3485

Whois: Response
AS10348 AS10450 AS10627 AS11082 AS11127 [etcetcetcetc]

Whois: Response C

!
no ip as-path access-list  100
ip as-path access-list 100 permit ^(_1273)+((_[0-9]+))*_(1248|1273|1755|1830|1902|1967|2109|2548|2592|2647|3092|3107|3233|3240|3252|3255|3261|3272|3292|3326|3334|3344|4513|4663|5380|5394|5398|5401|5412|5426|5432|5464|5498|5517|5521|5549|5556|5579)$
[etcetcetcetc]
[etcetcetcetc]
[just perfect]






RIPE Database Administration writes:
 > 
 > Dear All,
 > 
 > [ Apologies for duplicate messages ]
 > 
 > This mail is to inform you that version 3.0 beta of the RIPE Whois
 > Database is out. Read on! You will be affected too.
 > 
 > The RIPE Database is about to change its data format, from RIPE181 to
 > RPSL (the Routing Policy Specification Language, see RFC2622). This will
 > affect all object types, including "person", "domain" and "inetnum".
 > 
 > The version 2 of the RIPE Database, the one currently in production on
 > whois.ripe.net, will in the next months be replaced by version 3. All the
 > entries in the RIPE Database will be translated into RPSL format, and
 > that is the format you will get when you will be querying the Database.
 > 
 > Don't be mistaken: for the moment, whois.ripe.net continues running with
 > version 2 and answering to your queries in the old-fashioned way. But
 > this will not last forever; in a few months, all will become RPSL. So if
 > you use the Whois database, we encourage all of you to prepare for this
 > change as soon as possible.
 > 
 > We strongly suggest you to start to get used to RPSL and version 3.0 . 
 > In this aim, you can do the following:
 > 
 >         - Query rpsl.ripe.net at port 43. You will find there
 >           exactly the same objects that are in whois.ripe.net,
 >           mirrored live and in RPSL format. 
 > 
 >         - If you have any script that runs by querying whois.ripe.net, 
 >           test it by pointing it to rpsl.ripe.net and make it
 >           v3.0-compliant.
 > 
 >         - Try our CGI interface to the RPSL server: you can find it at
 >           http://www.ripe.net/ripencc/pub-services/db/reimp/. 
 > 
 >         - Get to know the new update path: use our "sandbox" database for
 >           RPSL updates. Send your updates to auto-rip@localhost and
 >           query the corresponding database at rpsl.ripe.net, port 4343 .
 > 
 > Remember that in a few months, that's the way the RIPE Database will be
 > running; so the earlier you start working with it, the less likely you
 > are to be unpleasantly surprised later.
 > 
 > We are currently preparing additional resources to help ease the
 > transition; we will announce them as soon as they are available, which
 > will happen later this month.
 > 
 > Please note that the software is still in a "beta" phase. So we need your
 > feedback! If you happen to find something that looks like a bug when you
 > are testing the RPSL database, don't hesitate... 
 > Send us a bug report at dbrip@localhost !
 > 
 > If you want to actively participate to the migration effort, you could   
 > join the "RIP migration Task force" and let yourself be heard. Just write
 > to ripe-dbm@localhost and ask to join the Task Force.
 > 
 > For the ones interested in viewing or trying the code, you can download
 > it at:
 > 
 >         ftp://ftp.ripe.net/ripe/dbase/reimp/whois-rip-3.0beta1.tar.gz
 > 
 > You can also join a discussion list related to version 3.0 beta of the
 > RIPE Database Software. To subscribe to this list, send a message to
 > majordomo@localhost with the line:
 > 
 > subscribe db-beta
 > 
 > in the body of your letter. It is a moderated mailing list so some delays
 > in subscription are possible.
 > 
 > 
 > Regards,
 > 
 > The RIPE Database Group.

-- 
Heiko Blume (HB21)                    
	    
	    

TCP/IP GmbH, Berlin (Germany)                 http://www.tcpip-gmbh.de
Woertherstr. 16, D-10405 Berlin        Phone: +49.30/443366-0 Fax: -15 
HR B 53443, AG Berlin-Charlottenburg
 
TCP/IP GmbH runs the Contrib.Net backbone       http://www.contrib.net
Ein Unternehmen der PTI (PRIMUS Telecommunications International) GmbH