Re: mech-v2: static MTU scope; feedback sought

[itojun@itojun.org (Jun-ichiro itojun Hagino)]

> On the other hand, there have been comments on the contrary, that 
> mismatching MTU/MRU is a bad thing, like pointed out by itojun.  I 
> remember the message but have been unable to find the message referred 
> to in:
> 
> http://ops.ietf.org/lists/v6ops/v6ops.2003/msg01718.html

	the operational problem we have experienced was between KAME and
	Juniper.  Juniper (JunOS) sets tunnel MTU to infinity by default, and
	KAME defaults to 1280.  with this setup ICMPv6 "need fragment" was
	not generated (don't remember from which end), and tunnel between
	Juniper and KAME did not work well too.  setting Juniper's MTU to
	1280 solved the problem.

	i'm not sure if Juniper's MTU configuration changes MRU or not.

itojun