- Test - lists.nanog.org

Windows 11 now implements RFC 7217 (stable privacy addresses)!
by Fernando Gont 13 Dec '22

13 Dec '22

Folks, After over 10 (yes, *ten*) years, we have finally addressed security/privacy issues in the generation of IPv6 stable addresses in most popular operating systems. The traditional scheme/algorithm to generate stable IPv6 addresses with SLAAC required that the underlying MAC address be employed to generate the Interface Identifier. That is, the underlying MAC address would be embedded in the lower bits of an IPv6 address. This scheme allowed for host-tracking (since MAC addresses are usually globally-unique), address scanning (since addresses will follow specific patterns) and a number of other issues. In 2011, I submitted an IETF Internet-Draft proposing a scheme for generating stable addresses with SLAAC, meant to replace the traditional scheme. The scheme could be summarised and simplified as: Interface_ID = Hash(Prefix, Secret). Thus, interface identifiers would be stable within the same subnet, but vary across subnets. [Replacing the traditional scheme with this new scheme was anything but easy -- if you're curious, please check the "IPv6 Addressing" section in <https://www.si6networks.com/2020/08/06/a-brief-history-of-recent-advances-i…> ] Over time, popular operating systems and packages adopted the proposed algorithm: the Linux kernel, NetworkManager, OpenBSD's slaacd, MacOS, etc. Eventually, virtually every popular OS had adopted the scheme.... except Windows. Based on a recent note by Brian Carpenter, I ended up testing Windows 11, and I can confirm that it does implement RFC 7217 / RFC 8064! Therefore, e.g. if multiple prefixes are employed on a subnet, the stable addresses for each of such prefixes will employ a different Interface Identifier, thus avoiding the security/privacy issues discussed above -- this is really good news! Unfortunately, Windows still generates temporary addresses with the algorithm specified in RFC 4941, thus resulting in all temporary addresses for a given interface employing the same Interface Identifier (!). This problem has been addressed in RFC 8981... but it's implementation is not yet widespread, yet (it has been incoporated in e.g. the Linux kernel, though). I just hope it doesn't take Windows and others yet another 10+ years to implement RFC 8981, to finally address the remaining security/privacy issues in IPv6 address generation! [Original article with screenshots: https://www.linkedin.com/posts/fernandogont_after-over-10-yes-ten-years-we-… ] Thanks! Regards, -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494

2 1

TATA Communications
by Norman Jester 12 Dec '22

12 Dec '22

Contact me off list... seeing major loss at 64.86.252.65 in your path. Norman Jester 619-319-7055

2 1

RE: Large prefix lists/sets on IOS-XR
by Jakob Heitz (jheitz) 09 Dec '22

09 Dec '22

Sander, How big? How slow? You can reply to me off or on list. About 8 to 10 years ago, we had a large effort to improve this. Now customers push many megabytes of prefix-sets several times a day and it works. I have sent some questions internally to get a better answer. Related, in 7.2.1, we added the as-set, which allows you to filter BGP routes by origin-as. It is similar to as-path-set. as-path-set is slow, using a linear lookup, but it is versatile, allowing ios-regex. as-set can only use numbers and only for origin-as, but it is fast using a log(N) lookup. Regards, Jakob. -----Original Message----- Date: Fri, 9 Dec 2022 00:02:52 +0100 From: Sander Steffann <sander(a)steffann.nl> Hi, What is the best/most efficient/most convenient way to push large prefix lists or sets to an XR router for BGP prefix filtering? Pushing thousands of lines through the CLI seems foolish, I tried using the load command but it seems horribly slow. What am I missing? :) Cheers! Sander --- for every complex problem, there?s a solution that is simple, neat, and wrong

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 09 Dec '22

09 Dec '22

This is an automated weekly mailing describing the state of the Global IPv4 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 https://thyme.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. IPv4 Routing Table Report 04:00 +10GMT Sat 10 Dec, 2022 BGP Table (Global) as seen in Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 916614 Prefixes after maximum aggregation (per Origin AS): 346701 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 443400 Total ASes present in the Internet Routing Table: 73926 Prefixes per ASN: 12.40 Origin-only ASes present in the Internet Routing Table: 63481 Origin ASes announcing only one prefix: 26081 Transit ASes present in the Internet Routing Table: 10445 Transit-only ASes present in the Internet Routing Table: 422 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 1039 Number of instances of unregistered ASNs: 1044 Number of 32-bit ASNs allocated by the RIRs: 40848 Number of 32-bit ASNs visible in the Routing Table: 33831 Prefixes from 32-bit ASNs in the Routing Table: 164978 Number of bogon 32-bit ASNs visible in the Routing Table: 16 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 516 Number of addresses announced to Internet: 3061103104 Equivalent to 182 /8s, 116 /16s and 186 /24s Percentage of available address space announced: 82.7 Percentage of allocated address space announced: 82.7 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 311058 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 239692 Total APNIC prefixes after maximum aggregation: 68356 APNIC Deaggregation factor: 3.51 Prefixes being announced from the APNIC address blocks: 234528 Unique aggregates announced from the APNIC address blocks: 97353 APNIC Region origin ASes present in the Internet Routing Table: 13152 APNIC Prefixes per ASN: 17.83 APNIC Region origin ASes announcing only one prefix: 3835 APNIC Region transit ASes present in the Internet Routing Table: 1756 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 31 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8409 Number of APNIC addresses announced to Internet: 773713792 Equivalent to 46 /8s, 29 /16s and 239 /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-151865 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: 267472 Total ARIN prefixes after maximum aggregation: 121859 ARIN Deaggregation factor: 2.19 Prefixes being announced from the ARIN address blocks: 269090 Unique aggregates announced from the ARIN address blocks: 129548 ARIN Region origin ASes present in the Internet Routing Table: 19058 ARIN Prefixes per ASN: 14.12 ARIN Region origin ASes announcing only one prefix: 6967 ARIN Region transit ASes present in the Internet Routing Table: 1939 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 35 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4697 Number of ARIN addresses announced to Internet: 1286705664 Equivalent to 76 /8s, 177 /16s and 146 /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-401308 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, 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: 262550 Total RIPE prefixes after maximum aggregation: 121662 RIPE Deaggregation factor: 2.16 Prefixes being announced from the RIPE address blocks: 259368 Unique aggregates announced from the RIPE address blocks: 155340 RIPE Region origin ASes present in the Internet Routing Table: 28184 RIPE Prefixes per ASN: 9.20 RIPE Region origin ASes announcing only one prefix: 12019 RIPE Region transit ASes present in the Internet Routing Table: 3963 Average RIPE Region AS path length visible: 4.2 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10917 Number of RIPE addresses announced to Internet: 716202624 Equivalent to 42 /8s, 176 /16s and 98 /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-213403 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: 117310 Total LACNIC prefixes after maximum aggregation: 28390 LACNIC Deaggregation factor: 4.13 Prefixes being announced from the LACNIC address blocks: 116624 Unique aggregates announced from the LACNIC address blocks: 48738 LACNIC Region origin ASes present in the Internet Routing Table: 11008 LACNIC Prefixes per ASN: 10.59 LACNIC Region origin ASes announcing only one prefix: 2669 LACNIC Region transit ASes present in the Internet Routing Table: 2267 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8766 Number of LACNIC addresses announced to Internet: 176063744 Equivalent to 10 /8s, 126 /16s and 133 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-273820 + 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: 28551 Total AfriNIC prefixes after maximum aggregation: 5649 AfriNIC Deaggregation factor: 5.05 Prefixes being announced from the AfriNIC address blocks: 36488 Unique aggregates announced from the AfriNIC address blocks: 11996 AfriNIC Region origin ASes present in the Internet Routing Table: 1705 AfriNIC Prefixes per ASN: 21.40 AfriNIC Region origin ASes announcing only one prefix: 591 AfriNIC Region transit ASes present in the Internet Routing Table: 329 Average AfriNIC Region AS path length visible: 5.0 Max AfriNIC Region AS path length visible: 37 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1042 Number of AfriNIC addresses announced to Internet: 108125184 Equivalent to 6 /8s, 113 /16s and 220 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks 41/8, 45/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 9808 9144 8884 50 CHINAMOBILE-CN China Mobile Communicati 7545 5945 786 694 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4883 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3625 1331 21 VIETEL-AS-AP Viettel Group, VN 7713 3504 1043 63 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3365 1867 87 VNPT-AS-VN VNPT Corp, VN 9498 2574 499 237 BBIL-AP BHARTI Airtel Ltd., IN 4766 2534 11252 598 KIXS-AS-KR Korea Telecom, KR 24560 2313 849 417 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 45090 2180 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute Complete listing at https://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 7714 10631 2892 AMAZON-02, US 11492 4548 301 567 CABLEONE, US 7155 3893 265 32 VIASAT-SP-BACKBONE, US 22773 3690 3059 312 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3528 1320 63 SHAW, CA 16625 3474 1817 2515 AKAMAI-AS, US 749 3030 50577 2297 DNIC-AS-00749, US 7018 2586 24125 1556 ATT-INTERNET4, US 30036 2579 369 336 MEDIACOM-ENTERPRISE-BUSINESS, US 396982 2567 3482 362 GOOGLE-CLOUD-PLATFORM, US Complete listing at https://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 6964 1730 151 UNI2-AS, ES 9121 6366 1692 17 TTNET, TR 20940 4063 3400 183 AKAMAI-ASN1, NL 39891 4010 234 47 ALJAWWALSTC-AS, SA 8551 3700 374 38 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2941 2290 907 ROSTELECOM-AS, RU 9009 2644 252 1362 M247, RO 47331 2591 387 1954 TTNET, TR 34984 2250 357 609 TELLCOM-AS, TR 6849 2194 339 20 UKRTELNET, UA Complete listing at https://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10854 3338 596 Uninet S.A. de C.V., MX 10620 3463 507 853 Telmex Colombia S.A., CO 11830 2255 369 64 Instituto Costarricense de Electricidad 13999 2160 353 569 Mega Cable, S.A. de C.V., MX 28573 1337 2327 257 Claro NXT Telecomunicacoes Ltda, BR 6503 1293 338 521 Axtel, S.A.B. de C.V., MX 3816 1291 740 156 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1154 370 22 Telefonica del Peru S.A.A., PE 11664 1136 184 473 Techtel LMDS Comunicaciones Interactiva 26615 987 2466 43 TIM SA, BR Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24835 1548 537 31 RAYA-AS, EG 24863 1537 393 21 LINKdotNET-AS, EG 36992 1356 1520 269 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 1014 67 40 ORANGE-COTE-IVOIRE, CI 36935 880 520 42 Vodafone-, EG 6713 613 1863 34 IAM-AS, MA 15399 519 53 42 WANANCHI-, KE 37342 442 32 1 MOVITEL, MZ 2018 375 319 72 TENET-1, ZA Complete listing at https://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10854 3338 596 Uninet S.A. de C.V., MX 9808 9144 8884 50 CHINAMOBILE-CN China Mobile Communicati 16509 7714 10631 2892 AMAZON-02, US 12479 6964 1730 151 UNI2-AS, ES 9121 6366 1692 17 TTNET, TR 7545 5945 786 694 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4883 4192 75 ERX-CERNET-BKB China Education and Rese 11492 4548 301 567 CABLEONE, US 20940 4063 3400 183 AKAMAI-ASN1, NL 39891 4010 234 47 ALJAWWALSTC-AS, SA Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9144 9094 CHINAMOBILE-CN China Mobile Communications Grou 12479 6964 6813 UNI2-AS, ES 9121 6366 6349 TTNET, TR 7545 5945 5251 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 7714 4822 AMAZON-02, US 4538 4883 4808 ERX-CERNET-BKB China Education and Research Net 11492 4548 3981 CABLEONE, US 39891 4010 3963 ALJAWWALSTC-AS, SA 20940 4063 3880 AKAMAI-ASN1, NL 7155 3893 3861 VIASAT-SP-BACKBONE, US Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 65000 PRIVATE 2.92.64.0/20 8371 VIMPELCOM-NN Vimpelcom, Nizh 65000 PRIVATE 2.92.80.0/20 8371 VIMPELCOM-NN Vimpelcom, Nizh 398083 UNALLOCATED 5.133.124.0/24 399587 UT, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 16641 UNALLOCATED 8.10.194.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.10.210.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.12.76.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.12.250.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.14.115.0/24 3356 LEVEL3, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.131.185.0/24 Origin: 174 COGENT-174, US 23.131.185.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.186.0/24 Origin: 174 COGENT-174, US 23.131.186.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.187.0/24 Origin: 174 COGENT-174, US 23.131.187.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.188.0/24 Origin: 46450 PILOT, US 23.131.188.0/24 Transit: 1299 TWELVE99 Arelion, fka Telia Carrier, SE 23.131.189.0/24 Origin: 150303 SOLORDP-AS-AP SoloRDP, IN 23.131.189.0/24 Transit: 140947 SNTHOSTINGS-AS-AP SnTHostings, IN Complete listing at https://thyme.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:16 /9:13 /10:39 /11:100 /12:294 /13:584 /14:1202 /15:2050 /16:13516 /17:8320 /18:13915 /19:25212 /20:44298 /21:52360 /22:110154 /23:97972 /24:545764 /25:805 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 5999 6964 UNI2-AS, ES 9121 5528 6366 TTNET, TR 8151 4844 10854 Uninet S.A. de C.V., MX 11492 3455 4548 CABLEONE, US 6327 3336 3528 SHAW, CA 39891 3193 4010 ALJAWWALSTC-AS, SA 8551 3166 3700 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 7155 2982 3893 VIASAT-SP-BACKBONE, US 22773 2724 3690 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2237 2579 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1732 2:1024 3:168 4:5 5:4067 6:109 7:5 8:1580 9:1 11:173 12:1613 13:370 14:2374 15:287 16:75 17:371 18:395 20:242 21:4 22:188 23:6001 24:2451 25:4 27:2703 29:19 31:2486 32:103 34:8 35:95 36:1811 37:4573 38:3919 39:816 40:144 41:3935 42:1134 43:2313 44:305 45:16389 46:4173 47:378 49:1722 50:1939 51:246 52:1522 54:394 55:839 56:8 57:78 58:1789 59:1158 60:1006 61:2428 62:2599 63:1956 64:5628 65:2327 66:4841 67:3032 68:1372 69:4155 70:1281 71:665 72:2990 74:2614 75:1466 76:599 77:2257 78:3969 79:2940 80:2045 81:1822 82:1488 83:1228 84:1498 85:3747 86:749 87:1927 88:2841 89:3501 90:581 91:7624 92:1983 93:2569 94:3530 95:4821 96:1317 97:344 98:1173 99:740 100:69 101:1059 102:2476 103:30573 104:4573 105:483 106:825 107:2551 108:918 109:4330 110:2044 111:3305 112:2032 113:1571 114:1604 115:2038 116:1901 117:2466 118:2320 119:1920 120:1726 121:1108 122:2590 123:2139 124:1576 125:2222 128:1266 129:979 130:978 131:2006 132:803 133:400 134:1903 135:294 136:880 137:921 138:2578 139:1500 140:1033 141:1476 142:1413 143:1463 144:1200 145:351 146:1893 147:1512 148:2280 149:1883 150:865 151:1148 152:1846 153:458 154:3845 155:1411 156:1634 157:1284 158:1041 159:2244 160:2576 161:1429 162:3534 163:1473 164:1678 165:1625 166:847 167:1732 168:3854 169:920 170:4570 171:872 172:3523 173:3090 174:1037 175:1144 176:3631 177:4788 178:3548 179:2137 180:2367 181:3374 182:3264 183:1935 184:2364 185:19983 186:4619 187:3944 188:4075 189:3450 190:9032 191:1478 192:11005 193:8807 194:7224 195:5094 196:2983 197:2363 198:6013 199:6108 200:7726 201:5847 202:10640 203:10056 204:4608 205:3518 206:3813 207:3407 208:4125 209:4828 210:4429 211:2494 212:4060 213:3539 214:1111 215:55 216:6597 217:2637 218:1273 219:575 220:2032 221:954 222:839 223:2013 End of report

1 0

FCC order regarding Urth Access LLC
by Sean Donelan 08 Dec '22

08 Dec '22

The FCC is (slowly, slowly) increasing robocall enforcement. It issued a cease and desist letter, and directed all voice service providers to take steps to effectively mitigate suspected illegal robocall traffic made by or on behalf of the following: (1) Urth Access, LLC (Urth Access); (2) Fire Data LLC; (3) US Acquisitions LLC; (4) Dawood & Dawood; (5) Dawood and Company; (6) their individual associates; and (7) associated entities (collectively, the Student Loan Robocall Operation). https://www.fcc.gov/document/fcc-orders-blocking-student-loan-scam-robocall… As always consult with your own corporate lawyers. The FCC order has lots of words which mean different things to a lawyer. The FCC gets grumpy when companies fail to reply to its letters.

1 0

Spoofer Report for NANOG for Nov 2022
by CAIDA Spoofer Project 08 Dec '22

08 Dec '22

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 Nov 2022: ASN Name Fixed-By 2152 CSUNET-NW 2022-11-16 19318 IS-AS-1 2022-11-28 Further information for the inferred remediation is available at: https://spoofer.caida.org/remedy.php Source Address Validation issues inferred during Nov 2022: ASN Name First-Spoofed Last-Spoofed 7029 WINDSTREAM 2016-06-21 2022-11-24 209 CENTURYLINK-US-LEGACY-QWEST 2016-08-16 2022-11-30 6128 CABLE-NET-1 2016-09-03 2022-11-28 20412 CLARITY-TELECOM 2016-09-30 2022-11-30 271 BCNET 2016-10-24 2022-11-24 33452 RW 2018-09-19 2022-11-21 21804 ACCESS-SK 2019-06-09 2022-11-24 53641 TOMALESBAYLAN 2019-11-29 2022-11-25 397270 NETINF-PRIMARY 2020-04-03 2022-11-28 398836 NP-NETWORKS 2021-03-12 2022-11-27 394414 E2WS 2022-05-08 2022-11-19 397086 LAYER-HOST-HOUSTON 2022-06-16 2022-11-27 11976 FIDN 2022-11-16 2022-11-24 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

Reminder OARC 40 - Call for Contribution
by John Todd 08 Dec '22

08 Dec '22

Reminder: Deadline for OARC 40 abstract submission - December 20, 23:59 UTC Please note that, we are looking for contributions and remote participation is actively supported -------- Subject: OARC 40 - Call for Contribution OARC 40 will be a two-day hybrid meeting held on 16 & 17 February in Atlanta (GA), USA at 10:00 AM (Local time - EST (UTC-05:00)). The onsite part of the meeting will be colocated with NANOG 87. The Programme Committee is seeking contributions from the community. All DNS-related subjects and suggestions for discussion topics are welcome. For inspiration, we provide a non-exhaustive list of ideas: • Operations: Any operational gotchas, lessons learned from an outage, details/reasons for a recent outage (how to improve TTR, tooling). • Deployment: DNS config management and release process. • Monitoring: Log ingestion pipeline, analytics infrastructure, anomaly detection. • Scaling: DNS performance management and metrics. Increasing DNS Server Efficiency • Security/Privacy: DNSSEC signing and validation, key storage, rollovers, qname minimization, DoH/DoT The presentations can be either a full-length presentation - 20 mins (+5 mins Q/A) or a lightning presentation - 10 mins (+5 mins for Q/A) Workshop Milestones: 2022-10-22 Submissions open via Indico 2022-12-20 Deadline for submission (23:59 UTC) 2023-01-10 Preliminary list of contributions published 2023-01-17 Full agenda published 2023-01-30 Deadline for slideset submission and Rehearsal 2023-02-16 OARC 40 Workshop - Day1 2023-02-17 OARC 40 Workshop - Day2 The Registration page and details for presentation submission are published at: <https://www.dns-oarc.net/oarc40> To allow the Programme Committee to make objective assessments of submissions, so as to ensure the quality of the workshop, submissions SHOULD include slides. Draft slides are acceptable on submission. Guidelines for presentation slides: https://www.grammarly.com/blog/presentation-tips/ Additional information for speakers of OARC 40 • your talk will be broadcast live and recorded for future reference • your presentation slides will be available for delegates and others to download and refer to, before, during and after the meeting • Remote speakers have mandatory rehearsal on 2023-01-31 at 14:00 UTC. It would be very useful to have your slides (even if draft) ready for this. Note: DNS-OARC provides registration fee waivers for the workshop to support those who are part of underrepresented groups to speak at and/or attend DNS-OARC. More details will be provided when registration opens. If you have questions or concerns you can contact the Programme Committee: https://www.dns-oarc.net/oarc/programme via submissions(a)dns-oarc.net John Todd, for the DNS-OARC Programme Committee OARC depends on sponsorship to fund its workshops and associated social events. Please contact sponsor(a)dns-oarc.net if your organization is interested in becoming a sponsor. (Please note that OARC is run on a non-profit basis, and is not in a position to reimburse expenses or time for speakers at its meetings.) -- John Todd - jtodd(a)quad9.net General Manager - Quad9 Recursive Resolver

1 0

Early Bird Reg. Ends Monday! + Light Up Your Immune System + More
by Nanog News 08 Dec '22

08 Dec '22

*NANOG 87 Early Bird Registration Ends Monday* *Deadline for Discounted Pricing Ends 12, December* Join us for NANOG 87 in Atlanta, GA, 13 - 15, February! Early bird discounted rates will end Monday, 12, December. *REGISTER NOW! <https://www.nanog.org/events/nanog-87/>* *Light Up Your Immune System This Holiday Season* The jolliness of the season can bring abnormally high levels of sugar, alcohol, and stress to our daily routines, making us more susceptible to seasonal flu and cold bugs. *Stay Jolly This Season* Your best defense is a hearty offense. So, boost your immune system with these achievable tips. *READ MORE <https://www.nanog.org/stories/healthy-for-the-holidays/>* *Trending on NANOG TV!* *Have You Watched our Latest Content on NANOG TV?* Check out one of our most viewed videos of all time. *Tutorial: Everything You Always Wanted to Know About Optical <https://www.youtube.com/watch?v=mWqe8_5SUvk>* This popular tutorial is tailored for network engineers + has been updated to cover the latest technologies. Example topics include: - How fiber works (the basics, fiber types, limitations, etc.) - Working with optics (choosing the right type, designing optical networks, etc.) - Optical power (understanding dBm, loss, using light meters, etc.) - DWDM (how it works, muxes, oadms, amps, etc.) - Dispersion (what is it, why do we care, how do we fix it) - Optical Myths. I.e., can I hurt myself looking into the fiber? Can I overload my optic? *WATCH NOW <https://www.nanog.org/news-stories/nanog-tv/>*

1 0

Experiences with commercial NOS vendors in white box space
by Graham Johnston 07 Dec '22

07 Dec '22

Good day. I'm curious to hear from those with direct, hopefully in-production, experience in using a commercial network operating system vendor along with white box switches. I'm specifically looking for operators in the service provider space, rather than data center or enterprise. I'm largely focused on Jericho2/Qumran2 based devices, with what would likely be modest feature requirements. We currently use MPLS with RSVP to build automatic paths, but don't do anything specific for traffic engineering. Segment routing isn't a requirement for today. Currently use more traditional forms of MPLS services for customer L2 and L3 VPNs, but are investigating a transition to EVPN. Automation is very much important to us, as are routing security features. Based on research, and use of vertically integrated Jericho-based switches, we aren't concerned about QoS as our needs aren't super complex. I guess I'm largely saying that we don't expect the ASIC to be the weak point in our use case, but rather the NOS or the nature of support from the vendor. I'm aware of IPInfusion and their OcNOS product, but the CLI and config syntax feels dated. I feel like I've been ruined by Cisco RPL, Juniper policy-statements, and Arista RCF and expect I would find wanting more than what route-map syntax has to offer. Can I accomplish the same complex routing policies via route-maps that I can with more modern solutions, and I'm just assuming it's limiting? Is it fair to say that even if I can achieve the same functionality, that route-maps are the poorer choice when it comes to the human interaction aspect? I know of Arrcus, but don't know much more than I can see on their website. Edge-core has an interesting reference in its Open Networking Solution Guide on their website in which they position Arrcus for core applications and IPInfusion for access and aggregation. All of which could be meaningless based on the varied definitions and expectations of what a core network is and does. Is it feature rich or just a set of fast LSR P-routers? The Edge-Cor guide also identifies Exaware and Capgemini, both of whom I know little about. Are there viable SP focused NOS vendors that I haven't touched on? Thanks in advance for any reply, be it on-list or off-list. Regards, Graham

3 2

the ipv4 vs ipv6 growth debate
by Dave Taht 06 Dec '22

06 Dec '22

I use a web plugin tool called ipvfoo to track my actual ipv4 vis ipv6 usage. I wish it worked over time. With very few exceptions I am still regularly calling ipv4 addresses in most webpages. Has anyone done a more organized study of say, the top 1 million, and how many still require at least some ipv4 to exist, and those trends over time? -- This song goes out to all the folk that thought Stadia would work: https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-69813666656… Dave Täht CEO, TekLibre, LLC

5 8