Re: Please review: 6MAN WG Adoption call: draft-baker-6man-hbh-header-handling-03

Fernando Gont <fgont@si6networks.com> Tue, 20 October 2015 00:37 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2699B1B2B6C for <ipv6@ietfa.amsl.com>; Mon, 19 Oct 2015 17:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 OyuWzk_9-3x9 for <ipv6@ietfa.amsl.com>; Mon, 19 Oct 2015 17:37:46 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 1D8471B2B37 for <ipv6@ietf.org>; Mon, 19 Oct 2015 17:37:45 -0700 (PDT)
Received: from [181.46.190.53] (helo=[172.16.17.13]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1ZoKvn-0000Os-TK; Tue, 20 Oct 2015 02:37:36 +0200
Subject: Re: Please review: 6MAN WG Adoption call: draft-baker-6man-hbh-header-handling-03
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, otroan@employees.org, 6man WG <ipv6@ietf.org>
References: <8BD907B6-DCCF-4F3B-917C-DC82A8D49BB0@employees.org> <5623F573.6070105@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5625896D.3040408@si6networks.com>
Date: Mon, 19 Oct 2015 21:23:09 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <5623F573.6070105@gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/f3fEhMnreDD1fo3IXQaMbLF9Uyo>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 20 Oct 2015 00:37:48 -0000

Hi, All,

+1 to adoption and everything Brian noted, modulo one issue noted below:

On 10/18/2015 04:39 PM, Brian E Carpenter wrote:
> Hi,
> 
> Yes, I think the WG should adopt this topic. In particular, I support
> the key recommendation:
> 
>> Packets containing the Hop-by-Hop Extension Header SHOULD be
>> processed at substantially the same rate as packets that do not.
> 
> I do have a few comments on the current text:
> 
>> At this writing, there are several defined Hop-by-Hop options:
> 
> This list should probably mention the experimental options defined
> in RFC 4727.
> 
>> 2.3.  Adding headers or options in transit
> 
> I have extreme doubts about this. I believe that RFC 2460 intended to
> forbid this but was loosely worded ("extension headers are not processed
> by any node along a packet's delivery path"). When the time comes, I will
> argue  that 2460bis should correct this. In any case, if this section is
> retained, it needs to discuss MTU issues. I don't see why that belongs
> in the Security Considerations.
> 
>> 3.  Interoperation with RFC 2460
> 
> Should probably be adjusted to refer to 2460bis.

I'd say both 2460 and 2460bis.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492