- Test - lists.nanog.org

WATCH as Vint Cerf talks about "Interplanetary Networking" + Hackathon: For the Passionate Engineer
by Nanog News 24 May '21

24 May '21

Don't Miss Vint Cerf <https://youtu.be/XCFhrMhkCe0>present "The Evolution of Interplanetary Networking" *WATCH NOW:* <https://youtu.be/XCFhrMhkCe0>In this clip, NANOG 82 Keynote speaker and a "Father of the Internet" Vint Cerf explains how the discussion of "interplanetary networking" began. "...And our conclusion was why don't we think about building a network that could operate across the entire solar system in order to provide communications capability for both manned and robotic spacecraft. So, that is what launched us into a discussion about interplanetary networking," Vint Cerf Don't miss the rest of Cerf's *earth-shattering* talk at NANOG 82 Virtual. <https://www.nanog.org/events/nanog-82/> <https://www.nanog.org/events/nanog-82/> *Answer your burning questions:* there will be a live Q+A session following the presentation. Hackathon: Creative Outlet for the Passionate Engineer *Hackathons are not only a key part of our conferences, but a unique opportunity* to engage in the sheer “joy of creation,” collaboration and learning within the networking industry. *“It’s relatively easy to take a class and do homework, but this is a venue for people who are really passionate about what they are doing,” *NANOG Hackathon Committee Chair and Netflix Director of Engineering Michael Costello said. *“It's an opportunity for participants to do something that is not required, but instead in service of learning, **expressing and enhancing their own level of excellence,” *Costello continued. *READ MORE * <https://www.nanog.org/stories/nanog-hackathon-creative-outlet-for-the-passi…> *Women in Tech: We want to hear from you! * - What topics would you like to discuss in break-out rooms? - What topics have not been addressed that need to be discussed? *Please send all topics to nanogpc(a)nanog.org with subject line "women in tech"* *NANOG 82 Networking Sessions:* *Newcomers *Monday: an opportunity for those new to NANOG to connect with NANOG veterans *Women in Tech *Tuesday: an opportunity to discuss diversity issues, develop solutions, and connect with mentors and peers *Birds of a Feather (BOF) *Wednesday: informal networking around specific topics related to network operations

1 0

BGP Traffic Engineering - Active\Passive
by nanoguser100 21 May '21

21 May '21

