March 2018 - Test - lists.nanog.org

MANRS IXP Webinar: Tuesday, 13 March
by Chris Grundemann 09 Mar '18

09 Mar '18

Hail NANOGers! If you operate an IX in North America, this message is for you. (I'm passing it along on behalf of my former colleagues at the Internet Society.) Hope to "see" you on the webinar this Tuesday! ——— Hi, The MANRS IXP Partnership program is designed to invite and encourage participation of IXPs in MANRS (Mutually Agreed Norms for Routing Security). In accordance with the principles of the initiative, the membership depends on the visible commitment to improve the routing security of the peering fabric and Internet infrastructure in general and demonstrated by the implementation of defined Actions. The Internet Society is looking for leading IXPs around the world that have a track record in contributing to routing security, already implement the majority of Actions and are willing to participate in the launch of this program, planned in early 2018. The set of Actions was developed by the development team consisting of IXP representatives around the world. It has been reviewed in by various IXP communities, such as EURO-IX, LAC-IX, Af-IX. I’d like to invite you to participate in a webinar on March 13 at 14:00 EDT (18:00 UTC) where we present the IXP Partnership Program and the Actions to the North-American IXP community and invite your feedback. Call details are below. We would also ask you to disseminate the information about the webinar to the NA IX community. MANRS (https://www.manrs.org) is a collaborative initiative, coordinated by the Internet Society. It was launched in November 2014 and has received much encouragement from all sections of the Internet industry. The key objective of MANRS is to gain industry-wide agreement on a minimum set of practices for secure routing across the Internet, through coordinated action by many parties. MANRS was designed for network operators, but other parties can play an important role in facilitating improvements in routing security such as Internet Exchange Points (IXPs). Many of them represent active communities with common operational objectives and already contribute to a more resilient and secure Internet infrastructure. Thanks! Mark Buell Regional Bureau Director, North America Internet Society Details: Topic: MANRS and IXPs Time: Mar 13, 2018 7:00 PM Amsterdam, Berlin, Rome, Stockholm, Vienna Join from PC, Mac, Linux, iOS or Android: https://isoc.zoom.us/j/288357813 Or iPhone one-tap : US: +16699006833,,288357813# or +16465588656,,288357813# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 558 8656 Meeting ID: 288 357 813 International numbers available: https://isoc.zoom. us/zoomconference?m=WXysPTqEpKm5ELZq6evhxxHUX43prdSf -- @ChrisGrundemann http://chrisgrundemann.com

1 0

Zayo zColo Xcon Pricing
by James Laszko 09 Mar '18

09 Mar '18

One of our colo’s in San Diego was purchased by Zayo recently and I requested a new copper Ethernet xcon to be placed. After a few days I received a quote from my new rep quoting a MRC 3x what I’m currently paying for existing xcon’s as well as a hefty NRC as well. Anyone have any experience with this kind of thing? Anyone care to share what an average copper xcon, single floor, meet-me-room to cage, Ethernet from carrier circuit costs? (This xcon is approx 30 feet..) Thanks! James Sent from my iPad

15 21

Weekly Routing Table Report
by cscora＠apnic.net 09 Mar '18

09 Mar '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 10 Mar, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 689505 Prefixes after maximum aggregation (per Origin AS): 267381 Deaggregation factor: 2.58 Unique aggregates announced (without unneeded subnets): 332013 Total ASes present in the Internet Routing Table: 60061 Prefixes per ASN: 11.48 Origin-only ASes present in the Internet Routing Table: 51878 Origin ASes announcing only one prefix: 22755 Transit ASes present in the Internet Routing Table: 8183 Transit-only ASes present in the Internet Routing Table: 255 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 37 Max AS path prepend of ASN (262865) 25 Prefixes from unregistered ASNs in the Routing Table: 61 Number of instances of unregistered ASNs: 61 Number of 32-bit ASNs allocated by the RIRs: 21745 Number of 32-bit ASNs visible in the Routing Table: 17492 Prefixes from 32-bit ASNs in the Routing Table: 72632 Number of bogon 32-bit ASNs visible in the Routing Table: 12 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 329 Number of addresses announced to Internet: 2855882594 Equivalent to 170 /8s, 57 /16s and 79 /24s Percentage of available address space announced: 77.1 Percentage of allocated address space announced: 77.1 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: 229062 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 189556 Total APNIC prefixes after maximum aggregation: 54236 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 188509 Unique aggregates announced from the APNIC address blocks: 77335 APNIC Region origin ASes present in the Internet Routing Table: 8697 APNIC Prefixes per ASN: 21.68 APNIC Region origin ASes announcing only one prefix: 2465 APNIC Region transit ASes present in the Internet Routing Table: 1285 Average APNIC Region AS path length visible: 4.3 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3609 Number of APNIC addresses announced to Internet: 767978658 Equivalent to 45 /8s, 198 /16s and 108 /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: 205495 Total ARIN prefixes after maximum aggregation: 98454 ARIN Deaggregation factor: 2.09 Prefixes being announced from the ARIN address blocks: 206400 Unique aggregates announced from the ARIN address blocks: 97400 ARIN Region origin ASes present in the Internet Routing Table: 18111 ARIN Prefixes per ASN: 11.40 ARIN Region origin ASes announcing only one prefix: 6713 ARIN Region transit ASes present in the Internet Routing Table: 1803 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: 2316 Number of ARIN addresses announced to Internet: 1104738912 Equivalent to 65 /8s, 216 /16s and 250 /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: 187081 Total RIPE prefixes after maximum aggregation: 91044 RIPE Deaggregation factor: 2.05 Prefixes being announced from the RIPE address blocks: 183286 Unique aggregates announced from the RIPE address blocks: 109499 RIPE Region origin ASes present in the Internet Routing Table: 24958 RIPE Prefixes per ASN: 7.34 RIPE Region origin ASes announcing only one prefix: 11332 RIPE Region transit ASes present in the Internet Routing Table: 3497 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 28 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6747 Number of RIPE addresses announced to Internet: 714623104 Equivalent to 42 /8s, 152 /16s and 72 /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: 88834 Total LACNIC prefixes after maximum aggregation: 19593 LACNIC Deaggregation factor: 4.53 Prefixes being announced from the LACNIC address blocks: 90204 Unique aggregates announced from the LACNIC address blocks: 40049 LACNIC Region origin ASes present in the Internet Routing Table: 6889 LACNIC Prefixes per ASN: 13.09 LACNIC Region origin ASes announcing only one prefix: 1879 LACNIC Region transit ASes present in the Internet Routing Table: 1267 Average LACNIC Region AS path length visible: 5.1 Max LACNIC Region AS path length visible: 37 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4422 Number of LACNIC addresses announced to Internet: 172158944 Equivalent to 10 /8s, 66 /16s and 239 /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: 18476 Total AfriNIC prefixes after maximum aggregation: 4005 AfriNIC Deaggregation factor: 4.61 Prefixes being announced from the AfriNIC address blocks: 20777 Unique aggregates announced from the AfriNIC address blocks: 7466 AfriNIC Region origin ASes present in the Internet Routing Table: 1123 AfriNIC Prefixes per ASN: 18.50 AfriNIC Region origin ASes announcing only one prefix: 365 AfriNIC Region transit ASes present in the Internet Routing Table: 227 Average AfriNIC Region AS path length visible: 4.6 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 398 Number of AfriNIC addresses announced to Internet: 95974144 Equivalent to 5 /8s, 184 /16s and 115 /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 5420 4192 74 ERX-CERNET-BKB China Education and Rese 7545 3962 405 400 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2858 11132 776 KIXS-AS-KR Korea Telecom, KR 9829 2802 1499 540 BSNL-NIB National Internet Backbone, IN 7552 2667 1161 59 VIETEL-AS-AP Viettel Group, VN 9394 2630 4923 29 CTTNET China TieTong Telecommunications 45899 2530 1561 159 VNPT-AS-VN VNPT Corp, VN 17974 2331 930 80 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9808 2179 8699 32 CMNET-GD Guangdong Mobile Communication 4755 2086 417 215 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 3364 1323 86 SHAW - Shaw Communications Inc., CA 22773 3278 2988 148 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2167 405 108 MEGAPATH5-US - MegaPath Corporation, US 20115 2094 2483 435 CHARTER-NET-HKY-NC - Charter Communicat 16509 2037 4372 605 AMAZON-02 - Amazon.com, Inc., US 30036 1932 338 189 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 1929 5055 618 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 6389 1776 3671 36 BELLSOUTH-NET-BLK - BellSouth.net Inc., 11492 1750 228 577 CABLEONE - CABLE ONE, INC., US 7018 1682 20187 1248 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 3520 187 21 ALJAWWALSTC-AS, SA 12479 3447 1397 785 UNI2-AS, ES 20940 2821 820 2054 AKAMAI-ASN1, US 8551 2101 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2036 1864 704 ROSTELECOM-AS, RU 34984 1997 332 479 TELLCOM-AS, TR 9121 1926 1692 19 TTNET, TR 13188 1606 100 46 TRIOLAN, UA 6849 1241 355 21 UKRTELNET, UA 8402 1210 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 4313 3386 588 Uninet S.A. de C.V., MX 10620 3599 541 252 Telmex Colombia S.A., CO 11830 2642 370 66 Instituto Costarricense de Electricidad 6503 1631 437 53 Axtel, S.A.B. de C.V., MX 7303 1505 1025 198 Telecom Argentina S.A., AR 28573 1022 2246 194 CLARO S.A., BR 6147 1017 377 27 Telefonica del Peru S.A.A., PE 3816 1006 506 120 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 925 126 85 Alestra, S. de R.L. de C.V., MX 18881 907 1072 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 1168 398 50 LINKdotNET-AS, EG 37611 813 91 8 Afrihost, ZA 36903 737 370 139 MT-MPLS, MA 36992 683 1380 38 ETISALAT-MISR, EG 8452 615 1730 18 TE-AS TE-AS, EG 24835 602 850 15 RAYA-AS, EG 29571 466 68 12 ORANGE-COTE-IVOIRE, CI 37492 444 376 80 ORANGE-, TN 15399 361 35 7 WANANCHI-, KE 37342 360 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 5420 4192 74 ERX-CERNET-BKB China Education and Rese 8151 4313 3386 588 Uninet S.A. de C.V., MX 7545 3962 405 400 TPG-INTERNET-AP TPG Telecom Limited, AU 10620 3599 541 252 Telmex Colombia S.A., CO 39891 3520 187 21 ALJAWWALSTC-AS, SA 12479 3447 1397 785 UNI2-AS, ES 6327 3364 1323 86 SHAW - Shaw Communications Inc., CA 22773 3278 2988 148 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 4766 2858 11132 776 KIXS-AS-KR Korea Telecom, KR 20940 2821 820 2054 AKAMAI-ASN1, US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 8151 4313 3725 Uninet S.A. de C.V., MX 7545 3962 3562 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3520 3499 ALJAWWALSTC-AS, SA 10620 3599 3347 Telmex Colombia S.A., CO 6327 3364 3278 SHAW - Shaw Communications Inc., CA 22773 3278 3130 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 12479 3447 2662 UNI2-AS, ES 7552 2667 2608 VIETEL-AS-AP Viettel Group, VN 9394 2630 2601 CTTNET China TieTong Telecommunications Corpora 11830 2642 2576 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 65456 PRIVATE 31.171.126.0/23 199311 AZRT-LX Local Internet Exchang 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 65024 PRIVATE 87.103.234.0/24 39407 CHITATELECOM-AS, RU 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 65000 PRIVATE 95.179.70.0/24 65001 -Private Use AS-, ZZ 65000 PRIVATE 95.179.92.0/24 65001 -Private Use AS-, ZZ 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 Complete listing at http://thyme.rand.apnic.net/current/data-dsua 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 37.44.224.0/20 48666 AS-MAROSNET Moscow, Russia, RU 41.76.136.0/22 37500 -Reserved AS-, ZZ 41.76.140.0/22 37500 -Reserved AS-, ZZ 41.78.92.0/22 14988 BTC-GATE1, BW 41.78.180.0/23 37265 -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:289 /13:563 /14:1094 /15:1898 /16:13320 /17:7834 /18:13573 /19:25192 /20:39115 /21:45117 /22:85179 /23:69049 /24:384896 /25:837 /26:599 /27:654 /28:36 /29:20 /30:17 /31:4 /32:57 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3155 3364 SHAW - Shaw Communications Inc., CA 39891 2946 3520 ALJAWWALSTC-AS, SA 22773 2534 3278 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 12479 2246 3447 UNI2-AS, ES 18566 2061 2167 MEGAPATH5-US - MegaPath Corporation, US 11830 1989 2642 Instituto Costarricense de Electricidad y Telec 30036 1687 1932 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1599 3599 Telmex Colombia S.A., CO 8551 1564 2101 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11492 1531 1750 CABLEONE - CABLE ONE, INC., US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1567 2:829 4:19 5:2801 6:59 7:1 8:1104 9:1 12:1883 13:207 14:1752 15:26 16:3 17:188 18:68 20:48 21:2 23:2558 24:2176 25:2 27:2304 31:1940 32:89 35:25 36:502 37:2700 38:1458 39:247 40:103 41:3044 42:548 43:1946 44:98 45:3853 46:3046 47:199 49:1354 50:1045 51:48 52:982 54:356 55:5 56:10 57:41 58:1576 59:1019 60:428 61:2142 62:1803 63:1803 64:4708 65:2223 66:4572 67:2358 68:1172 69:3199 70:1183 71:556 72:2101 74:2674 75:410 76:426 77:1541 78:1668 79:1856 80:1488 81:1442 82:1076 83:775 84:1020 85:2038 86:575 87:1267 88:915 89:2315 90:194 91:6284 92:1195 93:2370 94:2386 95:2742 96:656 97:356 98:927 99:124 100:79 101:1426 102:28 103:17255 104:3286 105:221 106:588 107:1799 108:706 109:2702 110:1579 111:1777 112:1329 113:1377 114:1113 115:1649 116:1648 117:1721 118:2173 119:1674 120:967 121:1070 122:2464 123:1820 124:1458 125:1876 128:975 129:618 130:443 131:1586 132:653 133:194 134:996 135:225 136:440 137:495 138:1941 139:572 140:418 141:686 142:787 143:964 144:798 145:453 146:1161 147:740 148:1546 149:700 150:740 151:1045 152:755 153:308 154:1038 155:760 156:850 157:777 158:624 159:1632 160:884 161:745 162:2572 163:527 164:1258 165:1396 166:398 167:1412 168:3045 169:808 170:3707 171:418 172:1058 173:1927 174:879 175:747 176:1866 177:3975 178:2419 179:1185 180:2243 181:2171 182:2462 183:1132 184:907 185:12812 186:3481 187:2299 188:2709 189:1976 190:8114 191:1415 192:9777 193:5879 194:4778 195:3974 196:2450 197:1444 198:5521 199:5880 200:7383 201:5006 202:10378 203:10110 204:4540 205:2846 206:3070 207:3177 208:3993 209:3933 210:4032 211:2118 212:3008 213:2687 214:907 215:61 216:5837 217:2126 218:899 219:621 220:1733 221:996 222:1045 223:1235 End of report

1 0

Playstation Vue over IPv6 from Frontier Tampa Bay, FL
by Clay Curtis 09 Mar '18

09 Mar '18

Playstation Vue is basically unusable when viewing over IPv6 from Tampa Bay Frontier network. A little background first... Almost all traffic from my metro area (Tampa Bay, FL) routes to Miami first, and then continues on to the IPv4 Internet. Frontier does not have residential IPv6 yet, so I am tunneling to the Hurricane Electric Miami POP to get IPv6 connectivity. Point being, the tunneling does not really have an adverse affect on latency. That said, IPv4 streaming is great because I head down to Miami and jump right over to Akamai for the content. 1 4 ms 5 ms 5 ms 192.168.4.1 2 * 18 ms 6 ms 192.168.100.1 3 8 ms 6 ms 6 ms 47.199.160.1 4 8 ms 9 ms 7 ms 172.99.45.80 5 12 ms 13 ms 13 ms ae8---0.scr02.mias.fl.frontiernet.net [74.40.3.73] 6 13 ms 13 ms 13 ms ae1---0.cbr01.mias.fl.frontiernet.net [74.40.1.126] 7 12 ms 12 ms 12 ms lag-101.ear3.Miami2.Level3.net [4.15.156.29] 8 13 ms 13 ms 13 ms NTT-level3-80G.Miami.Level3.net [4.68.127.54] 9 14 ms 13 ms 13 ms ae-4.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.40] 10 14 ms 14 ms 14 ms a204-2-178-194.deploy.akamaitechnologies.com [204.2.178.194] IPv6 on the other hand, goes down to Miami, up to Ashburn, and back to Miami. 1 clay584-1.tunnel.tserv12.mia1.ipv6.he.net (2001:470:4:4e5::1) 17.460 ms 17.231 ms 16.867 ms 2 10ge13-20.core1.mia1.he.net (2001:470:0:8c::1) 13.187 ms 13.446 ms 13.143 ms 3 100ge11-1.core1.atl1.he.net (2001:470:0:18d::1) 27.223 ms 31.532 ms 27.294 ms 4 100ge8-1.core1.ash1.he.net (2001:470:0:114::2) 45.364 ms 39.037 ms 38.893 ms 5 xe-0.equinix.asbnva01.us.bb.gin.ntt.net (2001:504:0:2::2914:1) 39.565 ms 39.485 ms 39.870 ms 6 ae-2.r23.asbnva02.us.bb.gin.ntt.net (2001:418:0:2000::115) 39.356 ms 39.249 ms 42.904 ms 7 ae-1.r20.miamfl02.us.bb.gin.ntt.net (2001:418:0:2000::f2) 64.380 ms 65.897 ms 64.124 ms 8 ae-1.r05.miamfl02.us.bb.gin.ntt.net (2001:418:0:2000::26a) 65.341 ms 65.324 ms 65.114 ms 9 ae-8.a00.miamfl02.us.bb.gin.ntt.net (2001:418:0:2000::166) 68.843 ms 68.839 ms 69.295 ms 10 2001:418:0:5000::929 (2001:418:0:5000::929) 135.368 ms 84.350 ms 219.402 ms 11 g2600-1403-0015-0000-0000-0000-48f7-f02b.deploy.static.akamaitechnologies.c… (2600:1403:15::48f7:f02b) 68.629 ms 65.356 ms 65.352 ms >From what I can see it looks that Hurricane Electric only sees this prefix from Equinix and thus routes it up to Ashburn and back. I suppose there could be utilization issues along the path, but the path itself seems like it could be better and may improve streaming with PS Vue. Going halfway up the east coast just to come back to the same city (possibly the same facility) is not ideal. Is there anyone on list that can see if this can be improved? Thanks in advance, Clay

