- NANOG - lists.nanog.org

2006.06.06 NANOG-NOTES MPLS TE tutorial
by Matthew Petach 10 Jun '06

10 Jun '06

(still here, just been really busy at work today; will try to finish sending the notes out tonight. --Matt) 2006.06.06 MPLS TE tutorial Pete Templin, Nextlink [slides are at: http://www.nanog.org/mtg-0606/pdf/pete-templin.pdf http://www.nanog.org/mtg-0606/pdf/pete-templin-exercise.pdf He works in a Cisco shop, no JunOs experience Operator perspective, no logos Traffic engineering before MPLS --the "fish" problem. two parallel paths, one entry router, one exit router, you end up with all traffic taking one path, not using the other path. IGP metric adjustments can lead to routing loops hard to split traffic No redundancy left over if both paths filled, but can be good for using 2 out of 3 paths. MPLS TE fundamentals Packets are forwarded based on FIB or LFIB FIB/LFIBS built based on RIB TE tunnels; TE tunnel interface is a unidirectional logical link from one router to another. Once the tunnel is configured, a label is assigned for the tunnel that corresponds to the path through the MPLS network (LSP) TE tunnel basics Once traffic is routed onto the tunnel, the traffic flows through the tunnel based on the path. Return traffic could be placed onto a tunnel going the opposite direction, or simply routed by IGP Key terms for TE Headend router on which the tunnel is configured Tail destination address of tunnel Midpoint router(s) along the path along the tunnel LSP Basic TE config Global: mpls traffic-eng tunnels IGP: must be OSPF or IS-IS mpls traffic-eng rouer-id Loopback0 mpls traffic-eng <area X | level2> physical interfaces mpls ip mpls traffic-eng tunnels tells IGP to share TE info with other TE nodes interface TunnelX ip unnumbered loopback0 borrow the loopbak's address so we can forward traffic down the tunnel tunnel mode mpls traffic-eng tunnel destination <a.b.c.d> tunnel tail tunnel mpls traffic-eng path-option 10 dynamic find a dynamic path through network best path with sufficient bandwidth will discuss path selection in a bit Where are we at? Tunnels go from headend to tail end through midpoint routers over a deterministic path we know what commands go on a router for the global physical interface tunnel interface commands TE and bandwidth Physical interfaces can be told how much bandwidth can be reserved (used) ip rsvp bandwidth X X TE tunenls can be configured with how much bandwidth they need: tun mpls traff bandw Y Tunnels will reserve Y bw on outbound interfaces, and find a path across the network wth X(unused)>Y BW. This prevents oversubscription, or at least helps control it. You can allow for burst room, but for now we'll stick with static, non-oversubscribed links. TE BW operators can adjust the tunnel bandwidth values over time to match changes in traffic. If tunnels are dynamically placed, the tunnels will dynamically find a path through the network with sufficient bandwidth, or will go down. TE auto-bandwidth magic Tunnels can be configured to watch their actual traffic as in "shw int <blah>| inc rate" every five minutes, and update their reservation to match, at periodic intervals. Dynamic reservations to match the live network Bandwidth is 'reserved' using RSVP but not "saved" for TE Often buys enough time to identify the surge, see where the traffic is coming/going. The number is only a number in control plane; no actual impact on data plane, no shaping, no control on real data flows. tunnel mpls traffic-eng auto-bw frequency Y each auto-bw tunnel does "sh int" to capture its rate every 300* seconds each auto-bw tunnel updates "tunn mpls traff bandwidth X" every Y seconds The config actually changes; this will impact your RANCID tracking. It uses highest measured rate during the interval Y May want to tweak your load-interval, since it's a decaying function over time; 5 minute is a fairly smooth value. May need to tweak config check-in system to avoid getting flooded with bandwidth adjustments. Covered: TE tunnel basics router config basics general concepts about TE and bandwidth In this case, the shortest path that has X BW available for reservation actually, bw X at or below priority Y, but that's later. SPF calculations step 0: create a PATH list and a TENT list step 1: put "self" on PATH list. step 2: step 3: put PATH nodes' neighbors on TENT list step 4: if TENT list is empty, stop. step 5: jump back to step 2: Example exercise -- calculate router A's best path to router D using the handout. CSPF notes No load sharing is performed within a tunnel; as soon as a path is found, it wins CSPF tiebreakers: lowest IGP cost largest minimum available bandwidth lowest hop count top node on the PATH list Creating paths -- can be created dynamically, or statically via static paths. Dynamic: tunnel mpls traff path-option X dynamic Explicit paths paths can be crated manually by explicitly creating a path "ip explicit-path name <name?>" next-address X next-address Y tunnel mpls traff path-option X explicit name blah Paths can be created manually by explicity configuring a path that excludes an address; use any link EXCEPT this one. for backup links, oob links, etc. can't combine exclude-address and next-address on the same explicit path. Q: if all other paths go away, will an excluded path still be used? A: only if you have a fallback option of "dynamic" can't both include and exclude on same path. A TE tunnel can have multiple path options. lowest cost path option is attempted higher-cost paths attempted sequentially until a path can successfully established, or failure Usually best to have a dynamic option as the highest-cost option, to ensure you don't fall back to IGP (and lose traffic matrix accounting!) CSPF checks tunnel path options in sequence for one that has sufficient information. OK, we've got tunnels now--how do we share info around the network? TE info is shared around using IGP available bw per interface eight priority levels high priority tunnels can push low priority tunnels out of the way some dynamics as far as tunnel vs interface sizing administrative weight (TE specific IGP metric Affinity (customizable) You can configure different interfaces with bits that indicate territorial restrictions, or high-latency links, etc. Use the interface affinity bits, and match/exclude tunnel affinity bits to include or exclude certain links. This information is distributed immediately for "significant" changes periodically for "insignificant" changes immediately, if a change causes an error Significant changes occur when available bandwidth on an interface passes preset thresholds customizable with 16 thresholds. (based on percentages) Key points where information is passed from device to device. Insignificant changes flooded every 3 minutes, significant flooded immediately, by default. If a new path (dynamic or static) appears that's better than the current one re-optimize periodically, every hour from tunnel bringup by default manually "mpls traffic-eng reoptimize" event-driven when a link comes up optional: requires "mpls traff reo events link-up" not so good with flapping links, though. If you have a flapping link, TE tunnels will stay off that link for about an hour; you have flap dampening in your network. Up next, how to put IP traffic on tunnels static routes "ip route x.x.x.x y.y.y.y tuZ" policy-based routing route-map PBR permit 20 match ip addr ACL set ip next-hop tunX Autoroute Autoroute treat this tunnel as though it's a logically directly connected link to the tunnel tail updates the local router's RIB/FIB with "tunnelX" in place of the IGP next-hop; preserves the IGP cost all the way to the tail. One line of config per tunnel; it updates the LOCAL router's RIB/FIB; prior routers not made aware of this router as a next-hop for the tunnel tail. This is supported for IS-IS, but can be more difficult; you increase number of links in your IGP pretty quickly. tunn mpls traff autoroute announce autoroute and load-sharing parallel tunnels will load-share inversely proportional to their configured bandwidth auto-bandwith can really muck with these values! load-sharing can be tuned separately with "tunn mpls traff load-share X" Limited to CEF 16 buckets, depending on when it measures, can end with values drifting apart. If you use same "X" on two tunnels, they will load share equally. IGPs can load-share over equal-cost paths BUT TE tunnel cannot load-share over multiple physical interfaces TE diagnostics show ip route X sh run int tuX sh ip rsvp reservation show mpls traff tun suboptimal constr none shows headend tunnels taking suboptimal paths to the tunnel tail (eg, different from IGP best path) show mpls traff tun detailed info for all tunnel headends bandwidth info (auto-bw) MPLS labels, hop by hop path show mpls traff tun role <head|middle|remote|tail> remote is non-headend (not originating or ending on this router) show ip rsvp interfaces shows max allocated bw on an interface. MPLS VPNs if a tunnel tail is not the egress PE, add "mpls ip" to the tunnel configuration PE-P-P-PE-PE --adds another label onto the stack. If the last router VPN isn't on penultimate router, the TE label won't be recognized, it'll be dropped. This adds the TE label back on, keeps the LDP label as well as the VPN label still intact Add "mpls ldp discovery directed-hello accept" to config If you have unidirectional tunnels, that way when you're bringing up tunnels LDP info can be exchanged as you're going. Multicast: RPF calculations are normally based on unicast RIB Unidirectional TE tunnels cause RPF failures add "mpls traffic-engineering multicast-intact" to IGP config Bases RPF checks on RIB BEFORE TE tunnels are substituted Questions? templin at templin.org Swap to looking at operational network for some troubleshooting views. About 150-200Mb traffic aggregate, 4 pops, DAL and Houston, four parallel DS3s, 2 between core1's and 2 between core2's 30mbit IP RSVP reservation; TE kicks in, and moves traffic. Houston intercore links tends to not have traffic unless TE has kicked in. Aggressive 15 minute auto recalculations, since surprises can kick up fairly quickly. Room heads for cookies at 1526 hours Pacific Time

1 1

2006.06.07 NANOG-NOTES DNSSEC bootstrapping with DLV
by Matthew Petach 10 Jun '06

10 Jun '06

(last notes from NANOG37, yay! I definitely fell further behind this time around than in Dallas. Unfortunately, I don't think I'll be allowed to go to St. Louis, so I probably won't be able to provide notes for NANOG38. --Matt) 2006.06.07 Deploying DNSSEC--bootstrap yourself Joao Damas, ISC [notes are at http://www.nanog.org/mtg-0606/pdf/joao-damas.pdf DNSSEC status standard is complete and usable some minor nits with regards to some privacy issues 2 implementations: NSD, BIND at least one DNSSEC aware resolver (BIND 9.3.2 and later) Really, you just need some data. DNSSEC follows a hierarchical model for signatures. sign the root zone get root zone to delegation sign TLDs get TLDs to delegation-sign SLDs, etc. Today, the root zone remains unsigned likely will be this way for some time Very few TLDs have signed their zones and offer delegation signatures .se, .ru, .org DNSSEC provides for local trust anchors you can use trust-anchors clause in BIND problem: if you have too many, it becomes a nightmare to maintain, so it doesn't get used. very manual process Enter DLV, domain lookaside validation it's an implementation feature, not a change to the protocol; matter of local policy enables access to a remote, signed repository of trust anchors, via the DNS implemented in BINDs resolver so far more to follow? unfortunately, requires you to trust remote repository DLV lookup a DLV enabled resolver will try to find a secure entry point using regular DNSSEC; only if it fails is DLV used, if it is configured. [picture of DLV lookup chain] On resolver (BIND) add to named.conf in the options section //DNSSEC conifg dnnssec-enable yes dnssec-lookaside . trust-anchor dlv.isc.org.; get the key from ISC's web: http://www.isc.org/ops/dlv ISC is operating a DLV registry free of charge for anone who wants to secure their DNS Likely some closed orgs will use their own (eg mil) have a look, start using it! Any questions? Q: Mark Kosters, Verisign: Any plans to configure DLV registries per TLD? A: BIND code only allows for one right now. Q: Would be good to allow it to be configured per TLD. Q: Randy Bush, IIJ: some feeling or understanding how IANA, root would validate keys/zones it has keys for; don't understand how ISC proposes to validate keys it would be storing. He suggests they publish the security policy. A: In case of registrars proxying keys; they trust registrar. Otherwise, it's like PGP; show me your face, show me your key. Q: Paul vixie, ISC, following up on Mark Kosters; you can only have one DLV for any point in the namespace; you can specify a different one for a TLD than root; that allows a TLD DLV to be paranoid, like .mil. who doesn't want to trust anyone else with key information. If every TLD wanted to do that, they would find high levels of cut-and-paste fatigue, so ISC will operate a root level DLV server as well. Q: Rick Wesson, runs Alice's Registry, a small registrar. he's considering doing this, he can help DNS holders register their keys if people are interested, and will help get them into the DLV tree. Q: Sam Wiler?, Sparta: concerns from Randy about how ISC will authenticate the entries. Registrars should consider running their own DLV servers, as they have the relationship with the domain holder. Code? Apparently you don't need code... NANOG 37, ending slides. 425 attendees, 118 first timers lots of countries most USA, 11 canada, scattered others. ISP, then NSP, then other categories. top 3 companies represented: Cisco, Juniper, Equinix HUGE thanks to Rodney Joffe and Neustar for puling off a miracle to make this happen at the last minute! Thanks to sponsors, bear, gear, other. Susan R Harris, many thanks to her for all the work she has put in over the years and to make this happen! Also huge thanks to all the other people at Merit And we'll see you in St. Luis, Oct 8-10th, joint meeting with ARIN, things set in stone. Network will go down in 30 minutes or so--pack up and go home! :) I think that was the fastest closing I've seen at a NANOG yet. ^_^;;

1 0

2006.06.07 NANOG-NOTES Anycast benefits for k root server
by Matthew Petach 09 Jun '06

09 Jun '06

Break ends at 11:40, PGP signing will take place, and don't forget to fill out servers. ANYCAST fun for the final sessions. Lorenzo Colitti, RIPE NCC [slides are at: http://www.nanog.org/mtg-0606/pdf/lorenzo-colitti.pdf Agenda: introduction latency client-side server-side Benefit of individual nodes Stability Routing issues Why anycast? root server anycast widely deployed c, f, i j, k, m at least reasons for anycasting provide resiliency: eg contain DOS attacks spread server and network load increase performance but is it effective? measure latency ideally for every given client, BGP should chose node with lowest RTT. does it? from every client, measure RTTs to anycast IP address service interfaces of global nodes (not anycasted) for every client, compare K RTT to RTT of closest global node a = RTTk/min(RTTi) if 1, BGP is picking right node if > 1, BGP picks the wrong node if <1, seeing local node. Latency with TTM: methodology DNS queries from ~100 TTM test boxes dig hostname.bind see which host answers extract RTT take min of 5 queries check paths to service interfaces; is it same as prod IP according to RIS, mostly 'yes' TTM probe locations, mostly in europe Latency with TTM: results (5 nodes) most values are close to one; generally BGP doing pretty good job. from 2 nodes to 5 nodes (2 nodes, April 2005) (5 nodes, April 2006) mostly same results, clustered around one, whether 2 or 5 nodes. consistency of 'a' over time average of that over time. TT103 is outlier calculated over time, threw out that one outlier. results are pretty consistent. average is little higher than one, mostly consistent over time measuring from servers TTM latency measurements not optimal locations biased towards europe limited number of probes (~100) don't reflect k client distribution how to fix? ping clients from servers much larger dataset methodology process packet traces on k global nodes extract list of client IP addreses ping all addresses from all global nodes plot distribution of 'a' 6 hours of data 246,769,005 queries 845,328 unique IP addresses CDF of 'a' seen from servers results not as good as seen by TTM only 50% of clients have a = 1 about 10% are 4x slower/farther. probably due to TTM clustering in europe latency conclusions 5 node result vs 2 node, comparable, at least in TTM non-TTM results not so rosy. How many nodes are needed--is 5 enough? evaluate existing instances how to measure benefit of an instance? Assume optimal instance selection that is, every client sees closest instance this is upper benefit of benefit consistent to see if we've reached diminishing returns for every client, see how much its performance if the chosen node didn't exist. B is loss factor, how much a client would suffer if an instance were knocked out B = RTTknockout/RTT... Graph for LINX; 90% of clients wouldn't see an impact if it went away; 10% would see a worsening. geographic distribution pretty wide AMS-IX about 20% would suffer performance degregation; busiest two nodes, see a lot of clients, important to k deployment. If they plot it for both LINX and AMSIX together, about 65% wouldn't be affected, most of others would see 4x, 10% would be 7x worse. So taken together, the *two* nodes are important. Tokyo; best node for few clients; but those served, BADLY served by others; about 10% who would go more than 7x if it went way, those clients mostly Asia. Miami node at NOTA, moderate benefit for some clients, US and southAm would be badly served by europe or Tokyo. Delhi node is mostly ineffective, most would be served better by other nodes. Condense the graph into one number to get a value for effectiveness of each node. weighted average of B for each client. if benefit value is 1, node doesn't provide any benefit at all. larger numbers show higher benefits. Europe, when taken together, high benefit, as is Tokyo; Miami node not so effective, and Delhi is nearly ineffective. Does anycast provide any value then? knock out all except LINX; dark red curve (pre 1997) 10% wouldn't notice, 85% would get worse, benefit value is 18.8, so anycast does bring value. Stability the more routes competing in BGP with more nodes doesn't matter for single packet UDP exchanges does matter for TCP Look at node switches that occur. collect packet dumps on each node. extract all 53/UDP traffic k nodes only NTP synchronized if IP shows up on two nodes, log a switch. 5 nodes, april 2006, 0.06% saw switches 2830 switchers out of 845,328, 0.33% switchers no big issue with instance switchers. Routing issues k-root structure 5 global nodes (prepended) linkx, amsix, tokyo, mia, del different prepending values no-export causing reachability TT103 has value of 200, the graph axis is cut. tt103 is in Yokohama; Tokyo is 2ms away; but the query goes to Delhi through Tokyo to LA. 416ms vs 2, so value is 208. Thanks to Matsuzaki and Randy Bush, got BGP paths from AS2497 bad interaction of different prepending lengths need to fix prepending on Tokyo node. Delhi had shorter prepending. no-export and leaks local nodes can be worse than global nodes tt89, seeing Denic local node, 30ms instead of going to London. Local node, if no-export is ignored, announced to customer, they are more specific, leak to customers. no-export can lead to loss of reachability http://www.merit.edu/mail.archives/nanog/2005-10/msg01226.html problematic interaction of no-export with anycast use no-export to prevent local nodes from leaking if have an AS whose providers all peer with a local node and honor no-export customer never sees route for k IP address. solution, send out a less specific, covering prefix. Q: Mark Kosters, Verisign--saw much higher switching rates; can he define switching better? A: if an IP is seen at one location, then shifts to a different site, that's one switch; going back to the first node would be a second switch.

1 0

earthlink.net mail admin contact?
by Mark Jeftovic 09 Jun '06

09 Jun '06

Would somebody from earthlink.net mail ops please contact me off-list? thx -mark -- Mark Jeftovic <markjr(a)easydns.com> Founder & President, easyDNS Technologies Inc. ph. +1-(416)-535-8672 ext 225 fx. +1-(866) 273-2892

1 0

who runs http://www.networkthinktank.com/ ?
by Paul Vixie 09 Jun '06

09 Jun '06

the web site and whois info are just about as completely anonymous as can be.

4 3

Weekly Routing Table Report
by Routing Analysis Role Account 09 Jun '06

09 Jun '06

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 If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 10 Jun, 2006 Analysis Summary ---------------- BGP routing table entries examined: 190168 Prefixes after maximum aggregation: 104652 Unique aggregates announced to Internet: 93198 Total ASes present in the Internet Routing Table: 22396 Origin-only ASes present in the Internet Routing Table: 19479 Origin ASes announcing only one prefix: 9338 Transit ASes present in the Internet Routing Table: 2917 Transit-only ASes present in the Internet Routing Table: 60 Average AS path length visible in the Internet Routing Table: 3.5 Max AS path length visible: 24 Max AS path prepend of ASN (34527) 16 Prefixes from unregistered ASNs in the Routing Table: 7 Unregistered ASNs in the Routing Table: 5 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 9 Number of addresses announced to Internet: 1543668456 Equivalent to 92 /8s, 2 /16s and 130 /24s Percentage of available address space announced: 41.6 Percentage of allocated address space announced: 60.2 Percentage of available address space allocated: 69.1 Total number of prefixes smaller than registry allocations: 94114 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 40710 Total APNIC prefixes after maximum aggregation: 16880 Prefixes being announced from the APNIC address blocks: 38424 Unique aggregates announced from the APNIC address blocks: 18579 APNIC Region origin ASes present in the Internet Routing Table: 2598 APNIC Region origin ASes announcing only one prefix: 747 APNIC Region transit ASes present in the Internet Routing Table: 398 Average APNIC Region AS path length visible: 3.5 Max APNIC Region AS path length visible: 18 Number of APNIC addresses announced to Internet: 227781728 Equivalent to 13 /8s, 147 /16s and 172 /24s Percentage of available APNIC address space announced: 71.2 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911 APNIC Address Blocks 58/7, 60/7, 121/8, 122/7, 124/7, 126/8, 202/7 210/7, 218/7, 220/7 and 222/8 ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 97710 Total ARIN prefixes after maximum aggregation: 57771 Prefixes being announced from the ARIN address blocks: 71728 Unique aggregates announced from the ARIN address blocks: 26653 ARIN Region origin ASes present in the Internet Routing Table: 10759 ARIN Region origin ASes announcing only one prefix: 4051 ARIN Region transit ASes present in the Internet Routing Table: 993 Average ARIN Region AS path length visible: 3.3 Max ARIN Region AS path length visible: 18 Number of ARIN addresses announced to Internet: 293558272 Equivalent to 17 /8s, 127 /16s and 88 /24s Percentage of available ARIN address space announced: 76.1 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 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, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959 ARIN Address Blocks 24/8, 63/8, 64/5, 72/6, 76/8, 199/8, 204/6, 208/7 and 216/8 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 38053 Total RIPE prefixes after maximum aggregation: 25405 Prefixes being announced from the RIPE address blocks: 35075 Unique aggregates announced from the RIPE address blocks: 23703 RIPE Region origin ASes present in the Internet Routing Table: 8129 RIPE Region origin ASes announcing only one prefix: 4266 RIPE Region transit ASes present in the Internet Routing Table: 1342 Average RIPE Region AS path length visible: 4.0 Max RIPE Region AS path length visible: 20 Number of RIPE addresses announced to Internet: 252474756 Equivalent to 15 /8s, 12 /16s and 117 /24s Percentage of available RIPE address space announced: 79.2 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-41983 RIPE Address Blocks 62/8, 80/5, 88/6, 193/8, 194/7, 212/7 and 217/8 LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 11498 Total LACNIC prefixes after maximum aggregation: 3701 Prefixes being announced from the LACNIC address blocks: 9595 Unique aggregates announced from the LACNIC address blocks: 5546 LACNIC Region origin ASes present in the Internet Routing Table: 695 LACNIC Region origin ASes announcing only one prefix: 229 LACNIC Region transit ASes present in the Internet Routing Table: 133 Average LACNIC Region AS path length visible: 4.1 Max LACNIC Region AS path length visible: 24 Number of LACNIC addresses announced to Internet: 27317760 Equivalent to 1 /8s, 160 /16s and 214 /24s Percentage of available LACNIC address space announced: 40.7 LACNIC AS Blocks 26592-26623, 27648-28671, plus ERX transfers LACNIC Address Blocks 189/8, 190/8, 200/7 AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 2190 Total AfriNIC prefixes after maximum aggregation: 895 Prefixes being announced from the AfriNIC address blocks: 1501 Unique aggregates announced from the AfriNIC address blocks: 961 AfriNIC Region origin ASes present in the Internet Routing Table: 155 AfriNIC Region origin ASes announcing only one prefix: 45 AfriNIC Region transit ASes present in the Internet Routing Table: 25 Average AfriNIC Region AS path length visible: 3.5 Max AfriNIC Region AS path length visible: 16 Number of AfriNIC addresses announced to Internet: 4113152 Equivalent to 0 /8s, 62 /16s and 195 /24s Percentage of available AfriNIC address space announced: 12.3 AfriNIC AS Blocks 36864-37887 & ERX transfers AfriNIC Address Blocks 41/8, 196/8 APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4134 1242 7204 228 CHINANET-BACKBONE 4755 931 259 74 Videsh Sanchar Nigam Ltd. Aut 9583 903 109 16 Sify Limited 4766 690 4435 304 Korea Telecom (KIX) 1221 613 1668 471 Telstra Pty Ltd 9498 571 211 67 BHARTI BT INTERNET LTD. 7545 544 124 70 TPG Internet Pty Ltd 17488 519 32 10 Hathway IP Over Cable Interne 17676 486 7029 110 Softbank BB Corp. 9443 450 110 81 Primus Telecommunications 18101 414 85 24 Reliance Infocom Ltd Internet 17557 397 31 178 Pakistan Telecom 4802 378 80 167 Wantree Development 17849 359 22 114 Telecommunications Technology 17974 347 129 14 PT TELEKOMUNIKASI INDONESIA 2907 336 1733 312 SINET Japan 9929 326 222 58 China Netcom Corp. 7474 298 211 228 SingTel Optus Pty Ltd 9800 275 410 67 CHINA UNICOM 4837 266 2994 112 chinanet IDC center beijing n ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7018 1480 6151 945 AT&T WorldNet Services 4323 1310 740 259 Time Warner Telecom 721 1014 21998 313 DLA Systems Automation Center 6197 1005 625 471 BellSouth Network Solutions, 174 969 5787 904 Cogent Communications 19029 945 151 108 New Edge Networks 18566 943 272 8 Covad Communications 701 940 6753 776 UUNET Technologies, Inc. 2386 894 557 687 AT&T Data Communications Serv 1239 846 2789 600 Sprint 20115 713 617 381 Charter Communications 209 707 3687 551 Qwest 19262 667 2103 183 Verizon Global Networks 22773 664 1741 40 Cox Communications, Inc. 7011 638 218 415 Citizens Utilities 11492 622 87 22 Cable One 852 584 1084 382 Telus Advanced Communications 19916 563 49 54 OLM LLC 855 550 244 64 Canadian Research Network 5668 529 147 23 CenturyTel Internet Holdings, RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 702 573 1951 451 UUNET - Commercial IP service 3301 305 1327 292 TeliaNet Sweden 3352 305 1644 30 Ibernet, Internet Access Netw 3320 287 3989 240 Deutsche Telekom AG 8220 274 470 262 COLT Telecommunications 680 245 2025 242 DFN-IP service G-WiN 6746 238 90 212 Dynamic Network Technologies, 3246 236 504 226 Song Networks 8708 216 275 201 Romania Data Systems S.A. 24863 214 42 11 LINKdotNET AS number 3269 201 2182 72 TELECOM ITALIA 3215 200 1680 93 France Telecom Transpac 8551 200 198 24 Bezeq International 30890 193 17 71 SC Kappa Invexim SRL 1257 190 740 166 SWIPnet Swedish IP Network 8866 180 37 15 Bulgarian Telecommunication C 6830 172 781 36 UPC Distribution Services 786 171 1778 171 The JANET IP Service 5400 171 348 140 BT Ignite European Backbone 9121 169 931 28 TTnet Autonomous System LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 705 1082 224 UniNet S.A. de C.V. 22047 419 158 11 VTR PUNTO NET S.A. 11172 352 110 84 Servicios Alestra S.A de C.V 16814 329 20 8 NSS, S.A. 6147 267 134 22 Telefonica Del Peru 14117 201 12 6 Telefonica del Sur S.A. 10481 181 72 8 Prima S.A. 7303 175 81 25 Telecom Argentina Stet-France 6503 136 151 82 AVANTEL, S.A. 21826 133 17 23 INTERCABLE 11556 132 80 4 Cable-Wireless Panama 19169 126 8 26 Telconet 14259 119 10 15 GTD Internet S.A. 14522 115 18 9 SatNet S.A. 23216 114 21 9 RAMtelecom Telecomunicaciones 19429 110 60 44 E.T.B. 6505 109 88 79 Global One Communicaoes Ltda 7910 105 7 10 ANDINET ON LINE 5639 103 12 9 Telecommunications Services o 18822 98 7 9 TELEFONICA MANQUEHUE AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 3741 286 803 234 The Internet Solution 8452 166 60 7 TEDATA 6713 147 135 11 Itissalat Al-MAGHRIB 2018 131 314 105 Tertiary Education Network 5536 121 8 18 Internet Egypt Network 24835 116 48 6 RAYA Telecom - Egypt 33783 104 6 2 EEPAD TISP TELECOM & INTERNET 2905 73 155 66 The Internetworking Company o 15475 61 84 4 Nile Online 20928 59 16 2 Noor Advanced Technologies AS 15706 44 8 3 Sudatel Internet Exchange Aut 5713 39 294 35 Telkom SA Ltd 33774 31 7 21 AS Number for Telecom Algeria 12455 26 6 3 Jambonet Autonomous system 23889 26 8 11 MAURITIUS TELECOM 16637 25 18 23 Johnnic e-Ventures 8524 22 1 5 AUCEGYPT Autonomous System 10798 22 1 13 Standard Bank of South Africa 21280 21 4 4 Swift Global Kenya Ltd.Is an 33766 21 2 1 Nyala Communications Pty Ltd Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 4323 1310 1051 Time Warner Telecom 4134 1242 1014 CHINANET-BACKBONE 18566 943 935 Covad Communications 9583 903 887 Sify Limited 4755 931 857 Videsh Sanchar Nigam Ltd. Aut 19029 945 837 New Edge Networks 721 1014 701 DLA Systems Automation Center 22773 664 624 Cox Communications, Inc. 11492 622 600 Cable One 6197 1005 534 BellSouth Network Solutions, 19916 563 509 OLM LLC 17488 519 509 Hathway IP Over Cable Interne 5668 529 506 CenturyTel Internet Holdings, 9498 571 504 BHARTI BT INTERNET LTD. 855 550 486 Canadian Research Network 19262 667 484 Verizon Global Networks 8151 705 481 UniNet S.A. de C.V. 7545 544 474 TPG Internet Pty Ltd 3602 525 421 Sprint Canada, Inc. 22047 419 408 VTR PUNTO NET S.A. List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65128 PRIVATE 193.110.50.0/24 24652 Juniper Networks, Eu 24409 UNALLOCATED 203.119.29.0/24 9808 Guangdong Mobile Com 64515 PRIVATE 203.126.13.0/25 7610 SINGAPORE ADVANCE RE 64515 PRIVATE 203.126.13.128/26 7610 SINGAPORE ADVANCE RE 65280 PRIVATE 203.197.161.0/24 4755 Videsh Sanchar Nigam 65280 PRIVATE 203.200.14.0/24 4755 Videsh Sanchar Nigam 65280 PRIVATE 203.200.21.0/24 4755 Videsh Sanchar Nigam Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 132.0.0.0/10 721 DLA Systems Automation Center 137.0.0.0/13 721 DLA Systems Automation Center 158.0.0.0/13 721 DLA Systems Automation Center 183.206.196.0/24 2188 FR-RENATER-ASTER 192.44.0.0/24 5501 Fraunhofer Gesellschaft 192.44.0.0/19 702 UUNET - Commercial IP service 192.70.164.0/24 25689 National Research Council of 192.84.205.0/24 719 LANLINK autonomous system 192.172.0.0/19 721 DLA Systems Automation Center Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:18 /9:9 /10:9 /11:28 /12:92 /13:200 /14:360 /15:704 /16:8855 /17:3247 /18:5351 /19:11723 /20:13263 /21:11524 /22:14724 /23:15902 /24:103048 /25:387 /26:314 /27:182 /28:69 /29:67 /30:51 /31:0 /32:41 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 18566 926 943 Covad Communications 19029 876 945 New Edge Networks 6197 790 1005 BellSouth Network Solutions, 7018 780 1480 AT&T WorldNet Services 9583 733 903 Sify Limited 4323 641 1310 Time Warner Telecom 2386 613 894 AT&T Data Communications Serv 11492 613 622 Cable One 19916 557 563 OLM LLC 7011 547 638 Citizens Utilities 4766 500 690 Korea Telecom (KIX) 855 424 550 Canadian Research Network 5668 412 529 CenturyTel Internet Holdings, 15270 403 434 PaeTec.net -a division of Pae 1239 390 846 Sprint 4755 365 931 Videsh Sanchar Nigam Ltd. Aut 6517 364 395 Yipes Communications, Inc. 17849 359 359 Telecommunications Technology 702 356 573 UUNET - Commercial IP service 6198 354 508 BellSouth Network Solutions, Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:9 8:42 11:1 12:1618 13:1 15:15 16:3 17:3 18:4 20:41 24:734 25:1 32:57 38:229 40:54 41:3 44:3 47:6 52:4 55:1 56:3 57:25 58:183 59:217 60:182 61:863 62:775 63:1911 64:3173 65:2181 66:3061 67:613 68:663 69:1531 70:376 71:80 72:756 74:40 80:788 81:647 82:594 83:401 84:387 85:543 86:390 87:358 88:96 89:240 124:295 125:494 128:158 129:190 130:78 131:318 132:33 133:8 134:157 135:48 136:178 137:82 138:206 139:62 140:469 141:130 142:379 143:165 144:223 145:40 146:329 147:136 148:318 149:188 150:112 151:94 152:69 153:107 154:5 155:202 156:98 157:146 158:168 159:173 160:89 161:76 162:245 163:150 164:179 165:208 166:168 167:246 168:491 169:128 170:338 171:14 183:1 190:75 192:5744 193:3368 194:2640 195:1909 196:855 198:3910 199:3214 200:4487 201:978 202:6698 203:7034 204:3901 205:2033 206:2421 207:2901 208:2128 209:3776 210:1973 211:683 212:1259 213:1469 214:364 215:40 216:4177 217:1156 218:291 219:232 220:717 221:360 222:158 End of report

1 0

Re: a fun hijack: 1/8, 2/8, 3/8, 4/8, 5/8, 7/8, 8/8, 12/8 briefly announced by AS 23520 (today)
by Gadi Evron 09 Jun '06

09 Jun '06

On Thu, 8 Jun 2006, Ariel Biener wrote: > On Wednesday 07 June 2006 21:58, Gadi Evron wrote: > Gadi, > > There's no real need for such drastic measures over this. The Internet is no > longer a "safe" place, meaning that the sane NSPs/ISPs sanitize their networks > rather than trust someone else to do it for them, or trust someone else to never > make mistakes. As such, the diligent network operators and their networks will > not even be affected by this. Indeed, the Internet is not a safe place. It always surprises me when people think otherwise. Regardles, it is a place where someone else's mistake can cost YOU. > Also, there is a sentence that I like, I learned it from a proffessor here, but it > is well known: > > "Never attribute to malice something that can be easily explained by sheer stupidity". One of the most true I ever heard, and indeed, stupidity does hurt us. Does it matter if it is malicious by /intent/? > > > best, > > --Ariel > -- > Ariel Biener > e-mail: ariel(a)post.tau.ac.il > PGP: http://www.tau.ac.il/~ariel/pgp.html >

2 1

BGP Update Report
by cidr-report＠potaroo.net 09 Jun '06

09 Jun '06

BGP Update Report Interval: 26-May-06 -to- 08-Jun-06 (14 days) Observation Point: BGP Peering with AS4637 TOP 20 Unstable Origin AS Rank ASN Upds % Upds/Pfx AS-Name 1 - AS9121 27269 2.3% 65.4 -- TTNET TTnet Autonomous System 2 - AS17974 17031 1.4% 49.2 -- TELKOMNET-AS2-AP PT TELEKOMUNIKASI INDONESIA 3 - AS10139 16250 1.4% 53.5 -- MERIDIAN-PH-AP Meridian Telekoms 4 - AS13127 16050 1.4% 263.1 -- VERSATEL AS for the Trans-European Versatel IP Transport backbone 5 - AS11492 13075 1.1% 24.1 -- CABLEONE - CABLE ONE 6 - AS6830 11785 1.0% 72.7 -- UPC UPC Broadband 7 - AS17430 11322 1.0% 235.9 -- GWBN-CHENGDU Great Wall Broadband Network Service Co.,Ltd 8 - AS7018 10540 0.9% 24.9 -- ATT-INTERNET4 - AT&T WorldNet Services 9 - AS20115 9608 0.8% 19.9 -- CHARTER-NET-HKY-NC - Charter Communications 10 - AS24326 9325 0.8% 211.9 -- TTT-AS-AP TT&T Public Company Limited, Service Provider,Bangkok 11 - AS18231 8746 0.7% 69.4 -- EXATT-AS-AP Exatt Technologies Private Ltd. 12 - AS4755 8338 0.7% 10.2 -- VSNL-AS Videsh Sanchar Nigam Ltd. Autonomous System 13 - AS3462 7846 0.7% 182.5 -- HINET Data Communication Business Group 14 - AS7011 7094 0.6% 10.8 -- FRONTIER-AND-CITIZENS - Frontier Communications, Inc. 15 - AS5803 7030 0.6% 76.4 -- DDN-ASNBLK - DoD Network Information Center 16 - AS3475 6411 0.5% 278.7 -- LANT-AFLOAT - NCTAMS LANT DET HAMPTON ROADS 17 - AS2386 6400 0.5% 7.1 -- INS-AS - AT&T Data Communications Services 18 - AS23918 6319 0.5% 48.2 -- CBB-BGP-IBARAKI Connexion By Boeing Ibaraki AS 19 - AS17557 6207 0.5% 15.5 -- PKTELECOM-AS-AP Pakistan Telecom 20 - AS18207 6046 0.5% 31.7 -- BGBB-INDIA-AP Iqara Telecom India Pvt Ltd. TOP 20 Unstable Origin AS (Updates per announced prefix) Rank ASN Upds % Upds/Pfx AS-Name 1 - AS36877 5008 0.4% 2504.0 -- 2 - AS19982 5152 0.4% 1288.0 -- TOWERSTREAM-PROV - Towerstream 3 - AS35379 2494 0.2% 1247.0 -- EASYNET EASYNET s.c. 4 - AS21027 1233 0.1% 1233.0 -- ASN-PARADORES PARADORES Autonomous System 5 - AS39863 1011 0.1% 1011.0 -- CROSSNET Crossnet LLC 6 - AS34378 912 0.1% 912.0 -- RUG-AS Razguliay-UKRROS Group 7 - AS4678 3405 0.3% 851.2 -- FINE CANON NETWORK COMMUNICATIONS INC. 8 - AS36565 842 0.1% 842.0 -- COUNTY-OF-MONTGOMERY-PA - County of Montgomery 9 - AS25690 1367 0.1% 683.5 -- MAMSI - Mid Atlantic Medical Services Inc. 10 - AS16705 1340 0.1% 670.0 -- STORAGEAPPS - Storage Apps Inc. 11 - AS7013 1192 0.1% 596.0 -- NETSELECT - Health Sciences Libraries Consortium 12 - AS3944 586 0.1% 586.0 -- PARTAN-LAB - Partan & Partan 13 - AS14548 580 0.1% 580.0 -- LISTEN-SF-1 - Listen.com 14 - AS14410 2879 0.2% 575.8 -- DALTON - MCM, Inc., DBA: Internet@Dalton 15 - AS24775 4483 0.4% 560.4 -- AS24775 QinetiQ Ltd 16 - AS23917 1055 0.1% 527.5 -- BRIBIE-NET-AS-AP Bribie Island Net Multihomed, Brisbane 17 - AS3043 3126 0.3% 521.0 -- AMPHIB-AS - Amphibian Media Corporation 18 - AS12408 496 0.0% 496.0 -- BIKENT-AS Bikent Ltd. Autonomous system 19 - AS24896 460 0.0% 460.0 -- UKRINTELL-AS IntellCOM Provider LIR, Kiev, Ukraine Northern Nowhere 20 - AS21944 1360 0.1% 453.3 -- DTSI-1 - Data Technology Services Inc. TOP 20 Unstable Prefixes Rank Prefix Upds % Origin AS -- AS Name 1 - 152.74.0.0/16 3991 0.3% AS11340 -- Red Universitaria Nacional 2 - 81.212.149.0/24 3535 0.3% AS9121 -- TTNET TTnet Autonomous System 3 - 81.212.141.0/24 3503 0.2% AS9121 -- TTNET TTnet Autonomous System 4 - 61.0.0.0/8 3402 0.2% AS4678 -- FINE CANON NETWORK COMMUNICATIONS INC. 5 - 220.114.32.0/21 3158 0.2% AS17430 -- GWBN-CHENGDU Great Wall Broadband Network Service Co.,Ltd 6 - 211.162.88.0/21 3152 0.2% AS17430 -- GWBN-CHENGDU Great Wall Broadband Network Service Co.,Ltd 7 - 209.140.24.0/24 3101 0.2% AS3043 -- AMPHIB-AS - Amphibian Media Corporation 8 - 195.175.82.0/23 2806 0.2% AS9121 -- TTNET TTnet Autonomous System 9 - 196.47.64.0/22 2556 0.2% AS36877 -- 10 - 81.212.125.0/24 2495 0.2% AS9121 -- TTNET TTnet Autonomous System 11 - 196.47.68.0/22 2452 0.2% AS36877 -- 12 - 81.212.124.0/24 2449 0.2% AS9121 -- TTNET TTnet Autonomous System 13 - 209.160.56.0/22 1975 0.1% AS14361 -- HOPONE-DCA - HopOne Internet Corporation 14 - 206.251.163.0/24 1703 0.1% AS4314 -- I-55-INTERNET-SERVICES-INC - I-55 INTERNET SERVICES 15 - 211.162.82.0/23 1528 0.1% AS17430 -- GWBN-CHENGDU Great Wall Broadband Network Service Co.,Ltd 16 - 211.162.84.0/22 1528 0.1% AS17430 -- GWBN-CHENGDU Great Wall Broadband Network Service Co.,Ltd 17 - 220.114.40.0/22 1528 0.1% AS17430 -- GWBN-CHENGDU Great Wall Broadband Network Service Co.,Ltd 18 - 81.212.197.0/24 1317 0.1% AS9121 -- TTNET TTnet Autonomous System 19 - 194.61.180.0/23 1313 0.1% AS24775 -- AS24775 QinetiQ Ltd 20 - 64.17.224.0/19 1296 0.1% AS19982 -- TOWERSTREAM-PROV - Towerstream Details at http://bgpupdates.potaroo.net ------------------------------------ Copies of this report are mailed to: nanog(a)merit.edu eof-list(a)ripe.net apops(a)apops.net routing-wg(a)ripe.net afnog(a)afnog.org ausnog(a)ausnog.net

1 0

The Cidr Report
by cidr-report＠potaroo.net 09 Jun '06

09 Jun '06

This report has been generated at Fri Jun 9 21:48:37 2006 AEST. The report analyses the BGP Routing Table of an AS4637 (Reach) router and generates a report on aggregation potential within the table. Check http://www.cidr-report.org/as4637 for a current version of this report. Recent Table History Date Prefixes CIDR Agg 02-06-06 185948 122700 03-06-06 186208 122508 04-06-06 186215 122492 05-06-06 186199 122459 06-06-06 186279 122916 07-06-06 186581 122644 08-06-06 186580 122654 09-06-06 186532 122618 AS Summary 22301 Number of ASes in routing system 9342 Number of ASes announcing only one prefix 1467 Largest number of prefixes announced by an AS AS7018 : ATT-INTERNET4 - AT&T WorldNet Services 91563008 Largest address span announced by an AS (/32s) AS721 : DISA-ASNBLK - DoD Network Information Center Aggregation Summary The algorithm used in this report proposes aggregation only when there is a precise match using the AS path, so as to preserve traffic transit policies. Aggregation is also proposed across non-advertised address space ('holes'). --- 09Jun06 --- ASnum NetsNow NetsAggr NetGain % Gain Description Table 186522 122961 63561 34.1% All ASes AS4323 1305 266 1039 79.6% TWTC - Time Warner Telecom, Inc. AS4134 1229 291 938 76.3% CHINANET-BACKBONE No.31,Jin-rong Street AS18566 943 187 756 80.2% COVAD - Covad Communications Co. AS721 1014 317 697 68.7% DISA-ASNBLK - DoD Network Information Center AS22773 661 47 614 92.9% CCINET-2 - Cox Communications Inc. AS6197 1009 479 530 52.5% BATI-ATL - BellSouth Network Solutions, Inc AS7018 1467 944 523 35.7% ATT-INTERNET4 - AT&T WorldNet Services AS19916 563 65 498 88.5% ASTRUM-0001 - OLM LLC AS855 550 64 486 88.4% CANET-ASN-4 - Aliant Telecom AS17488 514 42 472 91.8% HATHWAY-NET-AP Hathway IP Over Cable Internet AS9498 572 149 423 74.0% BBIL-AP BHARTI BT INTERNET LTD. AS3602 524 104 420 80.2% AS3602-RTI - Rogers Telecom Inc. AS18101 414 28 386 93.2% RIL-IDC Reliance Infocom Ltd Internet Data Centre, AS15270 429 50 379 88.3% AS-PAETEC-NET - PaeTec.net -a division of PaeTecCommunications, Inc. AS17676 486 110 376 77.4% JPNIC-JP-ASN-BLOCK Japan Network Information Center AS4755 872 515 357 40.9% VSNL-AS Videsh Sanchar Nigam Ltd. Autonomous System AS11492 622 268 354 56.9% CABLEONE - CABLE ONE AS4766 657 307 350 53.3% KIXS-AS-KR Korea Telecom AS22047 419 78 341 81.4% VTR BANDA ANCHA S.A. AS812 370 30 340 91.9% ROGERS-CABLE - Rogers Cable Inc. AS6467 382 52 330 86.4% ESPIRECOMM - Xspedius Communications Co. AS16852 355 50 305 85.9% FOCAL-CHICAGO - Focal Data Communications of Illinois AS8151 705 404 301 42.7% Uninet S.A. de C.V. AS19262 664 370 294 44.3% VZGNI-TRANSIT - Verizon Internet Services Inc. AS14654 292 15 277 94.9% WAYPORT - Wayport AS16814 329 52 277 84.2% NSS S.A. AS3352 305 30 275 90.2% TELEFONICA-DATA-ESPANA Internet Access Network of TDE AS5668 528 253 275 52.1% AS-5668 - CenturyTel Internet Holdings, Inc. AS6198 509 241 268 52.7% BATI-MIA - BellSouth Network Solutions, Inc AS19115 348 86 262 75.3% CHARTER-LEBANON - Charter Communications Total 19037 5894 13143 69.0% Top 30 total Possible Bogus Routes 24.246.0.0/17 AS7018 ATT-INTERNET4 - AT&T WorldNet Services 24.246.128.0/18 AS7018 ATT-INTERNET4 - AT&T WorldNet Services 61.4.64.0/20 AS9929 CNCNET-CN China Netcom Corp. 64.17.32.0/24 AS13488 CBWU-13488 - Continental Broadband Florida, Inc DBA WebUnited 64.17.33.0/24 AS13488 CBWU-13488 - Continental Broadband Florida, Inc DBA WebUnited 64.17.37.0/24 AS13488 CBWU-13488 - Continental Broadband Florida, Inc DBA WebUnited 66.11.32.0/20 AS6261 VISINET - Visionary Systems, Inc. 66.37.96.0/20 AS3764 IA-HOU-AS - Internet America, Inc. 66.51.134.0/24 AS29876 LNTC - Latency LLC 66.96.0.0/20 AS3770 WORLDPATH-AS - WorldPath Internet Services 66.117.8.0/24 AS174 COGENT Cogent/PSI 66.163.96.0/20 AS25767 WAVEFORM - Waveform Technology, LLC 66.187.96.0/24 AS10026 ANC Asia Netcom Corporation 66.187.108.0/24 AS10026 ANC Asia Netcom Corporation 66.187.109.0/24 AS10026 ANC Asia Netcom Corporation 66.235.158.0/23 AS7018 ATT-INTERNET4 - AT&T WorldNet Services 69.31.151.0/24 AS26627 AS-PILOSOFT - Pilosoft, Inc. 69.39.193.0/24 AS25973 MZIMA - Mzima Networks, Inc. 69.39.195.0/24 AS25973 MZIMA - Mzima Networks, Inc. 69.39.196.0/24 AS25973 MZIMA - Mzima Networks, Inc. 91.192.0.0/16 AS12654 RIPE-NCC-RIS-AS RIPE NCC RIS Project. 91.255.248.0/21 AS12654 RIPE-NCC-RIS-AS RIPE NCC RIS Project. 125.213.0.0/16 AS4134 CHINANET-BACKBONE No.31,Jin-rong Street 131.64.0.0/12 AS721 DISA-ASNBLK - DoD Network Information Center 132.0.0.0/10 AS721 DISA-ASNBLK - DoD Network Information Center 137.0.0.0/13 AS721 DISA-ASNBLK - DoD Network Information Center 138.136.0.0/13 AS721 DISA-ASNBLK - DoD Network Information Center 151.135.0.0/16 AS4763 TELSTRANZ-AS TelstraClear Ltd 158.0.0.0/13 AS721 DISA-ASNBLK - DoD Network Information Center 163.142.0.0/16 AS2500 JPNIC-ASBLOCK-AP JPNIC 183.206.196.0/24 AS2188 FR-RENATER-ASTER Reseau Regional ASTER 192.30.93.0/24 AS17757 HPAUS-AP HP Australia 192.30.94.0/24 AS17757 HPAUS-AP HP Australia 192.40.105.0/24 AS12582 TSF-DATANET-NGD-AS TSF MPLS VPN Services 192.69.107.0/24 AS5515 SONERA-GLOBAL-IP Sonera Solution Autonomous System 192.69.108.0/24 AS5515 SONERA-GLOBAL-IP Sonera Solution Autonomous System 192.69.177.0/24 AS5515 SONERA-GLOBAL-IP Sonera Solution Autonomous System 192.70.164.0/24 AS25689 NRCNET-AS - National Research Council of Canada 192.81.183.0/24 AS719 ELISA-AS Elisa Oyj 192.81.184.0/24 AS719 ELISA-AS Elisa Oyj 192.88.99.0/24 AS16150 PORT80-GLOBALTRANSIT Port80 AB, Sweden 192.96.36.0/24 AS5713 AFRINIC African Network Information Center 192.96.37.0/24 AS10474 AFRINIC African Network Information Center 192.96.135.0/24 AS2018 TENET - 1 - The Uninet Project 192.96.136.0/23 AS2018 TENET - 1 - The Uninet Project 192.96.140.0/24 AS2018 TENET - 1 - The Uninet Project 192.96.143.0/24 AS2018 TENET - 1 - The Uninet Project 192.96.145.0/24 AS2018 TENET - 1 - The Uninet Project 192.96.177.0/24 AS6083 POSIX-AFRICA Posix Systems 192.96.250.0/24 AS2018 TENET - 1 - The Uninet Project 192.107.104.0/24 AS6458 GUATEL 192.122.212.0/24 AS209 ASN-QWEST - Qwest 192.124.252.0/22 AS680 DFN-IP service G-WiN 192.133.6.0/24 AS10282 EQUANT-CEEUR EQUANT AS for Central and Eastern Europe region 192.153.144.0/21 AS721 DISA-ASNBLK - DoD Network Information Center 192.168.255.255/32 AS4637 REACH Reach Network Border AS 192.172.0.0/19 AS721 DISA-ASNBLK - DoD Network Information Center 192.188.208.0/20 AS721 DISA-ASNBLK - DoD Network Information Center 193.36.1.0/24 AS8220 COLT COLT Telecommunications 193.37.69.0/24 AS2856 BT-UK-AS BTnet UK Regional network 193.110.77.0/24 AS3356 LEVEL3 Level 3 Communications 193.110.78.0/24 AS3356 LEVEL3 Level 3 Communications 193.110.79.0/24 AS3356 LEVEL3 Level 3 Communications 194.31.227.0/24 AS21461 TRANSFAIRNET Transfair-net GmbH Krefeld 194.59.176.0/20 AS1273 CW Cable & Wireless 194.153.156.0/24 AS24865 KMITCHELL-AS Keith Mitchell's Network 194.156.206.0/24 AS4589 EASYNET Easynet Group Plc 194.246.72.0/23 AS8893 ARTFILES-AS Artfiles New Media GmbH 195.189.254.0/23 AS31283 FASTHOST-AS FastHost AS - Norwegian based ISP 195.246.216.0/22 AS15622 MEOCOM old meocom Autonomous System 196.3.162.0/24 AS6083 POSIX-AFRICA Posix Systems 196.6.108.0/24 AS5713 AFRINIC African Network Information Center 196.6.175.0/24 AS3741 IS - The Internet Solution 196.6.176.0/23 AS3741 IS - The Internet Solution 196.6.183.0/24 AS3741 IS - The Internet Solution 196.6.196.0/24 AS3741 IS - The Internet Solution 196.6.199.0/24 AS3741 IS - The Internet Solution 196.6.208.0/24 AS3741 IS - The Internet Solution 196.6.211.0/24 AS3741 IS - The Internet Solution 196.6.212.0/23 AS3741 IS - The Internet Solution 196.6.212.0/24 AS3741 IS - The Internet Solution 196.6.222.0/23 AS3741 IS - The Internet Solution 196.6.237.0/24 AS3741 IS - The Internet Solution 196.10.119.0/24 AS2018 TENET - 1 - The Uninet Project 196.10.122.0/23 AS2018 TENET - 1 - The Uninet Project 196.10.136.0/22 AS3741 IS - The Internet Solution 196.10.140.0/22 AS3741 IS - The Internet Solution 196.10.231.0/24 AS3741 IS - The Internet Solution 196.10.251.0/24 AS2018 TENET - 1 - The Uninet Project 196.10.252.0/23 AS2018 TENET - 1 - The Uninet Project 196.10.254.0/24 AS2018 TENET - 1 - The Uninet Project 196.11.0.0/20 AS3741 IS - The Internet Solution 196.11.40.0/21 AS3741 IS - The Internet Solution 196.11.135.0/24 AS3741 IS - The Internet Solution 196.11.188.0/23 AS3741 IS - The Internet Solution 196.11.190.0/24 AS3741 IS - The Internet Solution 196.11.251.0/24 AS3741 IS - The Internet Solution 196.13.101.0/24 AS2018 TENET - 1 - The Uninet Project 196.13.102.0/23 AS2018 TENET - 1 - The Uninet Project 196.13.104.0/24 AS2018 TENET - 1 - The Uninet Project 196.13.108.0/24 AS3741 IS - The Internet Solution 196.13.116.0/22 AS2018 TENET - 1 - The Uninet Project 196.13.121.0/24 AS2018 TENET - 1 - The Uninet Project 196.13.125.0/24 AS2018 TENET - 1 - The Uninet Project 196.13.126.0/24 AS2018 TENET - 1 - The Uninet Project 196.13.127.0/24 AS3741 IS - The Internet Solution 196.13.128.0/22 AS3741 IS - The Internet Solution 196.13.144.0/22 AS2905 VZBSA Verizon South Africa 196.13.152.0/21 AS2905 VZBSA Verizon South Africa 196.13.160.0/24 AS2905 VZBSA Verizon South Africa 196.13.169.0/24 AS2018 TENET - 1 - The Uninet Project 196.13.174.0/23 AS2018 TENET - 1 - The Uninet Project 196.13.176.0/21 AS2018 TENET - 1 - The Uninet Project 196.13.188.0/22 AS2018 TENET - 1 - The Uninet Project 196.13.192.0/22 AS2018 TENET - 1 - The Uninet Project 196.13.196.0/24 AS2018 TENET - 1 - The Uninet Project 196.13.252.0/22 AS2018 TENET - 1 - The Uninet Project 198.23.26.0/24 AS4390 BELLATLANTIC-COM - Bell Atlantic, Inc. 198.54.82.0/24 AS2018 TENET - 1 - The Uninet Project 198.54.92.0/24 AS2018 TENET - 1 - The Uninet Project 198.54.222.0/24 AS2018 TENET - 1 - The Uninet Project 198.54.249.0/24 AS2018 TENET - 1 - The Uninet Project 198.54.250.0/24 AS2018 TENET - 1 - The Uninet Project 198.54.251.0/24 AS2018 TENET - 1 - The Uninet Project 198.97.72.0/21 AS721 DISA-ASNBLK - DoD Network Information Center 198.97.80.0/20 AS721 DISA-ASNBLK - DoD Network Information Center 198.97.96.0/19 AS721 DISA-ASNBLK - DoD Network Information Center 198.97.240.0/20 AS721 DISA-ASNBLK - DoD Network Information Center 198.101.4.0/22 AS721 DISA-ASNBLK - DoD Network Information Center 198.136.32.0/20 AS19329 MCNET - Martin County Board of County Commissioners 198.161.87.0/24 AS6539 GT-BELL - Bell Canada 198.163.155.0/24 AS684 MTSAL-ASN - MTS Allstream Inc. 198.167.0.0/16 AS7456 INTERHOP - Interhop Network SERVICES Inc. 198.168.0.0/16 AS701 ALTERNET-AS - UUNET Technologies, Inc. 198.169.0.0/16 AS803 SASKTEL - SaskTel 198.199.198.0/24 AS13671 VRIS-AS-BLOCK-13661-13675 - Verizon Internet Services Inc. 198.232.133.0/24 AS23075 SKOTOS-AS - Skotos Tech, Inc 199.9.128.0/17 AS668 ASN-ASNET-NET-AS - Defense Research and Engineering Network 199.10.0.0/16 AS721 DISA-ASNBLK - DoD Network Information Center 199.60.0.0/20 AS271 BCNET-AS - University of British Columbia 199.114.0.0/21 AS721 DISA-ASNBLK - DoD Network Information Center 199.114.128.0/18 AS721 DISA-ASNBLK - DoD Network Information Center 199.114.130.0/24 AS721 DISA-ASNBLK - DoD Network Information Center 199.114.132.0/24 AS721 DISA-ASNBLK - DoD Network Information Center 199.114.134.0/24 AS3541 ITSDN-U4 - DISA/UNRRA 199.114.136.0/24 AS27044 DDN-ASNBLK1 - DoD Network Information Center 199.114.138.0/24 AS721 DISA-ASNBLK - DoD Network Information Center 199.114.140.0/24 AS3544 ITSDN-U7 - DISA/UNRRA 199.114.142.0/24 AS721 DISA-ASNBLK - DoD Network Information Center 199.114.144.0/24 AS27064 DDN-ASNBLK1 - DoD Network Information Center 199.114.148.0/24 AS721 DISA-ASNBLK - DoD Network Information Center 199.114.150.0/24 AS721 DISA-ASNBLK - DoD Network Information Center 199.114.152.0/24 AS27033 DDN-ASNBLK1 - DoD Network Information Center 199.114.153.0/24 AS27034 DDN-ASNBLK1 - DoD Network Information Center 199.114.154.0/24 AS3542 ITSDN-U5 - DISA/UNRRA 199.114.160.0/24 AS1733 CENTAF-SWA - AF DDN PMO 199.121.0.0/16 AS721 DISA-ASNBLK - DoD Network Information Center 199.123.0.0/18 AS721 DISA-ASNBLK - DoD Network Information Center 199.123.16.0/20 AS721 DISA-ASNBLK - DoD Network Information Center 199.123.80.0/21 AS721 DISA-ASNBLK - DoD Network Information Center 199.189.32.0/19 AS7332 IQUEST-AS - IQuest Internet 199.202.0.0/16 AS701 ALTERNET-AS - UUNET Technologies, Inc. 199.246.116.0/24 AS813 UUNET-AS1 - UUNET Technologies, Inc. 202.9.64.0/19 AS9290 TPN-AS-AP Smart Global Network (M) Sdn Bhd 202.45.159.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 202.58.113.0/24 AS19161 INNOCOM-TELECOM - INNOCOM TELECOM 202.86.252.0/22 AS9304 HUTCHISON-AS-AP Hutchison Global Communications 202.86.253.0/24 AS9304 HUTCHISON-AS-AP Hutchison Global Communications 202.86.254.0/24 AS9304 HUTCHISON-AS-AP Hutchison Global Communications 202.86.255.0/24 AS9304 HUTCHISON-AS-AP Hutchison Global Communications 202.90.33.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.90.40.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.90.41.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.90.42.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.90.43.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.90.44.0/24 AS9830 SWIFTONLINE-AS-AP SWIFT ONLINE BORDER AS 202.93.0.0/20 AS4134 CHINANET-BACKBONE No.31,Jin-rong Street 202.124.192.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 202.124.193.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 202.124.194.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 202.124.195.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 202.124.196.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 202.124.197.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 202.124.198.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 202.124.199.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 202.124.200.0/22 AS15412 FLAG-AS Flag Telecom Global Internet AS 202.124.204.0/24 AS15412 FLAG-AS Flag Telecom Global Internet AS 202.124.205.0/24 AS15412 FLAG-AS Flag Telecom Global Internet AS 202.124.206.0/24 AS15412 FLAG-AS Flag Telecom Global Internet AS 202.124.207.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 202.131.64.0/19 AS9381 NEWTT-IP-AP Wharf T&T Ltd. 202.148.32.0/20 AS17495 GATEWAY-AP BROADBAND WIRELESSS INTERNET SERVICE PROVIDER 202.160.128.0/23 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.128.0/24 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.131.0/24 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.132.0/22 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.136.0/22 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.142.0/24 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.144.0/24 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.145.0/24 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.146.0/24 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.147.0/24 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.152.0/22 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.156.0/23 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.157.0/24 AS10113 DATAFAST-AP DATAFAST TELECOMMUNICATIONS LTD 202.160.158.0/23 AS9837 POWERTEL-AP Powertel Ltd 202.164.100.0/24 AS18101 RIL-IDC Reliance Infocom Ltd Internet Data Centre, 203.13.171.0/24 AS1221 ASN-TELSTRA Telstra Pty Ltd 203.62.0.0/17 AS7575 AARNET-AS-AP Australian Academic and Reasearch Network (AARNet) 203.78.48.0/20 AS9299 IPG-AS-AP Philippine Long Distance Telephone Company 203.89.134.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.139.0/24 AS17911 BRAINPK-AS-AP Brain Telecommunication Ltd. 203.89.143.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.144.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.147.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.148.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.149.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.150.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.151.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.153.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.158.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.89.159.0/24 AS17557 PKTELECOM-AS-AP Pakistan Telecom 203.99.142.0/24 AS9826 ILINK-HK-AP iLink.net Ltd 203.111.192.0/20 AS7473 SINGTEL-AS-AP Singapore Telecom 204.29.185.0/24 AS7268 ATHENET - Athenet Internet Services 204.48.118.0/23 AS29912 CITIZENS-PROPERTY-INSURANCE-CORPORATION - Citizens Property Insurance Corporation 204.48.119.0/24 AS29912 CITIZENS-PROPERTY-INSURANCE-CORPORATION - Citizens Property Insurance Corporation 204.153.104.0/24 AS10913 INTERNAP-BLK - Internap Network Services 204.153.106.0/24 AS10913 INTERNAP-BLK - Internap Network Services 204.153.107.0/24 AS10913 INTERNAP-BLK - Internap Network Services 204.154.125.0/24 AS3952 TELLABS-ASN - TELLABS Operations, Inc. 204.154.126.0/24 AS3952 TELLABS-ASN - TELLABS Operations, Inc. 204.154.127.0/24 AS3952 TELLABS-ASN - TELLABS Operations, Inc. 205.150.0.0/15 AS701 ALTERNET-AS - UUNET Technologies, Inc. 206.128.104.0/21 AS11709 VIC - VIRTUAL INTERACTIVE CENTER 206.167.57.0/24 AS376 RISQ-AS - Reseau Interordinateurs Scientique Quebecois (RISQ) 206.191.64.0/18 AS15290 ALLST-15290 - Allstream Corp. Corporation Allstream 206.191.96.0/19 AS15290 ALLST-15290 - Allstream Corp. Corporation Allstream 207.231.96.0/19 AS11194 NUNETPA - NuNet Inc 209.40.192.0/21 AS6487 CyberNet de Guatemala S.A. 209.40.200.0/21 AS6487 CyberNet de Guatemala S.A. 209.40.208.0/21 AS6487 CyberNet de Guatemala S.A. 209.40.216.0/21 AS6487 CyberNet de Guatemala S.A. 209.205.70.0/24 AS21578 Universidad autonoma de Bucaramanga 209.205.81.0/24 AS15066 SkyNet de Colombia S.A. 209.205.82.0/24 AS15066 SkyNet de Colombia S.A. 209.205.84.0/24 AS15066 SkyNet de Colombia S.A. 209.234.0.0/18 AS3845 STATE-NET - CS&W, Inc. 209.250.224.0/20 AS19318 NJIIX-AS-1 - NEW JERSEY INTERNATIONAL INTERNET EXCHANGE LLC 216.37.110.0/23 AS4264 CERNET-ASN-BLOCK - California Education and Research Federation Network 216.71.224.0/20 AS23527 COTELLIGENCE - Cotelligence, Inc. 216.201.72.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.73.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.74.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.75.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.76.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.77.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.78.0/24 AS14709 Telefonica Moviles Panama S.A. 216.201.79.0/24 AS14709 Telefonica Moviles Panama S.A. 216.228.64.0/21 AS6295 WHIDBEY1 - Whidbey Internet Services 216.228.224.0/20 AS13674 VRIS-AS-BLOCK-13661-13675 - Verizon Internet Services Inc. 216.240.240.0/20 AS7018 ATT-INTERNET4 - AT&T WorldNet Services 216.240.242.0/24 AS7018 ATT-INTERNET4 - AT&T WorldNet Services Please see http://www.cidr-report.org for the full report ------------------------------------ Copies of this report are mailed to: nanog(a)merit.edu eof-list(a)ripe.net apops(a)apops.net routing-wg(a)ripe.net afnog(a)afnog.org ausnog(a)ausnog.net

1 0

2006.06.07 NANOG-NOTES Issues with IPv6 multihoming
by Matthew Petach 09 Jun '06

09 Jun '06

(hope the inclusion of URLs in the notes isn't making them all end up in people's spam folders... --Matt) 2006.06.07 Vince Fuller, from Cisco and Jason Schiller from UUnet [slides are at: http://www.nanog.org/mtg-0606/pdf/vince-fuller.pdf IPv6 issues routing and multihoming scalability with respect to routing issues. how we got where we are today define "locator" "endpoint-id" and their functions Explain why these concepts matter, why this separation is a good thing understand that v4 and v6 mingle these functions, and why it matters recognized exponential growth - late 1980s CLNS as IP replacement dec 1990 IETF OSI, TP4 over CLNS--edict handed down from IETF revolt against that, IP won ROAD group and the "three trucks" 1991-1992 running out of "class-B" network numbers explosive growth of "default-free" routing table eventual exhaustion of 32-bit address space two efforts -- short-term vs long-term More at "the long and winding ROAD" http://rms46.vlsm.org/1/42.html Supernetting and CIDR 1992-1993 Two efforts to fix it; CIDR, short term effort, long term effort became IPv6. IETF ipng solicitation RFC 1550 Dec 1993 Direction and technical criteria for ipng choice RFC1719 and RFC 1726, Dec 1994 proliferation of proposals TUBA == IP over CLNS NIMROD==how to deal with it from high level Lots of flaming back and forth, not much good technical work. choice eventually made on political choices, not technical merit. Things lost in shuffle...er compromise included: variable length addresses decoupling of transport and network-layer addresses clear separation of endpoint-id/locator (more later) routing aggregation/abstraction "math is hard, let's go shopping" -- solving the real issues was set aside, people focused on writing packet headers instead identity -- what's in a name think of an "endpoint-id" as the "name" of a device or protocol stack instance that is communicating over a network in the real world, this is like your "name"--who you are. a "domain name" is a human readable analogue endpoint-IDs: persistent--long term binding, stays around as long as machine is up ease of administrative assignment hierarchy along organization boundry (like DNS), not topology portable: stay the same no matter where in the hierarchy you are Globally unique! unlike human names. ^_^ Locators: "where" you are in the network think of "source" and "dest" addresses in routing and forwarding as locators real-world analogy is street addresses or phone numbers. typically some hierarchy (like address), or like historical phone number (before portability!) Desireable properties of locators: hierarchical assignment according to topology (isomorphic) dynamic, transparent renumbering without disruption unique when fully specified, but may be abstracted to reduce unwanted state variable length realworld--don't need to exact street address in Australia to fly there Possbly applied to traffic without end-system knowledge effectively like NAT, but doesn't beak end-to-end Why should I care? v4/v6 there are only "addresses" which serve as both endpoint-ids and locators this means they don't have the desirable properties of either: assignment to organizations is painful because use as locator constrains it to be topological exceptions to topology create additional global state renumbering is hard; DHCP isn't enough, sessions get distrupted, source-based filtering breaks, etc. Doesn't scale for large numbers of "provider-indep" or multihomed sites why should I care? currently, v6 is only a few hundred prefixes; won't be a problem until it really ccatches on, at which point it's too late. larger v6 space gives potentially more pain NAT is effectively id/locator split--what happens if NAT goes away in v6? scale of IP networks still very small compared to what it could grow to re-creating the routing swamp with ipv6 with longer addresses could be disasterous; not clear if internet could be saved in that case. Been ignored by IETF for 10+ years concepts have been known since 60s. Can v6 be fixed? And what is GSE, anyhow? Mike O'Dell proposed this in 1997 with 8+8/GSE keep v6 packet format, implement id/locator split http://ietfreport.isoc.org/idref/draft-ietf-ipngwg-gseaddr basic idea: separate 16-byte addrss into 8-byte EID and 8-byte routing goop/locator change TCP/UDP to only care about 8-bytes. allow routing system to muck with other 8 bytes in-flight achieves goal of EID/locator split while keeping most of IPv6, hopefully without requiring new database for EID-to-locator mapping Allows for scalable multi-homing Renumbering can be fast and painless/transparent to hosts. GSE issues problems with it--incompatible changes to TCP/UDP in 1997, no IPv6 installed base, easy to change; now, v6 deployed, is it too late to change? violation of end-to-end principle. perceived security weakness of trusting "naked" EID (steve bellovin says this is a non-issue) mapping of EID to EID+RG may add complexity to DNS depending on how implemented scalable TE not in original design; will differ from v4 TE, may invole NAT-like RG re-wriete currently not being pursued--killed by IETF politics. GSE is only one approach isn't only way to do this, but is a straightforward retro-fit to existing protocols other approaches: [see slide, flipped past pretty quickly] big problem, *no* approaches being pursued. what about shim6/multi6 approx 3-year-old IETF effort to retro-fit an endpoint-id/locator split... [wow, he's running low on time, cranking through it] Nobody really likes it, but for different cases/reasons. What if nothing changed how about a "thought experiment" make assumptions about v6 and internet growth take a guess at growth trends pose some questions cloudy crystal ball v6 deployed in parallel to v4, widely adopted v4 will be predominant; will be used indefinitely v4 routing state growth will continue to grow at superlinear rate, up to or beyond address exhaustion will just get chunked up smaller and smaller routers in DFZ zone will continue to need more and more state. v6 prefix assignments allow orgs to aggregate their space into a single prefix. shim6 won't see large adoption v4 style multihoming will expand into v6 Questions to worry about how much routing state growth due to orgs needing multiple prefixes? will growth rate decrease to number of ASes? in v4, prefix to AS is 6:1, will it be 1:1 in v6? can we reduce unintentional deagg? what is churn rate? can we reduce intentional deagg? if we add more state to routing for security, what happens to CPUs? (SBGP/soBGP) Geoff Huston's v4 BGP growth report starting to look like quadratic growth... Jason's analysis: future routing state size v6 widespread adoption *will* happen; what will it look like? looks at v4 routing table to decide what likely scenario is. Based on Tony Bates CIDR report. prefixes: 180,219, 111K aggregated; so 1/3 are traffic engineering prefixes so, current 180K v4 prefixes 21K v6 prefixes 61K v6 TE prefixes 50-150K internal routes for tier 1 40-120K customer VPN/deagg'd routes 352-532K prefixes total a single AS that has multiple non-contiguous assignments that would still announce same number of prefixes. with removal of NAT, will people who hid multiple blocks for TE behind NATs, will they need more prefixes? what about new v6 only networks for mobile phones, etc? intentional deaggregates seems to be steepest quadratic curve on his chart. He plots UUnet internal deaggs, they are also quadratic. 650K to 1M routes in 5 years in 10 years, 1.1M low to 1.8M on high side. Marshall Eubanks on ppml Are these numbers ridiculous? How many multi-homed sites could there really be? consider as upper bound the number of small-to-med businesses worldwide, suggests up to 6M SMB prefixes would show up. Jason's conclusion--make sure we know what we're getting into when we talk about v6 without fixing the routing hierarchy. Can router vendors build boxes to solve this, or do we need to fix the protocols? Vince notes the hardware vendors loved the quadratic growth in the late nineties, with 3 year turnovers; helped Cisco become the giant it is. IETF Been there IAB/IESG is actively hostile NANOG/RIPE/APRICOT? ITU (enemy of internet for years) architecture-discuss(a)ietf.org ppml(a)arin.net ipmh-interest(a)external.cisco.com bunch of recommended reading slides. 10 minutes over into lightning talks already. 5 minutes of questions, and then MUST move on. Q: Steve Bellovin, columbia university--been pushing id/locator sep since 1986; nobody had been working on it; Vint Cerf said he tried it way back when, it's hard. He does note this still has open denial of service challenges that need to be addressed; but Steve does agree they aren't show stoppers. Q: Randy Bush, IIJ, been discussing this know for quite some time--where to talk about it? it's been talked about everywhere, problem is the people who need to write it are burned out. Alain Durand is a perfect example of ipv6 usage that doesn't pollute the global table. Should we bother, or just resign ourselves to signing up for buying new routers every 3 years? Q: Alan--is there a mathematical model that looks at the different routing protocols, BGP in particular, to show where it simply will fail to converge? A: Not sure--NSF, Craig Labovitz did some research on it; imagine a perfect network, infinite CPU, zero latency; can someone do the math and find out where the hard ceiling is? Sounds like a fine research question. Q: Jared Mauch, NTT, what alternatives do we have for BGP, or what are we doing to resolve that issue. A: problem isn't BGP, it's the amount of state being held, regardless of how you pass it around. Q: Jared notes operator burnout is significant, and the frustration with IETF is serious; can we solve this on our own outside the IETF? Q: Tony Hain, Cisco. Security infrasctrure built around overload; that it can look at locator to know 'who' is being talked to. Mike O'Dell also responsible for part of the problem if you are going to play, there is ONE global default free zone. Does that assumption make sense? Take it up on the mailing list, on architecture discuss and ipmh. Q: Rob Seastrom: fundamental disconnect, rough consensus and working code disconnect. Nobody has working code, so this discussion is simply flailing. Discussion on mailing list may be bringing vendors to table. On to the lightning talks!!

1 0