March 2001 - routing-wg - mailman.ripe.net

Re: RIPE: last call for comments RPSL transition
by SchmitzJo＠aol.com 02 Mar '01

02 Mar '01

Dear Christian, you wrote: > well I'd say go for it. Thank you for your support. > But let me kindly ask for the following thingies: > > since the RIPE-NCC is now in charge of the maintenance of the RAtoolset > please make sure that there's a release available (specifically > RTconfig) which is fully compatible with the RIPE RPSL server by mid of > March 2001 latest. I believe that this request is more than legitimate, and that the NCC is hearing you very well - after all it is in all our interest to have this running. > > It appears that this might be available already (since Feb20 ?), > however, the link to > > "RtConfig Patch for the RAToolSet" of the "RPSL Migration" homepage is > broken. This is currently worked on, as I hear. > > In addition, any clear links to concise How2do documents on RAToolSet > and RtConfig would be appreciated. On the one hand, I think the best source for that still is http://www.isi.edu/ra/RAToolSet/ On the other hand, we will have a tutorial on the RAToolSet during RIPE39. This has been confirmed by now, and I believe that additional documentation will become available around it. Thanks Joachim --- JS395-RIPE -- standard disclaimer ---

1 0

Re: RIPE: last call for comments RPSL transition
by SchmitzJo＠aol.com 02 Mar '01

02 Mar '01

Dear Ping Lu, you wrote: > We had a lively discussion about the RPSL transition during the RIPE-38 > meeting. This is correct, and I very much appreciate the input you provided during our joint working group session. > Well, if we can't fight them then the best thing to do is to join them. Do I need to be worried now? I never considered this to be a fight ;-) > With the company's support behind us, we (Cable & Wireless Global) as a > legacy LIR (used to be MCI) > would like to work with RIPE to help the RPSL transition. > > CW will adopt a similar schedule as RIPE's to transform our Routing Registry > into the new RPSL format. > This will probably make all the mirroring LIRs' job much easier and > hopefully all the downstream ISPs happier (only the RPSL format to deal > with). > > So GO FOR IT. I welcome your approval. I believe I do not exaggerate stating that you can count on the support from the RIPE community and the NCC in particular in the transition effort. Thanks Joachim --- JS395-RIPE -- standard disclaimer ---

1 0

RE: RIPE: last call for comments RPSL transition
by Christian Panigl, ACOnet/VIX/UniVie 01 Mar '01

01 Mar '01

Hi Joachim, well I'd say go for it. But let me kindly ask for the following thingies: since the RIPE-NCC is now in charge of the maintenance of the RAtoolset please make sure that there's a release available (specifically RTconfig) which is fully compatible with the RIPE RPSL server by mid of March 2001 latest. It appears that this might be available already (since Feb20 ?), however, the link to "RtConfig Patch for the RAToolSet" of the "RPSL Migration" homepage is broken. In addition, any clear links to concise How2do documents on RAToolSet and RtConfig would be appreciated. Thanks and kind regards CP --- ---------------------------------------------------------------------- --- --- Christian Panigl : Vienna University Computer Center - ACOnet --- --- VUCC - ACOnet - VIX : -------------------------------------------- --- --- Universitaetsstrasse 7 : Mail: Panigl(a)CC.UniVie.ac.at (CP8-RIPE) --- --- A-1010 Vienna / Austria : Tel: +43 1 4277-14032 (Fax: -9140) --- --- ---------------------------------------------------------------------- ---

2 1

RE: RIPE: last call for comments RPSL transition
by Lu, Ping 01 Mar '01

01 Mar '01

