RE: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 08 October 2013 15:29 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 0BF0321E80F0; Tue, 8 Oct 2013 08:29:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 oB+e-sin+Nx9; Tue, 8 Oct 2013 08:29:06 -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 6FC6721E80AC; Tue, 8 Oct 2013 08:28:56 -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 r98FStlG011151; Tue, 8 Oct 2013 10:28:55 -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 r98FSrpP010698 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 8 Oct 2013 10:28:54 -0500
Received: from XCH-BLV-502.nw.nos.boeing.com (130.247.25.191) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 8 Oct 2013 08:28:53 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-502.nw.nos.boeing.com ([169.254.2.118]) with mapi id 14.02.0328.011; Tue, 8 Oct 2013 08:28:53 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "C. M. Heard" <heard@pobox.com>
Subject: RE: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
Thread-Topic: Adrian Farrel's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
Thread-Index: AQHOw7v2kD1BJLnfPEa6uJw0JWHTepnq7I1w
Date: Tue, 08 Oct 2013 15:28:52 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811DA86@XCH-BLV-504.nw.nos.boeing.com>
References: <20131007144327.16131.88173.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1310070914240.13173@shell4.bayarea.net> <52530921.3060202@gmail.com> <Pine.LNX.4.64.1310071315370.13828@shell4.bayarea.net> <52534F31.2020906@gmail.com>
In-Reply-To: <52534F31.2020906@gmail.com>
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: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Adrian Farrel <adrian@olddog.co.uk>, "draft-ietf-6man-ext-transmit@tools.ietf.org" <draft-ietf-6man-ext-transmit@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, The IESG <iesg@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: Tue, 08 Oct 2013 15:29:12 -0000

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> Sent: Monday, October 07, 2013 5:18 PM
> To: C. M. Heard
> Cc: 6man-chairs@tools.ietf.org; Adrian Farrel; draft-ietf-6man-ext-
> transmit@tools.ietf.org; ipv6@ietf.org; The IESG
> Subject: Re: Adrian Farrel's No Objection on draft-ietf-6man-ext-
> transmit-04: (with COMMENT)
> 
> On 08/10/2013 10:28, C. M. Heard wrote:
> ...
> 
> > Maybe I'm making too much of this.  Certainly a reasonable action
> > for a middlebox that's told to pass packets with extension header
> > types 253 and 254 is to stop parsing when it encounters those next
> > header types and forward the packet in question.  Maybe that's
> > obvious to everyone -- but it seems to me that the spec, as written,
> > is actually asking for something different.
> 
> There's no header length field in an IPv6 header. That means that
> since header types 253 and 254 might be used either for experimental
> extension headers or for experimental payload types, there's no
> generic way for a middlebox to tell the difference. I think that's
> an issue that the current draft cannot resolve. I suspect we probably
> need an extra sentence to state the problem, but the authors will
> wait for direction on that.

When Wireshark encounters a header type 253 or 254, it assumes it is
an unknown extension header of length 8 bytes, then skips ahead and
attempts to parse anything that follows as additional headers.

Wireshark can be thought of as a middlebox of sorts (albeit one
that does not alter the traffic flow), and it wouldn't be hard to
imagine real middleboxes that do the same thing when they encounter
253/254.

Thanks - Fred
fred.l.templin@boeing.com
 
>     Brian
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------