Re: Review of draft-ietf-6man-hbh-header-handling-01

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 07 March 2016 04:06 UTC

Return-Path: <brian.e.carpenter@gmail.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 719BA1A88C5; Sun, 6 Mar 2016 20:06:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 mXAMY7KIBdMw; Sun, 6 Mar 2016 20:06:44 -0800 (PST)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 079681A88BE; Sun, 6 Mar 2016 20:06:44 -0800 (PST)
Received: by mail-pf0-x231.google.com with SMTP id 63so71799263pfe.3; Sun, 06 Mar 2016 20:06:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=M97ZpP6VwuEQsKYaEXFyXPIAuLBmH4httQXlMIgtVkM=; b=P/etF524SX6ud4reU/dei0s8t9PvwW34HFCnVinH6OcB2DJWiDQvYV21Akjcze/gMy OM5jzLj+l60gEihAVQvndMDRQ0Q39ZHn86buPasn38DhJk4QI/a9Ca6C7gz73dhNmjoZ qPUNDEdjBG7TtkaOA5IMW+5nWqjCfCJ30k8Zw0qxbQ9xUbTxB6D4ww0hc9ozZ8UkMsoQ CexhOBoZGLOUQQ72rQXPju4WNUoO5iS4AizKkqWY82/HfZ7qTWVRk5AwgZTb4H1nRSae ZU3rz+xPN2Rap7phaKFoSof8JZiSAkLvjX3GqgxiUlWnCMTVFJb/oy99KfAdKINhoxhW cq3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=M97ZpP6VwuEQsKYaEXFyXPIAuLBmH4httQXlMIgtVkM=; b=cqFNHhxUsABye9o3c6sXxdZBSdn186bPpdGfWYEKjJUEgNSUG76x+iRcJsDfb1KZuc Qpa+9hqRHfYkH2z+daZhijXZM1DlznP6mEqzCPsW6IWhIRhVs6rqhUNvKEfW/Y+DMufc dI0lsSKFUPgjhOp5lN6zGxG1iQUuxKSqMk6Zrhpv4qE1n8TzuvtWDPQ05EDVoef1N9mc BzzclNSBizgBRAcTAgzzeBAVK2I2Xz7Q+ZJhaOXipXhP2qJQ9bDSSyyjIh7t9JI617m2 R0roNcnYvVm5pUGxyG3zVPwo+icGNADaLNnV/cGPjtopJ1nZZAbl9EAxxaFQ5w6h6amB ISgw==
X-Gm-Message-State: AD7BkJIGGRjmKcSzW4eq5ucSWg3DxvChUBV4xUDyCZoJBHSa7cM/4cyTnn2zGfgvdatFjA==
X-Received: by 10.98.79.205 with SMTP id f74mr30283266pfj.68.1457323603611; Sun, 06 Mar 2016 20:06:43 -0800 (PST)
Received: from ?IPv6:2406:e007:530d:1:28cc:dc4c:9703:6781? ([2406:e007:530d:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id u5sm20557754pfi.15.2016.03.06.20.06.39 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 06 Mar 2016 20:06:41 -0800 (PST)
Subject: Re: Review of draft-ietf-6man-hbh-header-handling-01
To: "Fred Baker (fred)" <fred@cisco.com>, Fernando Gont <fgont@si6networks.com>
References: <56D946D2.4020607@si6networks.com> <56DA0756.8070801@gmail.com> <56DA74D9.40304@si6networks.com> <B98CA008-EB3B-495B-BF63-857A58D44580@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56DCFE4C.4000205@gmail.com>
Date: Mon, 07 Mar 2016 17:06:36 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <B98CA008-EB3B-495B-BF63-857A58D44580@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/926D2-R0MMn8_r82Drp7lO3dlHg>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-hbh-header-handling@ietf.org" <draft-ietf-6man-hbh-header-handling@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: Mon, 07 Mar 2016 04:06:45 -0000

On 07/03/2016 11:33, Fred Baker (fred) wrote:
> Something to discuss wth the chairs, I suppose. The first question is whether 2460bis is ready about when it is, or one is later.
> 
> I'd like to believe this is close to done, and I suspect Bob would like to believe 2460bis is close to done.... If so, the chairs may prefer to somehow incorporate it into 2460bis and ship it.

I don't see that happening, because 2460bis is supposed to be aimed at
Internet Standard status and that requires solid operational experience
for all features. hbh-header-handling is some years from that situation,
unfortunately. So I can only see it as a Proposed Standard update
to the future Internet Standard.

(You may recall draft-loughney-newtrk-one-size-fits-all. I always
thought that would have saved us a lot of bureaucracy.)

   Brian

>> On Mar 5, 2016, at 6:55 AM, Fernando Gont <fgont@si6networks.com> wrote:
>>
>> On 03/04/2016 07:08 PM, Brian E Carpenter wrote:
>>>
>>> Also, I would suggest sequencing this draft to come out *after* 2460bis.
>>> It might have the distinction of being the first RFC to update 2460bis.
>>
>> Not that I like to point this out, but...
>> One one hand, if we're working on rfc2460bis, then one would argue that
>> if we're to intentionally stall draft-ietf-6man-hbh-header-handling so
>> that it gets published after rfc2460bis, then why not incorporate it in
>> rfc2460bis?
>>
>> I'd expect that this doc is published soon & as is: It updates
>> RFC2460... and then rfc2460bis picks RFC2460 plus updates.
>>
>> --
>> Fernando Gont
>> SI6 Networks
>> e-mail: fgont@si6networks.com
>> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>>
>>
>>
>>
>