Hi Friends! Everyone loves debating MTU sizes, right?! With the upcoming new MEF3.0 (AI) standard potentially requiring support for higher than 9100 byte payloads, I'm trying to decide on a good new "standard" to configure on internal backbone/IGP links. We're effectively talking about "Super Jumbo Frames", or SJFs, looking to support at least 9400 payloads (to be future proof). With previous hardware generations limiting most of us to 9216, a lot of ISPs chose 9192 as the base Ethernet MTU (= 9178 IP), allowing for simple underlays (e.g. vlan-tunneling IGP connections through L2 switches) if necessary. While it's of course only a requirement to keep a consistent MTU across your own network, there are benefits to using industry standardized value(s), as some of the current generation hardware limits the number of different MTU values you’re able to configure in parallel on the same NP. Looking at my own network, I have a hard limit right now at 9646 bytes (NCS 5700, Jericho2). Potential new MTUs I'm considering: - 9622 (supporting 24 bytes underlay, like we had for 9192) - 9530 (supporting 116 bytes underlay, same as MEF3.0 [9100] has from 9216) With us looking at deploying SRv6, looking at an IPv6 SRH with 4 SIDs: Ethernet (14) [+ VLAN (4)] + IPv6 (40) + SRH (72) = 130 bytes total By chance this is matching the total frame size with a customer payload of 9400. Is 9530 a good value? What would you configure? (Am I simply overthinking this?) BR, // CF