1 0

2nd call for presentations RIPE 76
by Benno Overeinder 08 Mar '18

08 Mar '18

Dear colleagues, Please note the approaching deadline of *11 March 2018* for RIPE 76 plenary programme submissions. You can find the CFP for RIPE 76 below or at https://ripe76.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings, see the "Speakers" paragraph in CFP for more information. Kind regards, Benno Overeinder RIPE PC Chair https://ripe76.ripe.net/ripe-pc/ -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 76 will take place from 14-18 May in Marseille, France. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 76. See the full descriptions of the different presentation formats, https://ripe76.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *11 March 2018*. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) Speakers Presenters, RIPE Working Group Chairs and the RIPE Programme Committee are required to cover their own costs to attend a RIPE Meeting (meeting ticket, travel and accommodation). We have various ticket options available depending on your needs. In extraordinary circumstances, the RIPE Chair can waive the meeting fee for presenters. These requests are dealt with on a case-by-case basis via pc(a)ripe.net. Also note that, on an individual basis, participants can apply for a RIPE Fellowship to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship Submissions Presenters should be clear on whether they wish to submit a presentation for a plenary or working group (WG) session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe76.ripe.net/plenary-or-wg/ RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour (during evening sessions) - Lightning talks: 10 minutes total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe76.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe76.ripe.net/submit-topic/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. If you have any questions or requests concerning content submissions, please email pc(a)ripe.net. -- Benno J. Overeinder NLnet Labs https://www.nlnetlabs.nl/

