May 2018 - Test - lists.nanog.org

Anyone on from Comcast?
by Janet Sullivan 07 May '18

07 May '18

I've spent my morning in customer support hell. Sorry for the noise, but if someone with clue could help a gig residential customer getting 3 Mbit/s, I'd love you.

1 0

Route Reflector Client Design Question
by Erik Sundberg 07 May '18

07 May '18

I have a RR Client design question...... CORE1-------------------2x10G-----------------------CORE2 | | | | | 10G Ring | | | | | PE1----------PE2----------PE3----------PE4----------PE5 -Core1 & Core2 are RR Reflectors with full IPV4 Tables (ASR9K) -MPLS LDP Enabled -IGP is ISIS -Each PE peers only with Core1 and Core2 as RR Clients with iBGP -PE's are only receiving a default route from the Core Routers due to TCAM size of 20K (ASR920's\ME3800's) -The ring does not have that much traffic on it <500m, so I do not want to use additional 10G ports on the Core's and is why I have it in a 10G U ring. -Primary link to the cores is via the PE1 --- CORE1 Like......... For this discussion the link between PE5 to CORE2 is set up as a backup link. The scenario is I have traffic between PE2 and PE3. Since the PE's are only receiving a default route from the Cores. Traffic is label switch from PE2 - PE1 - Core1 does a IP lookup at Ingress then label switches back to PE1-PE2-PE3. This ends up being 5 hops and doubling the traffic on the link to the Cores. My questions is how do I get traffic to go directly between the PE's without going to the Core Routers? 1. Can I enable iBGP between the PE's in a full mesh to allow traffic between the PE's without going to the core's. Or does this break the Route Reflector model? 2. Create a route policy on the Core's advertising routes learned from the PE's back to all the PE's on the ring. 3. Is this one of the down sides to U Rings? 4. Leave it alone and move on to bigger and better things.... Thanks Erik ________________________________ CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error please notify the sender immediately by replying to this e-mail. You must destroy the original transmission and its attachments without reading or saving in any manner. Thank you.

9 12

NSR / NSF
by Hari . 05 May '18

05 May '18

Checking on best practice being followed with regards to enabling NSF or NSR or both on ASR 9k. Which option can be beneficial and considered to be a standard approach. Thanks!

2 1

RE: Route Reflector Client Design Question
by Jakob Heitz (jheitz) 04 May '18

04 May '18

You could optimize the packet hop count by making smaller but more rings. For example, make one ring with CORE1, CORE2, PE1, PE2, PE3. And another ring with CORE1, CORE2, PE4, PE5. If you configure "route-reflector-client" on the CORE, and mesh the clients, then you can additionally configure "bgp client-to-client reflection disable". However, if the CORE is just sending a default route, then you probably have default-originate and no RR clients on the CORE. Then you don't need to disable reflection, because it's not reflecting anyway. (reflection refers to the reflection of routes, not reflection of packets). You could send limited important or heavily used prefixes between the PEs using route policy without blowing up the TCAM. Regards, Jakob. -----Original Message----- From: Erik Sundberg <ESundberg(a)nitelusa.com> I have a RR Client design question...... CORE1-------------------2x10G-----------------------CORE2 | | | | | 10G Ring | | | | | PE1----------PE2----------PE3----------PE4----------PE5 -Core1 & Core2 are RR Reflectors with full IPV4 Tables (ASR9K) -MPLS LDP Enabled -IGP is ISIS -Each PE peers only with Core1 and Core2 as RR Clients with iBGP -PE's are only receiving a default route from the Core Routers due to TCAM size of 20K (ASR920's\ME3800's) -The ring does not have that much traffic on it <500m, so I do not want to use additional 10G ports on the Core's and is why I have it in a 10G U ring. -Primary link to the cores is via the PE1 --- CORE1 Like......... For this discussion the link between PE5 to CORE2 is set up as a backup link. The scenario is I have traffic between PE2 and PE3. Since the PE's are only receiving a default route from the Cores. Traffic is label switch from PE2 - PE1 - Core1 does a IP lookup at Ingress then label switches back to PE1-PE2-PE3. This ends up being 5 hops and doubling the traffic on the link to the Cores. My questions is how do I get traffic to go directly between the PE's without going to the Core Routers? 1. Can I enable iBGP between the PE's in a full mesh to allow traffic between the PE's without going to the core's. Or does this break the Route Reflector model? 2. Create a route policy on the Core's advertising routes learned from the PE's back to all the PE's on the ring. 3. Is this one of the down sides to U Rings? 4. Leave it alone and move on to bigger and better things....

