December 2017 - NANOG - lists.nanog.org

mailchimp contact
by Dennis Burgess 26 Dec '17

26 Dec '17

Would a MailChimp contact pelase hit me off-list :) Dennis Burgess - Network Solution Engineer - Consultant MikroTik Certified Trainer/Consultant<http://www.linktechs.net/productcart/pc/viewcontent.asp?idpage=5> - MTCNA, MTCRE, MTCWE, MTCTCE, MTCINE For Wireless Hardware/Routers visit www.linktechs.net<http://www.linktechs.net/> Radio Frequency Coverages: www.towercoverage.com<http://www.towercoverage.com/> Office: 314-735-0270 E-Mail: dmburgess(a)linktechs.net<mailto:dmburgess@linktechs.net>

1 0

Re: AS PATH limits
by Ken Chase 23 Dec '17

23 Dec '17

If you're on cogent, since 22:30 UTC yesterday or so this has been happening (or happened). *> 186.177.184.0/23 38.*.*.* 45050 0 174 262206 262206 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 ? oddly, i see other pops with 174 sources giving a more sane route (even 6939 is giving us a route that goes thru 174 after 2 hops). 'Sup, 174? Wonder if this is just stuck in the router Im looking at and the update process is failing because the route is too long to process properly for removal or something. mmm, bugs!) /kc -- Ken Chase - math(a)sizone.org Guelph Canada

9 19

Re: AS PATH limits
by Scott Weeks 22 Dec '17

22 Dec '17

--- bill(a)herrin.us wrote: From: William Herrin <bill(a)herrin.us> Well, that's a brilliant platitude, but what do you do when it breaks over and over until the other guy upgrades? --------------------------------------------------- Filter that network out of your tables until it's fixed? :) scott

2 1

Weekly Routing Table Report
by cscora＠apnic.net 22 Dec '17

