Re: Is Fragmentation at IP layer even needed ?

Fernando Gont <fgont@si6networks.com> Mon, 08 February 2016 23:58 UTC

Return-Path: <fgont@si6networks.com>
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 7109F1B3DAF for <ietf@ietfa.amsl.com>; Mon, 8 Feb 2016 15:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 NRJI07m9Lvm0 for <ietf@ietfa.amsl.com>; Mon, 8 Feb 2016 15:58:33 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 224C71B3DAE for <ietf@ietf.org>; Mon, 8 Feb 2016 15:58:33 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.164.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id EC5DC206AA8; Tue, 9 Feb 2016 00:52:22 +0100 (CET)
Subject: Re: Is Fragmentation at IP layer even needed ?
To: Mark Andrews <marka@isc.org>, Ronald Bonica <rbonica@juniper.net>
References: <CAOJ6w=EvzE3dM4Y2mFFR=9YyPBdmFu_jkF4-42LjkdbRd3yz_w@mail.gmail.com> <BLUPR05MB1985F5F2BB3118362C67B921AED50@BLUPR05MB1985.namprd05.prod.outlook.com> <20160208200943.A615941B5B96@rock.dv.isc.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B92962.4080803@si6networks.com>
Date: Mon, 08 Feb 2016 20:48:50 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160208200943.A615941B5B96@rock.dv.isc.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mpzvXWisCYbCZ9LSgrFMofltunY>
Cc: ietf <ietf@ietf.org>
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: Mon, 08 Feb 2016 23:58:36 -0000

On 02/08/2016 05:09 PM, Mark Andrews wrote:
> In message <BLUPR05MB1985F5F2BB3118362C67B921AED50@BLUPR05MB1985.namprd05.prod.
> outlook.com>, Ronald Bonica writes:
>> Hi Alexey,
>>
>> This question comes up every few years. The short answer is:
>>
>>
>> -          The vast majority of Internet traffic rides over TCP or UDP
>>
>> -          Generally speaking, traffic that rides over TCP does not rely
>> on IP fragmentation
>>
>> -          However, traffic the rides over UDP absolutely relies on IP
>> fragmentation
>>
>> So, as things stand, IP fragmentation is required to support UDP.
>> However, the conversation doesnt end at that.
>>
>> Operational experience has taught us that IPv6 fragmentation does not
>> work so well. Unlike IPv4, IPv6 encodes fragmentation information in an
>> IPv6 extension header. Sadly, many operators discard packets containing
>> that extension header. So, as specified, IPv6 provides fragmentation
>> services, but as deployed, it does not.
> 
> Actually fragmentation works well unless you have a firewall that
> drops fragments.  When they are not being deliberately blocked the
> packets get through and are reassembled.  It is also not many
> operators.  It is some operators.
> 
> Additionally there is zero reasons why firewalls can't open <src,
> dst, frag offset != 0> when they open <src, dst, proto, src port,
> dst port> for reply traffic for those that are paranoid about just
> letting all non-zero fragment offset through.  I just let the
> non-zero offset fragments through.

If and only if the packets do not employ other EHs and all the nodes
behind the fw implement RFC5722...

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492