- routing-wg - mailman.ripe.net

The Cidr Report
by Tony Bates 11 Mar '01

11 Mar '01

This is an auto-generated mail on Fri Mar 9 23:00:00 PST 2001 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 09Mar01 0) General Status Table History ------------- Date Prefixes 020301 97761 030301 97965 040301 99978 050301 97915 060301 98487 070301 98007 080301 97909 090301 98107 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 91.16.23.0/24 from AS11770 AS Summary ---------- Number of ASes in routing system: 10176 Number of ASes announcing only one prefix: 5971 (3385 cidr, 2586 classful) Largest number of cidr routes: 954 announced by AS701 Largest number of classful routes: 1612 announced by AS1221 1) Gains by aggregating at the origin AS level --- 09Mar01 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS1221 1612 1211 401 24.9% Telstra Pty Ltd AS2764 754 539 215 28.5% connect.com.au pty ltd AS701 1416 1258 158 11.2% UUNET Technologies, Inc. AS8006 145 19 126 86.9% Systems & Software Consortium, In AS7545 190 70 120 63.2% TPG Internet Pty Ltd AS9269 162 53 109 67.3% Internet service Provider in Hong AS6429 213 107 106 49.8% RdC Internet AS6595 161 62 99 61.5% DoD Education Activity Network As AS705 331 238 93 28.1% UUNET Technologies, Inc. AS4293 380 287 93 24.5% Cable & Wireless USA AS13999 102 11 91 89.2% Mega Cable S.A. de C.V. AS8013 324 238 86 26.5% PSINet Ltd. Canada AS4151 229 147 82 35.8% USDA AS7018 648 569 79 12.2% AT&T AS4755 209 130 79 37.8% Videsh Sanchar Nigam Ltd. Autonom AS1942 136 64 72 52.9% FR-CICG-GRENOBLE AS816 386 315 71 18.4% UUNET Canada AS577 240 170 70 29.2% Bell Advanced Communications Inc. AS174 496 428 68 13.7% PSINet Inc. AS724 214 148 66 30.8% DLA Systems Automation Center AS5106 101 37 64 63.4% Ameritech Advanced Data Services, AS11170 64 1 63 98.4% Bewell Net AS7657 169 108 61 36.1% The Internet Group Limited AS3749 120 59 61 50.8% Tennessee Board of Regents AS3464 153 93 60 39.2% Alabama SuperComputer Network AS226 154 94 60 39.0% Los Nettos AS376 133 76 57 42.9% Reseau Interordinateurs Scientiqu AS16758 63 6 57 90.5% IKON Office Solutions AS6413 67 11 56 83.6% Southern Online Systems, Inc. AS7568 83 28 55 66.3% C.S. Communications Co., Ltd. For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report

2 1

Manual for installing the RAToolSet?
by stijn.deklerk＠bt.com 09 Mar '01

09 Mar '01

Hello, I'm trying to use you RAToolSet. Unfortunately I can't seem to be able to find a installation procedure anywhere. I got the lot un gzipped un Tarred, and established internet connectivity. When I start any executable in the opt/RAToolSet/bin, a process is being started, but nothing happens, not even an error message is displayed. Hope you can enlighten me. Thanks, Cheers Stijn de Klerk

2 1

Weekly Routing Table Report
by Routing Analysis 08 Mar '01