22 Dec '17

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, CaribNOG 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 23 Dec, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 676712 Prefixes after maximum aggregation (per Origin AS): 263365 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 327650 Total ASes present in the Internet Routing Table: 59421 Prefixes per ASN: 11.39 Origin-only ASes present in the Internet Routing Table: 51300 Origin ASes announcing only one prefix: 22596 Transit ASes present in the Internet Routing Table: 8121 Transit-only ASes present in the Internet Routing Table: 251 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 30 Max AS path prepend of ASN ( 29046) 25 Prefixes from unregistered ASNs in the Routing Table: 79 Number of instances of unregistered ASNs: 79 Number of 32-bit ASNs allocated by the RIRs: 20993 Number of 32-bit ASNs visible in the Routing Table: 16811 Prefixes from 32-bit ASNs in the Routing Table: 69214 Number of bogon 32-bit ASNs visible in the Routing Table: 10 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 329 Number of addresses announced to Internet: 2859271842 Equivalent to 170 /8s, 109 /16s and 6 /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.8 Total number of prefixes smaller than registry allocations: 224135 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 185943 Total APNIC prefixes after maximum aggregation: 53409 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 185047 Unique aggregates announced from the APNIC address blocks: 77442 APNIC Region origin ASes present in the Internet Routing Table: 8547 APNIC Prefixes per ASN: 21.65 APNIC Region origin ASes announcing only one prefix: 2408 APNIC Region transit ASes present in the Internet Routing Table: 1245 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 30 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3421 Number of APNIC addresses announced to Internet: 770053922 Equivalent to 45 /8s, 230 /16s and 23 /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: 202379 Total ARIN prefixes after maximum aggregation: 97452 ARIN Deaggregation factor: 2.08 Prefixes being announced from the ARIN address blocks: 203716 Unique aggregates announced from the ARIN address blocks: 95500 ARIN Region origin ASes present in the Internet Routing Table: 18029 ARIN Prefixes per ASN: 11.30 ARIN Region origin ASes announcing only one prefix: 6674 ARIN Region transit ASes present in the Internet Routing Table: 1779 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2281 Number of ARIN addresses announced to Internet: 1106986784 Equivalent to 65 /8s, 251 /16s and 71 /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: 182847 Total RIPE prefixes after maximum aggregation: 89132 RIPE Deaggregation factor: 2.05 Prefixes being announced from the RIPE address blocks: 178751 Unique aggregates announced from the RIPE address blocks: 107603 RIPE Region origin ASes present in the Internet Routing Table: 24765 RIPE Prefixes per ASN: 7.22 RIPE Region origin ASes announcing only one prefix: 11320 RIPE Region transit ASes present in the Internet Routing Table: 3518 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6513 Number of RIPE addresses announced to Internet: 713948800 Equivalent to 42 /8s, 141 /16s and 254 /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: 87520 Total LACNIC prefixes after maximum aggregation: 19386 LACNIC Deaggregation factor: 4.51 Prefixes being announced from the LACNIC address blocks: 88799 Unique aggregates announced from the LACNIC address blocks: 39619 LACNIC Region origin ASes present in the Internet Routing Table: 6686 LACNIC Prefixes per ASN: 13.28 LACNIC Region origin ASes announcing only one prefix: 1824 LACNIC Region transit ASes present in the Internet Routing Table: 1240 Average LACNIC Region AS path length visible: 5.2 Max LACNIC Region AS path length visible: 29 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4209 Number of LACNIC addresses announced to Internet: 172723424 Equivalent to 10 /8s, 75 /16s and 140 /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: 17942 Total AfriNIC prefixes after maximum aggregation: 3926 AfriNIC Deaggregation factor: 4.57 Prefixes being announced from the AfriNIC address blocks: 20070 Unique aggregates announced from the AfriNIC address blocks: 7218 AfriNIC Region origin ASes present in the Internet Routing Table: 1113 AfriNIC Prefixes per ASN: 18.03 AfriNIC Region origin ASes announcing only one prefix: 369 AfriNIC Region transit ASes present in the Internet Routing Table: 218 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 387 Number of AfriNIC addresses announced to Internet: 95150080 Equivalent to 5 /8s, 171 /16s and 224 /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 5425 4194 86 ERX-CERNET-BKB China Education and Rese 7545 3271 403 389 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2839 11130 762 KIXS-AS-KR Korea Telecom, KR 17974 2782 918 77 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9829 2765 1499 540 BSNL-NIB National Internet Backbone, IN 45899 2561 1530 154 VNPT-AS-VN VNPT Corp, VN 7552 2429 1158 56 VIETEL-AS-AP Viettel Group, VN 9394 2168 4923 26 CTTNET China TieTong Telecommunications 9808 2112 8699 32 CMNET-GD Guangdong Mobile Communication 4755 2086 417 211 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 3341 1323 86 SHAW - Shaw Communications Inc., CA 22773 3307 2951 146 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2169 405 108 MEGAPATH5-US - MegaPath Corporation, US 20115 2066 2324 465 CHARTER-NET-HKY-NC - Charter Communicat 16509 1985 4081 581 AMAZON-02 - Amazon.com, Inc., US 6389 1960 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 209 1943 5063 648 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 30036 1865 332 247 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 11492 1700 233 579 CABLEONE - CABLE ONE, INC., US 7018 1670 20197 1242 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 39891 3519 186 23 ALJAWWALSTC-AS, SA 20940 2857 848 2060 AKAMAI-ASN1, US 8551 2480 378 42 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2082 1809 683 ROSTELECOM-AS, RU 34984 2043 331 452 TELLCOM-AS, TR 12479 1975 1068 127 UNI2-AS, ES 9121 1932 1691 17 TTNET, TR 13188 1605 100 46 TRIOLAN, UA 6849 1227 355 21 UKRTELNET, UA 8402 1225 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 3651 3467 600 Uninet S.A. de C.V., MX 10620 3578 539 261 Telmex Colombia S.A., CO 11830 2630 370 66 Instituto Costarricense de Electricidad 6503 1617 437 53 Axtel, S.A.B. de C.V., MX 7303 1498 1022 194 Telecom Argentina S.A., AR 6147 1193 377 27 Telefonica del Peru S.A.A., PE 28573 1022 2259 189 CLARO S.A., BR 3816 1015 509 115 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 920 126 85 Alestra, S. de R.L. de C.V., MX 18881 904 1065 27 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 1196 398 48 LINKdotNET-AS, EG 37611 779 91 8 Afrihost, ZA 36903 737 370 135 MT-MPLS, MA 36992 678 1383 31 ETISALAT-MISR, EG 8452 526 1730 18 TE-AS TE-AS, EG 24835 515 850 15 RAYA-AS, EG 29571 444 36 13 CITelecom-AS, CI 37492 435 367 77 ORANGE-, TN 37342 356 32 1 MOVITEL, MZ 15399 349 35 7 WANANCHI-, KE 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 5425 4194 86 ERX-CERNET-BKB China Education and Rese 8151 3651 3467 600 Uninet S.A. de C.V., MX 10620 3578 539 261 Telmex Colombia S.A., CO 39891 3519 186 23 ALJAWWALSTC-AS, SA 6327 3341 1323 86 SHAW - Shaw Communications Inc., CA 22773 3307 2951 146 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 7545 3271 403 389 TPG-INTERNET-AP TPG Telecom Limited, AU 20940 2857 848 2060 AKAMAI-ASN1, US 4766 2839 11130 762 KIXS-AS-KR Korea Telecom, KR 17974 2782 918 77 TELKOMNET-AS2-AP PT Telekomunikasi Indo Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 39891 3519 3496 ALJAWWALSTC-AS, SA 10620 3578 3317 Telmex Colombia S.A., CO 6327 3341 3255 SHAW - Shaw Communications Inc., CA 22773 3307 3161 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8151 3651 3051 Uninet S.A. de C.V., MX 7545 3271 2882 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2782 2705 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 11830 2630 2564 Instituto Costarricense de Electricidad y Telec 8551 2480 2438 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 45899 2561 2407 VNPT-AS-VN VNPT Corp, VN Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 64525 PRIVATE 45.119.143.0/24 133275 GIGANTIC-AS Gigantic Infotel P 64525 PRIVATE 45.125.62.0/24 133275 GIGANTIC-AS Gigantic Infotel P 65530 PRIVATE 45.249.40.0/24 133720 SOFTCALLCOC-AS SOFT CALL CUST- 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW 419333 UNALLOCATED 84.17.91.0/24 41933 IPRAGAZ-AS Istanbul/ TURKEY, T 64609 PRIVATE 94.245.126.0/24 6584 MICROSOFT-GP-AS - Microsoft Co 65000 PRIVATE 95.179.2.0/24 65001 -Private Use AS-, ZZ 65000 PRIVATE 95.179.3.0/24 65001 -Private Use AS-, ZZ 65000 PRIVATE 95.179.69.0/24 65001 -Private Use AS-, ZZ Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 14.128.14.0/23 10247 NETLINE, ZA 14.192.50.0/23 10247 NETLINE, ZA 14.192.58.0/23 10247 NETLINE, ZA 27.100.7.0/24 56096 UNKNOWN 36.255.250.0/23 10247 NETLINE, ZA 41.78.180.0/23 37265 -Reserved AS-, ZZ 43.228.144.0/22 9829 BSNL-NIB National Internet Backbone, IN 43.251.20.0/22 9381 WTT-AS-AP WTT HK Limited, HK 43.251.84.0/22 133676 PNPL-AS Precious netcom pvt ltd, IN 43.251.84.0/23 133676 PNPL-AS Precious netcom pvt ltd, IN 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:15 /9:12 /10:37 /11:99 /12:279 /13:557 /14:1089 /15:1897 /16:13408 /17:7789 /18:13677 /19:25255 /20:38926 /21:44300 /22:82564 /23:66626 /24:377942 /25:836 /26:605 /27:661 /28:36 /29:21 /30:17 /31:4 /32:60 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3133 3341 SHAW - Shaw Communications Inc., CA 39891 2946 3519 ALJAWWALSTC-AS, SA 22773 2552 3307 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2063 2169 MEGAPATH5-US - MegaPath Corporation, US 11830 1976 2630 Instituto Costarricense de Electricidad y Telec 8551 1944 2480 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 1632 1865 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1576 3578 Telmex Colombia S.A., CO 11492 1498 1700 CABLEONE - CABLE ONE, INC., US 9121 1408 1932 TTNET, TR Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1573 2:826 4:18 5:2640 6:39 8:1094 9:1 12:1854 13:196 14:1759 15:28 16:3 17:185 18:76 20:53 21:12 23:2481 24:1922 25:2 27:2354 31:1963 32:87 35:22 36:455 37:2466 38:1465 39:171 40:101 41:3032 42:535 43:1918 44:89 45:3458 46:2911 47:191 49:1370 50:1052 51:47 52:918 54:355 55:6 56:7 57:43 58:1574 59:1005 60:380 61:1989 62:1761 63:1828 64:4640 65:2242 66:4484 67:2307 68:1192 69:3163 70:1132 71:587 72:2114 74:2695 75:392 76:423 77:1551 78:1608 79:1929 80:1464 81:1418 82:1068 83:764 84:1005 85:1980 86:492 87:1214 88:914 89:2316 90:174 91:6278 92:1032 93:2349 94:2384 95:2708 96:667 97:356 98:961 99:107 100:153 101:1532 102:10 103:16522 104:3197 105:215 106:520 107:1786 108:820 109:2898 110:1540 111:1730 112:1284 113:1389 114:1123 115:1600 116:1663 117:1637 118:2208 119:1651 120:910 121:1059 122:2414 123:1873 124:1484 125:1838 128:959 129:580 130:435 131:1636 132:593 133:193 134:987 135:221 136:449 137:458 138:1984 139:555 140:388 141:681 142:769 143:937 144:793 145:195 146:1146 147:684 148:1487 149:646 150:720 151:1002 152:754 153:306 154:973 155:745 156:744 157:741 158:597 159:1641 160:847 161:734 162:2546 163:533 164:967 165:1478 166:398 167:1349 168:3134 169:789 170:3618 171:402 172:1017 173:1917 174:842 175:771 176:1867 177:3940 178:2496 179:1142 180:2247 181:2137 182:2408 183:1034 184:894 185:11869 186:3454 187:2326 188:2646 189:1941 190:8216 191:1347 192:9720 193:5860 194:4778 195:3992 196:2319 197:1438 198:5535 199:5889 200:7252 201:4895 202:10394 203:9930 204:4560 205:2874 206:3043 207:3108 208:3998 209:3933 210:3989 211:2131 212:2918 213:2615 214:859 215:65 216:5727 217:2112 218:911 219:628 220:1734 221:980 222:743 223:1226 End of report

