- routing-wg - mailman.ripe.net

RIPE Database Software V3.0 compliance test.
by DB-News 30 Mar '01

30 Mar '01

Dear Colleagues, If you have software that works with RIPE Database Software, then you should make sure that it works with Version 3.0, which will be put into production next month. Compliance tests are available at: http://www.ripe.net/ripencc/pub-services/db/rpsl/usercl.html More information about Version 3.0 of the RIPE Database Software and how it will affect you is available at: http://www.ripe.net/rpsl/ If you have any questions, please contact <ripe-dbm(a)ripe.net>. Regards, A. M. R. Magee -------------- Database Group RIPE NCC

1 0

Weekly Routing Table Report
by Routing Analysis 29 Mar '01

29 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 30 Mar, 2001 Analysis Summary ---------------- BGP routing table entries examined: 102113 Origin ASes present in the Internet Routing Table: 10430 Origin ASes announcing only one prefix: 3741 Transit ASes present in the Internet Routing Table: 1375 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: 17 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: 1214667866 Equivalent to 72 /8s, 102 /16s and 92 /24s Percentage of available address space announced: 32.8 Percentage of allocated address space announced: 64.3 Percentage of available address space allocated: 51.0 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 15583 Prefixes being announced from the APNIC address blocks: 14173 APNIC Region origin ASes present in the Internet Routing Table: 1211 APNIC Region origin ASes announcing only one prefix: 435 APNIC Region transit ASes present in the Internet Routing Table: 198 Average APNIC Region AS path length visible: 5.1 Max APNIC Region AS path length visible: 15 Number of APNIC addresses announced to Internet: 69169775 Equivalent to 4 /8s, 31 /16s and 114 /24s Percentage of available APNIC address space announced: 68.0 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: 70655 Prefixes being announced from the ARIN address blocks: 47994 ARIN Region origin ASes present in the Internet Routing Table: 6353 ARIN Region origin ASes announcing only one prefix: 1858 ARIN Region transit ASes present in the Internet Routing Table: 651 Average ARIN Region AS path length visible: 5.2 Max ARIN Region AS path length visible: 14 Number of ARIN addresses announced to Internet: 179855217 Equivalent to 10 /8s, 184 /16s and 95 /24s Percentage of available ARIN address space announced: 82.5 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: 15858 Prefixes being announced from the RIPE address blocks: 12560 RIPE Region origin ASes present in the Internet Routing Table: 2866 RIPE Region origin ASes announcing only one prefix: 1448 RIPE Region transit ASes present in the Internet Routing Table: 524 Average RIPE Region AS path length visible: 6.0 Max RIPE Region AS path length visible: 15 Number of RIPE addresses announced to Internet: 93806295 Equivalent to 5 /8s, 151 /16s and 94 /24s Percentage of available RIPE address space announced: 79.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 20480 - 21503 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 2083 692 Telstra 703 451 264 UUNET Technologies, Inc. 2764 429 139 connect.com.au pty ltd 2907 373 892 SINET Japan 4755 296 110 VSNL India 4538 244 1032 China Education and Research 9269 206 24 Hong Kong CTI 7474 195 86 Optus Communications 4134 182 603 Data Communications Bureau 4763 179 35 Telstra New Zealand 4766 178 626 KORnet Powered BY Korea Telec 1237 168 71 System Engineering Research I 7657 164 12 The Internet Group Limited 7545 150 10 TPG Internet Pty Ltd 4740 145 10 Ozemail 3462 138 205 Data Communications Institute 4786 128 7 NetConnect Communications Pty 4713 126 427 NTT-OCNET 7539 124 38 Delegated to TWNIC for subseq 7617 123 46 One.Net Pty Ltd RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 702 417 624 UUNET Technologies, Inc. 3301 395 329 TeliaNet Sweden 1257 287 248 Swipnet AB 1270 276 455 UUNET Germany 680 208 913 Deutschef Forschurgsnetz 3215 202 227 RAIN 5515 191 335 Sonera Finland 719 190 146 LANLINK 786 183 959 JANET IP Service 3320 157 454 Deutsche Telekom AG 1849 149 255 UUNET UK (formerly PIPEX) 517 128 134 Xlink 3303 124 298 Swisscom 5400 124 33 Concert Internet Plus Europea 2856 122 388 BTnet UK Regional network 8708 105 5 Romania Data System 1901 99 77 EUnet Austria 1267 98 979 IUnet S.p.A 2830 95 38 UUNET UK (formerly PIPEX) 1290 85 205 PSINet UK Ltd. ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 701 2442 3623 UUNET Technologies, Inc. 705 1183 55 UUNET Technologies, Inc. 1 968 4504 BBN Planet 7018 948 3057 AT&T 7046 803 544 UUNET Technologies, Inc. 1239 636 1600 Sprint ICM-Inria 2914 610 1222 Verio, Inc. 174 582 2777 PSINet Inc. 3561 558 1240 Cable & Wireless USA 3549 540 496 Global Crossing 4293 477 52 Cable & Wireless USA 209 450 723 Qwest 690 404 64 Merit Network 2548 397 514 Digital Express Group, Inc. 3908 378 270 Supernet, Inc. 8112 370 64 Bell Atlantic Internet Soluti 4323 338 136 Time Warner Communications, I 8151 329 191 UniNet S.A. de C.V. 11371 329 49 Rhythms NetConnections 3967 328 222 Exodus Communication Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2442 3623 UUNET Technologies, Inc. 1221 2083 692 Telstra 705 1183 55 UUNET Technologies, Inc. 1 968 4504 BBN Planet 7018 948 3057 AT&T 7046 803 544 UUNET Technologies, Inc. 1239 636 1600 Sprint ICM-Inria 2914 610 1222 Verio, Inc. 174 582 2777 PSINet Inc. 3561 558 1240 Cable & Wireless USA 3549 540 496 Global Crossing 4293 477 52 Cable & Wireless USA 703 451 264 UUNET Technologies, Inc. 209 450 723 Qwest 2764 429 139 connect.com.au pty ltd 702 417 624 UUNET Technologies, Inc. 690 404 64 Merit Network 2548 397 514 Digital Express Group, Inc. 3301 395 329 TeliaNet Sweden 3908 378 270 Supernet, Inc. List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 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, 65008 PRIVATE 193.48.190.0/24 2200 INRIA-Rocquencourt 65008 PRIVATE 193.49.4.0/24 2200 INRIA-Rocquencourt 65008 PRIVATE 194.167.0.0/24 2200 INRIA-Rocquencourt 65535 PRIVATE 203.24.169.0/24 17486 Swiftel Communicatio 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 106.1.1.0/24 5705 Sirius Solutions, Inc. 106.1.2.0/24 5705 Sirius Solutions, Inc. Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:21 /9:4 /10:4 /11:9 /12:30 /13:64 /14:202 /15:328 /16:6907 /17:1108 /18:2079 /19:6515 /20:4962 /21:4391 /22:6761 /23:8638 /24:58825 /25:269 /26:345 /27:146 /28:111 /29:73 /30:160 /31:1 /32:160 Number of /24s announced per /8 block (Global) ---------------------------------------------- 9:3 12:340 13:10 15:1 17:1 24:687 26:1 32:10 38:7 44:3 47:1 53:2 55:1 57:9 61:41 62:134 63:1883 64:1429 65:541 66:209 91:1 106:2 128:31 129:122 130:21 131:24 132:11 133:1 134:147 135:8 136:16 137:114 138:246 139:52 140:106 141:174 142:55 143:150 144:35 145:11 146:134 147:92 148:143 149:136 150:25 151:362 152:968 153:33 154:13 155:75 156:37 157:107 158:59 159:79 160:17 161:56 162:90 163:134 164:134 165:118 166:173 167:90 168:81 169:31 170:220 171:2 192:5350 193:1827 194:2038 195:774 196:381 198:3619 199:3364 200:1876 202:2435 203:4976 204:3374 205:2241 206:2747 207:2793 208:2932 209:3183 210:487 211:169 212:810 213:351 214:8 215:11 216:2865 217:165 End of report

