IETF Logo Mail Archive

Re: [Int-area] IPv6 fragmentation for IPv4

Joe Touch <touch@isi.edu> Tue, 23 May 2017 18:01 UTC

Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BC28129C4A for <int-area@ietfa.amsl.com>; Tue, 23 May 2017 11:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
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 uQR9-6WnLp9t for <int-area@ietfa.amsl.com>; Tue, 23 May 2017 11:01:26 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83DE4126BF7 for <int-area@ietf.org>; Tue, 23 May 2017 11:01:26 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v4NI0exs011895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 23 May 2017 11:00:50 -0700 (PDT)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "int-area@ietf.org" <int-area@ietf.org>
References: <da864471c7b648eea3d9d93029209660@XCH15-06-08.nw.nos.boeing.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <e62dc1c0-c209-f834-c52c-9b8879048d86@isi.edu>
Date: Tue, 23 May 2017 11:00:40 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <da864471c7b648eea3d9d93029209660@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/OyeRPmblO6-fsg7tqb1coBUuPG4>
Subject: Re: [Int-area] IPv6 fragmentation for IPv4
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 May 2017 18:01:27 -0000

Hi, Fred (et al.),

On 5/23/2017 9:17 AM, Templin, Fred L wrote:
> Joe, I wanted to run an idea by you. We all know that IPv4 fragmentation has
> problems because of the 16-bit ID field. So, why not insert an IPv6 Fragment
> Header between the IPv4 header and the upper layer protocol data, then
> use IPv6-style fragmentation instead of IPv4 fragmentation?

IPv4 fragmentation has several impediments:
    - small ID field
    - lack of a reassembly checksum
    - lack of a fixed-location flow ID

Using IPv6-Frag as the next header solves only the first of these. The
last is significant - putting a new header would defeat IPv4 flow ECMP
even for the first fragment. IPv6 includes a flow field that serves this
purpose.

Joe

v2.23.0 | Report a Bug | By Email