Re: [v6ops] [E] New Version Notification for draft-mishra-v6ops-variable-slaac-problem-stmt-01.txt

Philip Homburg <pch-v6ops-9@u-1.phicoh.com> Tue, 03 November 2020 12:02 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48DB63A08AB for <v6ops@ietfa.amsl.com>; Tue, 3 Nov 2020 04:02:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 P91r_kmNmtKP for <v6ops@ietfa.amsl.com>; Tue, 3 Nov 2020 04:02:37 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFC693A083F for <v6ops@ietf.org>; Tue, 3 Nov 2020 04:02:35 -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 m1kZv1E-0000HJC; Tue, 3 Nov 2020 13:02:32 +0100
Message-Id: <m1kZv1E-0000HJC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-9@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <160409793214.22613.15041785352190993395@ietfa.amsl.com> <CAJhXr98mPsopQrUiKfXGuN+wxSEtNiP00LBEGrYObz62FHSa_Q@mail.gmail.com> <CABNhwV1LTcVKobDpiEjnxqKbX9drz1od+RNg7EdX_WO04JQgUw@mail.gmail.com> <49DFF195-CB76-4575-BA29-F134F99D6EE1@gmail.com> <CAKD1Yr2tUg7GZcne1SkgZZYHJ3Prr=F3hMRDTAZ2=H+UgK2FWg@mail.gmail.com> <48D68317-0DB0-4FAA-8CB5-D23F7B9245D1@gmail.com> <A9B8FDDC-01B0-4523-99AC-47A6868767F1@employees.org>
In-reply-to: Your message of "Mon, 2 Nov 2020 14:49:59 +0100 ." <A9B8FDDC-01B0-4523-99AC-47A6868767F1@employees.org>
Date: Tue, 03 Nov 2020 13:02:31 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/CuAArSCLODhpPE21A-ORv-v3f6s>
Subject: Re: [v6ops] [E] New Version Notification for draft-mishra-v6ops-variable-slaac-problem-stmt-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2020 12:02:38 -0000

>While the draft has a particular solution in mind, I wouldn't mind discussing 
>the problems the draft enumerates.

I'm curious why existing mechanisms for distributing prefixes are not enough.

On landlines we have a very successful deployment of DHCPv6 IA_PD. We have
homenet for distributing prefixes within a site (and for simple cases, nested
DHCPv6 IUA_PD works as well).

We have RIR policies that allow sites to get a /48, also for individual
consumers.

So why then have people problems giving each subnet its own /64?

- Is this a protocol issue?
- Is a technical issue? (equipment that doesn't support prefix delegation)
- Is it economical and if so where? RIR fees, cost of equipment, support, etc.

For example, if customers of 5G mobile need to have multiple subnets behind
the mobile link, why do the mobile telcos only provide a /64?

Why does the draft list a home network as a problem (Section 4.4)? Is this
for the rare case that the upstream ISP doesn't support DHCPv6 IA_PD?

Somehow the draft completely fails to mention DHCP prefix delegation. Which
is weird because it is the main mechanism for provides sites with enough
space to number the sites' subnets.