1 0

RE: Another issue related to the migration
by Hallgren, Michael 29 Mar '01

29 Mar '01

Hi, > > > Dear Colleagues, [...] > > Our suggestion how to deal with these objects is: > > 1. Send a message to the maintainers of these objects asking > them to change the > name to avoid conflict with RPSL specification. > 2. Give two-week notice period after which ripe-dbm will > convert non compliant > as-names using the following mapping: AS-ASNAME -> AS_ASNAME. > > This is more a "cosmetic" change as as-name is not even a > lookup key in the RIPE > Database. Yes. Agree. Been hinting customers to trash/modify such names prior to migration date - not knowing whether or not such conflict would be treated auto-magically... Regards Michael > > Your comments and suggestions are appreciated. > > Best regards, > > > Andrei Robachevsky > DB Group Manager > RIPE NCC > -- Michael Hallgren, Eng., Teleglobe, MH2198-RIPE

1 0

Another issue related to the migration
by Andrei Robachevsky 29 Mar '01

29 Mar '01

Dear Colleagues, [Apologies for duplicate messages] One issue related to RIPE-181 to RPSL migration escaped our attention and has not been discussed. It is related to reserved prefixes that cannot appear in object names according to RPSL specification (RFC2622) which says: "Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names." Unfortunately "as-name:" attribute is an object name in RPSL and we have 133 aut-num objects with as-name starting with reserved 'AS-' prefix. Our suggestion how to deal with these objects is: 1. Send a message to the maintainers of these objects asking them to change the name to avoid conflict with RPSL specification. 2. Give two-week notice period after which ripe-dbm will convert non compliant as-names using the following mapping: AS-ASNAME -> AS_ASNAME. This is more a "cosmetic" change as as-name is not even a lookup key in the RIPE Database. Your comments and suggestions are appreciated. Best regards, Andrei Robachevsky DB Group Manager RIPE NCC

