Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08

Tim Chown <> Thu, 30 March 2017 19:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D01581292FC; Thu, 30 Mar 2017 12:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7ZjZYj5cFtNV; Thu, 30 Mar 2017 12:26:07 -0700 (PDT)
Received: from ( [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 92F58126B72; Thu, 30 Mar 2017 12:26:06 -0700 (PDT)
Received: from (localhost []) by (8.13.8/8.13.8) with ESMTP id v2UJQ2u0026523; Thu, 30 Mar 2017 20:26:02 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 v2UJQ2u0026523
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple;; s=201304; t=1490901963; bh=eSbJ1LvwGAIkTkXpXudA0NKu9jA=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=puIoOd4K0mut1FooXADzlJkND9swmmnEk9Kn9+jkKlm/YkenrMJsGL0EPY00SPNJX A7M3q6tIdbAr1MxRHuN8R0doVpjIghJSaf8CKEB/x18XavZspjEugYgDZShdf0ZCFF teezY5s9e1AIlltEsq8ZXBQYyhA0SrdBLtfvYaRU=
Received: from ( [2001:630:d0:f102::25d]) by ( [2001:630:d0:f102::25e]) envelope-from <> with ESMTP (valid=N/A) id y2YKQ21151011028gw ret-id none; Thu, 30 Mar 2017 20:26:02 +0100
Received: from ( [IPv6:2001:67c:370:128:14f6:e8a6:bc91:a44d]) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id v2UJPuSC028259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Mar 2017 20:25:57 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
From: Tim Chown <>
In-Reply-To: <>
Date: Thu, 30 Mar 2017 20:25:56 +0100
Cc: "" <>, 6man WG <>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|6fa5e3b676a6186d2c95426220e13766y2YKQ203tjc||>
References: <> <> <> <> <> <> <> <> <> <> <>
To: IETF Discussion <>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: ssss
X-smtpf-Report: sid=y2YKQ2115101102800; tid=y2YKQ21151011028gw; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v2UJQ2u0026523
Archived-At: <>
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 30 Mar 2017 19:26:10 -0000


> On 30 Mar 2017, at 19:19, 神明達哉 <> wrote:
> At Thu, 30 Mar 2017 11:52:41 -0500,
> Robert Raszuk <> wrote:
>> Ok so till a new document updates 2460bis any further work on EHs is frozen
>> as it would reference 2460bis with new text. That was my main point.
> I don't get the "update" can start immediately once such a
> draft new proposal is available.  The update won't be formally
> completed until it gets some formal state like a standard track RFC,
> and it will take time, but that wouldn't necessarily mean a further
> work is "frozen"; it's not very clear to me what this term means in
> this context, but it's quite common development takes place while the
> spec is being discussed as a draft, and it's also not uncommon some
> commercial operators even start deploying it.  On the other hand, even
> if we now agreed that rfc2460bis should explicitly allow such "further
> work", the discussion itself would take long and wouldn't be completed
> soon.
> But IMO it's irresponsible to leave the text ambiguous and let some
> other people misunderstand it, possibly even more casually and/or in
> the global Internet, for the comfort of some particular future work.
> I think we're now trying to help avoid the latest clarification in
> rfc2460bis to be interpreted as an "outright ban" of future updates
> while still trying to be responsible for the soundness of the global
> Internet.  In my understanding Brian's additional text is one such
> attempt (I also proposed text in that sense at the time of WGLC,
> although it wasn't adopted in the end).  If that text is still not
> enough we can discuss how to phrase it.  And, while I suspect people
> who wanted to keep the ambiguity will never be satisfied with the
> result as long as the added clarification remains, I believe that's a
> reasonable compromise to achieve a balance between being responsible
> and not (unintentionally) discouraging future updates.

Repeating what I said at the mic, my views echo those of Jinmei, Michael, Lorenzo and Brian. I agree with the decision to progress RFC2460-bis to IS including Suresh’s text. I’d also like to see Brian’s short amendment included, which makes explicit Internet scope as the default target.

Advancing 2460bis doesn’t freeze work on SR; that work can continue today. I don’t see the new SR header insertion draft completing in “a couple of weeks”; it’s much more likely to take several months or even a year to progress through WG adoption and eventual publication, to ensure good and robust input. For adoption, I’d expect many people to want the draft to include text on a) why vanilla encapsulation is not sufficient and b) how the insertion can guaranteed to be done safely for specific scenario(s). But that’s all very possible.

And please do note that publishing 2460-bis as an Internet Standard does not set it in stone. Your SR work can update it, as could other future RFC(s) on other new mechanism(s) or innovation(s) that have yet to be proposed. I’d argue that it’s pretty likely we’ll see other RFCs update 2460-bis; that shouldn’t be a surprise if it’s a protocol that we’ll be using for the next 20-30 years or more. For each, we’ll just see “Updated by:” tags in the RFC header. The current RFC2460 has accumulated nine such tags in 19 years, so about one every two years.

On enterprise deployment I’d argue that, if anything, moving to IS should help strengthen the case for deployment, because it confirms proven widescale deployment.  The four criteria for moving to IS are described in Section 2.2 of RFC6410, but are summarised as "a high degree of technical maturity and by a generally held belief that the specified protocol or service provides significant benefit to the Internet community”. I’d hope we have very strong consensus on that statement.