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

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

To: "Fred L. Templin" <ftemplin@iprg.nokia.com>
Subject: Re: Path MTU for draft-ietf-v6ops-mech-v2-00.txt
From: Erik Nordmark <Erik.Nordmark@sun.com>
Date: Sat, 26 Apr 2003 23:33:30 +0200 (CEST)
Cc: Erik Nordmark <Erik.Nordmark@sun.com>, v6ops@ops.ietf.org
In-reply-to: "Your message with ID" <3EA9BBCE.50604@iprg.nokia.com>
Reply-to: Erik Nordmark <Erik.Nordmark@sun.com>

>     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?

  Erik

Follow-Ups:
- Re: Path MTU for draft-ietf-v6ops-mech-v2-00.txt
  - From: itojun@iijlab.net

References:
- Re: Path MTU for draft-ietf-v6ops-mech-v2-00.txt
  - From: "Fred L. Templin" <ftemplin@IPRG.nokia.com>

Prev by Date: Re: Path MTU for draft-ietf-v6ops-mech-v2-00.txt
Next by Date: Re: why do we have two v6ops home pages?
Previous by thread: Re: Path MTU for draft-ietf-v6ops-mech-v2-00.txt
Next by thread: Re: Path MTU for draft-ietf-v6ops-mech-v2-00.txt
Index(es):
- Date
- Thread