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

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



I agree with Itojun

According to the text, this is configurable value with a default
of 1280.  This makes it no different then any other IPv6 link.

That is simplest case and lets keep it this way.

-vlad

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




--
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Vladislav Yasevich		Tru64 UNIX Network Group
Hewlett Packard 		Tel: (603) 884-1079
Nashua, NH 03062		ZKO3-3/T07