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

Nick Hilliard <nick@foobar.org> Fri, 27 November 2020 11:24 UTC

Return-Path: <nick@foobar.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 1467C3A08BB for <ipv6@ietfa.amsl.com>; Fri, 27 Nov 2020 03:24:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, 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 eeMTn9k8xThu for <ipv6@ietfa.amsl.com>; Fri, 27 Nov 2020 03:24:54 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [46.182.8.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F3F83A08B1 for <ipv6@ietf.org>; Fri, 27 Nov 2020 03:24:53 -0800 (PST)
X-Envelope-To: ipv6@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 0ARBOmjX004656 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Nov 2020 11:24:49 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Subject: Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?
To: Lorenzo Colitti <lorenzo@google.com>
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
References: <m1kiLjK-0000EaC@stereo.hq.phicoh.net> <7BB64BE0-6A62-4711-91E4-1393EDC0809E@employees.org> <m1kiaW6-0000IFC@stereo.hq.phicoh.net> <074a3f13-732a-a495-9a6f-5d2c2e1d7961@foobar.org> <CAKD1Yr01KFF47DgCx69E487_E_ZoNCMqoK-K9N-4uYXcnPDOvQ@mail.gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <a3500368-5244-567b-9825-2b051062563e@foobar.org>
Date: Fri, 27 Nov 2020 11:24:47 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.39
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr01KFF47DgCx69E487_E_ZoNCMqoK-K9N-4uYXcnPDOvQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/IYefZpK6moO7tc81DUyWky24M-A>
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 11:24:56 -0000

Lorenzo Colitti wrote on 27/11/2020 10:19:
> I don't think that's the case. I'm sure there are residential broadband 
> deployments that use Framed-Ipv6-Prefix radius attribute to assign the 
> directly-connected IPv6 prefix to the customer. I once designed a 
> network like that many years ago, and the BNGs at that time already 
> supported it.

No doubt this functionality exists somewhere - with sufficient thrust, 
pigs fly just fine.

Nick