08 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 09 Mar, 2001 Analysis Summary ---------------- BGP routing table entries examined: 101587 Origin ASes present in the Internet Routing Table: 10242 Origin ASes announcing only one prefix: 3665 Transit ASes present in the Internet Routing Table: 1374 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 15 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: 2 Number of addresses announced to Internet: 1244351344 Equivalent to 74 /8s, 43 /16s and 75 /24s Percentage of available address space announced: 33.6 Percentage of allocated address space announced: 65.8 Percentage of available address space allocated: 51.0 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 15875 Prefixes being announced from the APNIC address blocks: 14211 APNIC Region origin ASes present in the Internet Routing Table: 1190 APNIC Region origin ASes announcing only one prefix: 428 APNIC Region transit ASes present in the Internet Routing Table: 197 Average APNIC Region AS path length visible: 5.0 Max APNIC Region AS path length visible: 14 Number of APNIC addresses announced to Internet: 67053608 Equivalent to 3 /8s, 255 /16s and 40 /24s Percentage of available APNIC address space announced: 65.9 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: 69945 Prefixes being announced from the ARIN address blocks: 47720 ARIN Region origin ASes present in the Internet Routing Table: 6241 ARIN Region origin ASes announcing only one prefix: 1824 ARIN Region transit ASes present in the Internet Routing Table: 655 Average ARIN Region AS path length visible: 5.2 Max ARIN Region AS path length visible: 14 Number of ARIN addresses announced to Internet: 211929698 Equivalent to 12 /8s, 161 /16s and 202 /24s Percentage of available ARIN address space announced: 97.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: 15753 Prefixes being announced from the RIPE address blocks: 12466 RIPE Region origin ASes present in the Internet Routing Table: 2810 RIPE Region origin ASes announcing only one prefix: 1413 RIPE Region transit ASes present in the Internet Routing Table: 520 Average RIPE Region AS path length visible: 6.0 Max RIPE Region AS path length visible: 15 Number of RIPE addresses announced to Internet: 92205759 Equivalent to 5 /8s, 126 /16s and 242 /24s Percentage of available RIPE address space announced: 78.5 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 2375 679 Telstra 2764 474 141 connect.com.au pty ltd 703 401 253 UUNET Technologies, Inc. 2907 378 909 SINET Japan 4755 297 112 VSNL India 4740 273 17 Ozemail 4538 264 1055 China Education and Research 9269 205 24 Hong Kong CTI 7545 201 7 TPG Internet Pty Ltd 7474 200 87 Optus Communications 7657 198 12 The Internet Group Limited 4763 177 35 Telstra New Zealand 4134 176 570 Data Communications Bureau 4766 175 620 KORnet Powered BY Korea Telec 3462 137 205 Data Communications Institute 7539 137 91 Delegated to TWNIC for subseq 4786 134 8 NetConnect Communications Pty 7586 129 10 Paradox Digital Pty. Ltd 9797 128 8 Asia Online Australia 7617 124 46 One.Net Pty Ltd RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 702 404 629 UUNET Technologies, Inc. 3301 399 321 TeliaNet Sweden 1257 288 248 Swipnet AB 1270 273 451 UUNET Germany 3215 248 190 RAIN 680 204 889 Deutschef Forschurgsnetz 5515 195 343 Sonera Finland 719 190 146 LANLINK 786 183 959 JANET IP Service 3320 166 462 Deutsche Telekom AG 1849 148 255 UUNET UK (formerly PIPEX) 1942 139 53 GIP Renater 517 131 136 Xlink 3303 131 286 Swisscom 2856 123 388 BTnet UK Regional network 5400 114 32 Concert Internet Plus Europea 1267 97 978 IUnet S.p.A 1901 96 69 EUnet Austria 2830 89 30 UUNET UK (formerly PIPEX) 3269 86 275 TELECOM ITALIA ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 701 2373 3684 UUNET Technologies, Inc. 1 997 4549 BBN Planet 7018 925 3043 AT&T 705 875 46 UUNET Technologies, Inc. 7046 719 525 UUNET Technologies, Inc. 1239 641 1573 Sprint ICM-Inria 174 616 2800 PSINet Inc. 2914 612 1252 Verio, Inc. 3561 574 1267 Cable & Wireless USA 3549 554 534 Global Crossing 4293 479 58 Cable & Wireless USA 209 463 675 Qwest 816 425 74 UUNET Canada4 2548 398 515 Digital Express Group, Inc. 3908 375 277 Supernet, Inc. 8151 365 197 UniNet S.A. de C.V. 8013 337 62 PSINet Ltd. Canada 690 329 19 Merit Network 11371 327 49 Rhythms NetConnections 3967 322 221 Exodus Communication Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 1221 2375 679 Telstra 701 2373 3684 UUNET Technologies, Inc. 1 997 4549 BBN Planet 7018 925 3043 AT&T 705 875 46 UUNET Technologies, Inc. 7046 719 525 UUNET Technologies, Inc. 1239 641 1573 Sprint ICM-Inria 174 616 2800 PSINet Inc. 2914 612 1252 Verio, Inc. 3561 574 1267 Cable & Wireless USA 3549 554 534 Global Crossing 4293 479 58 Cable & Wireless USA 2764 474 141 connect.com.au pty ltd 209 463 675 Qwest 816 425 74 UUNET Canada4 702 404 629 UUNET Technologies, Inc. 703 401 253 UUNET Technologies, Inc. 3301 399 321 TeliaNet Sweden 2548 398 515 Digital Express Group, Inc. 2907 378 909 SINET Japan 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 91.16.23.0/24 11770 Net56 100.100.100.0/24 9318 AS Object of HANARO Telecom i 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:4 /11:9 /12:31 /13:62 /14:203 /15:318 /16:6904 /17:1085 /18:2046 /19:6434 /20:4853 /21:4352 /22:6679 /23:8586 /24:58696 /25:280 /26:350 /27:156 /28:111 /29:65 /30:184 /31:0 /32:152 Number of /24s announced per /8 block (Global) ---------------------------------------------- 9:3 12:317 13:10 15:1 24:674 26:1 32:5 38:8 44:3 47:1 53:2 55:1 57:8 61:39 62:123 63:1836 64:1426 65:225 66:166 91:1 100:1 128:30 129:105 130:20 131:32 132:11 133:3 134:138 135:8 136:16 137:112 138:239 139:54 140:103 141:26 142:58 143:45 144:189 145:9 146:133 147:90 148:123 149:132 150:26 151:358 152:949 153:35 154:12 155:72 156:31 157:106 158:58 159:76 160:16 161:55 162:60 163:134 164:129 165:122 166:174 167:90 168:80 169:30 170:205 171:2 192:5353 193:1824 194:2029 195:812 196:388 198:3699 199:3344 200:1836 202:2439 203:5108 204:3517 205:2355 206:2745 207:2852 208:2931 209:3367 210:499 211:165 212:793 213:299 214:9 215:11 216:2845 217:129 End of report