Hi, Joachim, We had a lively discussion about the RPSL transition during the RIPE-38 meeting. Well, if we can't fight them then the best thing to do is to join them. With the company's support behind us, we (Cable & Wireless Global) as a legacy LIR (used to be MCI) would like to work with RIPE to help the RPSL transition. CW will adopt a similar schedule as RIPE's to transform our Routing Registry into the new RPSL format. This will probably make all the mirroring LIRs' job much easier and hopefully all the downstream ISPs happier (only the RPSL format to deal with). So GO FOR IT. Ping Lu Cable & Wireless Global Network Tools and Analysis Group, USA W: +1-703-292-2359 E: plu(a)cw.net > -----Original Message----- > From: SchmitzJo(a)aol.com [mailto:SchmitzJo@aol.com] > Sent: Friday, February 16, 2001 6:46 PM > To: routing-wg(a)ripe.net; db-wg(a)ripe.net; lir-wg(a)ripe.net; > local-ir(a)ripe.net > Cc: andrei(a)ripe.net; joao(a)ripe.net; hph(a)a.sol.no; > woeber(a)cc.univie.ac.at; schmitzjo(a)aol.com > Subject: RIPE: last call for comments RPSL transition > Importance: Low > > > Hello all, > > as you are aware, we are preparing the migration of the RIPE database > software to support and deploy the new RPSL format. The required steps > have been discussed in depth on various occassions (for references, > see end of mail). > > We are now preparing the most important step, really > transitioning from > old > RIPE-181 to new RPSL format: > > proposed transition date is 23-Apr-2001. > > This step, once taken, will not be reversed. The majority of the user > community takes a neutral role, while some want an earlier, > and a few a > later > date for migration. During the joint session of Routing and DB WG at > RIPE38, > the chairmen of both WGs were tasked to file a last call for > comments on > that > date, in particular whether there are serious, unresolvable > technical or > operational problems which would benefit from a slightly > longer warning > period. > > According to consensus at the session: If you are convinced that the > transition date as proposed would lead to significant operational > problems, please explain and justify why within the next 2 weeks: > > deadline for transition comments: 1-Mar-2001 > > Only well founded reasoning (including an educated guess > about the time > and resources required to resolve the issue) shall be accepted by the > community in order to consider postponing the transition. > > With the discussion about the migration going on for quite > some time, and > information available from various places, we do not expect a > delay, but > we would want to give everybody a last opportunity to comment. > > To summarize the dates, we are looking at: > > o 23-Apr-2001: switching to the RPSL database > - All objects are automatically converted to RPSL format > - Queries return RPSL only > - Mirroring follows new format and rules at > whois.ripe.net, port 4444 > - RPSL formatted updates can be submitted to auto-rpsl(a)ripe.net > - RIPE-181 updates are still accepted at auto-dbm(a)ripe.net, > but are autmatically converted to RPSL > - RFC2725 (Routing Policy Security System) rules apply throughout > > o 14-May-2001: exchanging mail addresses for submitting > RIPE181 and RPSL- > formatted updates > - auto-dbm(a)ripe.net only accepts RPSL updates > - RIPE-181 updates are still possible but now go to > auto-181(a)ripe.net > and are automatically converted to RPSL (again, > RFC2725 rules apply > here as well) > > o 15-Oct-2001: RIPE-181 updates are no longer accepted > > For further reading, please refer to the migration web page > http://www.ripe.net/rpsl > or for the discussion during the joint session of the DB/Routing WGs > please review the minutes. > > For technical specifications of RPSL please refer to > - rfc2622: "Routing Policy Specification Language (RPSL)" > Status: PROPOSED STANDARD, > - rfc2650: "Using RPSL in Practice" > Status: INFORMATIONAL > - rfc2725: "Routing Policy System Security" > Status: PROPOSED STANDARD > > Thanks a lot - the RIPE NCC and the chairmen of > Routing: Joachim Schmitz > DB: Wilfried Woeber > LIR: Hans Peter Holen > >

2 1

Weekly Routing Table Report
by Routing Analysis 01 Mar '01