1 0

Weekly Routing Table Report
by cscora＠apnic.net 04 May '18

04 May '18

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG, IRNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 05 May, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 698222 Prefixes after maximum aggregation (per Origin AS): 268829 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 336897 Total ASes present in the Internet Routing Table: 60652 Prefixes per ASN: 11.51 Origin-only ASes present in the Internet Routing Table: 52419 Origin ASes announcing only one prefix: 22938 Transit ASes present in the Internet Routing Table: 8233 Transit-only ASes present in the Internet Routing Table: 267 Average AS path length visible in the Internet Routing Table: 4.0 Max AS path length visible: 30 Max AS path prepend of ASN ( 30873) 28 Prefixes from unregistered ASNs in the Routing Table: 51 Number of instances of unregistered ASNs: 51 Number of 32-bit ASNs allocated by the RIRs: 22423 Number of 32-bit ASNs visible in the Routing Table: 18107 Prefixes from 32-bit ASNs in the Routing Table: 75449 Number of bogon 32-bit ASNs visible in the Routing Table: 14 Special use prefixes present in the Routing Table: 3 Prefixes being announced from unallocated address space: 297 Number of addresses announced to Internet: 2858741122 Equivalent to 170 /8s, 100 /16s and 237 /24s Percentage of available address space announced: 77.2 Percentage of allocated address space announced: 77.2 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.9 Total number of prefixes smaller than registry allocations: 232759 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 191019 Total APNIC prefixes after maximum aggregation: 54116 APNIC Deaggregation factor: 3.53 Prefixes being announced from the APNIC address blocks: 189798 Unique aggregates announced from the APNIC address blocks: 77981 APNIC Region origin ASes present in the Internet Routing Table: 8773 APNIC Prefixes per ASN: 21.63 APNIC Region origin ASes announcing only one prefix: 2452 APNIC Region transit ASes present in the Internet Routing Table: 1307 Average APNIC Region AS path length visible: 4.0 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3737 Number of APNIC addresses announced to Internet: 766870786 Equivalent to 45 /8s, 181 /16s and 133 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-137529 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 207973 Total ARIN prefixes after maximum aggregation: 99038 ARIN Deaggregation factor: 2.10 Prefixes being announced from the ARIN address blocks: 209004 Unique aggregates announced from the ARIN address blocks: 98978 ARIN Region origin ASes present in the Internet Routing Table: 18167 ARIN Prefixes per ASN: 11.50 ARIN Region origin ASes announcing only one prefix: 6717 ARIN Region transit ASes present in the Internet Routing Table: 1794 Average ARIN Region AS path length visible: 3.6 Max ARIN Region AS path length visible: 20 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2346 Number of ARIN addresses announced to Internet: 1104906784 Equivalent to 65 /8s, 219 /16s and 138 /24s 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, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-397212 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 190494 Total RIPE prefixes after maximum aggregation: 91847 RIPE Deaggregation factor: 2.07 Prefixes being announced from the RIPE address blocks: 186369 Unique aggregates announced from the RIPE address blocks: 111090 RIPE Region origin ASes present in the Internet Routing Table: 25164 RIPE Prefixes per ASN: 7.41 RIPE Region origin ASes announcing only one prefix: 11421 RIPE Region transit ASes present in the Internet Routing Table: 3507 Average RIPE Region AS path length visible: 4.1 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6956 Number of RIPE addresses announced to Internet: 715766144 Equivalent to 42 /8s, 169 /16s and 185 /24s 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-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-207259 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 90085 Total LACNIC prefixes after maximum aggregation: 19812 LACNIC Deaggregation factor: 4.55 Prefixes being announced from the LACNIC address blocks: 91488 Unique aggregates announced from the LACNIC address blocks: 40942 LACNIC Region origin ASes present in the Internet Routing Table: 7111 LACNIC Prefixes per ASN: 12.87 LACNIC Region origin ASes announcing only one prefix: 1966 LACNIC Region transit ASes present in the Internet Routing Table: 1306 Average LACNIC Region AS path length visible: 4.7 Max LACNIC Region AS path length visible: 25 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4651 Number of LACNIC addresses announced to Internet: 172820960 Equivalent to 10 /8s, 77 /16s and 9 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 18598 Total AfriNIC prefixes after maximum aggregation: 3969 AfriNIC Deaggregation factor: 4.69 Prefixes being announced from the AfriNIC address blocks: 21266 Unique aggregates announced from the AfriNIC address blocks: 7658 AfriNIC Region origin ASes present in the Internet Routing Table: 1142 AfriNIC Prefixes per ASN: 18.62 AfriNIC Region origin ASes announcing only one prefix: 381 AfriNIC Region transit ASes present in the Internet Routing Table: 230 Average AfriNIC Region AS path length visible: 4.4 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 417 Number of AfriNIC addresses announced to Internet: 97989120 Equivalent to 5 /8s, 215 /16s and 50 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5392 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4393 415 430 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2892 11137 791 KIXS-AS-KR Korea Telecom, KR 7552 2807 1156 71 VIETEL-AS-AP Viettel Group, VN 9829 2761 1498 543 BSNL-NIB National Internet Backbone, IN 9394 2614 4922 26 CTTNET China TieTong Telecommunications 45899 2528 1574 160 VNPT-AS-VN VNPT Corp, VN 17974 2293 928 79 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9808 2190 8699 32 CMNET-GD Guangdong Mobile Communication 4755 2100 417 206 TATACOMM-AS TATA Communications formerl Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 6327 3389 1323 84 SHAW - Shaw Communications Inc., CA 22773 3289 2968 147 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2168 405 109 MEGAPATH5-US - MegaPath Corporation, US 20115 2099 2503 455 CHARTER-NET-HKY-NC - Charter Communicat 16509 2086 4590 650 AMAZON-02 - Amazon.com, Inc., US 11492 2005 240 450 CABLEONE - CABLE ONE, INC., US 209 1969 5070 607 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 30036 1968 339 177 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 16625 1760 862 1261 AKAMAI-AS - Akamai Technologies, Inc., 7018 1704 20213 1257 ATT-INTERNET4 - AT&T Services, Inc., US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 4116 1519 499 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 20940 2662 719 1958 AKAMAI-ASN1, US 8551 2079 378 44 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2040 1876 707 ROSTELECOM-AS, RU 34984 2018 334 484 TELLCOM-AS, TR 9121 1979 1692 19 TTNET, TR 13188 1609 100 43 TRIOLAN, UA 6849 1241 355 21 UKRTELNET, UA 8402 1237 544 14 CORBINA-AS OJSC "Vimpelcom", RU Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 4445 3387 586 Uninet S.A. de C.V., MX 10620 3591 542 244 Telmex Colombia S.A., CO 11830 2647 369 78 Instituto Costarricense de Electricidad 6503 1612 437 53 Axtel, S.A.B. de C.V., MX 7303 1517 1025 193 Telecom Argentina S.A., AR 28573 1036 2251 184 CLARO S.A., BR 3816 1009 505 123 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 998 377 31 Telefonica del Peru S.A.A., PE 11172 927 126 85 Alestra, S. de R.L. de C.V., MX 18881 909 1074 29 TELEFÔNICA BRASIL S.A, BR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1185 396 45 LINKdotNET-AS, EG 37611 835 107 9 Afrihost, ZA 36903 741 372 137 MT-MPLS, MA 36992 697 1412 42 ETISALAT-MISR, EG 8452 683 1730 18 TE-AS TE-AS, EG 24835 608 850 15 RAYA-AS, EG 37492 452 376 81 ORANGE-, TN 29571 422 68 10 ORANGE-COTE-IVOIRE, CI 15399 362 35 7 WANANCHI-, KE 37342 361 32 1 MOVITEL, MZ Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5392 4192 74 ERX-CERNET-BKB China Education and Rese 8151 4445 3387 586 Uninet S.A. de C.V., MX 7545 4393 415 430 TPG-INTERNET-AP TPG Telecom Limited, AU 12479 4116 1519 499 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 10620 3591 542 244 Telmex Colombia S.A., CO 6327 3389 1323 84 SHAW - Shaw Communications Inc., CA 22773 3289 2968 147 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 4766 2892 11137 791 KIXS-AS-KR Korea Telecom, KR 7552 2807 1156 71 VIETEL-AS-AP Viettel Group, VN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 7545 4393 3963 TPG-INTERNET-AP TPG Telecom Limited, AU 8151 4445 3859 Uninet S.A. de C.V., MX 39891 3778 3758 ALJAWWALSTC-AS, SA 12479 4116 3617 UNI2-AS, ES 10620 3591 3347 Telmex Colombia S.A., CO 6327 3389 3305 SHAW - Shaw Communications Inc., CA 22773 3289 3142 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 2807 2736 VIETEL-AS-AP Viettel Group, VN 9394 2614 2588 CTTNET China TieTong Telecommunications Corpora 11830 2647 2569 Instituto Costarricense de Electricidad y Telec Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 230105 UNALLOCATED 38.110.79.0/24 23015 CMC180-TOR-AS - Cambridge Merc 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW 65537 DOCUMENT 62.162.120.0/24 6821 MT-AS-OWN bul. Orce Nikolov bb 419333 UNALLOCATED 84.17.91.0/24 41933 IPRAGAZ-AS Istanbul/ TURKEY, T 65024 PRIVATE 87.103.232.0/24 39407 CHITATELECOM-AS, RU 65024 PRIVATE 87.103.233.0/24 39407 CHITATELECOM-AS, RU 65024 PRIVATE 87.103.234.0/24 39407 CHITATELECOM-AS, RU 65024 PRIVATE 95.189.78.0/24 39407 CHITATELECOM-AS, RU 65024 PRIVATE 95.189.80.0/22 39407 CHITATELECOM-AS, RU Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 100.66.224.0/19 209 CENTURYLINK-US-LEGACY-QWEST - Qwest Communicati 100.127.16.0/23 28885 OMANTEL-NAP-AS OmanTel NAP, OM 100.127.18.0/23 28885 OMANTEL-NAP-AS OmanTel NAP, OM Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 27.100.7.0/24 56096 UNKNOWN 41.76.136.0/22 37500 -Reserved AS-, ZZ 41.76.136.0/24 37500 -Reserved AS-, ZZ 41.76.138.0/24 37500 -Reserved AS-, ZZ 41.76.139.0/24 37500 -Reserved AS-, ZZ 41.76.140.0/22 37500 -Reserved AS-, ZZ 41.76.140.0/24 37500 -Reserved AS-, ZZ 41.76.141.0/24 37500 -Reserved AS-, ZZ 41.76.142.0/24 37500 -Reserved AS-, ZZ 41.76.143.0/24 37500 -Reserved AS-, ZZ Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:14 /9:11 /10:37 /11:100 /12:288 /13:564 /14:1093 /15:1904 /16:13393 /17:7876 /18:13601 /19:25214 /20:39396 /21:45121 /22:86865 /23:70104 /24:390366 /25:848 /26:649 /27:648 /28:36 /29:20 /30:17 /31:4 /32:53 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3178 3389 SHAW - Shaw Communications Inc., CA 39891 2946 3778 ALJAWWALSTC-AS, SA 12479 2860 4116 UNI2-AS, ES 22773 2545 3289 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2061 2168 MEGAPATH5-US - MegaPath Corporation, US 11830 1994 2647 Instituto Costarricense de Electricidad y Telec 11492 1745 2005 CABLEONE - CABLE ONE, INC., US 30036 1720 1968 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1601 3591 Telmex Colombia S.A., CO 8551 1541 2079 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1581 2:840 4:19 5:2840 6:65 7:1 8:1116 12:1878 13:185 14:1750 15:28 16:3 17:203 18:68 20:49 21:7 23:2650 24:2212 25:2 27:2362 31:1973 32:87 35:27 36:505 37:2769 38:1451 39:262 40:118 41:3142 42:571 43:1944 44:112 45:4422 46:3046 47:204 49:1313 50:1056 51:307 52:1020 54:370 55:3 56:12 57:42 58:1602 59:991 60:433 61:2162 62:1828 63:1795 64:5021 65:2209 66:4666 67:2367 68:1139 69:3191 70:1150 71:563 72:2105 74:2715 75:414 76:437 77:1551 78:1705 79:1851 80:1511 81:1412 82:1077 83:777 84:1055 85:2055 86:589 87:1306 88:939 89:2325 90:206 91:6357 92:1172 93:2368 94:2382 95:2823 96:658 97:357 98:942 99:133 100:80 101:1280 102:47 103:17676 104:3623 105:231 106:659 107:1862 108:713 109:2728 110:1605 111:1773 112:1275 113:1263 114:1115 115:1632 116:1641 117:1729 118:2194 119:1661 120:987 121:1052 122:2450 123:1807 124:1430 125:1895 128:1012 129:649 130:457 131:1588 132:670 133:195 134:1017 135:224 136:469 137:494 138:1924 139:604 140:393 141:695 142:819 143:961 144:794 145:461 146:1190 147:780 148:1593 149:703 150:726 151:1058 152:768 153:312 154:1066 155:765 156:934 157:779 158:657 159:1739 160:933 161:753 162:2586 163:554 164:1049 165:1580 166:439 167:1405 168:3108 169:800 170:3699 171:433 172:1127 173:1995 174:907 175:769 176:1885 177:4053 178:2439 179:1196 180:2251 181:2217 182:2393 183:1149 184:987 185:13459 186:3625 187:2377 188:2781 189:2017 190:8101 191:1473 192:9827 193:5910 194:4767 195:3953 196:2499 197:1454 198:5541 199:5880 200:7387 201:4989 202:10349 203:10172 204:4561 205:2904 206:3104 207:3206 208:3992 209:3948 210:4037 211:2113 212:3009 213:2735 214:952 215:60 216:5924 217:2132 218:909 219:628 220:1752 221:993 222:1032 223:1249 End of report

