- Test - lists.nanog.org

Leasing /22
by Ryan Gard 28 Jan '18

28 Jan '18

We're on the hunt yet again for an additional /22 to lease, and are wondering what the best options are out there? Our usual suspects that we've reached out to in the past seem to be plum out... Any recommendations? Thanks! -- Ryan Gard

13 20

Anyone using Cogent Ethernet
by Mike Hammett 28 Jan '18

28 Jan '18

I much prefer using WDM transport as opposed to Ethernet\VPLS transport due to it being significantly harder (I try not to say impossible) to oversubscribe. That said, it isn't always available at a decent rate at a given location. Cogent has a reputation (right or wrong) for running things a little hot. Have any of you used Cogent Ethernet\VPLS services? What are you experiences? Offlist is fine if you don't want it public. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

13 20

evil ipv6 bit?
by Baldur Norddahl 26 Jan '18

26 Jan '18

Hello After some apparently unrelated changes, one of my routers stopped routing traffic to a few IPv6 destinations. After a lot of experimentation, including rebooting (did not help), I found this: archive.ubuntu.com: 2001:67c:1360:8001::17 "ping6 vrf internet 2001:67c:1360:8001::17" from the router shell works. ping6/traceroute from a customer connection has the packet dropped by the router. Traceroute gets nothing back at all. 2001:67c:1360:7fff:: is ok. Does not reply to ping because I just made up that address. But I get a valid traceroute all the way to the destination. Anything between 2001:67c:1360:8000:: and 2001:67c:1360:ffff:ffff:ffff:ffff:ffff is dropped. My route table looks like this: albertslund-edge1#show ipv6 forwarding route vrf internet 2001:67c:1360:8001::17 IPv6 Routing Table: Headers: Dest: Destination, Gw: Gateway, Pri: Priority; Codes : K: kernel, I1: isis-l1, SFN: sf-nat64, R: ripng, AF: aftr, B: bgp, D: direct, I2: isis-l2, SLN: sl-nat64, O: ospfv3, D6: dhcp, P: ppp, S: static, N: nd, V: vrrp, A: address, M: multicast, UI: user-ipaddr, GW-FWD: PS-BUSI,GW-UE: PS-USER,LDP-A: LDP-AREA, UN: user-network, US: user-special; Dest Owner Metric Interface Pri Gw 2001:67c:1360::/48 B 0 xgei-0/0/0/6 200 ::ffff:185.24.168.254 ::/0 B 0 xgei-0/0/0/6 200 ::ffff:185.24.168.254 Notice how this is a /48 route and one bit at the /49 level changes how it is routed. That is not right. I tried adding a /128 static route but that does not do anything. The packet is still dropped. I just now discovered this: google.com: 2a00:1450:400e:807::200e That address works fine. But then I changed that one bit in the address: 2a00:1450:400e:8807::200e and voila, the router drops the packet. Now I am stumbled. What could the 49th bit in the destination IPv6 address field in a packet mean to the router, that would make it drop the packet? Some extra information about the network: We are using MPLS with l3vpn (vrf) and l2vpn (vpls). The traffic is qinq tagged before being transported in a l2vpn towards the router in question. The l2vpn does not transport the outer vlan tag. The l2vpn is then terminated on a loopback cable. On the other end of that loopback cable we receive the traffic as ordinary qinq tagged without MPLS tagging. It is on this interface the router apparently drops the packet. It might conceivably also drop the packet on the way out of the l2vpn. I have a similar setup, but instead of a loopback cable, the l2vpn is terminated on another MPLS switch, which then connects to a router of the same model. This setup does not have the problem. The change I introduced was changing from an internal interface called "bvi" to the loopback cable. The bvi interface is a simulated loopback cable construct. We are dropping the bvi interface because it is very buggy. We did not have this problem with the bvi interface however. The hardware is ZTE M6000-S V3.00.20(3.40.1). Thanks, Baldur

4 3

Weekly Routing Table Report
by cscora＠apnic.net 26 Jan '18