1 0

Looking for a network abuse contact at CenturyLink
by Bill Weiss 08 Mar '18

08 Mar '18

I know, it's a big place. I'd like to talk about something I'm seeing from your networks and see if you agree on what it could be. This includes legacy Qwest, CenturyTel, etc. I could list ASNs but it's kind of a long list, as you'd expect :) Thank you, and sorry for the noise. -- Bill Weiss

1 0

Google
by Daniel Temple 07 Mar '18

07 Mar '18

I'm having a problem with some Google services that seems to be related to our public IP block. Anyone have a contact there that could check the IP block against any sort of google black list? Thanks Daniel Temple WISP Administrator CMB Systems, Inc 92-1 Hwy 64 West Cashiers, NC 28717 Direct: 828-743-2470 ext.209 FAX: 828-743-3155 daniel(a)pyranah.com <mailto:daniel@pyranah.com> Confidentiality Notice This message is being sent by or on behalf of CMB Systems, Inc. It is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message.

1 0

Someone from T-Mobile who can shake a ticket loose?
by Chris Boyd 06 Mar '18

06 Mar '18

Sorry for using the white paging phone, but I have an IPv4 reachability ticket that I opened back in January that’s stuck in limbo. Ticket number is either 26088938 or 18444951. Users on T-Mobile data can’t reach services in 208.89.64.0/21, specifically 208.89.64.154. —Chris

2 1

Nominum NS2 Reach
by Rubens Kuhl 06 Mar '18

06 Mar '18

Hi there. I found the available product information on NS2 Reach (Nominum) to not dive into real product behavior like if it requires every HTTP traffic to be PBR to the box, or possible deployment scenarios without intercepting all HTTP traffic. Anyone can shed a light on its workings, or point to a NetEng description of it ? Tks, Rubens

2 2

NYC to Albany - Wavelength service
by Robert Blayzor 06 Mar '18

06 Mar '18

Anyone know of any carriers offering DWDM wavelength paths between NYC and Albany, NY? (Not OTU2 or OTU4). Looking for carrier to carry color (alien wave). Please contact me off list. Thanks -- inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP: https://inoc.net/~rblayzor/

1 0