Re-use of fragment header in SEAL
Brian Haberman <brian@innovationslab.net> Sat, 19 October 2013 14:27 UTC
Return-Path: <brian@innovationslab.net>
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 93A6911E81C7 for <ipv6@ietfa.amsl.com>; Sat, 19 Oct 2013 07:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level:
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 r2MM-hIjkwfB for <ipv6@ietfa.amsl.com>; Sat, 19 Oct 2013 07:27:14 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 64D2F11E81A9 for <ipv6@ietf.org>; Sat, 19 Oct 2013 07:27:14 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id E99228807C; Sat, 19 Oct 2013 07:27:13 -0700 (PDT)
Received: from Littlejohn.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 86A1313680E2; Sat, 19 Oct 2013 07:27:13 -0700 (PDT)
Message-ID: <526296B8.5080108@innovationslab.net>
Date: Sat, 19 Oct 2013 10:27:04 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re-use of fragment header in SEAL
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="TjL1sTEHLtUiSL6495ivnBRI3Nc4jCjbQ"
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: Sat, 19 Oct 2013 14:27:21 -0000
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.
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