01 Mar '01

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to bgp-stats(a)lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 02 Mar, 2001 Analysis Summary ---------------- BGP routing table entries examined: 101782 Origin ASes present in the Internet Routing Table: 10158 Origin ASes announcing only one prefix: 3648 Transit ASes present in the Internet Routing Table: 1351 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 16 Illegal AS announcements present in the Routing Table: 14 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 3 Number of addresses announced to Internet: 1245881361 Equivalent to 74 /8s, 66 /16s and 164 /24s Percentage of available address space announced: 33.6 Percentage of allocated address space announced: 65.9 Percentage of available address space allocated: 51.0 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 15777 Prefixes being announced from the APNIC address blocks: 14124 APNIC Region origin ASes present in the Internet Routing Table: 1171 APNIC Region origin ASes announcing only one prefix: 429 APNIC Region transit ASes present in the Internet Routing Table: 192 Average APNIC Region AS path length visible: 5.0 Max APNIC Region AS path length visible: 14 Number of APNIC addresses announced to Internet: 70384792 Equivalent to 4 /8s, 49 /16s and 252 /24s Percentage of available APNIC address space announced: 69.2 APNIC AS Blocks 4608 - 4864, 7467 - 7722, 9216 - 10239, 17408 - 18431 APNIC Address Blocks 61/8, 202/7, 210/7 and 218/8 ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 70153 Prefixes being announced from the ARIN address blocks: 47971 ARIN Region origin ASes present in the Internet Routing Table: 6186 ARIN Region origin ASes announcing only one prefix: 1815 ARIN Region transit ASes present in the Internet Routing Table: 638 Average ARIN Region AS path length visible: 5.2 Max ARIN Region AS path length visible: 14 Number of ARIN addresses announced to Internet: 194580734 Equivalent to 11 /8s, 153 /16s and 16 /24s Percentage of available ARIN address space announced: 89.2 ARIN AS Blocks 1 - 1876, 1902 - 2042, 2044 - 2046, 2048 - 2106 2138 - 2584, 2615 - 2772, 2823 - 2829, 2880 - 3153 3354 - 4607, 4865 - 5119, 5632 - 6655, 6912 - 7466 7723 - 8191, 10240 - 12287, 13312 - 15359 16384 - 17407, 18432 - 20479 ARIN Address Blocks 63/8, 64/7, 66/8, 199/8, 200/8, 204/6, 208/7 and 216/8 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 15838 Prefixes being announced from the RIPE address blocks: 12549 RIPE Region origin ASes present in the Internet Routing Table: 2800 RIPE Region origin ASes announcing only one prefix: 1404 RIPE Region transit ASes present in the Internet Routing Table: 519 Average RIPE Region AS path length visible: 5.9 Max RIPE Region AS path length visible: 16 Number of RIPE addresses announced to Internet: 109079953 Equivalent to 6 /8s, 128 /16s and 109 /24s Percentage of available RIPE address space announced: 92.9 RIPE AS Blocks 1877 - 1901, 2042, 2047, 2107 - 2136, 2585 - 2614 2773 - 2822, 2830 - 2879, 3154 - 3353, 5377 - 5631 6656 - 6911, 8192 - 9215, 12288 - 13311, 15360 - 16383 RIPE Address Blocks 62/8, 193/8, 194/7, 212/7 and 217/8 APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /19 equiv Description 1221 2389 1189 Telstra 2764 426 140 connect.com.au pty ltd 703 401 253 UUNET Technologies, Inc. 2907 378 909 SINET Japan 4755 296 111 VSNL India 4740 275 17 Ozemail 4538 220 1006 China Education and Research 4618 211 56 Internet Thailand 9269 205 24 Hong Kong CTI 7474 202 89 Optus Communications 7545 201 7 TPG Internet Pty Ltd 7657 192 12 The Internet Group Limited 4763 177 35 Telstra New Zealand 4766 175 620 KORnet Powered BY Korea Telec 4134 173 557 Data Communications Bureau 3462 137 205 Data Communications Institute 4786 131 8 NetConnect Communications Pty 7539 131 82 Delegated to TWNIC for subseq 7586 131 10 Paradox Digital Pty. Ltd 7617 125 46 One.Net Pty Ltd RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 3301 403 330 TeliaNet Sweden 702 397 607 UUNET Technologies, Inc. 1257 290 248 Swipnet AB 3215 274 183 RAIN 1270 272 450 UUNET Germany 680 203 889 Deutschef Forschurgsnetz 719 190 146 LANLINK 786 184 960 JANET IP Service 5515 169 318 Sonera Finland 3320 167 462 Deutsche Telekom AG 1849 149 263 UUNET UK (formerly PIPEX) 1942 139 53 GIP Renater 517 134 136 Xlink 3303 129 277 Swisscom 2856 125 388 BTnet UK Regional network 3352 114 321 Ibernet, Internet A 5400 112 31 Concert Internet Plus Europea 1901 104 77 EUnet Austria 1267 98 986 IUnet S.p.A 2830 89 30 UUNET UK (formerly PIPEX) ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 701 2693 3546 UUNET Technologies, Inc. 1 1000 4549 BBN Planet 7018 921 3024 AT&T 705 781 51 UUNET Technologies, Inc. 7046 724 525 UUNET Technologies, Inc. 1239 645 1554 Sprint ICM-Inria 2914 617 1261 Verio, Inc. 174 613 2808 PSINet Inc. 3561 580 1276 Cable & Wireless USA 3549 540 497 Global Crossing 2551 490 344 NETCOM On-Line Communication 4293 476 58 Cable & Wireless USA 209 468 674 Qwest 3908 394 280 Supernet, Inc. 2548 393 514 Digital Express Group, Inc. 8151 366 197 UniNet S.A. de C.V. 271 350 270 BCnet Backbone 8013 339 63 PSINet Ltd. Canada 690 332 35 Merit Network 11371 327 49 Rhythms NetConnections Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2693 3546 UUNET Technologies, Inc. 1221 2389 1189 Telstra 1 1000 4549 BBN Planet 7018 921 3024 AT&T 705 781 51 UUNET Technologies, Inc. 7046 724 525 UUNET Technologies, Inc. 1239 645 1554 Sprint ICM-Inria 2914 617 1261 Verio, Inc. 174 613 2808 PSINet Inc. 3561 580 1276 Cable & Wireless USA 3549 540 497 Global Crossing 2551 490 344 NETCOM On-Line Communication 4293 476 58 Cable & Wireless USA 209 468 674 Qwest 2764 426 140 connect.com.au pty ltd 3301 403 330 TeliaNet Sweden 703 401 253 UUNET Technologies, Inc. 702 397 607 UUNET Technologies, Inc. 3908 394 280 Supernet, Inc. 2548 393 514 Digital Express Group, Inc. List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 65535 PRIVATE 62.4.68.96/27 6461 AboveNet Communicati 2027 UNALLOCATED 150.185.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.185.128.0/18 8143 Publicom Corp. 2027 UNALLOCATED 150.186.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.187.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.188.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.189.0.0/16 10530 Interpacket Group, I 1877 UNALLOCATED 192.108.196.0/24 1800 SPRINT 1877 UNALLOCATED 192.108.209.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.210.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.214.0/24 1800 SPRINT 5757 UNALLOCATED 192.239.13.0/24 701 UUNET Technologies, 65500 PRIVATE 203.166.86.0/24 10084 Western Australian I 5757 UNALLOCATED 207.19.224.0/24 701 UUNET Technologies, Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 39.96.40.224/30 14408 iCAIR 91.16.23.0/24 11770 Net56 103.22.7.0/24 9768 PubNet (Korea Telecom) Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:23 /9:4 /10:5 /11:9 /12:31 /13:61 /14:201 /15:314 /16:6889 /17:1070 /18:2095 /19:6411 /20:4792 /21:4338 /22:6640 /23:8610 /24:58989 /25:279 /26:352 /27:151 /28:111 /29:76 /30:178 /31:0 /32:153 Number of /24s announced per /8 block (Global) ---------------------------------------------- 9:3 12:311 13:10 15:1 17:1 24:673 26:1 32:6 38:8 44:3 47:1 53:2 55:1 57:8 61:38 62:123 63:1813 64:1375 65:157 66:146 91:1 103:1 128:34 129:110 130:20 131:31 132:11 133:3 134:136 135:8 136:16 137:112 138:239 139:54 140:102 141:35 142:57 143:44 144:193 145:10 146:132 147:92 148:123 149:123 150:24 151:357 152:979 153:35 154:12 155:73 156:29 157:105 158:56 159:78 160:16 161:55 162:60 163:132 164:129 165:114 166:175 167:90 168:81 169:31 170:202 171:2 192:5349 193:1833 194:2014 195:817 196:366 198:3712 199:3422 200:1830 202:2423 203:5177 204:3656 205:2467 206:2777 207:3001 208:2944 209:3345 210:426 211:145 212:818 213:295 214:9 215:11 216:2817 217:132 End of report