1 0

Small full BGP table capable router with low power consumption
by Adam Lawson 22 Dec '17

22 Dec '17

Hi, I'm looking for suggestions on 1U-2U sized router with 1G interface which can handle both IPv4 and IPv6 full BGP table and doesn't consume too much power. The router needs to be squeezed in to a rack which doesn't have a lot of space nor power. As for space, maybe I can make space for 3U or 4U but as for power, I can only do around 1.5A@100V on average. (There is room for burst power usage.) The following are the one's I can think of: - Juniper M7i with C-FEB-E (base 1.59A) - Brocade CER2024F (1.35A) - Mikrotik CCR, UBNT EdgeRouter Pro/Infinity - A server with Vyos, vMX or ASR1000v Does anyone have other recommendations? Thanks, Adam

17 27

Bandwidth distribution per ip
by Denys Fedoryshchenko 21 Dec '17

21 Dec '17

National operator here ask customers to distribute bandwidth between all ip's equally, e.g. if i have /22, and i have in it CDN from one of the big content providers, this CDN use only 3 ips for ingress bandwidth, so bandwidth distribution is not equal between ips and i am not able to use all my bandwidth. And for me, it sounds like faulty aggregation + shaping setup, for example, i heard once if i do policing on some models of Cisco switch, on an aggregated interface, if it has 4 interfaces it will install 25% policer on each interface and if hashing is done by dst ip only, i will face such issue, but that is old and cheap model, as i recall. Did anybody in the world face such requirements? Is such requirements can be considered as legit?

