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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sat, 03 June 2017 10:15 UTC

Return-Path: <alexandre.petrescu@gmail.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 02638127136 for <ipv6@ietfa.amsl.com>; Sat, 3 Jun 2017 03:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.678
X-Spam-Level: *
X-Spam-Status: No, score=1.678 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 wc7-at4bOxPf for <ipv6@ietfa.amsl.com>; Sat, 3 Jun 2017 03:15:43 -0700 (PDT)
Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [IPv6:2a01:e0c:1:1599::13]) (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 4943B1279EB for <ipv6@ietf.org>; Sat, 3 Jun 2017 03:15:42 -0700 (PDT)
Received: from [192.168.0.26] (unknown [82.229.156.225]) by smtp4-g21.free.fr (Postfix) with ESMTP id 385F319F4F3 for <ipv6@ietf.org>; Sat, 3 Jun 2017 12:15:35 +0200 (CEST)
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> <d3558856-6faf-1d50-870a-c9db1e91e34c@innovationslab.net> <20170603003552.7A0327ADD848@rock.dv.isc.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <5f7b9da2-98e1-dc7d-9441-928fcc3e8075@gmail.com>
Date: Sat, 03 Jun 2017 12:15:35 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170603003552.7A0327ADD848@rock.dv.isc.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/AXxsZaHn8oFC9vNP9yOB-y9YNbs>
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: Sat, 03 Jun 2017 10:15:44 -0000


Le 03/06/2017 à 02:35, Mark Andrews a écrit :
>
> In message <d3558856-6faf-1d50-870a-c9db1e91e34c@innovationslab.net>,
> Brian Hab erman writes:
>> 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
>
> The ISP could give each phone a /48.

Ask an operator, he'd say /56 instead of /48, if at all.  And it would 
be a non-operational specific purpose trial.

Ask another operator, he'd say '64share' everywhere, despite IETF saying 
it's INFORMATIONAL.

Ask an end-user, he'd say operators are difficult, better do NAT.

Alex

> There is NOTHING stopping the ISP giving a /48 today.  IPv6 is sized
> to allow this.  When you stop trying to hand out the minimum and
> start handing out reasonable quantities of subnets the so called
> problems go away.
>
>> 2. The phone delegates longer prefixes to the devices behind it
>> from the /64
>
> The phone then hands out /64's to devices behind it on demand.
>
>> 3. The ISP router has a single /64 route that points to the phone
>
> The ISP's router has a single /48 that points to the phone.
>
>> Regards, Brian
>