IETF Logo Mail Archive

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

Brian Haberman <brian@innovationslab.net> Fri, 02 June 2017 20:13 UTC

Return-Path: <brian@innovationslab.net>
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 D1BB8124BE8 for <ipv6@ietfa.amsl.com>; Fri, 2 Jun 2017 13:13:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.009
X-Spam-Level:
X-Spam-Status: No, score=0.009 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 flPkTwowg9PD for <ipv6@ietfa.amsl.com>; Fri, 2 Jun 2017 13:13:39 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B95B61201FA for <ipv6@ietf.org>; Fri, 2 Jun 2017 13:13:39 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 8C19D880E7 for <ipv6@ietf.org>; Fri, 2 Jun 2017 13:13:39 -0700 (PDT)
Received: from clemson.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 5A7943280AE4 for <ipv6@ietf.org>; Fri, 2 Jun 2017 13:13:39 -0700 (PDT)
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
To: ipv6@ietf.org
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> <78fe298cb5484d50a56cf6ed4ddafb54@XCH15-06-08.nw.nos.boeing.com> <6bba4c2b58964787860f2c7acf130959@XCH15-06-11.nw.nos.boeing.com>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <d3558856-6faf-1d50-870a-c9db1e91e34c@innovationslab.net>
Date: Fri, 02 Jun 2017 16:13:31 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <6bba4c2b58964787860f2c7acf130959@XCH15-06-11.nw.nos.boeing.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="mx4F1cxRGW5uFNFXs2UBw9sqbK1HELw4L"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8sdg3P7mKHBvAwqJgM6YByOZoWk>
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 20:13:41 -0000

Hi Bert,

On 6/2/17 4:03 PM, Manfredi, Albert E wrote:
> -----Original Message-----
> From: Templin, Fred L 
> 
>> 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.
> 
> Sorry, I have to make an important correction:
> 
> Presumably, using some sort of internal address format, also /64, such as privacy addresses? Yes, true, but ...

I interpreted Fred's proposal as:

1. ISP gives the phone a /64

2. The phone delegates longer prefixes to the devices behind it from the /64

3. The ISP router has a single /64 route that points to the phone

Regards,
Brian

v2.23.0 | Report a Bug | By Email