IETF Logo Mail Archive

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

Nick Hilliard <nick@foobar.org> Fri, 27 November 2020 10:16 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 829143A1593 for <ipv6@ietfa.amsl.com>; Fri, 27 Nov 2020 02:16:52 -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 LI9t-pC1ATuN for <ipv6@ietfa.amsl.com>; Fri, 27 Nov 2020 02:16:49 -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 6C2193A1590 for <ipv6@ietf.org>; Fri, 27 Nov 2020 02:16:44 -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 0ARAGfI6095851 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Nov 2020 10:16:42 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: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>
Cc: ipv6@ietf.org
References: <m1kiLjK-0000EaC@stereo.hq.phicoh.net> <7BB64BE0-6A62-4711-91E4-1393EDC0809E@employees.org> <m1kiaW6-0000IFC@stereo.hq.phicoh.net>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <074a3f13-732a-a495-9a6f-5d2c2e1d7961@foobar.org>
Date: Fri, 27 Nov 2020 10:16:40 +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: <m1kiaW6-0000IFC@stereo.hq.phicoh.net>
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/tsADnZNYAq6M66pQdrslDblm-a4>
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 10:16:52 -0000

Philip Homburg wrote on 27/11/2020 09:58:
>> Lets ask the question differently. Would RS/RA be a good protocol
>> for address assignment?
> 
> RA is widely used for SLAAC. Though SLAAC has a few renumbering issues.
> 
> On the other hand, in the mode DHCPv6 PD is commonly used, it is a bad protocol.

You can't run a flexible address assignment protocol without a 
provisioning database. ND is typically implemented in o/s kernels, so 
interfacing this with user-mode radius is architecturally troublesome.

As a separate issue, adding this level of complexity also goes against 
many of the design principals that ND was intended to fulfil.  It could 
be argued that these principals are already being infringed on, but a PD 
extension would take this several steps further.

Nick

v2.23.0 | Report a Bug | By Email