1 0

Open Souce Network Operating Systems
by Colton Conor 04 May '18

04 May '18

If one were to deploy whitebox switches, X86 servers, low cost ARM and MIBPS CPE devices, and basically anything that can run linux today, what network operating system would you recommend? The goal would be to have a universal network operating system that runs across a variety of devices. >From low cost residential CPE's with wifi to switches to BGP speaking routers. Is there anything that can do it all today? I will use something like OpenWRT as an example. I don't consider this anywhere near carrier grade, but it runs on X86 and low cost routers. I don't think it will run on whitebox switches though. Mikrotik RouterOS would be another example as it can run on low cost Routerboards, and X86 servers. But it is not opensouce. Is there any up and coming projects to look into?

14 17

survey on BGP prefix hijacking
by Alberto Dainotti 02 May '18

02 May '18

Dear NANOG Community, BGP prefix hijacking remains a problem for Internet routing, despite the (partial) use of RPKI or detection services. We would like to hear your opinions on BGP prefix hijacking (concerns, existing defenses, needs, etc.) that would help us research new defense mechanisms both for its detection and mitigation. Please help us by answering this short (< 10min, 21 questions) and anonymous survey. Survey URL: http://tinyurl.com/hijack-survey *** The survey *** This survey is part of a joint research effort by CAIDA (www.caida.org) and the ICS-FORTH (www.ics.forth.gr) research institute, to study (a) operator awareness of BGP prefix hijacking attacks/incidents, (b) presently used defenses against BGP prefix hijacking, (c) the willingness to adopt new defense mechanisms, and (d) reasons that may hinder the deployment of BGP prefix hijacking defenses. We expect the findings of this survey to increase the understanding of existing BGP hijacking defenses and the needs of network operators, as well as help us design and implement new defense mechanisms that we will present to the operator and scientific communities. A summary of the aggregate results will be published as a part of an article/conference paper. Thank you in advance, and we look forward to your responses! Alberto (CAIDA) and Pavlos (ICS-FORTH)

