- routing-wg - mailman.ripe.net

Re: RIS Query
by Jacques Caron 08 Jun '00

08 Jun '00

Hi, At 21:20 06/06/00, Henk Uijterwaal (RIPE-NCC) wrote: >One thing we can do is add a query with a field "AS-PATH", you enter >network, peer, data and time, and the output would be something like: > >[...] >A 193.0.0.0/8 17/11/1999 206.251.0.85 3549 1740 11127 8708 >A 193.0.0.0/8 17/11/1999 193.0.0.56 3333 286 1740 11127 8708 >A 193.0.0.0/8 17/11/1999 195.8.100.22 8259 5413 1740 11127 8708 >A 193.0.0.0/8 17/11/1999 193.0.0.56 3333 1103 6453 1239 1785 11127 8708 >[...] > >If you had entered "11127" as the AS path, it would select all records, if >you had entered "1740 11127", then the first 3 will be highlighted, etc. The idea would be to have a table representation, with lines representing changes (updates) over time, and columns, representing peers. In the above case, with an input of "AS1=1740" and "AS2=1785", one might have: Date & Time |206.251.0.85|193.0.0.56|195.8.100.22|1740|1785 17/11/1999 01:23|1740 |1740 |1740 |3 |0 17/11/1999 02:34|1740 |1785 |1740 |2 |1 Of course, colours instead of 1740 and 1785 would be great :-) This way, one can see very quickly see which of multiple paths is used to get to a specific network among a large selection of peers, and how that changes over time (with the introduction of a new transit provider or of a new peering connection, with AS padding changes, etc.). It's just a more synthetic view of the current output, which only lists the updates themselves. While I'm at RIS-related matters, have you ever though about "reproducing" the recorded BGP updates? This could be useful for testing purposes: a real life sample of BGP updates from a wide selection of peers is always better than an always too simple lab setup... Some kind of "delayed playback". Might also be useful to reproduce known past "events"... Jacques. --- Jacques Caron PSINetworks Europe Network Engineer PSINet Europe Regional Peering Coordinator Planete.net IT Manager Mail: 8/10 rue Nieuport - 78140 Velizy - France Phone: +33 (0)1 34 63 19 71 - Fax: +33 (0)1 34 63 19 51

2 1

RIS
by Jacques Caron 06 Jun '00

06 Jun '00

Hi again, I guess another view might be interesting: have one column per peer (with the ability to select a subset of peers, of course), a line per update, and then in each "cell" the AS path received from that peer (if any). This enables to see which path is adopted by several peers for a multihomed network. Another option would be to be able to give an AS to "grep" into the AS paths, and show which cells contain it or not (or the same thing with several ASes and colored cells). Not sure this is very clear, so I'll give an example. Let's say network N is multihomed to two transit providers AS1 and AS2. Now, I want to see which path is taken from multiple locations to this network. I would input network N, peers A, B, C, D, the two ASes AS1 and AS2 and start/end times. Then it woud output a table with columns A, B C and D, a line per update, and on each line, a different color depending on whether the route received from that peer contains AS1 or AS2 (or both, or none, maybe). Optionally, an additional column giving the proportion of peers using AS1 or AS2 could be interesting. Sounds like a good idea? Jacques. --- Jacques Caron PSINetworks Europe Network Engineer PSINet Europe Regional Peering Coordinator Planete.net IT Manager Mail: 8/10 rue Nieuport - 78140 Velizy - France Phone: +33 (0)1 34 63 19 71 - Fax: +33 (0)1 34 63 19 51

2 1

Top 100 Maintainers List 20000605
by RIPE Database Administration 05 Jun '00

05 Jun '00

1 0

The Cidr Report
by Tony Bates 02 Jun '00

02 Jun '00

