Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets

Iljitsch van Beijnum <iljitsch@muada.com> Tue, 09 February 2010 22:54 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 C8F0828C168 for <behave@core3.amsl.com>; Tue, 9 Feb 2010 14:54:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, J_BACKHAIR_44=1]
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 EFtuEyo4ZBP9 for <behave@core3.amsl.com>; Tue, 9 Feb 2010 14:54:46 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 9AC533A7636 for <behave@ietf.org>; Tue, 9 Feb 2010 14:54:45 -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 o19MsOU5042209 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Feb 2010 23:54:25 +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: <E1829B60731D1740BB7A0626B4FAF0A64951038309@XCH-NW-01V.nw.nos.boeing.com>
Date: Tue, 09 Feb 2010 23:55:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <27AF6467-B1E0-4FB1-AE8D-DB9529AB4B89@muada.com>
References: <4B6F08CC.2070900@wand.net.nz> <063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007 @ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7 F 0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boei n g.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com> <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com> <E1829B60731D1740BB7A0626B4FAF0A6495103824D@XCH-NW-01V.nw.nos.boeing.com> <D6D71E40-644D-4D1C-B535-A31AAD0C7589@muada.com> <E1829B60731D1740BB7A0626B4FAF0A6495103828D@XCH-NW-01V.nw.nos.boeing.com> ! <5B264313-3BE0-4C44-9BD3-718FC6F8A9E5@muada.com> <E1829B60731D1740BB7A0626B4FAF0A64951038309@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1077)
Cc: "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
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: Tue, 09 Feb 2010 22:54:46 -0000

On 9 feb 2010, at 21:48, Templin, Fred L wrote:

>> Indeed. Note however that the same black hole would exist if both ends are IPv6 or both ends are IPv4 and there is no translator.

> Eh? For IPv6<->IPv6, we have been assured that PMTUD
> is fixed. Is that not the case?

Fixed how? I know Microsoft has PMTUD blackhole detection and maybe others as well, but that has nothing to do with IPv6. I've had my share of black holes with IPv6, although not recently.

> Also, for IPv4-to-IPv4 we have the convenient fact that
> links with MTU<1500 are rare in the Internet core so
> tripping over a low MTU link is a rare event.

PPP over ethernet is pretty common with ADSL and reduces a user's MTU below 1500, usually without the hosts knowing it. This is solved with adjusting (clamping) the value in the MSS option.

> Granted that does not get us on the path to 9KB MTUs,

Like I said before, you can do this without trouble. I didn't even mention the MSS, which will save you if there's a network in the middle that doesn't generate too bigs correctly.

>> I don't think we can reasonably expect NAT64s to fix all possible black
>> holes.

> It's not a matter of fixing all black holes; it is
> rather an analysis of what new sorts of black holes
> are made possible when translators are used.

Right. But your example wasn't very particular to the translation case.

>> In practice, I think NAT64 users would have to avoid reduced MTUs between the translator and the IPv6
>> hosts (and I would assume that a deployment that needs NAT64 is far enough along that it doesn't need
>> IPv6-in-IP tunneling)

> AFAICT, it may still be some time before ISP networks can
> enable ubiquitous native IPv6. For those that can't there
> is IPv6-in-IPv4 tunneling for the near term.

What kind of tunneling do you foresee? Obviously not 6to4. Other types of tunneling are more complex, native IPv6 makes life much simpler.

> Does that mean that those ISPs can't deploy translators?

No:

>> or artificially lower the IPv6 host MTU or the translator MTU / rewrite the MSS
>> if a reduced MTU is present between the translator and the IPv6 hosts.

> Artificially lowering the IPv6 host MTU may be unsatisfactory
> if the host is connected to a network where it could otherwise
> be using larger packet sizes. And, MSS clamping only works
> for TCP.

If you have a better solution I'm all ears.