Re: 64share v2

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 10 November 2020 21:58 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 93F7F3A1082 for <ipv6@ietfa.amsl.com>; Tue, 10 Nov 2020 13:58:16 -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_H4=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 U7PH0jabhOpQ for <ipv6@ietfa.amsl.com>; Tue, 10 Nov 2020 13:58:15 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 00FAF3A1087 for <ipv6@ietf.org>; Tue, 10 Nov 2020 13:58:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4CW1vV5l70z6G8D1; Tue, 10 Nov 2020 13:58:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1605045494; bh=O2vXXRlnk/86bmpAZBqD0d83XtyO1LkcKiGiY8ke0z0=; h=Subject:To:References:From:Date:In-Reply-To:From; b=A/jzJcfo6Yu0AhaPql09ppYQqLJ/80nmpaTdsQfGg6DSESz6WNYNsZUKo3NlVggl/ ylrCMEwmN/QcyXuZ1adoiSjK9h0BTDTKWHeuaVHM+ltGktyc/AwDaAZajQS/jvSCqv DQqimRmsGp+bCoc74HCR9AG/eiqU/yRJtXmNqC9Y=
X-Quarantine-ID: <dF34vbOo7K7n>
X-Virus-Scanned: Debian amavisd-new at a2.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 maila2.tigertech.net (Postfix) with ESMTPSA id 4CW1vV29ckz6G7qk; Tue, 10 Nov 2020 13:58:14 -0800 (PST)
Subject: Re: 64share v2
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man <ipv6@ietf.org>
References: <CAD6AjGR-NE_sJ_jp7nAT6OvNkcdE9qoWuGEiiVW7r9YtsQvbbw@mail.gmail.com> <43ebd660-3df6-bc9c-2ef3-bbfd72a64229@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <2a671ee3-e9f2-22c1-986b-236a7bdabf66@joelhalpern.com>
Date: Tue, 10 Nov 2020 16:58:12 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.2
MIME-Version: 1.0
In-Reply-To: <43ebd660-3df6-bc9c-2ef3-bbfd72a64229@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GbTpPzi8oJlPQGgFtOUc6BJRzoU>
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: Tue, 10 Nov 2020 21:58:17 -0000

I can't promise what 3GPP will do.  (Heck,< i can't even speak for what 
my employer wants from this.)

But I think it is useful to have the conversation with them.  I have 
talked to some folks involved, and believe that if we come to agreement 
that the change is useful, we could have a good discussion as to whether 
they agree.

Yours,
Joel

On 11/10/2020 4:49 PM, Brian E Carpenter wrote:
> On 10-Nov-20 21:10, Ca By wrote:
>> Folks,
>>
>> In an effort to progress the conversation, i created a simple and rough pre-00 i-d (as ietf is not accepting submissions now) for your review and comment
>>
>> https://pastebin.com/duyYRkzG
> 
> I'm having difficulty reconciling that with what I read at:
> https://mailarchive.ietf.org/arch/msg/v6ops/0d7lSiP_78td3vWBlMnVvmp7UAo/
> 
> If that email is correct, the 3GPP model is tightly bound to
> the /64 boundary and to the notion of giving a single address
> and predefined Interface ID to the UE. Also, since /64
> is still fixed by the addressing architecture, and RA PIOs
> are constrained by that architecture, I don't understand how
> a UE can be "given a prefix such as a /56 using RA".
> 
> Perhaps someone familiar with 3GPP internals, e.g. the authors
> of RFC6459, can comment?
> 
> Regards
>      Brian
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>