Re: Is Fragmentation at IP layer even needed ?

Joe Touch <touch@isi.edu> Tue, 09 February 2016 20:27 UTC

Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF5A1AD289 for <ietf@ietfa.amsl.com>; Tue, 9 Feb 2016 12:27:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKBvdK4f4NhP for <ietf@ietfa.amsl.com>; Tue, 9 Feb 2016 12:27:28 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68FF91AD272 for <ietf@ietf.org>; Tue, 9 Feb 2016 12:27:28 -0800 (PST)
Received: from [10.123.85.51] (usc-secure-wireless-088-051.usc.edu [68.181.88.51]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id u19KQXLI009303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 9 Feb 2016 12:26:53 -0800 (PST)
Subject: Re: Is Fragmentation at IP layer even needed ?
To: Ronald Bonica <rbonica@juniper.net>, Alexey Eromenko <al4321@gmail.com>, ietf <ietf@ietf.org>
References: <CAOJ6w=EvzE3dM4Y2mFFR=9YyPBdmFu_jkF4-42LjkdbRd3yz_w@mail.gmail.com> <BLUPR05MB1985F5F2BB3118362C67B921AED50@BLUPR05MB1985.namprd05.prod.outlook.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <56BA4B77.2050901@isi.edu>
Date: Tue, 09 Feb 2016 12:26:31 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <BLUPR05MB1985F5F2BB3118362C67B921AED50@BLUPR05MB1985.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WhDcMTBKIFw9VUGEI-TsCPhKKjM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 20:27:29 -0000


On 2/8/2016 9:21 AM, Ronald Bonica wrote:
> Many end-stations work around this problem by sending packets no longer
> that the IPv6 minimum MTU (1280 bytes). This ensures that IPv6
> fragmentation services will never be required.

IPv6 1280 may itself not be fragmented, but it may end up in multiple IP
fragments within an IP tunnel if the tunnel cannot assume an MTU that is
larger.

So if you have tunnels, fragmentation services are always ultimately
required.

Joe