7 11

Re: Companies using public IP space owned by others for internal routing
by Scott Weeks 21 Dec '17

21 Dec '17

--- owen(a)delong.com wrote: From: Owen DeLong <owen(a)delong.com> > But I'd argue that if I have personal nanotech, I *really* want > to use ULA addresses. They're *my* nanotech. :) Feel free. Personally, I still see ULA as an absurdity. ------------------------------------------------------------ Why? More tools to solve more problems. scott

1 0

Re: Bandwidth distribution per ip
by Blake Hudson 20 Dec '17

20 Dec '17

Denys Fedoryshchenko wrote on 12/20/2017 11:38 AM: > On 2017-12-20 19:16, Blake Hudson wrote: >> Denys Fedoryshchenko wrote on 12/20/2017 8:55 AM: >>> National operator here ask customers to distribute bandwidth between >>> all ip's equally, e.g. if i have /22, and i have in it CDN from one >>> of the big content providers, this CDN use only 3 ips for ingress >>> bandwidth, so bandwidth distribution is not equal between ips and i >>> am not able to use all my bandwidth. >>> >>> And for me, it sounds like faulty aggregation + shaping setup, for >>> example, i heard once if i do policing on some models of Cisco >>> switch, on an aggregated interface, if it has 4 interfaces it will >>> install 25% policer on each interface and if hashing is done by dst >>> ip only, i will face such issue, but that is old and cheap model, as >>> i recall. >>> >>> Did anybody in the world face such requirements? >>> Is such requirements can be considered as legit? >> >> Not being able to use all of your bandwidth is a common issue if you >> are provided a bonded connection (aka Link Aggregation Group). For >> example, you are provided a 4Gbps service over 4x1Gbps ethernet links. >> Ethernet traffic is not typically balanced across links per frame, >> because this could lead to out of order delivery or jitter, especially >> in cases where the links have different physical characteristics. >> Instead, a hashing algorithm is typically used to distribute traffic >> based on flows. This results in each flow having consistent packet >> order and latency characteristics, but does force a flow over a single >> link, resulting in the flow being limited to the performance of that >> link. In this context, flows can be based on src/dst MAC address, IP >> address, or TCP/UDP port information, depending on the traffic type >> (some IP traffic is not TCP/UDP and won't have a port) and equipment >> type (layer 3 devices typically hash by layer 3 or 4 info). >> >> Your operator may be able to choose an alternative hashing algorithm >> that could work better for you (hashing based on layer 4 information >> instead of layer 3 or 2, for example). This is highly dependent on >> your provider's equipment and configuration - it may be a global >> option on the equipment or may not be an option at all. Bottom line, >> if you expected 4Gbps performance for each host on your network, >> you're unlikely to get it on service delivered through 4x 1Gbps links. >> 10Gbps+ links between you and your ISP's peers would better serve >> those needs (any 1Gbps bonds in the path between you and your >> provider's edge are likely to exhibit the same characteristics). >> >> --Blake > > No bonding to me, usually it is dedicated 1G/10G/etc link. > Also i simulated this bandwidth for "hashability", and any layer4 > aware hashing > on cisco/juniper provided perfectly balanced bandwidth distribution. > On my tests i can see that they have some balancing clearly by dst ip > only. > Are you claiming that your bandwidth is being equally divided 1024 ways (you mentioned a /22) or just that each host (IP) is not receiving the full bandwidth? What is the bandwidth ordered and what is the bandwidth you're seeing per host(IP)?