26 Jan '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, 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 27 Jan, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 681768 Prefixes after maximum aggregation (per Origin AS): 264615 Deaggregation factor: 2.58 Unique aggregates announced (without unneeded subnets): 329600 Total ASes present in the Internet Routing Table: 59686 Prefixes per ASN: 11.42 Origin-only ASes present in the Internet Routing Table: 51539 Origin ASes announcing only one prefix: 22682 Transit ASes present in the Internet Routing Table: 8147 Transit-only ASes present in the Internet Routing Table: 244 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 34 Max AS path prepend of ASN ( 30873) 32 Prefixes from unregistered ASNs in the Routing Table: 56 Number of instances of unregistered ASNs: 57 Number of 32-bit ASNs allocated by the RIRs: 21301 Number of 32-bit ASNs visible in the Routing Table: 17091 Prefixes from 32-bit ASNs in the Routing Table: 70682 Number of bogon 32-bit ASNs visible in the Routing Table: 12 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 382 Number of addresses announced to Internet: 2864141986 Equivalent to 170 /8s, 183 /16s and 86 /24s Percentage of available address space announced: 77.4 Percentage of allocated address space announced: 77.4 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: 225073 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 188350 Total APNIC prefixes after maximum aggregation: 53700 APNIC Deaggregation factor: 3.51 Prefixes being announced from the APNIC address blocks: 187417 Unique aggregates announced from the APNIC address blocks: 77419 APNIC Region origin ASes present in the Internet Routing Table: 8612 APNIC Prefixes per ASN: 21.76 APNIC Region origin ASes announcing only one prefix: 2445 APNIC Region transit ASes present in the Internet Routing Table: 1266 Average APNIC Region AS path length visible: 4.3 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3505 Number of APNIC addresses announced to Internet: 772118050 Equivalent to 46 /8s, 5 /16s and 150 /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: 203112 Total ARIN prefixes after maximum aggregation: 97653 ARIN Deaggregation factor: 2.08 Prefixes being announced from the ARIN address blocks: 204292 Unique aggregates announced from the ARIN address blocks: 96430 ARIN Region origin ASes present in the Internet Routing Table: 18065 ARIN Prefixes per ASN: 11.31 ARIN Region origin ASes announcing only one prefix: 6688 ARIN Region transit ASes present in the Internet Routing Table: 1793 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2297 Number of ARIN addresses announced to Internet: 1110265632 Equivalent to 66 /8s, 45 /16s and 79 /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: 184061 Total RIPE prefixes after maximum aggregation: 89767 RIPE Deaggregation factor: 2.05 Prefixes being announced from the RIPE address blocks: 180043 Unique aggregates announced from the RIPE address blocks: 108365 RIPE Region origin ASes present in the Internet Routing Table: 24847 RIPE Prefixes per ASN: 7.25 RIPE Region origin ASes announcing only one prefix: 11347 RIPE Region transit ASes present in the Internet Routing Table: 3493 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6597 Number of RIPE addresses announced to Internet: 713684608 Equivalent to 42 /8s, 137 /16s and 246 /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: 88156 Total LACNIC prefixes after maximum aggregation: 19458 LACNIC Deaggregation factor: 4.53 Prefixes being announced from the LACNIC address blocks: 89462 Unique aggregates announced from the LACNIC address blocks: 39903 LACNIC Region origin ASes present in the Internet Routing Table: 6782 LACNIC Prefixes per ASN: 13.19 LACNIC Region origin ASes announcing only one prefix: 1841 LACNIC Region transit ASes present in the Internet Routing Table: 1255 Average LACNIC Region AS path length visible: 5.1 Max LACNIC Region AS path length visible: 31 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4306 Number of LACNIC addresses announced to Internet: 172245984 Equivalent to 10 /8s, 68 /16s and 67 /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: 18031 Total AfriNIC prefixes after maximum aggregation: 3994 AfriNIC Deaggregation factor: 4.51 Prefixes being announced from the AfriNIC address blocks: 20172 Unique aggregates announced from the AfriNIC address blocks: 7212 AfriNIC Region origin ASes present in the Internet Routing Table: 1111 AfriNIC Prefixes per ASN: 18.16 AfriNIC Region origin ASes announcing only one prefix: 360 AfriNIC Region transit ASes present in the Internet Routing Table: 224 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: 386 Number of AfriNIC addresses announced to Internet: 95422720 Equivalent to 5 /8s, 176 /16s and 9 /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 5439 4195 92 ERX-CERNET-BKB China Education and Rese 7545 3802 407 412 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2881 11132 770 KIXS-AS-KR Korea Telecom, KR 9829 2770 1499 540 BSNL-NIB National Internet Backbone, IN 17974 2766 934 77 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9394 2655 4923 27 CTTNET China TieTong Telecommunications 7552 2582 1157 63 VIETEL-AS-AP Viettel Group, VN 45899 2549 1550 154 VNPT-AS-VN VNPT Corp, VN 9808 2118 8699 32 CMNET-GD Guangdong Mobile Communication 4755 2083 417 209 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 3369 1323 86 SHAW - Shaw Communications Inc., CA 22773 3264 2951 143 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2167 405 108 MEGAPATH5-US - MegaPath Corporation, US 20115 2080 2363 436 CHARTER-NET-HKY-NC - Charter Communicat 16509 2009 4163 574 AMAZON-02 - Amazon.com, Inc., US 6389 1957 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 209 1933 5059 619 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 30036 1888 333 227 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 11492 1724 230 566 CABLEONE - CABLE ONE, INC., US 7018 1677 20167 1247 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 20940 2839 833 2056 AKAMAI-ASN1, US 8551 2235 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12479 2129 1108 216 UNI2-AS, ES 12389 2114 1859 698 ROSTELECOM-AS, RU 34984 2002 332 477 TELLCOM-AS, TR 9121 1939 1691 17 TTNET, TR 13188 1605 100 46 TRIOLAN, UA 8402 1271 544 14 CORBINA-AS OJSC "Vimpelcom", RU 6849 1228 355 21 UKRTELNET, UA 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 3857 3350 577 Uninet S.A. de C.V., MX 10620 3579 540 252 Telmex Colombia S.A., CO 11830 2635 370 66 Instituto Costarricense de Electricidad 6503 1629 437 53 Axtel, S.A.B. de C.V., MX 7303 1502 1024 193 Telecom Argentina S.A., AR 6147 1075 377 27 Telefonica del Peru S.A.A., PE 3816 1014 509 114 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 28573 1014 2241 189 CLARO S.A., BR 11172 919 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 1192 398 50 LINKdotNET-AS, EG 37611 786 91 8 Afrihost, ZA 36903 714 358 186 MT-MPLS, MA 36992 667 1379 36 ETISALAT-MISR, EG 8452 531 1730 18 TE-AS TE-AS, EG 24835 478 786 17 RAYA-AS, EG 29571 458 36 13 ORANGE-COTE-IVOIRE, CI 37492 449 367 77 ORANGE-, TN 15399 352 35 7 WANANCHI-, KE 23889 313 103 14 MauritiusTelecom, MU 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 5439 4195 92 ERX-CERNET-BKB China Education and Rese 8151 3857 3350 577 Uninet S.A. de C.V., MX 7545 3802 407 412 TPG-INTERNET-AP TPG Telecom Limited, AU 10620 3579 540 252 Telmex Colombia S.A., CO 39891 3520 187 21 ALJAWWALSTC-AS, SA 6327 3369 1323 86 SHAW - Shaw Communications Inc., CA 22773 3264 2951 143 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 4766 2881 11132 770 KIXS-AS-KR Korea Telecom, KR 20940 2839 833 2056 AKAMAI-ASN1, US 9829 2770 1499 540 BSNL-NIB National Internet Backbone, IN 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 3520 3499 ALJAWWALSTC-AS, SA 7545 3802 3390 TPG-INTERNET-AP TPG Telecom Limited, AU 10620 3579 3327 Telmex Colombia S.A., CO 6327 3369 3283 SHAW - Shaw Communications Inc., CA 8151 3857 3280 Uninet S.A. de C.V., MX 22773 3264 3121 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 17974 2766 2689 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 9394 2655 2628 CTTNET China TieTong Telecommunications Corpora 11830 2635 2569 Instituto Costarricense de Electricidad y Telec 7552 2582 2519 VIETEL-AS-AP Viettel Group, 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 65249 PRIVATE 5.42.234.0/23 35753 ITC ITC AS number, SA 65249 PRIVATE 5.42.234.0/24 35753 ITC ITC AS number, SA 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 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 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 23.159.192.0/24 54726 AET - AET Hosting Solutions, Inc., US 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 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:563 /14:1092 /15:1894 /16:13432 /17:7761 /18:13621 /19:25241 /20:38818 /21:44734 /22:83691 /23:67832 /24:380401 /25:842 /26:605 /27:661 /28:36 /29:20 /30:18 /31:4 /32:60 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3161 3369 SHAW - Shaw Communications Inc., CA 39891 2946 3520 ALJAWWALSTC-AS, SA 22773 2527 3264 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2061 2167 MEGAPATH5-US - MegaPath Corporation, US 11830 1981 2635 Instituto Costarricense de Electricidad y Telec 8551 1699 2235 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 1648 1888 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1580 3579 Telmex Colombia S.A., CO 11492 1507 1724 CABLEONE - CABLE ONE, INC., US 9121 1419 1939 TTNET, TR Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1574 2:837 4:18 5:2644 6:40 8:1090 9:1 12:1853 13:194 14:1756 15:27 16:3 17:184 18:65 20:53 21:3 23:2546 24:1737 25:2 27:2372 31:1948 32:88 35:23 36:479 37:2625 38:1443 39:188 40:101 41:3057 42:539 43:1951 44:94 45:3641 46:2990 47:194 49:1387 50:1041 51:47 52:939 54:353 55:4 56:7 57:42 58:1598 59:1014 60:389 61:2087 62:1823 63:1825 64:4695 65:2229 66:4470 67:2340 68:1177 69:3175 70:1135 71:560 72:2089 74:2625 75:398 76:420 77:1556 78:1629 79:1685 80:1494 81:1405 82:1062 83:780 84:1013 85:1973 86:553 87:1228 88:912 89:2344 90:180 91:6262 92:1161 93:2358 94:2389 95:2712 96:647 97:358 98:925 99:110 100:79 101:1528 102:15 103:16945 104:3267 105:209 106:525 107:1810 108:705 109:2952 110:1593 111:1747 112:1292 113:1388 114:1110 115:1581 116:1629 117:1695 118:2209 119:1679 120:949 121:1049 122:2479 123:1762 124:1466 125:1848 128:1016 129:599 130:440 131:1650 132:603 133:196 134:1002 135:228 136:441 137:476 138:1960 139:563 140:401 141:681 142:777 143:1006 144:801 145:197 146:1150 147:754 148:1474 149:698 150:728 151:981 152:758 153:309 154:984 155:747 156:753 157:762 158:607 159:1632 160:853 161:739 162:2558 163:519 164:976 165:1502 166:398 167:1381 168:3107 169:796 170:3656 171:406 172:1031 173:1903 174:860 175:765 176:1880 177:3932 178:2433 179:1183 180:2237 181:2148 182:2437 183:1092 184:906 185:12221 186:3488 187:2327 188:2631 189:1958 190:8097 191:1353 192:9789 193:5878 194:4761 195:3996 196:2346 197:1377 198:5523 199:5911 200:7271 201:4869 202:10411 203:9969 204:4539 205:2867 206:3016 207:3119 208:4013 209:3912 210:4009 211:2150 212:2969 213:2597 214:899 215:62 216:5861 217:2121 218:900 219:625 220:1728 221:996 222:1056 223:1238 End of report

