Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?

otroan@employees.org Fri, 27 November 2020 17:51 UTC

Return-Path: <otroan@employees.org>
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 0CAAE3A0AE5 for <ipv6@ietfa.amsl.com>; Fri, 27 Nov 2020 09:51:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 R5BmP-JHlKk9 for <ipv6@ietfa.amsl.com>; Fri, 27 Nov 2020 09:51:34 -0800 (PST)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDA233A0AD5 for <ipv6@ietf.org>; Fri, 27 Nov 2020 09:51:34 -0800 (PST)
Received: from astfgl.hanazo.no (201.51-175-101.customer.lyse.net [51.175.101.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 251314E11AD8; Fri, 27 Nov 2020 17:51:33 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 467A9463CB36; Fri, 27 Nov 2020 18:51:31 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
Subject: Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?
From: otroan@employees.org
In-Reply-To: <m1kigqX-0000ETC@stereo.hq.phicoh.net>
Date: Fri, 27 Nov 2020 18:51:30 +0100
Cc: 6man WG <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2BB24C1-F529-4712-AF8D-F0CE62066BC7@employees.org>
References: <m1kiLjK-0000EaC@stereo.hq.phicoh.net> <7BB64BE0-6A62-4711-91E4-1393EDC0809E@employees.org> <m1kiaW6-0000IFC@stereo.hq.phicoh.net> <5EB013E0-CC25-42AB-B5EF-3DBC82782B44@employees.org> <m1kidK6-00001eC@stereo.hq.phicoh.net> <965999C8-31C2-415C-9AB7-0B8129918BB9@employees.org> <m1kigqX-0000ETC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>
X-Mailer: Apple Mail (2.3654.20.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/MwqXNsSt9VTDUt9GWiNBXHCJ1hY>
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: Fri, 27 Nov 2020 17:51:36 -0000

Philip,

>> Can you please write a draft explaining how it is supposed to work?
>> And if it is true as you say that it is currently implemented and
>> deployed, what implementations support that, how do the topologies
>> look like etc? I work for a reasonably large vendor I can guarantee
>> you that we have not implemented support for ephemeral addressing.
>> ;-)
> 
> Maybe we are talking about different things.
> 
> What I'm talking about if that applications on phones keep working even if
> the phone witch between mobile and wifi connections or moves from one
> wifi to the next.
> 
> Similarly laptops can move from one wifi to the next. VM running on a laptop
> can be taken from one wifi to the next and keep working, etc.
> 
> Nobody expects to reboot a phone or laptop just because you connect to another
> wifi. In the case of the VMs running on my laptop, they are bridged, so they
> pick up new addresses even though there connections stay up.
> 
> Now the question is we can also make this work for prefixes. Can I give
> my VMs a separate prefix and expect that to be updated as I move around.
> 
> If vendors of network equipment don't care about this, then there is always
> IPv4 and NAT. Or maybe IPv6 and NAT.

For the case you cite IPv4 NAT would work equally well.

This started with a discussion how to support multiple links (i.e. more than a single /64).
We are the IETF and have a responsibility to solve the general problem.
A site with an arbitrary topology. Can you now please describe your solution?

Best regards,
Ole