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

Re: Path MTU for draft-ietf-v6ops-mech-v2-00.txt

I fail to see your point; how is 1280 "simpler" than 1380? It's
just a static MTU assignment in either case. You will need to
define "simplicity" for your arguement to even make sense.

Fred
ftemplin@iprg.nokia.com

itojun@iijlab.net wrote:

   To maximize efficiency and minimize IPv4 fragmentation for the
   predominant deployment case, the ISATAP interface MTU, or "LinkMTU"
   (see: [RFC2461], Section 6.3.2), SHOULD be set to no more than 1380
   bytes (1400 minus 20 bytes for IPv4 encapsulation)."
Can we have something similar for mech-v2?

I don't personally have a problem with raising the tunnel MTU in mech-v2



from 1280 to 1380.





What do others in the WG think?




	keep it to 1280.  it is the simplest value.  the most important point
	in non-dynamic tunnel mode is simplicity.

itojun