May 2025 - NANOG - lists.nanog.org

Re: 202505061814.AYC Re: 202505060938.AYC Re: IPv4 Leases
by Tom Beecher 07 May '25

07 May '25

Abraham- EZIP is a proposal. It could not be used operationally today for a multitude of reasons that those of us who actually do this stuff have tried to point out to you, but you continue to hand wave and ignore. There are lots of people who read this list and may be confused by your writings and think EZIP is a functional solution they could use today. This is, frankly, kinda of a dick move. EZIP is nothing more than the idea you have written down in your draft, and that in 9 years since you first proposed it, nobody has really cared about. ( https://mailarchive.ietf.org/arch/search/?q=%22draft-chen-ati-adaptive-ipv4… ) On Tue, May 6, 2025 at 11:14 PM Abraham Y. Chen <aychen(a)avinta.com> wrote: > Hi, Tom: > > 0) Thank you for your input. > > 1) You are very accurate in reciting the facts and events. However, I > am afraid that your conclusions might be flawed, because you probably > overlooked a couple subtle aspects behind the EzIP proposal: > > A. The primary purpose of the EzIP is to expand the size capacity > of the CG-NAT, nothing more. Besides activating the long-reserved 240/4 to > be used like 100.64/10 which has been proven not too challenging, there is > no other technical hurdle. As you may recall, CG-NAT was deployed over > quarter century ago despite the objections from IETF, anyway. > > B. EzIP will form an "Overlay Network" that can practically be > detached from the current Internet, while the two can work together as long > as the interface between them conforms with the established protocols. > Then, what happens within the EzIP can not be influenced from the outside. > This is nothing new, either. There were precedents in the past, such as the > Internet was deployed over PSTN with the dial-up modem serving as one of > the umbilical cords between the two. The IPv6 was built on top of of the > IPv4. Of course, the former was a big success story, while the latter is > still a WIP. > > C. There are much more than a handful devices that can support the > EzIP operation. Please have a look at Reference group E. on page 17 of the > below whitepaper: > > https://avinta.com/gallery/DeterministicInternet-SPKR.pdf > > D. In addition, IPv4 Unicast Extension Project has been working on > networking devices that support 240/4: > > > https://datatracker.ietf.org/doc/html/draft-schoen-intarea-unicast-240-08 > > Note that the products cited in the last two points are efforts by > many other groups. We just pool them together to be EzIP building blocks. > > Hope the above clears the air. > > Regards, > > > Abe (2025-05-06 23:14 EDT) > > > > On 2025-05-06 12:17, Tom Beecher wrote: > > Suriya- > > Just so it is clear, the technology that Abraham is referencing ( EZIP ) > is ONLY a proposal that has been made. It has not been accepted by any > standards body. It is not implemented or supported by any major router > vendor. It will not work for you. > > > On Tue, May 6, 2025 at 11:41 AM Abraham Y. Chen via NANOG < > nanog(a)lists.nanog.org> wrote: > >> Hi, Suriya: >> >> 0) I am glad that you requested off-list follow-ups, because what I >> am going to share is quite controversial. With a general distribution >> list, a discussion can easily be pulled off the track by personal / >> emotional opinions or business interests, as you might have noticed on >> the NANOG Forum in the past. >> >> 1) I would recommend you to consider replacing 100.64/10 netblock >> with 240/4 netblock for the CG-NAT configuration. This will reduce your >> need for IPv4 addresses by 64 fold, thus mitigating the IPv4 address >> shortage that you are facing. >> >> 2) Although there have been (and still are) various attempts to make >> use of the 240/4 netblock, none has approached it in a universal sense >> as our proposal, called EzIP (phonetic for Easy IPv4). Others are either >> piecemeal solutions for special cases or limited scope applications. >> They will fragment the Internet and lead to chaos. Characterized by >> Vint Cerf as an "Overlay Network", EzIP scheme forms a new layer of >> communication infrastructure that is independent of, yet in arm's-length >> with the current Internet core. So that, EzIP can retain the desired >> properties of the existing Internet, while shaking off the handicaps. >> The former maintains the operation characteristics as CG-NAT to avoid >> perturbing users, while the latter enables the Internet revamping into a >> new era. This far-reaching implication is possible because EzIP resolves >> the most fundamental issue of user identification resources. From such, >> many constraints are either relaxed or simply removed. >> >> 3) For a general introduction, please have a look at the below pair >> of documents. >> >> https://avinta.com/gallery/DeterministicInternetIntro-US.pdf >> >> https://avinta.com/gallery/DeterministicInternet-SPKR.pdf >> >> 4) Since this topic touches many aspects of the Internet and we are >> not an operatorbut just a system analyst, we likely have not covered >> many aspects that hands-on parties like you are familiar with. Please >> browse through our website to see other background information which may >> be relevant, then let us know your concerns. So that we can evaluate >> them for you. >> >> Regards, >> >> >> Abe (2025-05-06 11:40 EDT) >> VP Engineering >> Avinta Communications, Inc. >> Milpitas, CA 95035 USA >> O: +1(408)942-1485x66 >> M: +1(650)248-1829 >> Teams: Abraham.Y.Chen >> eMail: AYChen(a)Avinta.com >> WebSite: www.Avinta.com >> >> >> On 2025-05-06 04:36, Suriya Kamon via NANOG wrote: >> > Hi NANOG, >> > >> > We are running short of IPv4 addresses. >> > >> > We are a small ISP and longer prefixes are okay with us (even /24s). >> > >> > Please contact me off-list. >> > >> > (Proper ROA coverage is a must). >> > >> > Thanks. >> > >> > Best Regards, >> > Suriya >> > _______________________________________________ >> > NANOG mailing list >> > >> https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/3MYN3WE… >> >> >> >> -- >> This email has been checked for viruses by Avast antivirus software. >> www.avast.com >> _______________________________________________ >> NANOG mailing list >> >> https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/LTKZLWU… > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > Virus-free.www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_4161442180352669907_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >

1 0

IPv4 Leases
by Suriya Kamon 06 May '25

06 May '25

Hi NANOG, We are running short of IPv4 addresses. We are a small ISP and longer prefixes are okay with us (even /24s). Please contact me off-list. (Proper ROA coverage is a must). Thanks. Best Regards, Suriya

8 9

Re: outages list badly broken, flooding messages
by Josh Luthman 05 May '25

05 May '25

What's being migrated if not the subscription database? On Mon, May 5, 2025, 1:16 AM virendra rode <virendra.rode(a)gmail.com> wrote: > It is a new instance. I’m referring to the migration task from PUCK to PCH > in order to minimize the pain > > — > regards, > /vrode > > On May 4, 2025, at 17:10, Josh Luthman <josh(a)imaginenetworksllc.com> > wrote: > > > If it requires everyone to resubscribe why don't we just start up a whole > new instance? > > On Sun, May 4, 2025, 8:01 PM virendra rode via NANOG < > nanog(a)lists.nanog.org> wrote: > >> Testing is currently in progress, and as the newly implemented >> mailman3, I'm adapting to the system and retrieving data from the >> archives in preparation for go live on PCH infra. It's important to >> note that we may require the community to re-subscribe, we are still >> trying to determine that. >> >> More updates will be provided soon. >> >> >> /vrode >> >> >> On Sat, 2025-05-03 at 23:18 -0500, Andy Ringsmuth via NANOG wrote: >> > >> > >> > > On Apr 27, 2025, at 5:48 PM, Jared Mauch via NANOG >> > > <nanog(a)lists.nanog.org> wrote: >> > > >> > > On Sun, Apr 27, 2025 at 02:03:23PM -0500, Mike Hammett via NANOG >> > > wrote: >> > > > Meaning fixing Puck or the divorce of Outages from Puck? >> > > >> > > >> > > I'm working on fixing puck, there's a long backstory of what >> > > transpired here which resulted in having to revert to a backup from >> > > 2023 >> > > due to some issues related to a series of events that made it far >> > > easier >> > > to just revert to a backup than attempt to restore the stuation. >> > > >> > > Most things should be back now but the state of mailman in the >> > > modern universe is an ongoing problem. It depended on python2 and >> > > was >> > > never updated to support python3. >> > > >> > > Migrating to mailman3 is also a very large task, so in the midst >> > > of all the restoration efforts that had to be undertaken this was a >> > > lower priority item. >> > > >> > > It's extremely hard when you are carrying around nearly 30 years >> > > of legacy as well. >> > > >> > > Either way I expect it all to be resolved in the next ~24 hours >> > > or less one way or another. >> > > >> > > - Jared >> > > _______________________________________________ >> > >> > How goes the transition? Any help/resources/etc. needed? Or are >> > things all sorted out and working? >> > >> > >> > -Andy >> > _______________________________________________ >> > NANOG mailing list >> > >> https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/6I7B4KU… >> >> _______________________________________________ >> NANOG mailing list >> >> https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/F2COSML… > >

1 0

twitch contact?
by Bryan Holloway 03 May '25

03 May '25

If anyone from Twitch is lurking, could you please reach out to me off-list to resolve a long-standing peering issue? Thank you!

1 1

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 02 May '25

02 May '25

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 UKNOF, 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 03 May, 2025 IPv4 BGP Table (Global) as seen at Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 981456 Prefixes after maximum aggregation (per Origin AS): 377916 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 478912 Number of IPv4 prefixes with a valid ROA: 538157 Number of IPv4 prefixes with an invalid ROA: 1337 Number of IPv4 prefixes with no ROA: 441962 Total ASes present in the Internet Routing Table: 76883 Prefixes per ASN: 12.77 Origin-only ASes present in the Internet Routing Table: 65809 Origin ASes announcing only one prefix: 26961 Transit ASes present in the Internet Routing Table: 11074 Transit-only ASes present in the Internet Routing Table: 548 Average AS path length visible in the Internet Routing Table: 5.2 Max AS path length visible: 80 Max AS path prepend of ASN ( 37447) 75 Prefixes from unregistered ASNs in the Routing Table: 1051 Number of instances of unregistered ASNs: 1052 Number of 32-bit ASNs allocated by the RIRs: 46319 Number of 32-bit ASNs visible in the Routing Table: 38221 Prefixes from 32-bit ASNs in the Routing Table: 201679 Number of bogon 32-bit ASNs visible in the Routing Table: 24 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 471 Number of addresses announced to Internet: 3106221952 Equivalent to 185 /8s, 37 /16s and 47 /24s Percentage of available address space announced: 83.9 Percentage of allocated address space announced: 83.9 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: 321660 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 258056 Total APNIC prefixes after maximum aggregation: 77598 APNIC Deaggregation factor: 3.33 Prefixes being announced from the APNIC address blocks: 249144 Unique aggregates announced from the APNIC address blocks: 103259 APNIC Region origin ASes present in the Internet Routing Table: 14647 APNIC Prefixes per ASN: 17.01 APNIC Region origin ASes announcing only one prefix: 4464 APNIC Region transit ASes present in the Internet Routing Table: 1968 Average APNIC Region AS path length visible: 5.5 Max APNIC Region AS path length visible: 36 Number of APNIC region 32-bit ASNs visible in the Routing Table: 10129 Number of APNIC addresses announced to Internet: 749165568 Equivalent to 44 /8s, 167 /16s and 92 /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-155961 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: 289434 Total ARIN prefixes after maximum aggregation: 129789 ARIN Deaggregation factor: 2.23 Prefixes being announced from the ARIN address blocks: 290554 Unique aggregates announced from the ARIN address blocks: 138449 ARIN Region origin ASes present in the Internet Routing Table: 19254 ARIN Prefixes per ASN: 15.09 ARIN Region origin ASes announcing only one prefix: 7036 ARIN Region transit ASes present in the Internet Routing Table: 2005 Average ARIN Region AS path length visible: 4.6 Max ARIN Region AS path length visible: 35 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5207 Number of ARIN addresses announced to Internet: 1348693504 Equivalent to 80 /8s, 99 /16s and 110 /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-402332 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, 54/8, 55/8, 56/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: 273788 Total RIPE prefixes after maximum aggregation: 133740 RIPE Deaggregation factor: 2.05 Prefixes being announced from the RIPE address blocks: 271576 Unique aggregates announced from the RIPE address blocks: 174096 RIPE Region origin ASes present in the Internet Routing Table: 28918 RIPE Prefixes per ASN: 9.39 RIPE Region origin ASes announcing only one prefix: 12063 RIPE Region transit ASes present in the Internet Routing Table: 4009 Average RIPE Region AS path length visible: 5.3 Max RIPE Region AS path length visible: 44 Number of RIPE region 32-bit ASNs visible in the Routing Table: 12423 Number of RIPE addresses announced to Internet: 731379584 Equivalent to 43 /8s, 151 /16s and 247 /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-216475 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 53/8, 57/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: 123801 Total LACNIC prefixes after maximum aggregation: 29390 LACNIC Deaggregation factor: 4.21 Prefixes being announced from the LACNIC address blocks: 120355 Unique aggregates announced from the LACNIC address blocks: 48749 LACNIC Region origin ASes present in the Internet Routing Table: 11242 LACNIC Prefixes per ASN: 10.71 LACNIC Region origin ASes announcing only one prefix: 2703 LACNIC Region transit ASes present in the Internet Routing Table: 2506 Average LACNIC Region AS path length visible: 5.9 Max LACNIC Region AS path length visible: 56 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9189 Number of LACNIC addresses announced to Internet: 171770368 Equivalent to 10 /8s, 61 /16s and 2 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-274844 + 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: 35326 Total AfriNIC prefixes after maximum aggregation: 6781 AfriNIC Deaggregation factor: 5.21 Prefixes being announced from the AfriNIC address blocks: 49356 Unique aggregates announced from the AfriNIC address blocks: 13967 AfriNIC Region origin ASes present in the Internet Routing Table: 1910 AfriNIC Prefixes per ASN: 25.84 AfriNIC Region origin ASes announcing only one prefix: 695 AfriNIC Region transit ASes present in the Internet Routing Table: 377 Average AfriNIC Region AS path length visible: 6.1 Max AfriNIC Region AS path length visible: 80 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1273 Number of AfriNIC addresses announced to Internet: 104988928 Equivalent to 6 /8s, 66 /16s and 1 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & 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 9808 10460 8755 98 CHINAMOBILE-CN China Mobile Communication 7545 6215 843 655 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4769 4192 76 ERX-CERNET-BKB China Education and Resear 9498 4333 531 281 BBIL-AP BHARTI Airtel Ltd., IN 7552 3918 1332 26 VIETEL-AS-AP Viettel Group, VN 7713 3678 1044 66 TELKOMNET-AS-AP PT Telekomunikasi Indones 45899 3283 1869 102 VNPT-AS-VN VNPT Corp, VN 24560 2863 851 537 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 4766 2412 11525 646 KIXS-AS-KR Korea Telecom, KR 45090 2208 1439 86 TENCENT-NET-AP Shenzhen Tencent Computer 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 13232 39694 4324 AMAZON-02, US 11492 4711 312 591 CABLEONE, US 7155 3859 286 85 VIASAT-SP-BACKBONE, US 6327 3622 1320 81 SHAW, CA 174 3555 8753 908 COGENT-174, US 22773 3379 3033 176 ASN-CXA-ALL-CCI-22773-RDC, US 749 3254 54863 2505 DNIC-AS-00749, US 16625 3003 1257 2215 AKAMAI-AS, US 396982 2955 3657 469 GOOGLE-CLOUD-PLATFORM, US 36352 2773 227 851 AS-COLOCROSSING, 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 7720 1714 148 UNI2-AS, ES 39891 4797 293 62 ALJAWWALSTC-AS, SA 20940 3960 3395 127 AKAMAI-ASN1, NL 9009 3783 327 1968 M247, RO 12389 3077 2303 887 ROSTELECOM-AS PJSC Rostelecom. Technical 34984 2362 360 584 TELLCOM-AS, TR 212238 2113 150 1556 CDNEXT, GB 8452 1646 1852 14 TE-AS TE-AS, EG 13188 1606 100 34 TRIOLAN, UA 8551 1432 366 33 BEZEQ-INTERNATIONAL-AS Bezeqint Internet 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 12028 3243 585 UNINET, MX 10620 3521 485 995 Telmex Colombia S.A., CO 13999 2514 540 362 Mega Cable, S.A. de C.V., MX 11830 1994 369 64 Instituto Costarricense de Electricidad y 28573 1359 2438 262 Claro NXT Telecomunicacoes Ltda, BR 3816 1332 784 205 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 11664 1198 278 33 Techtel LMDS Comunicaciones Interactivas 6147 1189 371 22 Telefonica del Peru S.A.A., PE 22884 1057 67 375 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 6503 1043 374 163 Axtel, S.A.B. de C.V., MX 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 1744 631 30 RAYA-AS, EG 24863 1651 389 16 LINKdotNET-AS, EG 29571 1594 102 22 ORANGE-COTE-IVOIRE, CI 36992 1431 1518 283 ETISALAT-MISR, EG 36903 1249 554 96 MT-MPLS, MA 36935 1020 521 42 Vodafone-, EG 20011 980 185 285 INTERNET-SOLUTIONS, ZA 37069 932 1099 15 MOBINIL, EG 36914 550 82 3 KENET-AS, KE 15399 532 57 59 WANANCHI-, KE 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 16509 13232 39694 4324 AMAZON-02, US 8151 12028 3243 585 UNINET, MX 9808 10460 8755 98 CHINAMOBILE-CN China Mobile Communication 12479 7720 1714 148 UNI2-AS, ES 7545 6215 843 655 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4797 293 62 ALJAWWALSTC-AS, SA 4538 4769 4192 76 ERX-CERNET-BKB China Education and Resear 11492 4711 312 591 CABLEONE, US 9498 4333 531 281 BBIL-AP BHARTI Airtel Ltd., IN 20940 3960 3395 127 AKAMAI-ASN1, NL Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 8151 12028 11443 UNINET, MX 9808 10460 10362 CHINAMOBILE-CN China Mobile Communications Grou 12479 7720 7572 UNI2-AS, ES 7545 6215 5560 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4797 4735 ALJAWWALSTC-AS, SA 4538 4769 4693 ERX-CERNET-BKB China Education and Research Net 11492 4711 4120 CABLEONE, US 9498 4333 4052 BBIL-AP BHARTI Airtel Ltd., IN 7552 3918 3892 VIETEL-AS-AP Viettel Group, VN 20940 3960 3833 AKAMAI-ASN1, NL 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 22542 UNALLOCATED 8.7.205.0/24 3356 LEVEL3, US 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-D 46639 UNALLOCATED 8.17.66.0/24 701 UUNET, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 393266 UNALLOCATED 8.23.52.0/24 46887 CROWNCASTLE-AS46887, US 396894 UNALLOCATED 8.28.201.0/24 46887 CROWNCASTLE-AS46887, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 3356 LEVEL3, US 46639 UNALLOCATED 8.38.73.0/24 3356 LEVEL3, US 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 14.192.20.0/22 Origin: 26658 HENGTONG-IDC-LLC, US 14.192.20.0/22 Transit: 6939 HURRICANE, US 23.140.216.0/24 Origin: 27176 DATAWAGON, US 23.140.216.0/24 Transit: 20278 NEXEON, US 23.141.0.0/24 Origin: 395350 RESERVED, ZZ 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.152.48.0/24 Origin: 46167 RESERVED, ZZ 23.152.48.0/24 Transit: 7018 ATT-INTERNET4, US 23.155.208.0/24 Origin: 396169 AS-GHCIL-01, US 23.155.208.0/24 Transit: 35985 ONERINGNET-ATL-1, US 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:16 /10:41 /11:93 /12:300 /13:581 /14:1212 /15:2142 /16:13938 /17:8336 /18:13806 /19:24798 /20:44461 /21:52115 /22:112317 /23:101658 /24:604827 /25:799 /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 6642 7720 UNI2-AS, ES 8151 6231 12028 UNINET, MX 11492 3531 4711 CABLEONE, US 39891 3489 4797 ALJAWWALSTC-AS, SA 6327 3417 3622 SHAW, CA 7155 2818 3859 VIASAT-SP-BACKBONE, US 22773 2523 3379 ASN-CXA-ALL-CCI-22773-RDC, US 16509 2342 13232 AMAZON-02, US 30036 2230 2570 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2187 3521 Telmex Colombia S.A., CO Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1707 2:1506 3:654 4:9 5:4641 6:162 7:6 8:1559 9:1 11:172 12:1365 13:367 14:2553 15:352 16:282 17:369 18:916 20:514 21:4 22:188 23:7486 24:2751 25:2 27:2699 29:19 31:3230 32:39 33:1 34:80 35:204 36:2502 37:4690 38:9048 39:907 40:167 41:4180 42:946 43:2553 44:377 45:18582 46:5031 47:295 49:1930 50:1892 51:591 52:1548 54:301 55:1087 56:11 57:255 58:2129 59:1359 60:1169 61:2784 62:2941 63:1824 64:5455 65:2171 66:4636 67:3057 68:1137 69:3833 70:1091 71:619 72:2857 74:2778 75:1607 76:618 77:2729 78:1877 79:1761 80:2215 81:2043 82:3199 83:1440 84:1852 85:3414 86:1049 87:2402 88:1286 89:4336 90:782 91:8335 92:2722 93:2893 94:4090 95:4336 96:1416 97:312 98:995 99:669 100:72 101:1174 102:3878 103:32203 104:4815 105:749 106:1045 107:2620 108:1212 109:4082 110:2238 111:3350 112:2053 113:1533 114:1969 115:2145 116:2044 117:2737 118:2362 119:1922 120:1907 121:1425 122:2762 123:2171 124:1622 125:2877 126:91 128:1585 129:960 130:1292 131:1928 132:782 133:451 134:1537 135:331 136:1297 137:1158 138:2886 139:1610 140:1585 141:1495 142:1910 143:1677 144:1096 145:502 146:2162 147:2097 148:2679 149:2879 150:1254 151:1817 152:2103 153:497 154:8314 155:1661 156:3486 157:1885 158:1293 159:2442 160:3566 161:1902 162:3740 163:2101 164:1702 165:2200 166:1468 167:1875 168:4034 169:787 170:5074 171:1008 172:4411 173:3255 174:909 175:1295 176:3666 177:4701 178:3687 179:2270 180:2605 181:4060 182:3389 183:1822 184:2094 185:21540 186:5086 187:4453 188:4212 189:4219 190:9509 191:1485 192:11238 193:9465 194:7768 195:5520 196:3290 197:3683 198:6225 199:8492 200:8196 201:6323 202:10587 203:10553 204:4543 205:3610 206:4620 207:3559 208:4241 209:5210 210:4834 211:2639 212:4539 213:3700 214:1032 215:48 216:6689 217:3141 218:1384 219:539 220:2090 221:1056 222:855 223:2375 End of report

1 0

[NANOG] OAM and multiple choice questions
by David Zimmerman 01 May '25

01 May '25

Hi, all. A few months ago, I got really good guidance here to pursue OAM instead of trying to use BFD in unnatural ways. I've been reaching out to my vendors and through various searches, since the OAM space is wholly foreign to me, and I'm currently on four different paths: * IEEE 802.1ag<https://www.ieee802.org/1/pages/802.1ag.html> now part of IEEE 802.1Q-2022 CFM * IEEE 802.3ah<https://www.ieee802.org/21/doctree/2006_Meeting_Docs/2006-11_meeting_docs/8…> Ethernet OAM (aka Link OAM) * ITU-T Y.1731<https://www.itu.int/rec/T-REC-Y.1731> OAM functions and mechanisms for Ethernet based networks * MEF 17<https://www.mef.net/resources/mef-17-service-oam-framework-and-requirements/> Service OAM Framework and Requirements One of my vendors pointed out to me that recent search guidance is probably a bit hard to find because this is mostly service provider space (not the enterprise space I live in), and they generally have solved for this in the past and moved on. So I feel like these are four hills I'm simultaneously trying to climb instead of knowing one or two better ones and focusing on those. I'm curious for the folks here that have in fact solved for OAM on your networks — particularly in an MX480/MX304 Junos environment (I also have a bunch of Cat 8K/9K IOS-XE and some NCS5500 IOS-XR, but let's focus on Junos) — which standard you went with. If you can also speak to why you chose that path, that would help a lot. Extra bonus points if you have some configuration that you can share (privately if you wish) that helps my decision process for craft/complexity. -dp

4 6

Connect with Peering Community at our Next Conference + More!
by Nanog News 01 May '25

01 May '25

*** Connect with Peering Community at our Next Conference* ------------------------------------------------------------ *Register Now for the N94 Peering Forum* Applications will remain open until 20 applications are received or May 19, whichever is first. LEARN MORE (https://nanog.org/events/nanog-94/peering/) *** Take Advantage of our Upcoming IPv6 Clinic!* ------------------------------------------------------------ *Join Us for NANOG 94 in Denver (June 9-11)* We’re excited about the return of the IPv6 Clinic at NANOG 94, featuring AWS experts who will lead technical presentations, a hands-on workshop, and an interactive whiteboarding session. Registration is required, but free for those who are registered for NANOG 94. REGISTER NOW (https://nanog.org/events/n94-ipv6-clinic/) *** Sponsorships Still Available for N94!* ------------------------------------------------------------ *Invest in the Community We Have Built* Sponsorships are still available for Network Lounge, NANOG Showcase, + Beer N' Gear! Contact Shawn Winstead—swinstead(a)nanog.org for more info. *** Stay Connected* ------------------------------------------------------------ http://www.facebook.com http://www.instagram.com/nanog_org/ http://www.linkedin.com/company/nanog/ https://www.twitter.com/nanog/ http://nanog.org

1 0