3 2

IPSec SPI
by Mike Hammett 20 Dec '17

20 Dec '17

Is it possible for light packet loss (0.1% - 0.3%) to cause these errors: Dec 18 00:12:07.098: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet has invalid spi for destaddr=Z.Z.Z.Z, prot=50, spi=0x9E6D41B7(2657960375), srcaddr=B.B.B.B, input interface=GigabitEthernet0/2 Dec 18 00:20:47.848: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet has invalid spi for destaddr= Z.Z.Z.Z , prot=50, spi=0x430A8C9C(1124764828), srcaddr=A.A.A.A, input interface=GigabitEthernet0/2 Dec 18 00:28:39.781: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet has invalid spi for destaddr= Z.Z.Z.Z , prot=50, spi=0x8716502A(2266386474), srcaddr=A.A.A.A, input interface=GigabitEthernet0/2 I look it up and none of the pages I find say anything about connection quality and everything about configuration and timing. My client is insisting that it can't possibly be their problem and that it's entirely because of the packet loss. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

2 2

a new source for authoritative routing data: ARIN WHOIS
by Job Snijders 20 Dec '17

20 Dec '17

Dear NANOG, I'd like to share an update on some routing security activities that ARIN, NTT Communications, YYCIX (Calgary Internet Exchange), the NLNOG Foundation, and the arouteserver project have been collaborating on. Quite some puzzles pieces were brought together! :) Traditionally, there are two commonly-used methods to signal to your peers or upstream providers what Origin ASN(s) are allowed to originate a given IP prefix. As an operator, you can either create a "route object" in the IRR, or you can compose a Letter Of Agency (LOA) and send that to your upstream providerfor manual verification. When it comes to manual verification of routing data (such a LOA), one of the big questions is "what data source is actually authoritative for the verification?". In the ARIN registry the so-called "OriginAS" attribute can be used for this purpose. The OriginAS attribute can only be set or modified by authorized accounts (such as the holder of the IP space). This makes the OriginAS attribute a very reliable source of truth! ARIN shared some notes on LOAs & OriginAS in the following article: https://teamarin.net/2016/07/07/origin-as-an-easier-way-to-validate-letters… That teamarin posting got me thinking: clearly there is a lot of valuable routing information in the ARIN WHOIS registry. What if we make the process such that you don't have to email in a LOA, and, have the recipient verify it against against the web interface output (which you updated before sending in the LOA). What if the prefix-filter generation software could just programmatically fetch all (CIDR, OriginAS) tuples from the ARIN WHOIS registry and load that into the list of prefixes a customer is allowed to announce. Just like we do with IRR objects! A few weeks ago I approached John Curran from ARIN asking whether we could work out a mechanism to somehow obtain a computer parsable rendering of the CIDR/OriginAS data in the ARIN WHOIS registry. The path forward turned out to be an agreement between the NLNOG Foundation and ARIN, which authorises NLNOG to publish a subset of the bulk whois data in the convenient format (JSON) for operational purposes. The ARIN WHOIS (CIDR, OriginAS) tuples can be downloaded in JSON format here: http://irrexplorer.nlnog.net/static/dumps/arin-whois-originas.json.bz2 Because of the JSON dump, the ARIN WHOIS data can now be easily consumed by software programs. For example, the JSON file is now loaded into IRR Explorer as can be seen here: http://irrexplorer.nlnog.net/search/AS22512 You can see the 'arin-whois' column which lists what ASN(s) are authorized to announce the blocks (this, in addition to what is signaled in IRR or RPKI). The novel thing here is that JSON file not only allows you to look up an OriginAS using the IP prefix as a lookup key, but the reverse can now also be done: lookup what IP prefixes an ASN is allowed to originate (based on ARIN WHOIS data). Deployment Experience YYCIX: At this point you may be wondering - what does any of the above have to do with an Internet Exchange in Alberta, Canada (https://www.yycix.ca/) or a python-based IXP Route Server management software from Italian origins (http://arouteserver.readthedocs.io/en/latest/) ? :-) As an experiment to explore real world use of the ARIN WHOIS data and prove its value, I worked with Pier Carlo Chiodi (arouteserver) and Theo de Raadt (YYCIX) to consume the ARIN WHOIS data as an additional source in the prefix filter generation process governing the YYCIX route servers. The YYCIX route servers see roughly 80,000 prefixes. The results are fantastic: ~ 1,700 IPv4 prefixes that were previously rejected by the YYCIX route servers (because no IRR route object exists), are now accepted because those announcements can be verified against data from ARIN's WHOIS registry. This resolved roughly 23% of invalid path announcements sent to the YYCIX route servers. Deployment Experience NTT: Based on the above positive results, starting today, NTT is also accepting ARIN WHOIS OriginAS information in conjunction with IRR route objects. Our implementation fetches the ARIN WHOIS data, transforms it into RPSL format, and imports it into our IRRd instance at rr.ntt.net as IRR objects. This way we don't need to update our toolchain to make use of this new data source. An example is here: job@vurt:~$ whois -h rr.ntt.net -- "-sARIN-WHOIS 204.209.252.0/23" route: 204.209.252.0/23 descr: NET-204-209-252-0-1 origin: AS22512 remarks: This route object represents authoritative data retrieved from ARIN's WHOIS service. remarks: The original data can be found here: https://whois.arin.net/rest/net/NET-204-209-252-0-1 remarks: This route object is the result of an automated WHOIS-to-IRR conversion process. mnt-by: MAINT-JOB changed: job(a)ntt.net 20090220 source: ARIN-WHOIS NTT also observed a substantial number (similar to YYCIX) of BGP announcements from its customers that were previously rejected because of the lack of an IRR object, but now are validated via ARIN WHOIS. Conclusion: It is great to be able to offer network operators a choice: either register your BGP announcements as route objects in RPSL format in IRR, or use the ARIN WHOIS web interface, (or both) - either way, as IP transit carrier, we can now pick up your attestations in an automated fashion. This which improves accuracy and reduces red tape! :) Hopefully more carriers and IXPs will embrace the ARIN WHOIS data source in their automation toolchain. The code & procedures to make use of this source are open. I'm happy to help you both on-list and off-list. Kind regards, Job

3 2