Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 09 November 2020 15:17 UTC

Return-Path: <jmh@joelhalpern.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 08D933A1128; Mon, 9 Nov 2020 07:17:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 kgvl5QJ0NANX; Mon, 9 Nov 2020 07:17:02 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 2F85A3A0B2E; Mon, 9 Nov 2020 07:16:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4CVF2w6rCtz1nsT6; Mon, 9 Nov 2020 07:16:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1604935016; bh=+TqbCMOhdGCt/xvhLu6ZBNHcl1lYpvrdyeaLp1C88Cs=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=knhhJOTzbRmxzYZKc+AT60DEWLP1oN5POIHnutZoNELgrP+8BcLhLfd/cm8tClWNz 1Iv4FuaU1pcV5S15hCLFMTH83XGrG+TtqkicjGTjN5u+8Vag0BFwl9nPH2An1Ciy0H dw3cQvN0/0FZaVPSny32BeqMHL3cCs0qlGBoy9a0=
X-Quarantine-ID: <OG04GDZJVeEt>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4CVF2w0h88z1nsNY; Mon, 9 Nov 2020 07:16:56 -0800 (PST)
Subject: Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: draft-mishra-6man-variable-slaac@ietf.org, 6man WG <ipv6@ietf.org>
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <3c1c3ab5-5726-b141-e7ed-618984bbbdb1@gmail.com> <CABNhwV1zoZpZNjb54rEys4+49H3vpebZW2g9JbO1_58eR+WnQg@mail.gmail.com> <CAKD1Yr0vvyQnTGRoSh4qa4He1gq5HXXRaKU3pVLtCtDUzcwL_w@mail.gmail.com> <CAD6AjGQPatbg5=OaMzxJXy5mGZai1bqLfg8f+9SUnfg=s1kADg@mail.gmail.com> <FE260932-A064-493E-8CD5-D92B2725F9E6@employees.org> <CAD6AjGRXYqJhXL6ipbS_cWkE2mg3sU4tM5XCCvgiGvSALGfeeg@mail.gmail.com> <e7938c0f-758c-1f90-814a-46f8b262a134@gmail.com> <4f6d39bc-c7cb-fd44-dcef-1bab3f08a567@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <73972cc3-f0fc-a604-dfea-8a1df9c8e18f@joelhalpern.com>
Date: Mon, 09 Nov 2020 10:16:54 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.1
MIME-Version: 1.0
In-Reply-To: <4f6d39bc-c7cb-fd44-dcef-1bab3f08a567@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8mHfodQ4Q9l7B37oNfyUJNptPxo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 09 Nov 2020 15:17:04 -0000

It is clear to me that any solution will require changes on the UE / RG 
as well as in the ISP infrastructure.

If we take as an assumption that we want this to work without DHCP, then 
we presumably are changing RAs.
At that point,  the question I see is whether it is cleaner to specify 
how this works (maybe with an extra flag) using an RA to allocate a /56 
to the UE, or whether it is cleaner to change the rules to allow 
sub-allocation from /64 and change the RA to have bits indicating when 
the UE is doing that.
It seems to me that the former is MUCH cleaner than the later.

Yours,
Joel

On 11/9/2020 4:34 AM, Alexandre Petrescu wrote:
> 
> 
> Le 09/11/2020 à 02:25, Brian E Carpenter a écrit :
>> On 09-Nov-20 13:00, Ca By wrote:
>>>
>>>
>>> On Fri, Nov 6, 2020 at 1:05 AM <otroan@employees.org 
>>> <mailto:otroan@employees.org>> wrote:
> [...]
>> Just handing out a /56 to each PDP context would be so much better.
> 
> Sounds reasonable because a /56 is so much space, and can make several 
> /64s.
> 
> But still, it would not be enough.  How would the smartphone form an
> IPv6 address when receiving a /56 in the RA?  There is no spec that
> tells it how to, because the IID must be 64bit and the smartphone would
> not know how to pad the remaining 8 bits.
> 
> At that point the operator might want to put a /64 in an RA and also
> respond to DHCPv6-PD with a /56 inside.  It would be a double address
> architecture effort.
> 
> This is why I am wondering how would one think the smartphone would be
> happy enough when receiving a /56 in a DHCPv6 advertisement.
> 
> Alex
> 
>>
>> Brian
>>
>>>
>>> None of that exists today in mobile. I feel the effort and scale are 
>>> daunting, so i am not going to do it.
>>>
>>> But, getting a knob in the gateway to set the RA to be 60 (or other) 
>>> instead of 64 would be easy. And, that knob could be constrained to 
>>> only compatible device type (chef’s kisses!)... it can be done
>>>
>>>
>>>
>>> Best regards, Ole
>>>
>>>
>>> --------------------------------------------------------------------
>>>
>>>
>>>
>>>
> IETF IPv6 working group mailing list
>>> ipv6@ietf.org Administrative Requests: 
>>> https://www.ietf.org/mailman/listinfo/ipv6 
>>> --------------------------------------------------------------------
>>>
>>
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------