1 0

The Cidr Report
by Tony Bates 24 Mar '01

24 Mar '01

This is an auto-generated mail on Fri Mar 23 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 23Mar01 0) General Status Table History ------------- Date Prefixes 160301 97900 170301 98013 180301 97932 190301 97895 200301 97452 210301 97740 220301 97971 230301 98100 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- AS Summary ---------- Number of ASes in routing system: 6535 Number of ASes announcing only one prefix: 2606 (0 cidr, 2606 classful) Largest number of cidr routes: 0 announced by Largest number of classful routes: 1521 announced by AS1221 1) Gains by aggregating at the origin AS level --- 23Mar01 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS1221 1521 1147 374 24.6% Telstra Pty Ltd AS701 1433 1266 167 11.7% UUNET Technologies, Inc. AS9269 162 53 109 67.3% Internet service Provider in Hong AS6595 165 63 102 61.8% DoD Education Activity Network As AS6429 209 109 100 47.8% RdC Internet AS4151 255 156 99 38.8% USDA AS13999 104 8 96 92.3% Mega Cable S.A. de C.V. AS705 334 241 93 27.8% UUNET Technologies, Inc. AS4293 367 279 88 24.0% Cable & Wireless USA AS8013 317 233 84 26.5% PSINet Ltd. Canada AS7018 663 584 79 11.9% AT&T AS4755 211 136 75 35.5% Videsh Sanchar Nigam Ltd. Autonom AS577 234 165 69 29.5% Bell Advanced Communications Inc. AS5106 101 37 64 63.4% Ameritech Advanced Data Services, AS3464 153 91 62 40.5% Alabama SuperComputer Network AS724 211 150 61 28.9% DLA Systems Automation Center AS3749 119 60 59 49.6% Tennessee Board of Regents AS9498 74 17 57 77.0% BHARTI BT INTERNET LTD. AS16758 63 6 57 90.5% IKON Office Solutions AS6413 67 11 56 83.6% Southern Online Systems, Inc. AS4323 233 177 56 24.0% Time Warner Communications, Inc. AS376 133 77 56 42.1% Reseau Interordinateurs Scientiqu AS226 149 93 56 37.6% Los Nettos AS174 460 404 56 12.2% PSINet Inc. AS11170 60 4 56 93.3% Bewell Net AS7568 83 28 55 66.3% C.S. Communications Co., Ltd. AS1 604 550 54 8.9% BBN Planet AS6471 99 46 53 53.5% ENTEL CHILE S.A. AS11252 89 36 53 59.6% ISU Computer Center Bldg. 5 AS7657 140 89 51 36.4% The Internet Group Limited 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: Weekly Routing Table Report
by Philip Smith 23 Mar '01

23 Mar '01

At 04:03 23/03/2001 +1000, Routing Analysis wrote: >List of Unregistered ASNs (Global) >---------------------------------- > >Bad AS Designation Network Transit AS Description >20516 UNALLOCATED 192.117.224.0/21 8513 ITD Israel >20486 UNALLOCATED 193.178.213.0/24 9085 SUPER MEDIA Autonomo >20508 UNALLOCATED 213.88.96.0/22 12909 Ics.IP SpA >20507 UNALLOCATED 217.149.192.0/20 702 UUNET Technologies, >20483 UNALLOCATED 217.150.0.0/20 9110 AG TELECOM AS Russia >20521 UNALLOCATED 217.168.160.0/20 15735 Datastream internati Ooops, sorry about that, I only caught RIPE NCC's new AS block today, a bit too late for the report going out. Future ones are now fixed. philip --

1 0

RE: Summary of the Migration issues
by Lu, Ping 21 Mar '01

21 Mar '01

