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

Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com> Fri, 27 November 2020 10:13 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 149D73A1591 for <ipv6@ietfa.amsl.com>; Fri, 27 Nov 2020 02:13:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 Pc_i77p-VtFE for <ipv6@ietfa.amsl.com>; Fri, 27 Nov 2020 02:13:06 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97AAE3A1593 for <ipv6@ietf.org>; Fri, 27 Nov 2020 02:13:06 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1kiakS-0000KMC; Fri, 27 Nov 2020 11:13:04 +0100
Message-Id: <m1kiakS-0000KMC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Cc: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?
From: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <CABNhwV2-dH81CY4wSisV8BU-7H9m5a1xYMqTMecRxhNqZe=ApQ@mail.gmail.com> <CAKD1Yr1xV179LZ7Kxtk5mGruJcJ+BpGb2heBBy4ORtRU7bfvqw@mail.gmail.com> <CAMGpriWqnmL0qo0Hm=b+GbzcdCuXz6PM5aq8owE7-=ty5pDFsw@mail.gmail.com> <1DB65027-BEF2-4C0A-ACF4-C979DA7444C2@employees.org> <m1khXWs-00007wC@stereo.hq.phicoh.net> <47150D97-27D7-4AFD-8418-692D68D09828@employees.org> <m1khXol-0000MEC@stereo.hq.phicoh.net> <BD254B32-FAAE-4433-9CF5-2AF19275CA96@employees.org> <87b38a166eac450db943e005611974bf@huawei.com> <m1khZRX-00001XC@stereo.hq.phicoh.net> <27311.1606325147@localhost> <m1kiFrc-0000ETC@stereo.hq.phicoh.net> <28088.1606410874@localhost> <m1kiLjK-0000EaC@stereo.hq.phicoh.net> <1581.1606436160@localhost>
In-reply-to: Your message of "Thu, 26 Nov 2020 19:16:00 -0500 ." <1581.1606436160@localhost>
Date: Fri, 27 Nov 2020 11:13:03 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/e8m8kO2YaECOtj5_TJ3yO8n_jv4>
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:13:08 -0000

>None of that matters over PPP.
>It's a trivial request/response protocol in that case.
>No relays required if all the data comes from radius data as is often the
>case for BMS (DSL, PPPoE).

DHCP is far from trivial. There are all kinds of issues. Having to repopulate
FIB entries in a magic ways after a reboot of a router because the
downstream router believes it still has a valid lease.

Alternativly, we can leave it to the client to deal with that. Requiring the
client to have a reliable link state detector. Which can fail because people
relay packets in weird ways.

Another example is when user swaps CPEs and the new CPE doesn't get a lease
because the lease is still assigned to the old CPE.

Client side, there is a lot of protocol that is specified that is hardly used.