This is an auto-generated mail on Fri Jun 2 12:00:00 PDT 2000 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 02Jun00 0) General Status Table History ------------- Date Prefixes 080400 75151 090400 75137 100400 75215 110400 75403 120400 75730 130400 75919 010500 76182 020500 76265 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: 5027 Number of ASes announcing only one prefix: 1865 (0 cidr, 1865 classful) Largest number of cidr routes: 0 announced by Largest number of classful routes: 1002 announced by AS701 1) Gains by aggregating at the origin AS level --- 02Jun00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 437 152 285 65.2% BCnet Backbone AS7046 500 336 164 32.8% COQUI-NET PRTC Internet AS9269 167 29 138 82.6% Hong Kong CTI AS9706 153 26 127 83.0% Pusan Metropolitan City Office of AS1221 529 408 121 22.9% TELSTRA-AS AS2609 123 18 105 85.4% EUnet-TN AS7545 164 66 98 59.8% TPG Internet Pty Ltd AS7657 264 168 96 36.4% The Internet Group Limited AS174 552 464 88 15.9% Performance Systems International AS7496 126 39 87 69.0% Power Up AS9304 109 24 85 78.0% Hutchcity AS9557 100 17 83 83.0% Pakistan Telecommunication Compan AS6429 204 121 83 40.7% RDC-INTERNET AS577 248 172 76 30.6% Bell Backbone AS7029 146 71 75 51.4% ALLTELNET AS209 463 392 71 15.3% Qwest Communications AS7018 529 463 66 12.5% AT&T WorldNet Service Backbone AS1727 162 98 64 39.5% MRMS-WEST AS4293 253 190 63 24.9% Internal ASN for C&W AS724 205 143 62 30.2% DLA-ASNBLOCK-AS AS7260 111 50 61 55.0% NORLIGHT AS705 270 209 61 22.6% ALTERNET-AS AS3749 121 61 60 49.6% TECNET AS3602 307 249 58 18.9% Sprint Canada Inc. AS6595 107 50 57 53.3% DODDSEUR AS4740 336 279 57 17.0% Ozemail Pty Ltd (ASN-OZEMAIL) AS5106 81 29 52 64.2% AADS-COLUMBUS AS7568 63 18 45 71.4% C.S. Communications Co., Ltd. AS816 308 266 42 13.6% UUNET Canada (ASN-UUNETCA-AS4) AS6528 48 6 42 87.5% WORLD-LYNX 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

RIPE NCC Region Weekly Routing Report
by Routing Analysis 01 Jun '00

01 Jun '00