1 0

Announcement: Hardware upgrade of whois server
by RIPE Database Administration 07 Mar '01

07 Mar '01

Dear colleagues, After experiencing performance slow-down on our whois service, we decided to upgrade the hardware of our primary whois server. The upgrade will take place on 9 March, 2001, Friday. It will start at 8:00am CET and planned to last approximately 2 hours. During the operation, whois queries will be directed to our secondary server and the incoming update messages will be queued, to be processed later. We apologize for any inconvenience this may cause. Regards, Engin Gunduz ____________________________ RIPE Database Administration.

2 1

RIPE RPSL transition date set!
by SchmitzJo＠aol.com 05 Mar '01

05 Mar '01

Hello all, following up on our last call for comments on the RPSL transition for the RIPE database, we did not receive any mails or information which may have delayed the transition. In contrast, we received a set of supportive mails. Accordingly, the transition to RPSL will now follow the outlined dates: o 23-Apr-2001: switching to the RPSL database *** now set *** - 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 We will continue to update you prior to the dates detailed above. Thanks - the RIPE NCC and the chairmen of Routing: Joachim Schmitz DB: Wilfried Woeber LIR: Hans Peter Holen

1 2

The Cidr Report
by Tony Bates 03 Mar '01

03 Mar '01

This is an auto-generated mail on Fri Mar 2 23:00:00 PST 2001 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 02Mar01 0) General Status Table History ------------- Date Prefixes 230201 96158 240201 96768 250201 96770 260201 97876 270201 97797 280201 98047 010301 97829 020301 97761 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 91.16.23.0/24 from AS11770 *** Bogus 103.22.7.0/24 from AS9768 AS Summary ---------- Number of ASes in routing system: 10115 Number of ASes announcing only one prefix: 5957 (3388 cidr, 2569 classful) Largest number of cidr routes: 957 announced by AS701 Largest number of classful routes: 1715 announced by AS701 1) Gains by aggregating at the origin AS level --- 02Mar01 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS1221 1584 1187 397 25.1% Telstra Pty Ltd AS701 1715 1501 214 12.5% UUNET Technologies, Inc. AS8006 145 19 126 86.9% Systems & Software Consortium, In AS7545 190 70 120 63.2% TPG Internet Pty Ltd AS9269 161 52 109 67.7% Internet service Provider in Hong AS6429 213 108 105 49.3% RdC Internet AS6595 165 63 102 61.8% DoD Education Activity Network As AS13999 109 7 102 93.6% Mega Cable S.A. de C.V. AS4293 384 291 93 24.2% Cable & Wireless USA AS271 197 107 90 45.7% University of British Columbia AS8013 330 243 87 26.4% PSINet Ltd. Canada AS705 327 240 87 26.6% UUNET Technologies, Inc. AS4755 213 130 83 39.0% Videsh Sanchar Nigam Ltd. Autonom AS4151 219 142 77 35.2% USDA AS1942 136 64 72 52.9% FR-CICG-GRENOBLE AS7018 642 571 71 11.1% AT&T AS1727 176 105 71 40.3% Commander Naval Surface force US AS577 238 168 70 29.4% Bell Advanced Communications Inc. AS174 494 426 68 13.8% PSINet Inc. AS9498 87 20 67 77.0% BHARTI BT INTERNET LTD. AS724 215 149 66 30.7% DLA Systems Automation Center AS5106 101 37 64 63.4% Ameritech Advanced Data Services, AS11170 64 1 63 98.4% Bewell Net AS7046 312 250 62 19.9% UUNET Technologies, Inc. AS3749 119 58 61 51.3% Tennessee Board of Regents AS3464 153 93 60 39.2% Alabama SuperComputer Network AS226 154 94 60 39.0% Los Nettos AS7657 166 109 57 34.3% The Internet Group Limited AS16758 63 6 57 90.5% IKON Office Solutions AS6413 67 11 56 83.6% Southern Online Systems, Inc. For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report

1 0

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