Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
Iljitsch van Beijnum <iljitsch@muada.com> Mon, 08 February 2010 20:26 UTC
Return-Path: <iljitsch@muada.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F3CC28C176 for <behave@core3.amsl.com>; Mon, 8 Feb 2010 12:26:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bwwgv0-3TUbT for <behave@core3.amsl.com>; Mon, 8 Feb 2010 12:26:13 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 8DE6328C181 for <behave@ietf.org>; Mon, 8 Feb 2010 12:26:13 -0800 (PST)
Received: from [192.168.2.11] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o18KPoIi032656 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 8 Feb 2010 21:25:52 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <015801caa8e6$9b72fff0$c4f0200a@cisco.com>
Date: Mon, 08 Feb 2010 21:27:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com>
References: <4B6F08CC.2070900@wand.net.nz> <063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com> <4B704153.2020007@it.uc3m.es> <015801caa8e6$9b72fff0$c4f0200a@cisco.com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1077)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 20:26:14 -0000
On 8 feb 2010, at 18:46, Dan Wing wrote: > For stateful translation, it is _possible_ for the translator > to include MTU in its IPv4 and IPv6 tables, and do provide end-to-end > PMTUD even for links below 1280. To do this, a stateful translator > would maintain the MTU for all IPv4 hosts that currently have a mapping, > and go ahead and translate with DF=1. So in this case the translator receives IPv6 packets with or without a fragment header that are 1280 bytes but the IPv4 destination has a path MTU of (say) 576 bytes. This means the translator has to fragment. So essentially this means doing more work (keeping PMTUD state for the IPv4 path) in order to do even more work later (fragment). Not sure how that makes sense... If you simply set DF=0 for packets < 1280 bytes then the people who thought it was a good idea to set an unreasonably small MTU are the ones who get to fragment, which to me seems how it should be. (Although in practice few fragments will happen because in IPv4 PMTUD is only supported for TCP and TCP has the MSS option.) > Then, if an IPv4 ICMP PTB is > received and describes an MTU smaller than 1280, go ahead and translate > that to ICMPv6 (in the hopes of hitting the ~45% of hosts that will > successfully process it), You can always do that, yes.
- [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packe… Iljitsch van Beijnum
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Dan Wing
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… marcelo bagnulo braun
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Dan Wing
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Iljitsch van Beijnum
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Dan Wing
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Iljitsch van Beijnum
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Dan Wing
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Templin, Fred L
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Dan Wing
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Templin, Fred L
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Dan Wing
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Ramji Vaithianathan (rvaithia)
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Iljitsch van Beijnum
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Templin, Fred L
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Templin, Fred L
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Iljitsch van Beijnum
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Dan Wing
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Iljitsch van Beijnum
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Templin, Fred L
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Dan Wing
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Iljitsch van Beijnum
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Iljitsch van Beijnum
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Templin, Fred L
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Dan Wing
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Iljitsch van Beijnum
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Iljitsch van Beijnum
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Templin, Fred L
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Joel Jaeggli
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Iljitsch van Beijnum
- Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte p… Joel Jaeggli