This is an automated weekly mailing sent to the RIPE Routing WG e-mail list describing the state of the Internet Routing Table in Europe, Middle East and North Africa. 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>. Europe, Middle East, North Africa Report 02 Jun, 2000 Analysis Summary ---------------- BGP routing table entries examined: 80184 Origin ASes present in the Internet Routing Table: 7569 Origin ASes announcing only one prefix: 2468 Transit ASes present in the Internet Routing Table: 1071 Average AS path length visible in the Internet Routing Table: 5.2 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: 1172352014 Equivalent to 69 /8s, 224 /16s and 172 /24s Percentage of available address space announced: 31.6 Percentage of allocated address space announced: 63.7 Percentage of available address space allocated: 49.6 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 12709 Prefixes being announced from the RIPE address blocks: 9892 RIPE Region origin ASes present in the Internet Routing Table: 2030 RIPE Region origin ASes announcing only one prefix: 951 RIPE Region transit ASes present in the Internet Routing Table: 399 Average RIPE Region AS path length visible: 5.8 Max RIPE Region AS path length visible: 15 Number of RIPE addresses announced to Internet: 70745163 Equivalent to 4 /8s, 55 /16s and 124 /24s Percentage of available RIPE address space announced: 70.3 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 and 212/7 RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 3301 377 280 TeliaNet Sweden 1257 330 267 Swipnet AB 1270 256 413 UUNET Germany 1849 245 491 PIPEX 1275 235 1132 DFN IP Service 719 181 148 LANLINK 786 181 959 JANET IP Service 517 164 202 Xlink 5515 160 337 Sonera Finland 3320 149 285 Deutsche Telekom AG 1267 126 947 IUnet S.p.A 2609 126 4 EUnet-TN 2856 125 271 BTnet UK Regional network 3303 123 295 Swisscom 2874 120 77 Global One Services 3215 98 124 RAIN 9057 96 31 Level 3 public IP n 1901 90 74 EUnet Austria 8895 86 28 Saudi Arabia AS Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 1960 3248 UUNET Technologies, Inc. 7018 1052 3015 AT&T 1 883 4600 BBN Planet 1221 859 986 Telstra 7046 841 473 UUNET Technologies, Inc. 2914 776 1392 Verio, Inc. 1239 737 1634 Sprint ICM-Inria 3561 725 1631 Cable & Wireless USA 209 660 710 Qwest 174 639 2849 PSINet Inc. 705 537 34 UUNET Technologies, Inc. 271 469 411 BCnet Backbone 2764 459 113 connect.com.au pty ltd 3549 450 342 Frontier GlobalCenter 1740 444 636 CERFnet 3602 433 78 Sprint Canada 4740 395 84 Ozemail 4293 379 68 Cable & Wireless USA 3301 377 280 TeliaNet Sweden List of Illegal AS's (Global) ----------------------------- Bad AS Designation Network Transit AS Description 65530 PRIVATE 63.179.128.0/24 4999 Sprint 65530 PRIVATE 63.179.134.0/24 4999 Sprint 65530 PRIVATE 63.179.142.0/24 4999 Sprint 65530 PRIVATE 63.179.146.0/24 4999 Sprint 65530 PRIVATE 63.179.148.0/24 4999 Sprint 65530 PRIVATE 63.179.149.0/24 4999 Sprint 65530 PRIVATE 63.179.154.0/24 4999 Sprint 65530 PRIVATE 63.179.158.0/24 4999 Sprint 65530 PRIVATE 63.179.190.0/24 4999 Sprint 65530 PRIVATE 63.179.191.0/24 4999 Sprint 65530 PRIVATE 63.179.230.0/24 4999 Sprint 65530 PRIVATE 63.179.249.0/24 4999 Sprint 64602 PRIVATE 63.236.57.0/24 209 Qwest 64601 PRIVATE 63.236.90.0/24 209 Qwest 65500 PRIVATE 200.186.247.0/24 11415 IMPSAT Comunicacoes 64605 PRIVATE 208.47.206.0/24 209 Qwest 65014 PRIVATE 208.185.113.0/24 6461 AboveNet Communicati Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 39.96.40.224/30 14408 iCAIR 65.56.64.0/21 2941 Community News Service 109.177.9.0/24 1785 Sprint ICM Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:24 /9:4 /10:5 /11:9 /12:26 /13:49 /14:163 /15:276 /16:6494 /17:844 /18:1653 /19:5323 /20:3166 /21:3396 /22:5111 /23:6893 /24:46041 /25:125 /26:175 /27:84 /28:65 /29:69 /30:115 /31:0 /32:74 End of report

1 0

The Cidr Report
by Tony Bates 26 May '00

26 May '00

This is an auto-generated mail on Fri May 26 12:00:00 PDT 2000 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 26May00 0) General Status Table History ------------- Date Prefixes 080400 75151 090400 75137 100400 75215 110400 75403 120400 75730 130400 75919 010500 76182 020500 76265 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: 5027 Number of ASes announcing only one prefix: 1865 (0 cidr, 1865 classful) Largest number of cidr routes: 0 announced by Largest number of classful routes: 1002 announced by AS701 1) Gains by aggregating at the origin AS level --- 26May00 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 437 152 285 65.2% BCnet Backbone AS7046 500 336 164 32.8% COQUI-NET PRTC Internet AS9269 167 29 138 82.6% Hong Kong CTI AS9706 153 26 127 83.0% Pusan Metropolitan City Office of AS1221 529 408 121 22.9% TELSTRA-AS AS2609 123 18 105 85.4% EUnet-TN AS7545 164 66 98 59.8% TPG Internet Pty Ltd AS7657 264 168 96 36.4% The Internet Group Limited AS174 552 464 88 15.9% Performance Systems International AS7496 126 39 87 69.0% Power Up AS9304 109 24 85 78.0% Hutchcity AS9557 100 17 83 83.0% Pakistan Telecommunication Compan AS6429 204 121 83 40.7% RDC-INTERNET AS577 248 172 76 30.6% Bell Backbone AS7029 146 71 75 51.4% ALLTELNET AS209 463 392 71 15.3% Qwest Communications AS7018 529 463 66 12.5% AT&T WorldNet Service Backbone AS1727 162 98 64 39.5% MRMS-WEST AS4293 253 190 63 24.9% Internal ASN for C&W AS724 205 143 62 30.2% DLA-ASNBLOCK-AS AS7260 111 50 61 55.0% NORLIGHT AS705 270 209 61 22.6% ALTERNET-AS AS3749 121 61 60 49.6% TECNET AS3602 307 249 58 18.9% Sprint Canada Inc. AS6595 107 50 57 53.3% DODDSEUR AS4740 336 279 57 17.0% Ozemail Pty Ltd (ASN-OZEMAIL) AS5106 81 29 52 64.2% AADS-COLUMBUS AS7568 63 18 45 71.4% C.S. Communications Co., Ltd. AS816 308 266 42 13.6% UUNET Canada (ASN-UUNETCA-AS4) AS6528 48 6 42 87.5% WORLD-LYNX 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

