RE: Re-use of fragment header in SEAL
"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 21 October 2013 15:08 UTC
Return-Path: <Fred.L.Templin@boeing.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 323DF11E85ED for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 08:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.519
X-Spam-Level:
X-Spam-Status: No, score=-6.519 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sgz21uBifeJk for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 08:08:19 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 5817A11E85FF for <ipv6@ietf.org>; Mon, 21 Oct 2013 08:07:43 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9LF7gsu008120 for <ipv6@ietf.org>; Mon, 21 Oct 2013 10:07:42 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9LF7L3L007212 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 21 Oct 2013 10:07:42 -0500
Received: from XCH-BLV-402.nw.nos.boeing.com (130.247.25.31) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 21 Oct 2013 08:07:37 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-402.nw.nos.boeing.com ([169.254.2.160]) with mapi id 14.03.0158.001; Mon, 21 Oct 2013 08:07:37 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian Haberman <brian@innovationslab.net>
Subject: RE: Re-use of fragment header in SEAL
Thread-Topic: Re-use of fragment header in SEAL
Thread-Index: AQHOzNdeHEb9dzMx1kyeywzrFKUFx5n/Q/3A
Date: Mon, 21 Oct 2013 15:07:36 +0000
Message-ID: <2134F8430051B64F815C691A62D9831813500F@XCH-BLV-504.nw.nos.boeing.com>
References: <526296B8.5080108@innovationslab.net>
In-Reply-To: <526296B8.5080108@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
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, 21 Oct 2013 15:08:26 -0000
Hi Brian, > Fred, > The way you have re-used the Next Header value of the Fragment > Header may be troublesome. If someone updates 2460 to change the > Fragment Header (i.e., add additional info in the current Reserved > field), they will step on your use of the header and make them > indistinguishable. That is true, but if the SEAL document were the one to update RFC2460 then there would be no concerns for future collisions. So, in the next document version I will add "Updates RFC2460". Thanks for the comment. Fred fred.l.templin@boeing.com > Regards, > Brian
- Re-use of fragment header in SEAL Brian Haberman
- RE: Re-use of fragment header in SEAL Templin, Fred L
- Re: Re-use of fragment header in SEAL Bob Hinden
- RE: Re-use of fragment header in SEAL Templin, Fred L
- Re: Re-use of fragment header in SEAL Bob Hinden
- RE: Re-use of fragment header in SEAL Templin, Fred L