1 0

Release of patch for ripe-dbase-3.0beta2 software.
by RIPE NCC Staff 01 Mar '01

01 Mar '01

Dear Colleagues, [Apologies for multiple, identical messages]. This mail is to notify you that today, we have released a patch for the ripe-dbase-3.0beta2 software. This patch has several bug fixes. Specifically, this patch includes, amongst other fixes: - TEMPORARY tables in MySQL 3.23 are supported; - a major memory leak on Solaris 8 has been fixed; - CLIENTADDRESS referral now properly passes addresses; - the "-m" queries work now; - memory allocation bug in dbupdate is fixed; - multiple notification problems have been fixed; - improved acknowledgement and notification message formats. You can download this patch at the following URL: ftp://ftp.ripe.net/ripe/dbase/reimp/ripe-dbase-3.0beta3.patch.gz We remind you that you can also test the functionality of this patch for the RIP whois server in 2 ways: - By querying the host reimp.ripe.net at port 43; you will find there a Near-Real-Time Mirror of the RIPE Database. This mirror is in RPSL format. - By using the RIP Test Database. You can send test updates to this database at the address <auto-rip(a)ripe.net>, and you can query this database at reimp.ripe.net port 4343. We would be very pleased if you could test the patch in both ways, and let us know your opinions. Please send your comments and bug reports to the <db-beta(a)ripe.net> mailing list. To subscribe to this list, send a message to <majordomo(a)ripe.net> with the line: subscribe db-beta in the body of your message. This is a moderated mailing list so some delays in subscription are possible. If you are interested in providing to the community tools and documentation supporting the RIPE-181 to RPSL migration, you are welcome to join the reimp-mig-tf mailing list. To subscribe to this list, follow the instructions given above for subscribing to the db-beta list (doing s/db\-beta/reimp\-mig\-tf/, of course :-). If you have any questions, please contact <ripe-dbm(a)ripe.net>. Regards, A. M. R. Magee ______________ Databse Group RIPE NCC