1 0

[NANOG-announce] NANOG 72 agenda update and Hackathon
by Ryan Woolley via NANOG-announce 25 Jan '18

25 Jan '18

This message has been wrapped due to the DMARC policy setting to prevent NANOG subscribers from being unsubscribed due to bounces. _______________________________________________ NANOG-announce mailing list NANOG-announce(a)nanog.org https://mailman.nanog.org/mailman/listinfo/nanog-announce

1 0

TimeWarner (Spectrum) Voice contact
by Andy Ringsmuth 25 Jan '18

25 Jan '18

Anyone have a contact at TimeWarner (aka Spectrum) Voice services that you could pass along to me? MUCH appreciated! ---- Andy Ringsmuth andy(a)newslink.com News Link – Manager Technology, Travel & Facilities 2201 Winthrop Rd., Lincoln, NE 68502-4158 (402) 475-6397 (402) 304-0083 cellular

1 0

Re: Blockchain and Networking
by John R. Levine 24 Jan '18

24 Jan '18

> How about validating whether a given AS is an acceptable origin for a set > of prefixes? Seems like a problem (route hijacking) that's still been > looking for a solution. Lots of BGP routers, RRs, prefix databases are > around, maintained and generally online. Current practices are incomplete > and for many large carriers, operate on a 24 hour cycle which might not be > acceptable if the world had a more instant option in place. It is not my impression that maintaining an updatable database of (AS, prefix) pairs is particularly difficult. What's hard is figuring out who's allowed to put what into the database, and blockchains offer no help at all there. See https://xkcd.com/927/ Regards, John Levine, johnl(a)iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly

11 16

DSL CPE
by Mike Hammett 24 Jan '18

24 Jan '18

After a few off-list responses (and a couple on) encouraging me to use NANOG, here we go... I've recently walked in to a voice\DSL CLEC that has basically been left to entropy for the last ten years. A lot of the core systems just work, but a lot of things aren't exactly managed the best. They run a Calix\Occam ADSL2+\VDSL infrastructure. For those of you doing DSL, what CPE are you using? I'm looking at one that's just a basic modem where I have a more sophisticated router (or ATA\voice gateway) behind it and then one more generic for residential settings with WiFi and all that jazz. We're kinda debating whether we go just dumb Wi-Fi or something more advanced\powerful. I've heard a lot of good about the Calix GigaFamily in that regard. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

5 6

Twitter Netops Contact
by Jared Mauch 24 Jan '18

24 Jan '18

Is there someone from twitter who can contact me about the route leak that just occurred? Thanks, - Jared

1 0

Call for presentations RIPE 76
by Benno Overeinder 23 Jan '18

23 Jan '18

Dear colleagues, Please find the CFP for RIPE 76 below or at: https://ripe76.ripe.net/submit-topic/cfp/. The deadline for submissions is *11 March 2018*. 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