Some questions followed. Ping Lu Cable & Wireless Global Network Tools and Analysis Group, USA W: +1-703-292-2359 E: plu(a)cw.net [snip] > ---------------------------------------- > 1. Route object creation (RFC2725 implications) > > In order to create route object in the RIPE DB, one needs to have > corresponding objects (inetnum or less specific route, and > aut-num) and > pass proper authorization from these objects. > > The problem occurs when someone needs to register route > object which has > either prefix, or origin, or the both from non RIPE IP/ASN space. > > Proposed solution: > 1.1 An as-block object(s) encompassing the non RIPE ASN space will be > created with "mnt-lower:" protected by mntner with NONE auth. > > 1.2 An encompassing inetnum object with "mnt-routes:" protected by > mntner with NONE auth will be created. This will eliminate need for > corresponding inetnum creation and will reduce amount of redundant > information. > > 1.3 In case origin of a route object being created is from non RIPE > space, users will need to create corresponding aut-num object in the > RIPE DB. > Does 1.3 means RIPE is going accept non-RIPE aut-num(AN) object thus a mntner(MT) object to protect that AN thus some person(PN) objects associated with that MT ? And is RIPE going to allow the NONE auth specified in 1.1 and 1.2 to be changed to a real MT once the rightful holder created them ? > > 2. Updates in RIPE-181 format > How about the ftp mirror ? Will RIPE-181 format text files still be available to download after April 23, 2001 or just the RPSL format text files ? [big cut for the rest]

2 1

The Cidr Report
by Tony Bates 21 Mar '01

21 Mar '01

This is an auto-generated mail on Fri Mar 16 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 16Mar01 0) General Status Table History ------------- Date Prefixes 090301 98107 100301 97522 110301 97508 120301 97530 130301 97798 140301 98013 150301 98259 160301 97900 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: 10240 Number of ASes announcing only one prefix: 6004 (3405 cidr, 2599 classful) Largest number of cidr routes: 957 announced by AS701 Largest number of classful routes: 1594 announced by AS1221 1) Gains by aggregating at the origin AS level --- 16Mar01 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS1221 1594 1194 400 25.1% Telstra Pty Ltd AS701 1417 1256 161 11.4% UUNET Technologies, Inc. AS6499 170 60 110 64.7% Brooks Fiber Properties, Inc. AS9269 162 53 109 67.3% Internet service Provider in Hong AS6429 212 107 105 49.5% RdC Internet AS6595 161 62 99 61.5% DoD Education Activity Network As AS7545 169 76 93 55.0% TPG Internet Pty Ltd AS705 329 237 92 28.0% UUNET Technologies, Inc. AS4293 376 285 91 24.2% Cable & Wireless USA AS13999 102 11 91 89.2% Mega Cable S.A. de C.V. AS8013 326 242 84 25.8% PSINet Ltd. Canada AS7018 654 575 79 12.1% AT&T AS4151 226 148 78 34.5% USDA AS4755 207 133 74 35.7% Videsh Sanchar Nigam Ltd. Autonom AS577 239 169 70 29.3% Bell Advanced Communications Inc. AS724 222 155 67 30.2% DLA Systems Automation Center AS174 495 428 67 13.5% PSINet Inc. AS9498 83 18 65 78.3% BHARTI BT INTERNET LTD. AS5106 101 37 64 63.4% Ameritech Advanced Data Services, AS11170 64 1 63 98.4% Bewell Net AS3749 120 59 61 50.8% Tennessee Board of Regents AS3464 153 92 61 39.9% Alabama SuperComputer Network AS7657 163 103 60 36.8% The Internet Group Limited AS16758 63 6 57 90.5% IKON Office Solutions AS6413 67 11 56 83.6% Southern Online Systems, Inc. AS4323 233 177 56 24.0% Time Warner Communications, Inc. AS376 133 77 56 42.1% Reseau Interordinateurs Scientiqu AS226 149 93 56 37.6% Los Nettos AS1 605 550 55 9.1% BBN Planet AS6471 99 46 53 53.5% ENTEL CHILE S.A. 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

3 2

Re: Summary of the Migration issues
by Andrei Robachevsky 20 Mar '01

20 Mar '01