1 1

Internap Contact (Market St. Philadelphia)
by Alex Lembesis 02 May '18

02 May '18

Does anyone have a contact @ Internap that could help me off list? Our peering with them is down. Any help is appreciated, thanks! This message is intended solely for the designated recipient(s). It may contain confidential or proprietary information and may be subject to attorney-client privilege or other confidentiality protections. If you are not a designated recipient you may not review, copy or distribute this message. If you receive this in error, please notify the sender by reply e-mail and delete this message. Thank you.

1 0

Re: Company threatens to cut Northern Marianas cable
by Scott Weeks 01 May '18

01 May '18

------ sean(a)donelan.com wrote: -------- From: Sean Donelan <sean(a)donelan.com> In 2015, the only submarine cable connecting the Northern Marianas Islands, a U.S. Territory, was damaged by a boulder. It cut off all telecommunications to the U.S. Territory for several weeks. To obtain a second cable for the islands, the CNMI government signed an agreement to subsidize a second fiber optic cable. <snip> -------------------------------------------------------- Note that's the second cable; for redundancy. http://www.pireport.org/articles/2016/11/03/saipans-sugar-dock-beaches-be-c… "Last year, the severance of IT&E’s fiber optic cable—the CNMI’s lone undersea cable—effectively disconnected the islands from the rest of the world as Internet and phone lines went down and put commerce at a standstill." "Docomo Pacific, owned by NTT Docomo Inc. of Japan, decided to place its own fiber optic cable along the main islands of Saipan, Rota and Tinian." “Should there be a natural phenomenon, we don’t want to have all our eggs in the same basket. Having that separation would minimize that risk. We were also looking to create as much separation to existing cables as possible,” That they didn't have much satellite backup is surprising to say the least. Especially with O3B and others soon coming up. https://en.wikipedia.org/wiki/O3b_%28satellite%29 "The O3b constellation began offering service in March 2014" scott --- sean(a)donelan.com wrote: From: Sean Donelan <sean(a)donelan.com> In 2015, the only submarine cable connecting the Northern Marianas Islands, a U.S. Territory, was damaged by a boulder. It cut off all telecommunications to the U.S. Territory for several weeks. To obtain a second cable for the islands, the CNMI government signed an agreement to subsidize a second fiber optic cable. Apparently there is now a dispute about the subsidy. https://www.radionz.co.nz/international/pacific-news/356123/company-threate… A telecommunications company in the Northern Marianas is threatening to cut the fibre optic cable that connects Tinian and Rota to Saipan if the government fails to provide $US1.3 million it promised to pay for the service. Under a memorandum of agreement signed with the CNMI government in 2016, Docomo Pacific agreed to include Tinian and Rota in connecting their fibre optic cable 'ATISA' at a fee of $US650,000 per island. Earlier this week, the House of Representative included the $US1.3 million commitment to the telco in the $US15 million appropriations bill that also gave $US7 million to the CNMI Judiciary to fix its mould and air-conditioning problems. The legislation still needs to be passed by the senate and supported by the governor.

1 0

Company threatens to cut Northern Marianas cable
by Sean Donelan 01 May '18

01 May '18

In 2015, the only submarine cable connecting the Northern Marianas Islands, a U.S. Territory, was damaged by a boulder. It cut off all telecommunications to the U.S. Territory for several weeks. To obtain a second cable for the islands, the CNMI government signed an agreement to subsidize a second fiber optic cable. Apparently there is now a dispute about the subsidy. https://www.radionz.co.nz/international/pacific-news/356123/company-threate… A telecommunications company in the Northern Marianas is threatening to cut the fibre optic cable that connects Tinian and Rota to Saipan if the government fails to provide $US1.3 million it promised to pay for the service. Under a memorandum of agreement signed with the CNMI government in 2016, Docomo Pacific agreed to include Tinian and Rota in connecting their fibre optic cable 'ATISA' at a fee of $US650,000 per island. Earlier this week, the House of Representative included the $US1.3 million commitment to the telco in the $US15 million appropriations bill that also gave $US7 million to the CNMI Judiciary to fix its mould and air-conditioning problems. The legislation still needs to be passed by the senate and supported by the governor.

1 0