RE: A proposal for draft-ietf-6man-rfc4291bis-07

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Fri, 03 March 2017 02:06 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 6D9EE129455 for <ipv6@ietfa.amsl.com>; Thu, 2 Mar 2017 18:06:07 -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 zJ8LLGYgrCMW for <ipv6@ietfa.amsl.com>; Thu, 2 Mar 2017 18:06:06 -0800 (PST)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (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 7964C129431 for <ipv6@ietf.org>; Thu, 2 Mar 2017 18:06:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v232653b064094; Thu, 2 Mar 2017 19:06:05 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v2325xs8063699 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 2 Mar 2017 19:05:59 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (137.136.239.220) by XCH15-06-10.nw.nos.boeing.com (137.136.239.219) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 2 Mar 2017 18:05:58 -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; Thu, 2 Mar 2017 18:05:58 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: David Farmer <farmer@umn.edu>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: A proposal for draft-ietf-6man-rfc4291bis-07
Thread-Topic: A proposal for draft-ietf-6man-rfc4291bis-07
Thread-Index: AQHSk6aBc0GC3/s6VkejKSh9uOtZ66GCOwMggAAG9SCAAJgEgIAAB1oA//96qjA=
Date: Fri, 03 Mar 2017 02:05:58 +0000
Message-ID: <2126862bab4f49f492c40639ff1b829a@XCH15-06-11.nw.nos.boeing.com>
References: <CAN-Dau17q_BrUuzfvB1mLDt6p5UxYikphWaHpa8VQ2L-3kx-DA@mail.gmail.com> <a484b60f9d9b4fcea24dc320c550da2c@XCH15-06-11.nw.nos.boeing.com> <ee764408573b4db4b22e58c4ea5f289c@XCH15-06-11.nw.nos.boeing.com> <2c0ab33b-abbe-caf1-6147-0c583d7f5d61@gmail.com> <CAN-Dau0bSPiubeDOFeJAg6H0wP0ZNDS514eedmJtkOqHTXWOOw@mail.gmail.com>
In-Reply-To: <CAN-Dau0bSPiubeDOFeJAg6H0wP0ZNDS514eedmJtkOqHTXWOOw@mail.gmail.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/Eut_hnGVBLUUyaRvnLN2pSnybXg>
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, 03 Mar 2017 02:06:07 -0000

From: David Farmer [mailto:farmer@umn.edu]

>> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

>> Agreed. And I think there are actually two things to say here:
>>
>> 3.1. Any IPv6-over-foo spec must specify a recommended IID length.
>> 3.2. In the absence of such a spec, the recommended IID length is
>> 64 bits.
>>
>> Again, that breaks no running code, and it respects the architectural
>> statement that prefix_length + IID_length == 128, and the use of CIDR
>> routing and variable-length subnet masks.
>>
>>    Brian
>
> I'd be fine with that, but others seem to feel otherwise. Lorenzo
> and James?

That's why it's called "consensus." As opposed to unanimity.

> However, if a provider only delegates a /64, this new text ensures that
> prefix could be further subnetted down below /64 using manual config or
> possibly DHCPv6.

Exactly. So, how can we allow RFC 4291 bis to say that 64-bit IIDs are REQUIRED? We can't. That was my original point.

Bert