Dear Colleagues, [Apologies for duplicate messages] Please let me answer some of your questions. Frank Bohnsack asked: >> 1.3 In case origin of a route object being created is from non RIPE >> space, users will need to create corresponding aut-num object in the >> RIPE DB. > > * Means that, all non RIPE IP/ASN space is available on 23 of April as default > or should we send an request if needed ? > Non RIPE IP space will be protected by the encompassing inetnum object. There is no need to create a corresponding inetnum object in case of "foreign" route creation. In case 1.3 people will be able to create a corresponding aut-num object themselves. > * Should we still use the human mail interface for "aut-num" and "mntner" > creations on 23 of April ? > Yes. Except for aut-num creations in non RIP ASN space (case 1.3), when the request should be sent to <auto-dbm(a)ripe.net> or <auto-rpsl(a)ripe.net>. > * Can we assume that the database on 23 of April is the same like the current > RPSL mirror ? > RPSL mirror is being kept in sync with the production RIPE Database. That means the contents of the both databases is the same. This will slightly change at the beginning of April when we plan to begin final pre production phase. Several objects (like as-block, encompassing inetnum) will be added to RPSL database. In a few days we are going to present a detailed migration plan, and your comments are highly appreciated. Ernesto Baschny asked: > > PGP authorization scheme will not work with <auto-dbm(a)ripe.net> robot > > after 23 April. Updates requiring PGP auth should be sent directly to > > <auto-rpsl(a)ripe.net>. > > Does that refer only to route/inetnum objects, or to all (also > person-objects)? If so, can person-objects already be created > using the adress auto-rpsl(a)ripe.net the same way we used the > auto-dbm(a)ripe.net (with PGP)? This restriction applies to all updates/objects sent in RIPE-181 format to <auto-dbm(a)ripe.net>. So if you are using PGP authorization, starting from 23 of April you should send your updates to <auto-rpsl(a)ripe.net> in RPSL format. To avoid confusion <auto-rpsl(a)ripe.net> will not be valid until April 23. Best regards, Andrei Robachevsky DB Group Manager RIPE NCC

1 0

Summary of the Migration issues
by Andrei Robachevsky 19 Mar '01

19 Mar '01

Dear Colleagues, Please let me summarize the migration issues that have been discussed already and highlight some issues that require more attention. Best regards, Andrei Robachevsky DB Group Manager RIPE NCC ---------------------------------------- 1. Route object creation (RFC2725 implications) In order to create route object in the RIPE DB, one needs to have corresponding objects (inetnum or less specific route, and aut-num) and pass proper authorization from these objects. The problem occurs when someone needs to register route object which has either prefix, or origin, or the both from non RIPE IP/ASN space. Proposed solution: 1.1 An as-block object(s) encompassing the non RIPE ASN space will be created with "mnt-lower:" protected by mntner with NONE auth. 1.2 An encompassing inetnum object with "mnt-routes:" protected by mntner with NONE auth will be created. This will eliminate need for corresponding inetnum creation and will reduce amount of redundant information. 1.3 In case origin of a route object being created is from non RIPE space, users will need to create corresponding aut-num object in the RIPE DB. 2. Updates in RIPE-181 format Migration plan allows users to send updates in RIPE-181 format for some time (until May 14th to <auto-dbm(a)ripe.net>, from May 14th till October 15th to <auto-181(a)ripe.net>) after the migration. In such case objects are automatically converted to RPSL. However the switchover to the new version of the RIPE Database occurs on 23 of April, and since then the following constraints will apply: 2.1 PGP authentication PGP authorization scheme will not work with <auto-dbm(a)ripe.net> robot after 23 April. Updates requiring PGP auth should be sent directly to <auto-rpsl(a)ripe.net>. The problem occurs because after ripe181->RPSL transformation it is impossible to verify signature. For this reason, some updates requiring PGP auth may be rejected during migration. It advisable not to send such updates from 22 April, 9a.m. till 23 April 9a.m. 2.2 New syntax rules When processing an object after ripe181->RPSL conversion new v3.0 syntax rules apply. The results of this will be: - empty attributes (i.e. having no value) are not allowed; - some attributes that were optional before are now mandatory; Also some undocumented behaviour of the v2.x Database will not be supported, namely: - attribute aliases (please see list of aliases attached) are not allowed; - inetnum object cannot be specified in prefix notation. 2.3 New authorization rules New authorization rules defined by RFC2725 apply to creation of aut-num and route objects. See 1. 3. Objects with names containing reserved RPSL prefixes They will be renamed on 2 of April. All references will be updated accordingly. Currently there are 6 of them in the RIPE Database. mntner: AS-5532MNTB mntner: AS-NETLINK-MNT mntner: AS-THENET-MNT mntner: AS-NEW1-MNT mntner: RS-MNT mntner: AS-MNT 4. Broken PGP certificates. They will be deleted on 2 of April. ---------------------- v2.x attribute aliases (not supported in v3.0!): Alias Attrbute change -> changed email -> e-mail fax -> fax-no remark -> remarks deleted -> delete asname -> as-name rev-svr -> rev-srv network -> inetnum netnum -> inetnum

2 1