Re: 64share v2

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 10 November 2020 15:20 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 C9C113A0039 for <ipv6@ietfa.amsl.com>; Tue, 10 Nov 2020 07:20:56 -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 o6BAATgQmVAp for <ipv6@ietfa.amsl.com>; Tue, 10 Nov 2020 07:20:54 -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 EF4003A1012 for <ipv6@ietf.org>; Tue, 10 Nov 2020 07:20:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4CVs5257lTz1ntWp; Tue, 10 Nov 2020 07:20:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1605021654; bh=YO5i2nsjFMZ+5TXrljR4JbIRT1dJ9aGYRizFLMDt0XY=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=IWT4VIYeef97P15x4BsbEcx8zPGu3wPhkVUe44akCUY9pT2yp5kpznA6eh/nx2P5i P17/mjZKqoQuIaHNa9Hut52IRLGBj6fx2rPtWxofnFUgOF243cVfLTXGgoHXtJ+uK9 s2Sv+2G0lKiulsTUJMDqaL4nL97WUIpA/acp7D6A=
X-Quarantine-ID: <YXnUWO2bEz_A>
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 4CVs520m2cz1ntWm; Tue, 10 Nov 2020 07:20:54 -0800 (PST)
Subject: Re: 64share v2
To: otroan@employees.org
Cc: 6man WG <ipv6@ietf.org>
References: <CAD6AjGR-NE_sJ_jp7nAT6OvNkcdE9qoWuGEiiVW7r9YtsQvbbw@mail.gmail.com> <CAKD1Yr0G8PjzE+pULte_AaOi=RHMLyto-YUQerGjQ=iOYnz+iA@mail.gmail.com> <0986B112-2159-4045-87F9-876B58F1D896@employees.org> <CAKD1Yr0h9=7p+n=qnH1o1EHqtPrsaYebgvHciOJpP3=iXgNgKQ@mail.gmail.com> <0C739112-D8EA-42C3-BEFD-88C014D5BCD0@employees.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <62bc0e56-85b8-42ea-c46b-4f2205dc435f@joelhalpern.com>
Date: Tue, 10 Nov 2020 10:20:53 -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: <0C739112-D8EA-42C3-BEFD-88C014D5BCD0@employees.org>
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/t-v2R18FnAxAXlQkF-rifoXNlp8>
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 15:20:57 -0000

Ole, I do not understand what you are asking.
network A is allocating to rotuer B over a point-to-point link a prefix. 
  (The router might be a 3GPP UE.  It might be a fixed wireless RG. 
Doesn't matter.)
If there is a network behind B, the B can use that prefix for that 
network.  Obviously, if it is multi-hop network and we want to get 
multiple levels of allocation, then other tools are needed.  That was 
the homenet problem.
This approach does not claim to solve the whole homenet problem.  It 
solves a simple and common problem.

Yours,
Joel

On 11/10/2020 5:32 AM, otroan@employees.org wrote:
> Lorenzo,
> 
>> 3GPP networks do have this property. The PIO lifetime in the RA is set to infinite and the actual lifetime is the link lifetime. By and large that seems to work in practice :-)
> 
> It works fine for the directly connected node.
> Now please put a large network behind this link and tell me how that goes...
> 
> Cheers,
> Ole
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>