- Test - lists.nanog.org

Using RFC1918 on Global table as Loopbacks
by Javier Gutierrez 06 Oct '23

06 Oct '23

Hi, I have recently encountered some operational differences at my new organization that are not what I have been exposed to before, where the loopback of the core network devices is being set from RFC1918 while on the global routing table. I'm sure this is not a major issue but I have mostly seen that ISPs use global IPs for loopbacks on devices that would and hold global routing. My question is, what is the most used or recommended way to do this, if I continue to use RFC1918 I will save some very much desired public address space, but would this come back to bite me in the future? Kind regards, Javier Gutierrez,

7 6

APRICOT 2024: Call for Programme Committee Volunteers
by Mark Tinka 06 Oct '23

06 Oct '23

Hi everyone. The APRICOT 2024 Organising Committee would like to welcome everyone to join us in Bangkok, Thailand, from 21st February to 1st March 2024. The APRICOT 2024 Programme Committee is responsible for the solicitation and selection of suitable presentation and tutorial content for the APRICOT 2024 conference (https://2024.apricot.net/) We are now seeking nominations from the community to join the APRICOT 2024 PC to assist with the development of the programme for APRICOT 2024. Eligible PC candidates must have attended recent APRICOT events, have broad technical knowledge of Internet operations, and have good familiarity with the format of APRICOT. Having constructive opinions and ideas about how the programme content might be improved is of high value too. PC members are expected to work actively to solicit content and review submissions for technical merit. The PC meets by conference call, weekly in frequency during the three months prior to APRICOT. If you are interested in joining the PC and meet the above eligibility criteria, please send a brief note to "pc-chairs at apricot.net". The note must include affiliation (if any) and a brief description about why you would make a good addition to the PC. The PC Chairs will accept nominations received by 17:00 UTC+8 on Friday 20th October 2023, and will announce the new PC shortly thereafter. Many thanks! Mark Tinka & Mark Duffell For the APRICOT 2024 Organising Committee --

1 0

Re: maximum ipv4 bgp prefix length of /24 ?
by Mark Tinka 06 Oct '23

06 Oct '23

On 10/5/23 08:24, Geoff Huston wrote: > The IPv6 FIB is under the same pressure from more specifics. Its taken > 20 years to get there, but the IPv6 FIB is now looking stable at 60% > opf the total FIB size [2]. For me, thats a very surprising outcome in > an essentially unmanaged system. Were you expecting it to be lower than IPv4? Mark.

3 2

Re: maximum ipv4 bgp prefix length of /24 ?
by Jakob Heitz (jheitz) 05 Oct '23

05 Oct '23

Each unit of mask length increase doubles the size of the table theoretically. About 60% of the table is /24 routes. Just going to /25 will probably double the table size. Not sure I'd like to extrapolate the estimate out to /27. Kind Regards, Jakob ----------------------------------------------------------------------------- Date: Fri, 29 Sep 2023 00:25:55 +0300 From: VOLKAN SAL?H <volkan.salih.06(a)gmail.com> To: nanog(a)nanog.org hello, I believe, ISPs should also allow ipv4 prefixes with length between /25-/27 instead of limiting maximum length to /24.. I also believe that RIRs and LIRs should allocate /27s which has 32 IPv4 address. considering IPv4 world is now mostly NAT'ed, 32 IPv4s are sufficient for most of the small and medium sized organizations and also home office workers like youtubers, and professional gamers and webmasters! It is because BGP research and experiment networks can not get /24 due to high IPv4 prices, but they have to get an IPv4 prefix to learn BGP in IPv4 world. What do you think about this? What could be done here? Is it unacceptable; considering most big networks that do full-table-routing also use multi-core routers with lots of RAM? those would probably handle /27s and while small networks mostly use default routing, it should be reasonable to allow /25-/27? Thanks for reading, regards..

9 14

Autoresponders gone wild - edg.io (or Meta), make it stop
by Jon Lewis 05 Oct '23

05 Oct '23

I'm on my last full day at StackPath, and a couple of autoresponders are making my work email even less usable than usual. It would seem G-Core Labs S.A. (ASN 199524) sent a peering request cc'd to every address they could find relevant to @INEX LAN1 Dublin, and the various autoresponders have been duking it out since about 5:49am Eastern. The only one still emailing everyone several times/minute is support(a)edg.io. If anyone knows someone at edg.io who can make this stop, please suggest they do so asap. It would appear noc(a)meta.com is also involved, but at least Meta's autoresponder has the good sense/programming to not spam the entire recipient list...but it likely playing ping pong with support(a)edg.io. Date: Thu, 5 Oct 2023 11:41:41 -0700 (PDT) From: Edgio Support <support(a)edg.io> Reply-To: support(a)edg.io To: [long list removed] Message-ID: <10724763.48851.1696531301960(a)app137049.phx101.service-now.com> Subject: Incident INC1751177 -- You are on the watchlist for ticket PTKT3218420 -- comments added ... Comments: 2023-10-05 11:45:29 PDT - Guest (Additional comments (client notes)) Reply from: noc(a)meta.com ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route StackPath, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________

1 0

N89 Keynote + Taste the Best of San Diego Without Ever Leaving Conference + More
by Nanog News 05 Oct '23

05 Oct '23

* Introducing N89 Keynote Speakers! * * Don't Miss Out — Sync Your Calendars Now * * Monday Keynote:* The Expanding Landscape of Internet Governance: Why Network Operators Need a Global View w/ President and CEO of ARIN, John Curran. * Tuesday Keynote:* Fireside Chat with COO of Arista Networks, Anshul Sadana + NANOG Producer Elizabeth Drolet. Get to know the man behind the tech and learn more about how to stay successful in today's rapidly changing environment. <https://nanog.org/events/nanog-89/> * LEARN MORE <https://nanog.org/events/nanog-89/>* * Taste the Best of San Diego Without Ever Leaving Conference* * N89 Venue Offers Activities + Award-Winning Dining On-Site* Surrounded by the remarkable San Diego skyline and secluded by the breathtaking bay waters, Loews Coronado Bay Resort is known as a “private oasis.” It is additionally a hot spot for endless activities and award-winning local dining. There is something for everyone, from sailboat excursions, gondola rides, bike paths, scenic beach strolls to an ocean-inspired spa. * READ MORE <https://nanog.org/stories/articles/n89-attendees-taste-the-best-of-san-dieg…>* *Coming to the NANOG 89 Stage* *View Full Agenda Now* + The Return of NANOG Jeopardy! w/ Charles Rumford + The History and Future of Ethernet - 50th Anniversary w/ Mikaell Holmberg + Pushing Nx400G Further w/ Filipe Correia + Bringing True Load Balancing to Your On-Premises Kubernetes Cluster w/ Mauricio Rojas + DScope: A Cloud-Native Internet Telescope w/ Eric Pauley + Much, Much, More! *VIEW AGENDA* <https://nanog.org/events/nanog-89/nanog-89-agenda/> *NANOG 89 Meeting Floor Plans* *On-Site Map for Various Locations at Conference* Did you know that meeting floor plans for the NANOG 89 conference venue are available? Map out your speaker + networking schedule today. Go to the NANOG 89 Agenda page and scroll to the bottom to enlarge any floor plan. *VIEW NOW <https://nanog.org/events/nanog-89/nanog-89-agenda/>Still Time to Register Virtually!* *Can't Make it San Diego? Join Us virtually!* Stream live presentations, participate in real-time chat forums, enjoy 360 views of General Session + more. *REGISTER NOW <https://nanog.org/events/nanog-89/>*

1 0

Re: maximum ipv4 bgp prefix length of /24 ?
by Mark Tinka 05 Oct '23

05 Oct '23

On 10/5/23 08:32, Geoff Huston wrote: > Not really. > > The stability of number in IPv4 as compared to the monotonic rise in IPv6 is what I find to be curious. I think the fact that RIR's allocate very large IPv6 address space to their members may well be what is driving this. Historically, network operators do enjoy de-aggregating address space. One can get significantly more /48's out of a /32 (or shorter) than they would /24's out of any IPv4 allocation they acquired. One way to control this escalation is to shorten the maximum prefix length that all operators are willing to accept into the DFZ. The other way would be to get RIR's to lengthen the minimum allocation they can make to their members. Neither of these solutions is likely to be popular, but nor is having to pay large sums of money for more FIB. Mark.

1 0

cogent spamming directly from ARIN records?
by Mel Beckman 04 Oct '23

04 Oct '23

This morning I received an email from someone at Cogent asking about an ASN I administer. They didn’t give any details, but I assumed it might be related to some kind of network transport issue. I replied cordially, asking them what they needed. The person then replied with a blatant spam, advertising Cogent IP services, in violation of the U.S. CAN-SPAM Act’s prohibition against deceptive UCE. I believe they got the contact information from ARIN, because the ARIN technical POC is the only place where my name and the ASN are connected. I believe this is a violation of Cogent’s contract with ARIN. Does anybody know how I can effectively report this to ARIN? If we can’t even police infrastructure providers for spamming, LIOAWKI. -mel beckman

20 33

ARIN Election
by Nicholas Warren 04 Oct '23

04 Oct '23

Does anyone know how many people will be elected from each category? I don't regularly keep up with everyone's business. So, are any of candidates overachievers or, well, underachievers? Nich Warren

2 1

Re: maximum ipv4 bgp prefix length of /24 ?
by Jakob Heitz (jheitz) 03 Oct '23

03 Oct '23

Among the issues: Suppose the FIB has all the /24 components to make a /20, so it programs a /20. Then one of the /24's changes nexthop. It now has to undo all that compression by reinstalling some of the routes and figuring out the minimum set of /21, /22, /23, /24 to make it happen. Then to avoid a transient, it needs to make before break. Quite a bit of FIB programming needs to happen just to modify a single /24. Then the next /24 in the set also modifies its nexthop. and so on for 100000 routes. All because a peer link flapped. Affecting convergence. Then you need to buy a line card that can hold all the individual routes, because you can't always compress, because not all the routes in your compressed set have the same nexthop during a transient. Finally, it's all nicely compressed. Now what? You have lots of empty slots in your FIB. I'm sure lots of nerds can come up with transient reduction algorithms, but I'd rather not. Kind Regards, Jakob --------------------------------------------------------------- Date: Sat, 30 Sep 2023 20:04:29 -0700 From: Owen DeLong <owen(a)delong.com> Not sure why you think FIB compression is a risk or will be a mess. It?s a pretty straightforward task. Owen

13 24