1 0

Release of patch for ripe-dbase-3.0beta2 software.
by RIPE Database Administration 01 Mar '01

01 Mar '01

Dear Colleagues, [Apologies for multiple mails]. This mail is to notify you that today, we have released a patch for the ripe-dbase-3.0beta2 software. This patch has several bug fixes. Specifically, this patch includes, amongst other fixes: - TEMPORARY tables in MySQL 3.23 are supported; - a major memory leak on Solaris 8 has been fixed; - CLIENTADDRESS referral now properly passes addresses; - the "-m" queries work now; - memory allocation bug in dbupdate is fixed; - multiple notification problems have been fixed; - improved acknowledgement and notification message formats. You can download this patch from the following URL: ftp://ftp.ripe.net/ripe/dbase/reimp/ripe-dbase-3.0beta3.patch.gz We remind you that you can also test the functionality of this patch for the RIP whois server in 2 ways: - By querying the host reimp.ripe.net at port 43; you will find there a Near-Real-Time Mirror of the RIPE Database. This mirror is in RPSL format. - By using the RIP Test Database. You can send test updates to this database at the address <auto-rip(a)ripe.net>, and you can query this database at reimp.ripe.net port 4343. We would be very pleased if you could test the patch in both ways, and let us know your opinions. Please send your comments and bug reports to the <db-beta(a)ripe.net> mailing list. To subscribe to this list, send a message to <majordomo(a)ripe.net> with the line: subscribe db-beta in the body of your letter. This is a moderated mailing list so some delays in subscription are possible. If you are interested in providing to the community tools and documentation supporting the RIPE-181 to RPSL migration, you are welcome to join the reimp-mig-tf mailing list. To subscribe to this list, follow the instructions given above for subscribing to the db-beta list (doing s/db\-beta/reimp\-mig\-tf/, of course :-). If you have any questions, please contact <ripe-dbm(a)ripe.net>. Regards, A. M. R. Magee ______________ Database Group RIPE NCC

1 0