RE: PMTUD and MTU < 1280
"Dan Wing" <dwing@cisco.com> Mon, 25 July 2011 18:50 UTC
Return-Path: <dwing@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 349CC21F8BA6 for <ipv6@ietfa.amsl.com>; Mon, 25 Jul 2011 11:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.127
X-Spam-Level:
X-Spam-Status: No, score=-104.127 tagged_above=-999 required=5 tests=[AWL=-1.828, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EqJ9E63lheeL for <ipv6@ietfa.amsl.com>; Mon, 25 Jul 2011 11:50:21 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD0F21F885C for <ipv6@ietf.org>; Mon, 25 Jul 2011 11:50:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=3275; q=dns/txt; s=iport; t=1311619821; x=1312829421; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=qE80Pdd0wpTCGEulb1utcyN4Yhe/ptNmHlX+KTmt9P0=; b=kkXZ5HB1yBGmmGv7QQ07u3gBStOFFSwWHiaOsTEAPWyJGnxd2IxWivY4 LjdEjTOFeF4mIHdbQfEjv9momm6hLi9+KmNoaGYiHj1BhckX2epVB4lA5 OInFmhyQXM1Z9eTYPBMWBmNS2k3KLFw64tTPaZwD8UN4usbDcA5R6g2hw U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au8AAA+6LU6rRDoG/2dsb2JhbAApCwEBAQECAQEBAQUMARtKCwUHAQQCCg8CBAEBNAcUBhIWDQ4IAQEFFw8Yl1uBa41sd4h8BKFYniSGPwSHJpxG
X-IronPort-AV: E=Sophos;i="4.67,264,1309737600"; d="scan'208";a="6222556"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-5.cisco.com with ESMTP; 25 Jul 2011 18:50:20 +0000
Received: from dwingWS (sjc-vpn5-1896.cisco.com [10.21.95.104]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p6PIoJI0029568; Mon, 25 Jul 2011 18:50:19 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Rémi Després' <despres.remi@laposte.net>
References: <264DF4B8-A7F3-4DB3-B58D-BBAC2A48B470@gmail.com> <A3E346FA-E5A4-4755-9D35-08CB10494424@apple.com> <01d201cc48e1$0784d8d0$168e8a70$@com> <010826E2-D6DF-488D-B5C4-CE14E47C7EE7@free.fr> <04db01cc4acf$d9074600$8b15d200$@com> <98B94666-CD24-4D1A-B25F-F6238CC3708E@laposte.net>
In-Reply-To: <98B94666-CD24-4D1A-B25F-F6238CC3708E@laposte.net>
Subject: RE: PMTUD and MTU < 1280
Date: Mon, 25 Jul 2011 14:50:19 -0400
Message-ID: <071801cc4afb$b3ead4a0$1bc07de0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcxK8k2ECM4NLCxCSWmRf6fnhcsRBAACKxZQ
Content-Language: en-us
Cc: ipv6@ietf.org, 'RJ Atkinson' <rja.lists@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 18:50:22 -0000
> -----Original Message----- > From: Rémi Després [mailto:despres.remi@laposte.net] > Sent: Monday, July 25, 2011 1:43 PM > To: Dan Wing > Cc: 'james woodyatt'; 'RJ Atkinson'; ipv6@ietf.org > Subject: Re: PMTUD and MTU < 1280 > > Dan, > > 1. > The point I wanted to check is just, slightly reformulated): > "May a simple IPv6 host have no support of packet-reassembly, and > simply accept packets up to 1280 octets." The earlier part of this thread was talking about sending; you're now bringing up receiving. IMO, if the packet came from IPv4, and that IPv4 network had a small MTU (e.g., 576) causing fragmentation, then such an IPv6 receiver will be unable to receive the packet. > In my understanding, the answer should be yes. > - This doesn't depend on whether sources know or not whether their > destinations are IPv6 or IPv4 only. > - If the destination happens to be IPv6, current RFC's don't permit > intermediate nodes to refuse 1280 packets as being too big. > > 2. > How sources can be sure to have e2e transparency in IPv6 is a different > question, but IMHO an important one. > > For instance, if a destination address is obtained from the DNS in a > AAAA, with no A for the same URL and without any well-known prefix > indicating that there is an embedded-IPv4-address, I hope the source > can be guaranteed that e2e transparency won't be broken? I don't think so. DNS64 comes to mind. > I won't have time personally to contribute much on this, but the > subject would usefully be clarified, IMHO. The RFCs are pretty clear, IMO. Implementers don't want to read them all the way. -d > Regards, > RD > > > Le 25 juil. 2011 à 15:36, Dan Wing a écrit : > > >>>> > >>>> ... > >>> > >>> Its behavior violates the last paragraph of Section 5 of RFC2460. > >> > >> Violation _only in case_ of "an IPv6 packet that is sent to an IPv4 > >> destination". > > > > But how does one determine an IPv6 packet is, or isn't, going > > to an IPv4 destination? I don't think it's possible to determine > > if there is an IPv6/IPv4 translator on the path. > > > > -d > > > > > >> If the destination is IPv6, a PMTU below 1280 remains therefore a > >> network failure. > >> This authorizes a simple IPv6 host to refuse packets beyond 1280 > octets > >> and to have no support of packet-reassembly. > >> > >> Right? > >> > >> Regards, > >> RD > >> > >> > >> > >>> > >>> -d > >>> > >>>> > >>>> -- > >>>> james woodyatt <jhw@apple.com> > >>>> member of technical staff, core os networking > >>>> > >>>> > >>>> > >>>> ------------------------------------------------------------------ > -- > >>>> IETF IPv6 working group mailing list > >>>> ipv6@ietf.org > >>>> Administrative Requests: > https://www.ietf.org/mailman/listinfo/ipv6 > >>>> ------------------------------------------------------------------ > -- > >>> > >>> ------------------------------------------------------------------- > - > >>> IETF IPv6 working group mailing list > >>> ipv6@ietf.org > >>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > >>> ------------------------------------------------------------------- > - > >
- Re: PMTUD and MTU < 1280 Erik Nordmark
- Re: PMTUD and MTU < 1280 Karl Auer
- Re: PMTUD and MTU < 1280 Florian Weimer
- Re: PMTUD and MTU < 1280 Erik Nordmark
- PMTUD and MTU < 1280 Karl Auer
- Re: PMTUD and MTU < 1280 Philip Homburg
- Re: PMTUD and MTU < 1280 Florian Weimer
- Re: PMTUD and MTU < 1280 Erik Nordmark
- Re: PMTUD and MTU < 1280 Florian Weimer
- Re: PMTUD and MTU < 1280 Philip Homburg
- Re: PMTUD and MTU < 1280 Erik Nordmark
- Re: PMTUD and MTU < 1280 Philip Homburg
- Re: PMTUD and MTU < 1280 Brian E Carpenter
- Re: PMTUD and MTU < 1280 Erik Nordmark
- Re: PMTUD and MTU < 1280 Philip Homburg
- Re: PMTUD and MTU < 1280 RJ Atkinson
- Re: PMTUD and MTU < 1280 james woodyatt
- Re: PMTUD and MTU < 1280 Philip Homburg
- Re: PMTUD and MTU < 1280 Mark Andrews
- RE: PMTUD and MTU < 1280 Dan Wing
- RE: PMTUD and MTU < 1280 Dan Wing
- RE: PMTUD and MTU < 1280 Dan Wing
- RE: PMTUD and MTU < 1280 Dan Wing
- Re: PMTUD and MTU < 1280 Rémi Després
- Re: PMTUD and MTU < 1280 Mark Andrews
- Re: PMTUD and MTU < 1280 Rémi Després