- NANOG - lists.nanog.org

SLAAC in renumbering events
by Fernando Gont 10 Mar '19

10 Mar '19

Folks, If you follow the 6man working group of the IETF you may have seen a bunch of emails on this topic, on a thread resulting from an IETF Internet-Draft we published with Jan Žorž about "Reaction of Stateless Address Autoconfiguration (SLAAC) to Renumbering Events" (Available at: https://github.com/fgont/draft-slaac-renum/raw/master/draft-gont-6man-slaac… ) Short version of story: There are a number of scenarios where SLAAC hosts may end up using stale configuration information. For example, a typical IPv6 deployment scenario is that in which a CPE router requests an IPv6 prefix to an ISP via DHCPv6-PD, and advertises a sub-prefix of of the leased prefix on the LAN-side, via SLAAC. In such scenarios, if the CPE router crashes and reboots, it may loose all information about the previously-leased prefix. Upon reboot, the CPE router may be leased a new prefix that will result in a new sub-prefix being advertised on the LAN-side of the CPE router. As a result, hosts will normally configure addresses for the newly-advertised prefix, but will normally also keep (and use) the previously-configured (and now stale!) IPv6 addresses, leading to interoperability problems. The RIPE-690 BCOP document had originally tried to address this problem by recommending operators to lease stable IPv6 prefixes to CPE routers. However, for a variety of reasons ISP may not be able (or may not want) to lease stable prefixes, and may instead lease dynamic prefixes. Most of the voices on the 6man wg mailing-list fell into one of the following camps: * "ISPs should be leasing stable prefixes -- if they don't, they are asking for trouble!" * "CPE routers should record leased prefixes on stable storage, such that they can 'deprecate' such prefixes upon restart -- if they don't, they are asking for trouble!" * "No matter whose fault is this (if there is any single party to blame in the first place), we should improve the robustness of IPv6 deployments" Our Internet-Draft tries to improve the current state of affairs via the following improvements: * Allow hosts to gracefully recover from stale network configuration information -- i.e., detect and discard stale network configuration information * Have SLAAC routers employ more appropriate timers, such that information is phased-out in a timelier manner -- unless it is actively refreshed by Router Advertisement messages * Specify the interaction between DHCPv6-PD and SLAAC -- which was rather under-specified * Require CPE routers to store leased prefixes on stable storage, and deprecate stale prefixes (if necessary) upon restart We are looking forward to more input on the document (or any comments on the issue being discussed), particularly from operators. So feel free to send your comments on/off list as you prefer Thanks! Cheers, -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

4 4

Technical bandwidth requirements for Emergency Alerts
by Sean Donelan 09 Mar '19

09 Mar '19

Some background information for network engineers unfamilar with emergency alerts. In the United States, there are approximately 500,000 emergency alerts nationwide a year, not counting another million or so test alerts. Only about 7,500 emergency alerts are severe enough to activate public warning systems. Most emergency alerts are intended for other emergency management agencies and officials. The rest are advisories, watches, updates and cancels. The peak emergency alert busy day is 4 alerts per minute nationwide. Although stress testing indicates most emergency alert systems should be able to handle more. Emergency alerts are not evenly distributed across the country. Some geographic areas have nearly none. Other geographic areas have many, e.g. tornado alley and atlantic coastlines. Since the 1950s, there has never been an actual nationwide emergency alert, i.e. presidential alert message. Emergency alerts are almost all state, local and weather alerts. Test alerts are the most common alert type. The IPAWS system supports very geo-targetted alerts, and supports opting in or opting out of specific types of alerts. When government officials use those options, and alert distributions implement those options. When the IPAWS emergency alert standards were being written, 1.5 Mbps DSL lines and even 128Kbps ISDN lines were still common, so the IPAWS emergency alert message sizes were made relatively small. But it was still an huge improvement over the previous EAS radio and TV broadcast modem data bursts from the 1980s/1990s, which were limited to 256 characters. The average IPAWS emergency alert is 5KB to 15KB in size. Including audio and image files, the entire emergency alert can be about 5MB in size. In the U.S., audio and image files are transmitted separately because rural Internet connections were too slow at the time. Canada's AlertReady system is more recent, and can handle larger alert messages. In Canada, audio and image files are transmitted as part of the satellite IP multicast emergency alert message. The small 90-character cellular phone message was also due to the limited bandwidth available in cellular networks at the time. Newer cell broadcast networks can handle nearly 1,000 character messages. Starting in May 2019, the U.S. WEA mobile alerts will increase to 360 characters. Changes are slow. It takes less than 10 seconds to transmit an IPAWS emergency alert nationwide. Although radio and TV may delay transmitting an emergency alert up to 15 minutes, i.e. during commercial breaks. The goal for earthquake alert messages is less than 3 seconds, which is not currently achievable. All 500,000 emergency alerts do not need to be transmitted nationwide. An alert distributor can selectively transmits only relevant alerts to different geographic areas, and choose not to include less severe advisories or many tests. Training for state and local government officials issuing alerts is very underfunded, and they make mistakes. The public hates emergency alert systems, until a tornado destroys their home in the middle of the night, and then they complain they didn't get an emergency alert.

1 0

Arista Layer3
by Romeo Czumbil 09 Mar '19

09 Mar '19

So I've been using Arista as layer2 for quite some time, and I'm pretty happy with them. Kicking the idea around to turn on some Layer3 features but I've been hearing some negative feedback. The people that I did hear negative feedback don't use Arista themselves. (they just heard....) So do we have any Arista L3 people out here that can share some negatives or positives? Use case: Just some MPLS IPv4/IPv6 routing, l2vpn OSPF/BGP Maybe 20k routes (no full internet routes) 7050 Series 7280 Series -Romeo

20 33

GPS week number rollover event on April 6th
by Gerry Boudreaux 09 Mar '19

09 Mar '19

For those who have GPS based NTP servers. https://ics-cert.us-cert.gov/sites/default/files/documents/Memorandum_on_GP… G

3 2

Assistance needed from Global Net Access / Zayo
by Christopher Smalling 08 Mar '19

08 Mar '19

Been having an issue with our public peering at an IX and have been getting the runaround from the NCC. AS 3595 (Global Net Access) has Zayo (AS 19092) as the contact. If anyone on here can assist, can you contact me off-list, please? -- [image: photo] Christopher Smalling NOC Support Technician at NeoNova O: 256-428-8788 • christopher.smalling(a)neonova.net www.neonova.net <https://neonova.net> <https://www.facebook.com/NeoNovaNNS/> <https://twitter.com/NeoNova_NNS> <http://www.linkedin.com/company/neonova-network-services>

2 1

Weekly Routing Table Report
by cscora＠apnic.net 08 Mar '19

08 Mar '19

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 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 09 Mar, 2019 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 740306 Prefixes after maximum aggregation (per Origin AS): 285904 Deaggregation factor: 2.59 Unique aggregates announced (without unneeded subnets): 356243 Total ASes present in the Internet Routing Table: 63449 Prefixes per ASN: 11.67 Origin-only ASes present in the Internet Routing Table: 54648 Origin ASes announcing only one prefix: 23590 Transit ASes present in the Internet Routing Table: 8801 Transit-only ASes present in the Internet Routing Table: 271 Average AS path length visible in the Internet Routing Table: 4.2 Max AS path length visible: 30 Max AS path prepend of ASN ( 16327) 25 Prefixes from unregistered ASNs in the Routing Table: 28 Number of instances of unregistered ASNs: 31 Number of 32-bit ASNs allocated by the RIRs: 26062 Number of 32-bit ASNs visible in the Routing Table: 21215 Prefixes from 32-bit ASNs in the Routing Table: 92922 Number of bogon 32-bit ASNs visible in the Routing Table: 26 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 255 Number of addresses announced to Internet: 2842211683 Equivalent to 169 /8s, 104 /16s and 181 /24s Percentage of available address space announced: 76.8 Percentage of allocated address space announced: 76.8 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.2 Total number of prefixes smaller than registry allocations: 248230 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 201454 Total APNIC prefixes after maximum aggregation: 57939 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 198125 Unique aggregates announced from the APNIC address blocks: 81878 APNIC Region origin ASes present in the Internet Routing Table: 9526 APNIC Prefixes per ASN: 20.80 APNIC Region origin ASes announcing only one prefix: 2681 APNIC Region transit ASes present in the Internet Routing Table: 1405 Average APNIC Region AS path length visible: 4.1 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 4521 Number of APNIC addresses announced to Internet: 769392130 Equivalent to 45 /8s, 219 /16s and 254 /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-139577 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: 218861 Total ARIN prefixes after maximum aggregation: 103735 ARIN Deaggregation factor: 2.11 Prefixes being announced from the ARIN address blocks: 217916 Unique aggregates announced from the ARIN address blocks: 104509 ARIN Region origin ASes present in the Internet Routing Table: 18393 ARIN Prefixes per ASN: 11.85 ARIN Region origin ASes announcing only one prefix: 6841 ARIN Region transit ASes present in the Internet Routing Table: 1867 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: 2597 Number of ARIN addresses announced to Internet: 1079341472 Equivalent to 64 /8s, 85 /16s and 113 /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-399260 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: 203693 Total RIPE prefixes after maximum aggregation: 97183 RIPE Deaggregation factor: 2.10 Prefixes being announced from the RIPE address blocks: 200075 Unique aggregates announced from the RIPE address blocks: 118662 RIPE Region origin ASes present in the Internet Routing Table: 25857 RIPE Prefixes per ASN: 7.74 RIPE Region origin ASes announcing only one prefix: 11479 RIPE Region transit ASes present in the Internet Routing Table: 3655 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: 7881 Number of RIPE addresses announced to Internet: 717789120 Equivalent to 42 /8s, 200 /16s and 151 /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-210331 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: 95556 Total LACNIC prefixes after maximum aggregation: 22755 LACNIC Deaggregation factor: 4.20 Prefixes being announced from the LACNIC address blocks: 96878 Unique aggregates announced from the LACNIC address blocks: 41670 LACNIC Region origin ASes present in the Internet Routing Table: 8131 LACNIC Prefixes per ASN: 11.91 LACNIC Region origin ASes announcing only one prefix: 2163 LACNIC Region transit ASes present in the Internet Routing Table: 1518 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 25 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 5691 Number of LACNIC addresses announced to Internet: 171980544 Equivalent to 10 /8s, 64 /16s and 55 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-270748 + 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: 20713 Total AfriNIC prefixes after maximum aggregation: 4270 AfriNIC Deaggregation factor: 4.85 Prefixes being announced from the AfriNIC address blocks: 27057 Unique aggregates announced from the AfriNIC address blocks: 9296 AfriNIC Region origin ASes present in the Internet Routing Table: 1252 AfriNIC Prefixes per ASN: 21.61 AfriNIC Region origin ASes announcing only one prefix: 426 AfriNIC Region transit ASes present in the Internet Routing Table: 248 Average AfriNIC Region AS path length visible: 4.4 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 525 Number of AfriNIC addresses announced to Internet: 103444224 Equivalent to 6 /8s, 42 /16s and 111 /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 7545 4662 542 544 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4657 4192 74 ERX-CERNET-BKB China Education and Rese 7552 3096 1240 49 VIETEL-AS-AP Viettel Group, VN 45899 3039 1737 111 VNPT-AS-VN VNPT Corp, VN 4766 2814 11125 767 KIXS-AS-KR Korea Telecom, KR 9829 2751 1496 551 BSNL-NIB National Internet Backbone, IN 9808 2431 8699 26 CMNET-GD Guangdong Mobile Communication 9394 2345 4906 29 CTTNET China TieTong Telecommunications 4755 2141 422 179 TATACOMM-AS TATA Communications formerl 9498 2012 426 162 BBIL-AP BHARTI Airtel Ltd., IN 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 3619 1326 93 SHAW - Shaw Communications Inc., CA 11492 3531 228 607 CABLEONE - CABLE ONE, INC., US 22773 3363 2976 164 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 16509 2503 5371 1061 AMAZON-02 - Amazon.com, Inc., US 16625 2288 1272 1756 AKAMAI-AS - Akamai Technologies, Inc., 20115 2148 2740 537 CHARTER-20115 - Charter Communications, 18566 2119 405 108 MEGAPATH5-US - MegaPath Corporation, US 30036 2118 351 178 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 5650 2093 3074 1462 FRONTIER-FRTR - Frontier Communications 209 2081 5094 582 CENTURYLINK-US-LEGACY-QWEST - CenturyLi Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 5379 1628 138 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 8551 3289 378 44 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2646 547 1920 AKAMAI-ASN1, US 12389 2227 2221 637 ROSTELECOM-AS, RU 34984 2060 340 536 TELLCOM-AS, TR 9121 1682 1693 19 TTNET, TR 13188 1604 100 46 TRIOLAN, UA 9009 1372 146 757 M247, GB 8402 1304 545 15 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 5600 3331 598 Uninet S.A. de C.V., MX 10620 2769 414 1053 Telmex Colombia S.A., CO 11830 2703 384 34 Instituto Costarricense de Electricidad 6503 1517 433 54 Axtel, S.A.B. de C.V., MX 7303 1432 965 233 Telecom Argentina S.A., AR 28573 1287 2247 181 CLARO S.A., BR 6147 1276 377 29 Telefonica del Peru S.A.A., PE 3816 1022 505 113 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 13999 937 518 246 Mega Cable, S.A. de C.V., MX 11172 932 144 66 Alestra, S. de R.L. de C.V., MX 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 1207 393 21 LINKdotNET-AS, EG 37611 915 107 9 Afrihost, ZA 24835 848 636 22 RAYA-AS, EG 36903 827 416 125 MT-MPLS, MA 36992 817 1535 60 ETISALAT-MISR, EG 8452 701 1731 20 TE-AS TE-AS, EG 29571 485 70 13 ORANGE-COTE-IVOIRE, CI 37492 470 470 57 ORANGE-, TN 15399 428 45 11 WANANCHI-, KE 37342 420 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 8151 5600 3331 598 Uninet S.A. de C.V., MX 12479 5379 1628 138 UNI2-AS, ES 7545 4662 542 544 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4657 4192 74 ERX-CERNET-BKB China Education and Rese 39891 3778 203 20 ALJAWWALSTC-AS, SA 6327 3619 1326 93 SHAW - Shaw Communications Inc., CA 11492 3531 228 607 CABLEONE - CABLE ONE, INC., US 22773 3363 2976 164 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 8551 3289 378 44 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 7552 3096 1240 49 VIETEL-AS-AP Viettel Group, VN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 12479 5379 5241 UNI2-AS, ES 4538 4657 4583 ERX-CERNET-BKB China Education and Research Net 7545 4662 4118 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 3758 ALJAWWALSTC-AS, SA 6327 3619 3526 SHAW - Shaw Communications Inc., CA 8551 3289 3245 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 3363 3199 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 3096 3047 VIETEL-AS-AP Viettel Group, VN 45899 3039 2928 VNPT-AS-VN VNPT Corp, VN 11492 3531 2924 CABLEONE - CABLE ONE, INC., US Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 230105 UNALLOCATED 38.110.79.0/24 23015 CMC180-TOR-AS - Cambridge Merc 266842 UNALLOCATED 45.238.156.0/22 265680 HNTELCO S.A, HN 65550 DOCUMENT 81.8.34.0/24 15924 BORUSANTELEKOM-AS, TR 65550 DOCUMENT 81.8.35.0/24 15924 BORUSANTELEKOM-AS, TR 1358592 UNALLOCATED 103.134.14.0/23 63956 COLO-AS-AP Colocation Australi 1358592 UNALLOCATED 103.134.15.0/24 63956 COLO-AS-AP Colocation Australi 65549 DOCUMENT 117.239.163.0/24 65544 UNKNOWN 224413 UNALLOCATED 131.221.136.0/24 264413 Conecta Telecom Ltda, BR 64339 UNALLOCATED 143.0.108.0/22 18747 IFX18747 - IFX Corporation, US 64355 UNALLOCATED 156.40.196.0/24 30387 NIH-NET-NCCS - National Instit Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 198.18.1.19/32 7497 CSTNET-AS-AP Computer Network Information Cente Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 27.100.7.0/24 56096 UNKNOWN 27.126.156.0/22 55827 UNKNOWN 27.126.156.0/23 55827 UNKNOWN 27.126.158.0/23 55827 UNKNOWN 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 41.220.48.0/20 36900 -Reserved AS-, ZZ 43.255.80.0/24 36351 SOFTLAYER - SoftLayer Technologies Inc., US 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:12 /9:10 /10:36 /11:100 /12:291 /13:567 /14:1135 /15:1907 /16:13350 /17:7927 /18:13900 /19:25551 /20:39894 /21:46168 /22:92576 /23:75521 /24:418423 /25:957 /26:840 /27:896 /28:27 /29:7 /30:14 /31:0 /32:197 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 4260 5379 UNI2-AS, ES 6327 3391 3619 SHAW - Shaw Communications Inc., CA 39891 2946 3778 ALJAWWALSTC-AS, SA 11492 2773 3531 CABLEONE - CABLE ONE, INC., US 8551 2744 3289 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2604 3363 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 11830 2048 2703 Instituto Costarricense de Electricidad y Telec 18566 2014 2119 MEGAPATH5-US - MegaPath Corporation, US 30036 1865 2118 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 5650 1761 2093 FRONTIER-FRTR - Frontier Communications of Amer Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1607 2:888 4:22 5:2763 6:45 7:1 8:1183 11:3 12:1859 13:313 14:1924 15:39 16:4 17:233 18:59 20:49 23:2596 24:2521 25:2 27:2538 31:2068 32:97 35:36 36:833 37:3013 38:1689 39:295 40:120 41:3175 42:746 43:2002 44:143 45:6902 46:3224 47:251 49:1362 50:1098 51:322 52:1024 54:289 55:2 56:9 57:40 58:1713 59:1074 60:497 61:2069 62:1988 63:1815 64:4994 65:2202 66:4824 67:2706 68:1152 69:3544 70:1329 71:601 72:2425 74:2762 75:515 76:546 77:1711 78:1762 79:2331 80:1768 81:1496 82:1128 83:870 84:1098 85:2241 86:539 87:1551 88:1034 89:2431 90:210 91:6579 92:1261 93:2442 94:2520 95:3208 96:918 97:346 98:947 99:206 100:88 101:1157 102:453 103:20213 104:3528 105:247 106:890 107:1766 108:699 109:3723 110:1632 111:1867 112:1410 113:1418 114:1134 115:1721 116:1712 117:1876 118:2155 119:1624 120:1023 121:1034 122:2294 123:1643 124:1450 125:1965 128:1254 129:822 130:525 131:1633 132:733 133:218 134:1050 135:241 136:559 137:706 138:1995 139:848 140:579 141:844 142:800 143:1070 144:837 145:510 146:1261 147:793 148:1695 149:816 150:777 151:1010 152:1018 153:323 154:2898 155:894 156:1735 157:919 158:666 159:1894 160:1523 161:911 162:2680 163:791 164:1127 165:1577 166:428 167:1391 168:3210 169:861 170:4002 171:565 172:1108 173:2174 174:1015 175:893 176:2328 177:4048 178:2544 179:1368 180:2126 181:2398 182:2679 183:1069 184:1174 185:14837 186:3746 187:2418 188:2890 189:1973 190:8293 191:1394 192:10031 193:6622 194:5392 195:4057 196:2994 197:1648 198:5820 199:5965 200:7127 201:5081 202:10235 203:10202 204:4598 205:3006 206:3237 207:3289 208:3966 209:4237 210:3932 211:1994 212:3069 213:2889 214:1087 215:53 216:5959 217:2233 218:921 219:581 220:1864 221:966 222:999 223:1441 End of report

1 0

Spoofer Report for NANOG for Feb 2019
by CAIDA Spoofer Project 08 Mar '19

08 Mar '19

In response to feedback from operational security communities, CAIDA's source address validation measurement project (https://spoofer.caida.org) is automatically generating monthly reports of ASes originating prefixes in BGP for systems from which we received packets with a spoofed source address. We are publishing these reports to network and security operations lists in order to ensure this information reaches operational contacts in these ASes. This report summarises tests conducted within usa, can. Inferred improvements during Feb 2019: ASN Name Fixed-By 16842 5DL 2019-02-01 7922 COMCAST-7922 2019-02-02 18451 LESNET 2019-02-11 12083 WOW-INTERNET 2019-02-21 Further information for the inferred remediation is available at: https://spoofer.caida.org/remedy.php Source Address Validation issues inferred during Feb 2019: ASN Name First-Spoofed Last-Spoofed 5650 FRONTIER-FRTR 2016-02-22 2019-02-20 15003 AS-UBIQUITY 2016-03-24 2019-02-01 19230 NANOG 2016-06-13 2019-02-20 7029 WINDSTREAM 2016-06-21 2019-02-15 209 CENTURYLINK-US-LEGACY-QWEST 2016-08-16 2019-02-26 6128 CABLE-NET-1 2016-09-03 2019-02-23 20412 CLARITY-TELECOM 2016-09-30 2019-02-21 6181 FUSE-NET 2016-10-10 2019-02-23 25787 ROWE-NETWORKS 2016-10-21 2019-02-14 174 COGENT-174 2016-10-21 2019-02-25 31857 PRIORITY-TERABIT 2016-10-25 2019-02-09 30341 SCTA-ASN 2016-10-31 2019-02-25 32440 LONI 2016-11-03 2019-02-26 12083 WOW-INTERNET 2016-11-09 2019-02-23 13427 SOFTCOM-INTERNET-COMMUNICATION 2016-11-14 2019-02-26 3549 LVLT-3549 2016-11-16 2019-02-22 7106 INDEPENDENTSFIBERNETWORK 2017-01-09 2019-02-18 21832 KELLINCOM-1 2017-02-03 2019-02-23 18451 LESNET 2017-02-22 2019-02-20 6597 CBDC-6597 2017-04-27 2019-02-08 701 UUNET 2017-06-14 2019-02-04 6461 ZAYO-6461 2017-06-21 2019-02-26 63296 AMARILLO-WIRELESS 2017-09-01 2019-02-27 7233 YAHOO-US 2017-09-07 2019-02-19 14051 SUREWEST 2017-10-26 2019-02-24 33523 ROWANUNIVERSITY 2017-10-29 2019-02-26 546 PARSONS-PGS-1 2017-11-20 2019-02-19 12222 AKAMAI 2018-02-14 2019-02-27 8100 ASN-QUADRANET-GLOBAL 2018-04-06 2019-02-28 4201 ORST 2018-04-19 2019-02-27 393564 SPOKANE 2018-06-05 2019-02-27 225 VIRGINIA 2018-06-18 2019-02-25 54804 CSMIII-BUNKIELA 2018-09-15 2019-02-04 33452 RW 2018-09-19 2019-02-22 20448 VPNTRANET-LLC 2018-09-20 2019-02-26 11996 LOBOIS 2018-09-24 2019-02-22 13825 TROYCABLE-NET 2018-11-21 2019-02-16 63275 RADIOWIRE 2019-02-07 2019-02-07 18534 FIBER-CA 2019-02-08 2019-02-08 10965 MRNET 2019-02-11 2019-02-11 715 WOODYNET-2 2019-02-13 2019-02-13 6360 UNIVHAWAII 2019-02-25 2019-02-25 Further information for these tests where we received spoofed packets is available at: https://spoofer.caida.org/recent_tests.php?country_include=usa,can&no_block… Please send any feedback or suggestions to spoofer-info(a)caida.org

1 0

Re: Re: Arista Layer3 (Colton Conor)
by Michael Starr 08 Mar '19

08 Mar '19

I can't comment on the direct comparison of the SLX9540, but we have 8x 7280SR deployed across our network (just migrated off all the Brocades we had) and have had amazing success with them. The number of informational or "show" commands isn't as extensive as some of the others that have been around for a while and the output of some of them is a little jarring, but otherwise I have no complaints. All of my BGP sessions (200-300 IX sessions, 2 transit providers, 28 iBGP) are fully populated in <10 seconds (i know many of your networks are much larger than ours). As for pricing, I don't have list, but for the box, memory upgrade, and routing license we paid much less than 100k -- Of course the port density Feel free to reach out directly for more specific information :) Mike On Fri, Mar 8, 2019 at 7:00 AM <nanog-request(a)nanog.org> wrote: Message: 8 Date: Thu, 7 Mar 2019 21:44:34 -0600 From: Colton Conor <colton.conor(a)gmail.com> To: "Kaiser, Erich" <erich(a)gotfusion.net> Cc: NANOG list <nanog(a)nanog.org> Subject: Re: Arista Layer3 Message-ID: <CAMDdSzOpE6Cnz+JUH=+31a2VGDcqQ5qi2nA16h8ethce1RxfvQ(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" So how does the 7280SR-48C6 compare to the SLX9540? They are the same Broadcom chipset right? So the real question, is how does the product differ in software? On Wed, Mar 6, 2019 at 10:58 AM Kaiser, Erich <erich(a)gotfusion.net> wrote: > Agreed. > > > On Wed, Mar 6, 2019 at 2:16 AM Brandon Martin <lists.nanog(a)monmotha.net> > wrote: > >> On 3/6/19 12:36 AM, Colton Conor wrote: >> > How much do these boxes cost? >> >> List is about $100k in North America for a 9640 with all the ports >> "unlocked", full hardware kit (PSUs, fans, etc.) and some >> maintenance/support. Take whatever your standard Brocade/Extreme >> discount from that tends to look like. I should hope nobody pays list >> or anywhere close. >> -- >> Brandon Martin >> >

2 1

IPv6 Security Frequently Asked Questions (FAQ)
by Fernando Gont 08 Mar '19

08 Mar '19

Folks, The Internet Society has posted the "IPv6 Security Frequently Asked Questions (FAQ)" I authored. The document is available (in HTML, and also easy-to-print PDF) at: https://www.internetsociety.org/deploy360/ipv6/security/faq/ If you think there are other questions that should be added, or have comments on the answers, please do let me know -- the document can eventually be revised. Thanks! Cheers, -- -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

2 3

WIndows Updates Fail Via IPv6
by Mark Tinka 07 Mar '19

07 Mar '19

Hi all. Anyone ever figured out why Windows updates fail when the computer has an IPv6 connection? Google has tickets and tickets of this to and outside of Microsoft since 2013, with no real solution or answer as to what the problem actually is. In essence, many of the solutions out there point toward making sure the updates do not occur over IPv6, which, in effect, is the same as disabling it. I have a family PC at home running Windows 10 Pro, and noticed updates would fail in recent months. It took me a moment to realize that this started happening only after I enabled IPv6 in the TCP/IP stack. Disabling it immediately solves the issue. Quite odd that this is happening in 2018... Mark.

20 49