Nanog, At my organization we historically would get T1 ISPs at our POPs and take full table + default. BGP would simply "do it's thing" and for the most part everything worked out. There are instances where we have had heavily lopsided traffic even though AS path length is the same. To make things easier to track we will do something such as: * BGP Peer ISP-A - Lower local pref, advertise all prefixes. * BGP Peer ISP-B - Normal local pref, prepend In the routing table it looks like: * ISP-A 1111 174 * ISP-B 1111 1111 1111 1111 1299 Ingress everything takes 174 for the most part (due to prepending), egress the same (due to local pref). Let's say there's a special AS, 9999 which despite AS path lengths being the same is way better latency in ISP-B. Correct me if I'm wrong here but I *could* take full table + AS 9999 on B meaning the traffic will prefer 'B' due it it having a more specific route since I'm only taking default from A (despite local pref). That will correct my egress situation but how can I fix ingress? Is it possible to prepend to JUST one upstream ASN so normal traffic takes ISP A back except 9999 traffic? to make: * ISP-A 1111 174 4444 * ISP-B 1111 1111 1111 1111 1299 4444 * ISP-A 1111 1111 1111 1111 1111 1111 174 9999 * ISP-B 1111 1111 1111 1111 1299 9999 If I'm unable to do that will most provider prepend on your behalf so that ISP-A would add the prepends for 9999 only? Now to mix this up let's say another ASN, 7777 was in-between 1299 and 9999 but latency wise the route was still faster. - nanoguser100 Sent with [ProtonMail](https://protonmail.com) Secure Email.

3 2

Weekly Routing Table Report
by cscora＠apnic.net 21 May '21

21 May '21

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 22 May, 2021 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 852994 Prefixes after maximum aggregation (per Origin AS): 321766 Deaggregation factor: 2.65 Unique aggregates announced (without unneeded subnets): 408191 Total ASes present in the Internet Routing Table: 71301 Prefixes per ASN: 11.96 Origin-only ASes present in the Internet Routing Table: 61330 Origin ASes announcing only one prefix: 25315 Transit ASes present in the Internet Routing Table: 9971 Transit-only ASes present in the Internet Routing Table: 310 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 38 Max AS path prepend of ASN ( 37385) 33 Prefixes from unregistered ASNs in the Routing Table: 1167 Number of instances of unregistered ASNs: 1172 Number of 32-bit ASNs allocated by the RIRs: 36084 Number of 32-bit ASNs visible in the Routing Table: 30022 Prefixes from 32-bit ASNs in the Routing Table: 139678 Number of bogon 32-bit ASNs visible in the Routing Table: 22 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 647 Number of addresses announced to Internet: 3039623808 Equivalent to 181 /8s, 44 /16s and 250 /24s Percentage of available address space announced: 82.1 Percentage of allocated address space announced: 82.1 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.5 Total number of prefixes smaller than registry allocations: 284362 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 229410 Total APNIC prefixes after maximum aggregation: 65589 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 225463 Unique aggregates announced from the APNIC address blocks: 90076 APNIC Region origin ASes present in the Internet Routing Table: 11607 APNIC Prefixes per ASN: 19.42 APNIC Region origin ASes announcing only one prefix: 3324 APNIC Region transit ASes present in the Internet Routing Table: 1631 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 31 Number of APNIC region 32-bit ASNs visible in the Routing Table: 6761 Number of APNIC addresses announced to Internet: 773922304 Equivalent to 46 /8s, 33 /16s and 30 /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-147769 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: 247633 Total ARIN prefixes after maximum aggregation: 113176 ARIN Deaggregation factor: 2.19 Prefixes being announced from the ARIN address blocks: 248026 Unique aggregates announced from the ARIN address blocks: 118149 ARIN Region origin ASes present in the Internet Routing Table: 18811 ARIN Prefixes per ASN: 13.19 ARIN Region origin ASes announcing only one prefix: 6809 ARIN Region transit ASes present in the Internet Routing Table: 1943 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 35 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3879 Number of ARIN addresses announced to Internet: 1271316992 Equivalent to 75 /8s, 198 /16s and 194 /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: 237595 Total RIPE prefixes after maximum aggregation: 110779 RIPE Deaggregation factor: 2.14 Prefixes being announced from the RIPE address blocks: 233575 Unique aggregates announced from the RIPE address blocks: 141918 RIPE Region origin ASes present in the Internet Routing Table: 27930 RIPE Prefixes per ASN: 8.36 RIPE Region origin ASes announcing only one prefix: 11985 RIPE Region transit ASes present in the Internet Routing Table: 3890 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 31 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10187 Number of RIPE addresses announced to Internet: 710306944 Equivalent to 42 /8s, 86 /16s and 108 /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: 111183 Total LACNIC prefixes after maximum aggregation: 26481 LACNIC Deaggregation factor: 4.20 Prefixes being announced from the LACNIC address blocks: 112298 Unique aggregates announced from the LACNIC address blocks: 47061 LACNIC Region origin ASes present in the Internet Routing Table: 10745 LACNIC Prefixes per ASN: 10.45 LACNIC Region origin ASes announcing only one prefix: 2697 LACNIC Region transit ASes present in the Internet Routing Table: 2030 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 29 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8384 Number of LACNIC addresses announced to Internet: 176203520 Equivalent to 10 /8s, 128 /16s and 167 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-272796 + 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: 26005 Total AfriNIC prefixes after maximum aggregation: 4964 AfriNIC Deaggregation factor: 5.24 Prefixes being announced from the AfriNIC address blocks: 32985 Unique aggregates announced from the AfriNIC address blocks: 10484 AfriNIC Region origin ASes present in the Internet Routing Table: 1468 AfriNIC Prefixes per ASN: 22.47 AfriNIC Region origin ASes announcing only one prefix: 500 AfriNIC Region transit ASes present in the Internet Routing Table: 305 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 38 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 811 Number of AfriNIC addresses announced to Internet: 107411200 Equivalent to 6 /8s, 102 /16s and 247 /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 7866 8995 52 CMNET-GD Guangdong Mobile Communication 7545 5790 783 669 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4753 4192 74 ERX-CERNET-BKB China Education and Rese 7713 3522 1023 56 TELKOMNET-AS-AP PT Telekomunikasi Indon 7552 3505 1330 20 VIETEL-AS-AP Viettel Group, VN 45899 2808 1896 54 VNPT-AS-VN VNPT Corp, VN 4766 2426 11104 562 KIXS-AS-KR Korea Telecom, KR 9498 2341 482 241 BBIL-AP BHARTI Airtel Ltd., IN 4755 2127 441 192 TATACOMM-AS TATA Communications formerl 45090 2116 1197 71 CNNIC-TENCENT-NET-AP Shenzhen Tencent C 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 16509 5218 9380 2271 AMAZON-02, US 11492 4806 318 586 CABLEONE, US 7155 4027 264 32 VIASAT-SP-BACKBONE, US 22773 3938 3002 247 ASN-CXA-ALL-CCI-22773-RDC, US 16625 3448 1769 2425 AKAMAI-AS, US 6327 3360 1317 68 SHAW, CA 30036 2570 373 127 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2524 5035 480 CENTURYLINK-US-LEGACY-QWEST, US 5972 2242 452 779 DNIC-ASBLK-05800-06055, US 20115 2170 2928 508 CHARTER-20115, 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 12479 6639 1725 146 UNI2-AS, ES 20940 3604 3347 202 AKAMAI-ASN1, NL 39891 3266 187 22 ALJAWWALSTC-AS, SA 8551 3097 378 40 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2917 2281 892 ROSTELECOM-AS, RU 9009 2427 253 1304 M247, GB 34984 2203 355 591 TELLCOM-AS, TR 13188 1609 100 31 TRIOLAN, UA 58224 1600 886 579 TCI, IR 61317 1548 284 785 ASDETUK http://www.heficed.com, GB 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 8601 3483 571 Uninet S.A. de C.V., MX 10620 3422 526 613 Telmex Colombia S.A., CO 11830 2494 369 62 Instituto Costarricense de Electricidad 13999 1725 434 444 Mega Cable, S.A. de C.V., MX 6503 1450 311 476 Axtel, S.A.B. de C.V., MX 28573 1381 2282 226 CLARO S.A., BR 3816 1233 648 150 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1120 377 38 Telefonica del Peru S.A.A., PE 11664 998 208 419 Techtel LMDS Comunicaciones Interactiva 11172 964 111 69 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 1591 393 22 LINKdotNET-AS, EG 24835 1452 494 28 RAYA-AS, EG 36992 1196 1473 176 ETISALAT-MISR, EG 36903 1183 537 110 MT-MPLS, MA 29571 731 68 11 ORANGE-COTE-IVOIRE, CI 6713 613 1863 34 IAM-AS, MA 36935 526 522 40 Vodafone-, EG 37342 487 32 1 MOVITEL, MZ 15399 481 48 24 WANANCHI-, KE 23889 439 232 16 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 8151 8601 3483 571 Uninet S.A. de C.V., MX 9808 7866 8995 52 CMNET-GD Guangdong Mobile Communication 12479 6639 1725 146 UNI2-AS, ES 7545 5790 783 669 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 5218 9380 2271 AMAZON-02, US 11492 4806 318 586 CABLEONE, US 4538 4753 4192 74 ERX-CERNET-BKB China Education and Rese 7155 4027 264 32 VIASAT-SP-BACKBONE, US 22773 3938 3002 247 ASN-CXA-ALL-CCI-22773-RDC, US 20940 3604 3347 202 AKAMAI-ASN1, NL Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 7866 7814 CMNET-GD Guangdong Mobile Communication Co.Ltd. 12479 6639 6493 UNI2-AS, ES 7545 5790 5121 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4753 4679 ERX-CERNET-BKB China Education and Research Net 11492 4806 4220 CABLEONE, US 7155 4027 3995 VIASAT-SP-BACKBONE, US 22773 3938 3691 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3505 3485 VIETEL-AS-AP Viettel Group, VN 7713 3522 3466 TELKOMNET-AS-AP PT Telekomunikasi Indonesia, ID 20940 3604 3402 AKAMAI-ASN1, NL Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, US 18604 UNALLOCATED 8.25.204.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 40544 UNALLOCATED 12.0.33.0/24 6461 ZAYO-6461, US 46505 UNALLOCATED 12.7.131.0/24 7018 ATT-INTERNET4, US 15132 UNALLOCATED 12.9.150.0/24 1239 SPRINTLINK, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 5.181.53.0/24 Origin: 48402 VIOUSLY, FR Transit: 8218 NEO-ASN legacy Neotelecoms, FR 23.141.0.0/24 Origin: 395350 UNASSIGNED Transit: 11426 TWC-11426-CAROLINAS, US 23.142.80.0/24 Origin: 398481 REDMERCURY, US Transit: 209319 IPV6ROUTING, US 23.162.32.0/24 Origin: 32444 SAFELINK-MV, US Transit: 6939 HURRICANE, US 27.100.7.0/24 Origin: 56096 UNASSIGNED Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 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:16 /9:13 /10:41 /11:102 /12:306 /13:587 /14:1190 /15:1996 /16:13482 /17:8331 /18:13927 /19:25796 /20:42259 /21:50247 /22:106775 /23:91043 /24:495481 /25:1402 /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 5596 6639 UNI2-AS, ES 11492 3835 4806 CABLEONE, US 6327 3167 3360 SHAW, CA 8151 3152 8601 Uninet S.A. de C.V., MX 7155 3115 4027 VIASAT-SP-BACKBONE, US 22773 2967 3938 ASN-CXA-ALL-CCI-22773-RDC, US 39891 2801 3266 ALJAWWALSTC-AS, SA 8551 2562 3097 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2237 2570 MEDIACOM-ENTERPRISE-BUSINESS, US 11830 1917 2494 Instituto Costarricense de Electricidad y Telec Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1890 2:1195 3:128 4:20 5:3563 6:66 7:5 8:1529 9:1 11:164 12:1743 13:364 14:2309 15:75 16:15 17:323 18:107 20:128 21:1 22:188 23:4744 24:2425 25:2 27:2524 29:19 31:2317 32:113 34:16 35:45 36:1561 37:3773 38:2142 39:624 40:159 41:3864 42:939 43:2104 44:253 45:14910 46:3698 47:319 49:1613 50:1784 51:100 52:1278 54:240 55:756 56:7 57:54 58:1708 59:1202 60:919 61:2318 62:2267 63:1969 64:5332 65:2381 66:5020 67:2901 68:1166 69:4062 70:1384 71:681 72:3164 74:2594 75:1488 76:691 77:2002 78:1694 79:2257 80:1873 81:1503 82:1374 83:1132 84:1276 85:2684 86:707 87:1820 88:968 89:3006 90:466 91:7320 92:1770 93:2531 94:3123 95:3518 96:1282 97:345 98:996 99:970 100:94 101:1037 102:1429 103:26087 104:3745 105:434 106:720 107:2275 108:716 109:4018 110:2005 111:3177 112:1981 113:1540 114:1459 115:1911 116:1889 117:2375 118:2345 119:1886 120:1468 121:1064 122:2274 123:2209 124:1591 125:2061 128:1261 129:1261 130:859 131:2032 132:754 133:356 134:1620 135:294 136:742 137:931 138:2314 139:1169 140:732 141:1182 142:1193 143:1294 144:1261 145:329 146:1410 147:1317 148:2196 149:1429 150:812 151:1073 152:1549 153:410 154:2456 155:1328 156:1510 157:1180 158:912 159:2043 160:2316 161:1165 162:3296 163:997 164:1519 165:1393 166:603 167:1771 168:3616 169:686 170:4263 171:770 172:2369 173:2954 174:995 175:1082 176:3153 177:4343 178:2906 179:1931 180:2264 181:2619 182:3205 183:2065 184:2420 185:18239 186:4208 187:3103 188:3293 189:2897 190:8854 191:1419 192:10676 193:8114 194:6613 195:4720 196:2886 197:2393 198:6081 199:6022 200:7411 201:5270 202:10588 203:10109 204:4644 205:3318 206:3527 207:3376 208:4014 209:4691 210:4242 211:2239 212:3688 213:3361 214:1217 215:62 216:6186 217:2518 218:1209 219:707 220:2079 221:981 222:881 223:1884 End of report

1 0

RE: BGP Traffic Engineering - Active\Passive
by tim＠pelican.org 21 May '21

21 May '21

On Friday, 21 May, 2021 16:13, "nanoguser100 via NANOG" <nanog(a)nanog.org> said: > Correct me if I'm wrong here but I *could* take full table + AS 9999 on B meaning > the traffic will prefer 'B' due it it having a more specific route since I'm only > taking default from A (despite local pref). That will correct my egress situation > but how can I fix ingress? For the egress situation, you could also start looking at accepting full table from A and B, but apply a route-map to routes received from B to alter the local-pref based on the AS-PATH. > Is it possible to prepend to JUST one upstream ASN so normal traffic takes ISP A > back except 9999 traffic? to make: > > * ISP-A 1111 174 4444 > * ISP-B 1111 1111 1111 1111 1299 4444 > * ISP-A 1111 1111 1111 1111 1111 1111 174 9999 > * ISP-B 1111 1111 1111 1111 1299 9999 > > If I'm unable to do that will most provider prepend on your behalf so that ISP-A > would add the prepends for 9999 only? This is a conversation you need to have with A and B, or look at their transit documentation, where available. Several of them have communities you can tag your routes with to vary how it is announced, which may include announce/don't, prepend N times, set local-pref within their own network, and on a region / country / exchange / peer basis. If you really need this functionality, that may drive your choices for A and B. Obviously you'd again need route maps to apply to correct communities to your own routes only towards the correct transit provider. Take a look at, for example https://www.gin.ntt.net/support-center/policies-procedures/routing/ - no particular recommendation, just a well-documented example I have to hand. Cheers, Tim.

1 0

Comcast RPKI origin validation
by Tony Tauber 21 May '21

21 May '21

Last week we at Comcast reached some substantial milestones in our RPKI rollout (validation on inter-provider sessions, ROAs for our address-space). Jason Livingood and I collaborated on a blog post, FWIW. https://corporate.comcast.com/stories/improved-bgp-routing-security-adds-an… Please forgive the somewhat less-technical public-facing verbiage. Thanks for all the support of people inside Comcast, particularly Courtney Smith, and also folks in the community on this long journey. (We have lots of address space spread over more than 20 regional networks as well as our Backbone network which made the ROA part a bit complicated. I issued over 9k ROAs or about a quarter of ARINs total.) Cheers, Tony https://rpki.cloudflare.com/?ohlcTa=ARIN&ohlcDate=18723&view=statistics&pre… [image: image.png]

2 1

Re: FCC accelerates STIR/SHAKEN deadlines
by Sean Donelan 20 May '21

20 May '21

On Thu, 20 May 2021, goemon(a)anime.net wrote: >> Shockingly (I'm shocked, shocked to find that gambling is going on in here) >> the commission found a subset of small voice service providers appear to be >> originating a large and increasing quantity of illegal robocalls. > > so they are illegal, then precisely what enforcement is currently being done > by the FCC? The FCC writes sternly worded letters. FCC Demands Two Companies Cease-and-Desist Illegal Robocall Campaigns These Are the Third Tranche of Enforcement Bureau Cease and Desist Letters https://www.fcc.gov/document/fcc-demands-two-companies-cease-and-desist-ill… FCC Issues Robocall Cease-And-Desist Letters to Six Voice Providers https://www.fcc.gov/document/fcc-issues-robocall-cease-and-desist-letters-s…

1 0

FCC accelerates STIR/SHAKEN deadlines
by Sean Donelan 20 May '21

20 May '21

The Federal Communications Commission voted today to accelerate the STIR/SHAKEN deadlines for certain small IP voice service provider networks to no later than June 30, 2022. Large IP VSP networks had a deadline of June 30, 2021. Shockingly (I'm shocked, shocked to find that gambling is going on in here) the commission found a subset of small voice service providers appear to be originating a large and increasing quantity of illegal robocalls. According to the FCC NPRM, a March 2021 report released by Transaction Network Services, a provider of call analytics, found that the problem of robocalls originated by certain smaller voice service providers has gotten worse: by the end of 2020, "[a]lmost 95% of high risk calls originate from non-Tier-1 telephone resources, up 3% from last year."

1 1

Buying IPs with poor reputation
by Ross Tajvar 19 May '21

19 May '21

I'm curious if anyone has experience deliberately buying blacklisted blocks, or blocks that otherwise have poor reputation. Is there a significant price difference? How do you seek them out? Most of the sellers I've found seem to focus on blocks with good reputation, or on improving the reputation of a bad block. But I am interested in purchasing some IPs for internal services where reputation doesn't really matter. Thanks, Ross

3 2

NAT/CGNAT IP address/users ratios
by Scott, Thomas 18 May '21

18 May '21

Hello NANOG (and friends), Asking if anyone would care to share their CGNAT and NAT ratios. We're looking at some best practices and I wanted to see what the community at large has seen working, and not working. I am by no means a NAT expert, and usually I see the other end where it's clearly *not* working. Does anyone have estimating formulas for devices/users to internal blocks to public IPs? Regards, [cid:image001.png@01D74BF4.DDAC29B0]<https://www.intelsat.com/> Thomas Scott Engineer, Network Operations 2875 Fork Creek Church Road, Ellenwood, GA 30294 +1 404-381-2446 | M +1 480-241-7422 www.intelsat.com<http://www.intelsat.com/> [https://www.intelsat.com/wp-content/uploads/2020/12/INTELSAT-Logo-Horiz_4C_…] As the foundational architects of satellite technology, Intelsat operates the largest, most advanced satellite fleet and connectivity infrastructure in the world. We apply our unparalleled expertise and global scale to reliably and seamlessly connect people, devices and networks in even the most challenging and remote locations. Transformation happens when businesses, governments and communities build a ubiquitous connected future through Intelsat's next-generation global network and simplified managed services. At Intelsat, we turn possibilities into reality. Imagine Here, with us, at Intelsat.com. For more information, visit www.intelsat.com<http://www.intelsat.com> and follow us on Facebook<https://www.facebook.com/#%21/pages/Intelsat/106822915740>, Twitter<https://twitter.com/INTELSAT> and LinkedIn<http://www.linkedin.com/company/5071?trk=vsrp_companies_res_name&trkInfo=VS…> This email message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Intelsat S.A. and its subsidiaries.

2 1

Georgia DOL Contact
by Joe Freeman 17 May '21

17 May '21

Is anyone on the list with Georgia Department of Labor? I've got customers having problems logging into their website and need a good contact there to troubleshoot. Routing appears ok as we can get to hosts on that subnet, so I suspect the issue is above layer 3. Thanks- Joe

1 0