RE: Objection to draft-ietf-6man-rfc4291bis-07.txt

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Fri, 24 February 2017 19:10 UTC

Return-Path: <albert.e.manfredi@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 B03E51294C0 for <ipv6@ietfa.amsl.com>; Fri, 24 Feb 2017 11:10:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 0HiroyZq_3Ia for <ipv6@ietfa.amsl.com>; Fri, 24 Feb 2017 11:10:16 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 633AF1294D3 for <ipv6@ietf.org>; Fri, 24 Feb 2017 11:10:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v1OJAFjr034823; Fri, 24 Feb 2017 12:10:15 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1OJABYm034786 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 24 Feb 2017 12:10:11 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 24 Feb 2017 11:10:09 -0800
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1263.000; Fri, 24 Feb 2017 11:10:10 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: james woodyatt <jhw@google.com>
Subject: RE: Objection to draft-ietf-6man-rfc4291bis-07.txt
Thread-Topic: Objection to draft-ietf-6man-rfc4291bis-07.txt
Thread-Index: AQHSjdpvHMQuOTwVQEa1egjWGUVyuqF3qhEAgAALKoCAAAOVAIAADWkAgAAHuYCAALoMAIAAdSGA//+I2SA=
Date: Fri, 24 Feb 2017 19:10:10 +0000
Message-ID: <304f89c9ec7c4931b3d854ff1d24f912@XCH15-06-11.nw.nos.boeing.com>
References: <20170223134026.GI5069@gir.theapt.org> <9277BC0B-04F3-4FC1-901E-F83A8F0E02D7@google.com> <58AF6429.70809@foobar.org> <902276E9-0521-4D4E-A42B-C45E64763896@google.com> <58AF726A.3040302@foobar.org> <F7C230DE-4759-4B78-ABF2-6799F85B3C62@google.com> <58B014F6.2040400@foobar.org> <6DA95097-8730-4353-A0C9-3EB4719EA891@google.com>
In-Reply-To: <6DA95097-8730-4353-A0C9-3EB4719EA891@google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/MBozFzYLKbrkg01D1jlYJsyUmx8>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 24 Feb 2017 19:10:18 -0000

From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of james woodyatt

> I know there are operating systems with billions of units in the field
> today that do exactly this because RFC 4291 and its predecessors have for
> years given them clear license to do so, and I don’t want to see the
> publication of I-D.ietf-6man-rfc4291bis as RFC come to remove this license
> as a side effect of promoting IPv6 to full Standard category.

But this is exactly why RFC 4291-bis has to get this right. The unicast address space 2000::/3 is the only one that should be so constrained. We need to nip this problem in the bud.

OSs can be updated, when it becomes necessary.

> You want to remove that license?

Remove that misinterpretation as a GENERAL rule for IPv6? Yes. Prefixes can be of any length, in general, in IPv6.

Bert