Re: [v6ops] [Snac] "router cascade with DHCPv6-PD"

Ole Troan <otroan@employees.org> Thu, 02 February 2023 13:25 UTC

Return-Path: <otroan@employees.org>
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 12BC7C14F730 for <v6ops@ietfa.amsl.com>; Thu, 2 Feb 2023 05:25:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=employees.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x5k6oQhgTapV for <v6ops@ietfa.amsl.com>; Thu, 2 Feb 2023 05:25:39 -0800 (PST)
Received: from vesa01.kjsl.com (vesa01.kjsl.com [IPv6:2607:7c80:54:6::11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CAB5C1575B3 for <v6ops@ietf.org>; Thu, 2 Feb 2023 05:24:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=employees.org; i=@employees.org; q=dns/txt; s=vesa202009; t=1675344299; x=1706880299; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=jdtfhQHF1DUo7M5iimtKdYPGTA3YE5/bgqw9X77rBkA=; b=hhNnryH+pR4Cz6EiG8n1VDIA6nLsWm4OgZLztx+2V4ZCZ72m8mufnUIx uxFUjgAJhOa9/sW7cmiM8M96H6B4HHnv5KyPGB5SKtKCoujR2d+oIRwfZ i/ldXZrZquIzxCimFz90Cz47Qn+RpOh9g7LDQyLywAM1sJ1ToN/gYZ88X WLIza1pjXg6vorpDoLiByRkF4069gr190wRWKZIFvJDnFpG4XqIGPaSoV mU40rDAtD4f5LOgIJmTG40Iz8RVINXPW9AlAOAAFsm7VObv3o+FKUdR2t vYHsCIP9pXxzDLzupbTS7mGkdRBkb9Bw04JRmXy+K1An68HRYbheWQYIc w==;
Received: from clarinet.employees.org ([IPv6:2607:7c80:54:3::74]) by vesa01.kjsl.com with ESMTP; 02 Feb 2023 13:24:58 +0000
Received: from smtpclient.apple (77.16.76.216.tmi.telenormobil.no [77.16.76.216]) (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 6F2194E11A6A; Thu, 2 Feb 2023 13:24:56 +0000 (UTC)
From: Ole Troan <otroan@employees.org>
Message-Id: <744C2F4B-DB48-4CB3-983B-C126AAE802D8@employees.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B2EFEB96-ED01-4F6A-82CE-42E231C2D68C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
Date: Thu, 02 Feb 2023 14:24:43 +0100
In-Reply-To: <CAPt1N1k6zeZBFN1a7zOXrC6g9_5kCSY9t_LKqhES2B6n5c2v9A@mail.gmail.com>
Cc: Klaus Frank <klaus.frank@posteo.de>, Gert Doering <gert@space.net>, snac@ietf.org, V6 Ops List <v6ops@ietf.org>, Juliusz Chroboczek <jch@irif.fr>, Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>
References: <Y813Mzn7ucC/YODu@Space.Net> <7EA5E930-4E81-4B79-BBD0-07FACDC5E4B5@employees.org> <Y82U2Sv39Gk9qesd@Space.Net> <729e9054-abcd-5c41-8db8-9b295f36cd05@posteo.de> <CAPt1N1k6zeZBFN1a7zOXrC6g9_5kCSY9t_LKqhES2B6n5c2v9A@mail.gmail.com>
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/GAVgnlCW6JGErWpVUY_4ZTh5ivo>
Subject: Re: [v6ops] [Snac] "router cascade with DHCPv6-PD"
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 02 Feb 2023 13:25:44 -0000

Ted,

Exactly!

> I don't know how you do stable prefix assignment to subnets with NDP/ICMP. I'm sure you could, but how much different than PD would it be at that point?

The original prefix delegation proposal did exactly that:
https://datatracker.ietf.org/doc/html/draft-haberman-ipngwg-auto-prefix-02

And the observation was then “this looks just like DHCP, why not use that?”

O.


> 
> On Thu, Feb 2, 2023 at 12:22 AM Klaus Frank <klaus.frank@posteo.de <mailto:klaus.frank@posteo.de>> wrote:
>> I agree, with that. And tbh, I personally think introducing DHCPv6-PD at 
>> all was a conceptional mistake. It's duties should have been carried out 
>> by ICMPv6 and NDP...
>> 
>> Also there is no real alternative for environments with dynamically 
>> assigned prefixes or where clients are roaming between networks and need 
>> a delegated prefix locally for e.g. Docker or VMs... Except for "use 
>> DHCPv6-PD to get the prefix, run a DIY script to update configuration 
>> files and restart radvd and/or bird..."
>> 
>> On 22.01.2023 20:56, Gert Doering wrote:
>> > DHCPv6-PD seems to be a half-finished routing protocol already, and trying to
>> > wiggle around admitting it.
>> >
>> > Gert Doering
>> >          -- NetMaster
>> >
>> > _______________________________________________
>> > v6ops mailing list
>> > v6ops@ietf.org <mailto:v6ops@ietf.org>
>> > https://www.ietf.org/mailman/listinfo/v6ops
>> -- 
>> Snac mailing list
>> Snac@ietf.org <mailto:Snac@ietf.org>
>> https://www.ietf.org/mailman/listinfo/snac