RIPE NCC Region Weekly Routing Report
by Routing Analysis 25 May '00

25 May '00

This is an automated weekly mailing sent to the RIPE Routing WG e-mail list describing the state of the Internet Routing Table in Europe, Middle East and North Africa. 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>. Europe, Middle East, North Africa Report 26 May, 2000 Analysis Summary ---------------- BGP routing table entries examined: 79625 Origin ASes present in the Internet Routing Table: 7527 Origin ASes announcing only one prefix: 2454 Transit ASes present in the Internet Routing Table: 1065 Average AS path length visible in the Internet Routing Table: 5.2 Max AS path length visible: 15 Illegal AS announcements present in the Routing Table: 15 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 5 Number of addresses announced to Internet: 1168086933 Equivalent to 69 /8s, 159 /16s and 151 /24s Percentage of available address space announced: 31.5 Percentage of allocated address space announced: 63.5 Percentage of available address space allocated: 49.6 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 12646 Prefixes being announced from the RIPE address blocks: 9847 RIPE Region origin ASes present in the Internet Routing Table: 2017 RIPE Region origin ASes announcing only one prefix: 952 RIPE Region transit ASes present in the Internet Routing Table: 399 Average RIPE Region AS path length visible: 5.8 Max RIPE Region AS path length visible: 15 Number of RIPE addresses announced to Internet: 70521327 Equivalent to 4 /8s, 52 /16s and 17 /24s Percentage of available RIPE address space announced: 70.1 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 and 212/7 RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 3301 373 272 TeliaNet Sweden 1257 330 267 Swipnet AB 1270 253 410 UUNET Germany 1849 238 492 PIPEX 1275 235 1132 DFN IP Service 786 181 959 JANET IP Service 719 179 145 LANLINK 517 163 201 Xlink 5515 159 338 Sonera Finland 3320 147 277 Deutsche Telekom AG 2609 127 4 EUnet-TN 2856 125 271 BTnet UK Regional network 3303 123 295 Swisscom 2874 122 85 Global One Services 1267 109 819 IUnet S.p.A 3215 97 124 RAIN 9057 93 29 Level 3 public IP n 1901 89 74 EUnet Austria 1290 85 195 PSINet UK Ltd. Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 1969 3240 UUNET Technologies, Inc. 7018 1039 3010 AT&T 1221 884 986 Telstra 1 879 4616 BBN Planet 7046 826 472 UUNET Technologies, Inc. 2914 732 1232 Verio, Inc. 1239 724 1631 Sprint ICM-Inria 3561 710 1630 Cable & Wireless USA 209 655 704 Qwest 174 651 2850 PSINet Inc. 705 580 35 UUNET Technologies, Inc. 271 469 411 BCnet Backbone 2764 459 113 connect.com.au pty ltd 3549 437 341 Frontier GlobalCenter 3602 434 77 Sprint Canada 1740 404 626 CERFnet 4740 398 83 Ozemail 3301 373 272 TeliaNet Sweden 4293 373 68 Cable & Wireless USA List of Illegal AS's (Global) ----------------------------- Bad AS Designation Network Transit AS Description 65530 PRIVATE 63.179.128.0/24 4999 Sprint 65530 PRIVATE 63.179.134.0/24 4999 Sprint 65530 PRIVATE 63.179.142.0/24 4999 Sprint 65530 PRIVATE 63.179.146.0/24 4999 Sprint 65530 PRIVATE 63.179.148.0/24 4999 Sprint 65530 PRIVATE 63.179.149.0/24 4999 Sprint 65530 PRIVATE 63.179.154.0/24 4999 Sprint 65530 PRIVATE 63.179.158.0/24 4999 Sprint 65530 PRIVATE 63.179.190.0/24 4999 Sprint 65530 PRIVATE 63.179.191.0/24 4999 Sprint 65530 PRIVATE 63.179.249.0/24 4999 Sprint 64602 PRIVATE 63.236.57.0/24 209 Qwest 64601 PRIVATE 63.236.90.0/24 209 Qwest 64605 PRIVATE 208.47.206.0/24 209 Qwest 65014 PRIVATE 208.185.113.0/24 6461 AboveNet Communicati Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 39.96.40.224/30 14408 iCAIR 65.56.64.0/21 2941 Community News Service 109.177.9.0/24 1785 Sprint ICM 219.91.160.0/22 7742 InternetNow, Inc. 219.91.164.0/23 7742 InternetNow, Inc. Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:24 /9:4 /10:5 /11:9 /12:26 /13:48 /14:163 /15:275 /16:6458 /17:831 /18:1644 /19:5290 /20:3119 /21:3364 /22:5036 /23:6838 /24:45871 /25:131 /26:178 /27:71 /28:44 /29:42 /30:89 /31:0 /32:65 End of report

