IETF Logo Mail Archive

RE: draft-bourbaki-6man-classless-ipv6-00

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 02 June 2017 19:35 UTC

Return-Path: <Fred.L.Templin@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 05D46129BB8 for <ipv6@ietfa.amsl.com>; Fri, 2 Jun 2017 12:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 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, T_FILL_THIS_FORM_SHORT=0.01] 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 iC2ll4v_2Y5k for <ipv6@ietfa.amsl.com>; Fri, 2 Jun 2017 12:35:51 -0700 (PDT)
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 7EAC11293E1 for <ipv6@ietf.org>; Fri, 2 Jun 2017 12:35:51 -0700 (PDT)
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 v52JZodl012539; Fri, 2 Jun 2017 12:35:50 -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 v52JZkbF012520 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL) for <ipv6@ietf.org>; Fri, 2 Jun 2017 12:35:46 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-10.nw.nos.boeing.com (2002:8988:efdb::8988:efdb) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 2 Jun 2017 12:35:45 -0700
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Fri, 2 Jun 2017 12:35:45 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
CC: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: draft-bourbaki-6man-classless-ipv6-00
Thread-Topic: draft-bourbaki-6man-classless-ipv6-00
Thread-Index: AQHS26olsSo24MvI90arLJF3XDEOhqISErGAgAAFyYCAAAZ9gIAAE+sA//+ZrfCAAAYWAIAAlQ4A//+MbiA=
Date: Fri, 02 Jun 2017 19:35:45 +0000
Message-ID: <78fe298cb5484d50a56cf6ed4ddafb54@XCH15-06-08.nw.nos.boeing.com>
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <20170602141259.GD30896@gir.theapt.org> <CAKD1Yr0DtQYvCYLQexhXe_nhb5rjeyhnB4bCveqyO5Xbuwdg1A@mail.gmail.com> <20170602145655.msfjw35qhoev4sm2@Vurt.local> <CAKD1Yr3gqFgq3dxFaBEV++q5cgx1AHzFLGRJ50DYJjVE69C7iA@mail.gmail.com> <f2260ee557014429a1fef32de040547b@XCH15-06-11.nw.nos.boeing.com> <d62ce5e3ea0f486eb4c9d54609a86b24@XCH15-06-08.nw.nos.boeing.com> <04bdfdfe018145e6aedbaa62ed6cbfb0@XCH15-06-11.nw.nos.boeing.com>
In-Reply-To: <04bdfdfe018145e6aedbaa62ed6cbfb0@XCH15-06-11.nw.nos.boeing.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ItsOmdhewFG8gjRsSHcQhyDvUzQ>
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: Fri, 02 Jun 2017 19:35:53 -0000

HI Bert,

> -----Original Message-----
> From: Manfredi, Albert E
> Sent: Friday, June 02, 2017 12:17 PM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
> Subject: RE: draft-bourbaki-6man-classless-ipv6-00
> 
> -----Original Message-----
> From: Templin, Fred L
> 
> > When you say "IoT", I think about my cellphone and all of its
> > associated devices. Or, my home router and all of the addressable
> > devices in my home. Giving each of them a /64 then allowing them
> > to portion their /64s internally as they see fit (e.g., subnetting
> > to longer prefixes) would not lead to NAT AFAICT.
> 
> True, Fred, but you have posited "giving each of them a /64,"

My meaning was for the ISP to give the cell phone or home gateway a /64,
then let the cell phone/ home gateway subnet the /64 to the IoT devices
within the subnetwork it provides as it sees fit. (Where I am using the
term "subnetwork" to refer to mobile hotspots, home networks, etc.)
One /64 goes in the ISP's routing system, but countless billions of
addresses/prefixes could be assigned within the subnetwork. There
is no NAT in that picture.

Thanks - Fred

> presumably by your ISP. I'm saying instead, you create a mobile hotspot
> with your smartphone, and your smartphone is only provided with a single /64. Now you need to provide routes to each device
> behind the smartphone, which can be aggregated from the smartphone's /64. Or similarly, any number of IoT devices, each provided
> with a /64, but each of them needing to create multiple subnets.
> 
> No matter what type of privacy or temporary addresses you use, a hard /64 boundary, without a NAT option, will prevent you from be
> able to aggregate routes. Any expansion at the edges would create a flat address space.
> 
> Ultimately, this increasing flat address space will become limiting, IPv6 or not.
> 
> Bert

v2.23.0 | Report a Bug | By Email