[Int-area] IPv6 fragmentation for IPv4

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 23 May 2017 16:17 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id C8A79129BAD for <int-area@ietfa.amsl.com>; Tue, 23 May 2017 09:17:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.821
X-Spam-Status: No, score=-2.821 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id A91IKcKqngkc for <int-area@ietfa.amsl.com>; Tue, 23 May 2017 09:17:21 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C080126BF0 for <int-area@ietf.org>; Tue, 23 May 2017 09:17:20 -0700 (PDT)
Received: from localhost (localhost []) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v4NGHJw5026718; Tue, 23 May 2017 09:17:19 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com []) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v4NGH8Pw026086 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Tue, 23 May 2017 09:17:08 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 23 May 2017 09:17:07 -0700
Received: from XCH15-06-08.nw.nos.boeing.com ([]) by XCH15-06-08.nw.nos.boeing.com ([]) with mapi id 15.00.1263.000; Tue, 23 May 2017 09:17:07 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "int-area@ietf.org" <int-area@ietf.org>, Joe Touch <touch@isi.edu>
Thread-Topic: IPv6 fragmentation for IPv4
Thread-Index: AdLT3WVYMdiisvTeTLyu7THIVnRQuA==
Date: Tue, 23 May 2017 16:17:07 +0000
Message-ID: <da864471c7b648eea3d9d93029209660@XCH15-06-08.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/Ga3BsiXa3IYJE-ETNre360iE-9k>
Subject: [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 16:17:23 -0000

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?

So, the IPv4 Protocol field would be set to '44', the IPv4 header would be
followed by an IPv6 Fragment Header, and the "Next Header" field in the
IPv6 Fragment Header would be set to the Protocol Number for the upper
layer protocol. Then, upon fragmentation, each fragment would have an
IPv4 header followed by an IPv6 Fragment Header.

This format is shown in Figure 6 in Appendix A of the AERO draft:


Does this look like something that should be broken out and put into a
little standalone document?

Thanks - Fred