Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Joe Touch <touch@isi.edu> Wed, 15 March 2017 20:34 UTC
Return-Path: <touch@isi.edu>
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 E046C131826; Wed, 15 Mar 2017 13:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
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 bgaQyHwoU87P; Wed, 15 Mar 2017 13:34:34 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (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 012F71315A7; Wed, 15 Mar 2017 13:34:33 -0700 (PDT)
Received: from [128.9.184.222] ([128.9.184.222]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v2FKYFrQ021996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Mar 2017 13:34:15 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Leddy, John" <John_Leddy@comcast.com>, Tim Chown <Tim.Chown@jisc.ac.uk>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com> <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk> <A67E1C07-282B-4422-A2FF-86F6CACBD775@cable.comcast.com> <ab7c95a5-9776-24b5-7c26-4c5987d4c948@isi.edu> <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com>
Cc: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <39a51f77-a89f-2a22-dd9b-af8255a4aa25@isi.edu>
Date: Wed, 15 Mar 2017 13:34:15 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/RJLfk3DQ7jjDWoafuQ5ImrfNPk0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 15 Mar 2017 20:34:35 -0000
Agreed. Joe On 3/15/2017 11:59 AM, Brian E Carpenter wrote: > On 16/03/2017 07:14, Joe Touch wrote: >> >> On 3/15/2017 9:33 AM, Leddy, John wrote: >>> Does this mean that only middle boxes, not covered by the architecture could insert an extension header for use within the domain? >> Please see my recent post about Stefano's issue. IMO, any opaque >> (distributed) system that acts like a host can follow the host (node) >> requirements. >> >> The instant that system is not opaque or fails to act like a single >> host, it becomes noncompliant. > That's the point. That's why the 6man WG shot down proposals to play > intra-domain tricks with the flow label a few years ago, and they > didn't even break PMTUD or IPsec/AH. > > In another form, the answer to John is that there are no protocol police, > so what consenting adults do inside their own networks simply isn't an > issue that an Internet-wide spec can or should address. And for sure, the > spec for IPvN for any value of N is an Internet-wide spec. > > If Stefano and colleagues describe how private domains can perform tricks > that MUST NOT be exported to the Internet, that is fine. Whether that > becomes a standards track document or an Independent Submission RFC is > another question. But IMHO it is completely orthogonal to the rough > consensus on 2460bis. > > Brian
- IETF Last Call conclusion for draft-ietf-6man-rfc… Suresh Krishnan
- Re: IETF Last Call conclusion for draft-ietf-6man… Stefano Previdi (sprevidi)
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Tim Chown
- Re: IETF Last Call conclusion for draft-ietf-6man… Leddy, John
- Re: IETF Last Call conclusion for draft-ietf-6man… 神明達哉
- Re: IETF Last Call conclusion for draft-ietf-6man… Voyer, Daniel
- Re: IETF Last Call conclusion for draft-ietf-6man… Joe Touch
- Re: IETF Last Call conclusion for draft-ietf-6man… Joe Touch
- Re: IETF Last Call conclusion for draft-ietf-6man… Fernando Gont
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Joe Touch
- Re: IETF Last Call conclusion for draft-ietf-6man… Mark Smith
- Re: IETF Last Call conclusion for draft-ietf-6man… Tim Chown
- Re: IETF Last Call conclusion for draft-ietf-6man… Xing Li
- Re: IETF Last Call conclusion for draft-ietf-6man… otroan
- Re: IETF Last Call conclusion for draft-ietf-6man… Stewart Bryant
- Re: IETF Last Call conclusion for draft-ietf-6man… Leddy, John
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Manual PMTUD [was ...rfc2460bis-08] Brian E Carpenter
- Re: Manual PMTUD [was ...rfc2460bis-08] Robert Raszuk
- Re: Manual PMTUD [was ...rfc2460bis-08] Brian E Carpenter
- Re: Manual PMTUD [was ...rfc2460bis-08] Mark Smith
- Re: Manual PMTUD [was ...rfc2460bis-08] Robert Raszuk
- Re: Manual PMTUD [was ...rfc2460bis-08] Brian E Carpenter
- Re: Manual PMTUD [was ...rfc2460bis-08] Timothy Winters
- Re: Manual PMTUD [was ...rfc2460bis-08] Michael Richardson
- Re: Manual PMTUD [was ...rfc2460bis-08] Brian E Carpenter
- Re: Manual PMTUD [was ...rfc2460bis-08] Joel M. Halpern
- Re: Manual PMTUD [was ...rfc2460bis-08] Michael Richardson
- Re: Failure of AH (was: Manual PMTUD [was ...rfc2… Christian Huitema
- Re: Failure of AH (was: Manual PMTUD [was ...rfc2… Michael Richardson
- Re: Failure of AH Brian E Carpenter
- Re: Failure of AH Michael Richardson
- Re: IETF Last Call conclusion for draft-ietf-6man… Leddy, John
- Re: IETF Last Call conclusion for draft-ietf-6man… Tim Chown
- Re: IETF Last Call conclusion for draft-ietf-6man… Mark Townsley
- Re: IETF Last Call conclusion for draft-ietf-6man… Mark Townsley
- Re: IETF Last Call conclusion for draft-ietf-6man… Leddy, John
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Jeff Tantsura
- Re: IETF Last Call conclusion for draft-ietf-6man… Suresh Krishnan
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Re: IETF Last Call conclusion for draft-ietf-6man… Suresh Krishnan
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- RE: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- RE: IETF Last Call conclusion for draft-ietf-6man… Ackermann, Michael
- Re: IETF Last Call conclusion for draft-ietf-6man… 神明達哉
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Tim Chown
- Re: IETF Last Call conclusion for draft-ietf-6man… Tim Chown
- Re: IETF Last Call conclusion for draft-ietf-6man… Mark Smith
- RE: IETF Last Call conclusion for draft-ietf-6man… Ackermann, Michael
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Re: IETF Last Call conclusion for draft-ietf-6man… otroan
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Re: IETF Last Call conclusion for draft-ietf-6man… otroan
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Tim Chown
- Re: IETF Last Call conclusion for draft-ietf-6man… Jen Linkova
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Jen Linkova
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Re: IETF Last Call conclusion for draft-ietf-6man… Tim Chown
- RE: IETF Last Call conclusion for draft-ietf-6man… Ackermann, Michael
- Re: IETF Last Call conclusion for draft-ietf-6man… Suresh Krishnan
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Re: IETF Last Call conclusion for draft-ietf-6man… Martin Rex
- Re: IETF Last Call conclusion for draft-ietf-6man… Suresh Krishnan
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Re: IETF Last Call conclusion for draft-ietf-6man… Suresh Krishnan
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Fernando Gont
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Suresh Krishnan
- Re: IETF Last Call conclusion for draft-ietf-6man… Robert Raszuk
- Re: IETF Last Call conclusion for draft-ietf-6man… Brian E Carpenter
- Re: IETF Last Call conclusion for draft-ietf-6man… Bob Hinden