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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 09 February 2010 20:47 UTC

Return-Path: <Fred.L.Templin@boeing.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 9A22E3A73F6 for <behave@core3.amsl.com>; Tue, 9 Feb 2010 12:47:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.083
X-Spam-Level:
X-Spam-Status: No, score=-6.083 tagged_above=-999 required=5 tests=[AWL=-0.484, BAYES_00=-2.599, J_BACKHAIR_44=1, RCVD_IN_DNSWL_MED=-4]
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 rWlbmDUx9zwv for <behave@core3.amsl.com>; Tue, 9 Feb 2010 12:47:08 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 8518A3A7328 for <behave@ietf.org>; Tue, 9 Feb 2010 12:47:08 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o19Km6u9011552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 9 Feb 2010 12:48:06 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o19Km5jt023965; Tue, 9 Feb 2010 14:48:05 -0600 (CST)
Received: from XCH-NWHT-05.nw.nos.boeing.com (xch-nwht-05.nw.nos.boeing.com [130.247.25.109]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o19Km5vU023947 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 9 Feb 2010 14:48:05 -0600 (CST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-05.nw.nos.boeing.com ([130.247.25.109]) with mapi; Tue, 9 Feb 2010 12:48:05 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 09 Feb 2010 12:48:03 -0800
Thread-Topic: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
Thread-Index: Acqpxlb55ZCvlBsoTyWWPsAXGCZ1twAAVwlQ
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A64951038309@XCH-NW-01V.nw.nos.boeing.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>
In-Reply-To: <5B264313-3BE0-4C44-9BD3-718FC6F8A9E5@muada.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 20:47:09 -0000

Hi Iljitsch,

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: Tuesday, February 09, 2010 12:26 PM
> To: Templin, Fred L
> Cc: Dan Wing; behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> 
> On 9 feb 2010, at 20:10, Templin, Fred L wrote:
> 
> > Another concern I should have called out earlier is what
> > if the IPv6 host is on a 1500 link and opens a TCP
> > connection to the IPv4 server with MSS=1440. The IPv4
> > server sends a 1480b IPv4 packet that gets translated
> > into a 1500b IPv6 packet. The packet makes its way
> > through the IPv6 network toward the IPv6 host, but
> > first it hits a 1480 MTU link (e.g., and IPv6 over IPv4
> > tunnel). The ICMPv6 PTB gets triggered, then translated
> > into ICMPv4 fragmentation needed, then dropped by
> > a filtering gateway in the IPv4 Internet.
> 
> > Black hole, right?
> 
> 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?

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. Granted
that does not get us on the path to 9KB MTUs, but at
least it works in some fashion through good fortune.

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

> 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. Does that
mean that those ISPs can't deploy translators?

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

Fred
fred.l.templin@boeing.com