1 0

Top 100 Maintainers List 20000524
by RIPE Database Administration 24 May '00

24 May '00

1 0

Re: About address allocating (IPv6, variable length SLA/prefixes?)
by Ole Troan 22 May '00

22 May '00

> Architecturally, IPv6 has the equivalent of variable length subnet masks > built in. There are really only two boundaries that are not flexible- > the boundary between the format prefix and the rest of the address, and the > /64 boundary. (The format prefix is in fact variable length, but it is > architecturally defined.) So any IGP or EGP design needs to be fully flexible > to the left of /64. Subnetting to the right of /64 would be tricky. all IGP's and EGP's have to support all prefix-lengths. e.g you want to announce host routes, /96 for NAT-PT, etc. for that matter, the implementation(s) I know will let you create subnets of whatever size you like. /ot

3 3

Re: About address allocating (IPv6, variable length SLA/prefixes?)
by Wilfried Woeber, UniVie/ACOnet 22 May '00

22 May '00

Hi Francis et.al., as I said a couple of days ago in Budapest, I would like to see an explanation and/or review from the routing point of view. Judging from my (limited) knowledge about IPv6, going for a variable length SLA field would either leave us with "wasted" address space (as the network next door would be a different site and thus should have a different NLA field anyway), or we would end up with a variable length network prefix length (much like in the v4 environment), effectively extending the NLA field into the SLA field. Doing so would probably require a cross-check against existing IPv6-aware IGPs. That is where I would like to see input from the routing camp(s). Regards, Wilfried. ______________________________________________________________________ From: Francis Dupont <Francis.Dupont(a)enst-bretagne.fr> To: itojun(a)iijlab.net CC: Haisang Wu <hswu(a)ns.6test.edu.cn>, 6bone(a)ISI.EDU Subject: Re: About address allocating Date: Sat, 20 May 2000 15:17:57 +0200 In your previous mail you wrote: > hi, I have the following questions about address allocating: > I know SLA is /48, and interface ID should be 64 bits, > does it mean that the smallest unit when allocating address is /48? > In other words, if I allocate a /48 to a large university, could I > allocate a /48 to four middle schools, thus each middle school gets > an block less than /48, which is /50. Is this plan reasonable? > >=> we'd like to get a /48, ISPs would like to give a /64 to us: > - /48 seems a bit too large for a default allocation size > - /64 is unusable when you need subneting >then the current idea, as presented yesterday here in Budapest >at the RIPE meeting, is to introduce "small site" which get >/56 (on byte boundary, large enough for up to 256 subnetworks or >a few levels of hierarchy). >Then /56 will become the default allocation size in RIR >allocation & assignment document. I'm not sure if introducing "small sites" is a good thing... when we switch ISP and they force me to switch from /48 to /56, renumber becomes very hard. => the idea is that it is easier for someone which needs a /48 to deal with its ISP than for a common customer to fight in order to get a /48 because /64 is not enough: this is a compromise for common customers (ie you at home, IIJlab is strong enough to get a /x with x <= 48). I believe it is a good compromise... Regards Francis.Dupont(a)enst-bretagne.fr -------------------------------------------------------------------------------- _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3 2