Re: [Last-Call] [EXTERNAL] Re: Last Call: <draft-ietf-6man-mtu-option-12.txt> (IPv6 Minimum Path MTU Hop-by-Hop Option) to Experimental RFC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> On 4 Feb 2022, at 23:11, Tom Herbert <tom@xxxxxxxxxxxxxxx> wrote:
> 
> The obvious concern with this
> approach is that vendors might burn in the protocol into hardware,
> however I believe this problem is adequately mitigated by the various
> programmable hardware techniques (note that while software programmed
> protocols will solve the problem of quickly deploying new L3/L4
> protocols, changing L1/L2 characteristics like larger MTU still
> requires hardware change).

Burnt into hardware that will never support packets larger than 64kB doesn’t sound like a problem to me. 

O. 
-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux