[v6ops] Re: DHCPv6 PD in a multi-prefix environment

Ted Lemon <mellon@fugue.com> Wed, 24 July 2024 02:56 UTC

Return-Path: <mellon@fugue.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 14F92C18DB9E for <v6ops@ietfa.amsl.com>; Tue, 23 Jul 2024 19:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20230601.gappssmtp.com
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 lSWRc8m-SCtI for <v6ops@ietfa.amsl.com>; Tue, 23 Jul 2024 19:55:59 -0700 (PDT)
Received: from mail-oa1-x30.google.com (mail-oa1-x30.google.com [IPv6:2001:4860:4864:20::30]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B23FC151075 for <v6ops@ietf.org>; Tue, 23 Jul 2024 19:55:59 -0700 (PDT)
Received: by mail-oa1-x30.google.com with SMTP id 586e51a60fabf-260e6dfc701so3536384fac.3 for <v6ops@ietf.org>; Tue, 23 Jul 2024 19:55:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20230601.gappssmtp.com; s=20230601; t=1721789758; x=1722394558; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=AdtsdASG1m4CnA9DfjlAeF43jlsf1UT6cQqOUwYgUUk=; b=aBNl+Kv24QwADphyj3xUMwnCEZcNNWuCCR9JN8F3g5tI2i88CqIUoV5NhRVyImNX+x NAM3qtjGr0M7Q92vLqIpXrYAPw8nurZrfdS495rjgYQ+NU+Dvr7Dr7Zj8+6T2SyHg3Jl Cpwgf3ZvfCNFXYM+gWzenDlEJS7kVIn/6Kr2qckcspqSuPeVVJGrVF5mM0D9v7ubvabm KuC0m2PqYYJoS28xZuf8WcSN4unmAXJA7pnvTjZgWjJJhqay5KplcQ8Bcvnar2asiDh+ 15wF58CW8TmypZFlqWQL9AtBGwu1RyoHkc8f/J9srAfCuVMhnPxJB718dmaAFv+yxdZu hMiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721789758; x=1722394558; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=AdtsdASG1m4CnA9DfjlAeF43jlsf1UT6cQqOUwYgUUk=; b=eJ4W4uqXgF7ijFofC9XRpQh2KptpLFSBwOen09+YNne/Q1Rakfj7jwEUD/9iOxnqjX wig8FdG0RImbtRnzWnHp38n8/ZEgLEREEmZ+BnUlE684CsCWG7dhvQtSTT2qeOXoaEDu mrNkNjHESCdrWeRkoTXOkfZzpdeVgvm/OxJpbruYj+jcRPYI/Cer5eDdxNKyUsc1ZTzT vPpyf+0JjmpeZP8T5q6+b08EEnZCb4PGpTgtskFSDFJEg6r/rmRCxzQ5gxFLFwLV+2Gg fT3gfpDB741KojeKtO+/EVE1xlD60Z1WG8ulhWCBMyKO8zKGqg6xIKCv5YhAsWIunqRc mhUw==
X-Gm-Message-State: AOJu0Yxg7oWn9ROdUDZ6vZWmbuwhWabcRXkCICKPA0eNJoV5CMEW4888 9OInT70ErsgZnnJjbMI5R/HAGvSNbTJF7QrhHRth7v/u5FcVbqZm+yJ3QfFzQBVoUy6N7MibzMc QDW+4hckhg2IcNEMmA3j5LW0bCwLeKnjQzlGEtA==
X-Google-Smtp-Source: AGHT+IGvf9v11RMDsgkKo8+iZDqR5PJpCbQ3evKfUQEGcHl8FnK/BWWnBXhD90Uhs0G5ZfOd0dhC0KIYRlcF8kJajLA=
X-Received: by 2002:a05:6871:825:b0:25e:19fe:f240 with SMTP id 586e51a60fabf-2648c9c4df5mr878125fac.9.1721789758028; Tue, 23 Jul 2024 19:55:58 -0700 (PDT)
MIME-Version: 1.0
References: <CAN-Dau1tRp02p58O8RKcCAVeXKqnkJt_b14KM5iCcDTm4JmnGQ@mail.gmail.com> <CAPt1N1ntZmL47HH-zkryVey6NmzEenKfBzZ90hcUQaduZV3sLw@mail.gmail.com> <CAN-Dau1udnxJTWWknwwTjzTa7cQejoE0qcVk94u5ijd3RaBXrw@mail.gmail.com>
In-Reply-To: <CAN-Dau1udnxJTWWknwwTjzTa7cQejoE0qcVk94u5ijd3RaBXrw@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 23 Jul 2024 19:55:21 -0700
Message-ID: <CAPt1N1mEPLo6BN6=xLd7r+WJ7PiNhjW3GtUboZtTBZeU6dy-0Q@mail.gmail.com>
To: David Farmer <farmer@umn.edu>
Content-Type: multipart/alternative; boundary="000000000000e7dd2a061df56a58"
Message-ID-Hash: OD77UAMHTZ3IHQIOMYOMCBQXJFVHZAC3
X-Message-ID-Hash: OD77UAMHTZ3IHQIOMYOMCBQXJFVHZAC3
X-MailFrom: mellon@fugue.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: V6 Ops List <v6ops@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [v6ops] Re: DHCPv6 PD in a multi-prefix environment
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/uB_bGDuwaXS0Px2474T_AhP8tGo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>

No, I mean can you describe a real-world scenario where this would happen.
I get that you could configure a DHCP server to do this. The question is,
when would someone configure the DHCP server that way?

On Tue, Jul 23, 2024 at 7:49 PM David Farmer <farmer@umn.edu> wrote:

> I already did scenario A.3 in draft-ietf-snac-simple. It is appropriate
> for the SNAC router to obtain a ULA prefix instead of a GUA prefix to
> reduce the attack surface of the IOT devices.
>
> On Tue, Jul 23, 2024 at 9:33 PM Ted Lemon <mellon@fugue.com> wrote:
>
>> Can you give us an example of a situation where such a decision would
>> need to be made?
>>
>> On Tue, Jul 23, 2024 at 6:48 PM David Farmer <farmer=
>> 40umn.edu@dmarc.ietf.org> wrote:
>>
>>> The classic ISP use case for DHCPv6 PD, as envisioned initially by
>>> RFC3633 and integrated into RFC8415, typically expected a single prefix to
>>> be delegated to a requesting router from the ISP. Meanwhile, many of the
>>> draft-ietf-v6ops-cpe-lan-pd use cases probably expect a subdelegation from
>>> this ISP provided prefix. Nevertheless, an RFC7084 CE Router may also have
>>> a ULA prefix to subdelegate from, and a ULA prefix may be more appropriate
>>> for some of the use cases. Not to mention, there may be prefixes from more
>>> than one ISP or additional prefixes while renumbering.
>>>
>>> Should the delegating router in draft-ietf-v6ops-cpe-lan-pd advertise
>>> subdelegations from all prefixes it may have and let the requesting router
>>> choose one or more? How does the requesting router know which prefixes it
>>> is appropriate to select in what circumstances? If the delegating router
>>> doesn't advertise subdelegations from all prefixes, how does it know which
>>> prefixes to advertise to which requesting routers?
>>>
>>> You can also ask the question from the opposite direction: How does the
>>> requesting router solicit for a ULA prefix instead of a GUA prefix if that
>>> is more appropriate for its use case?
>>>
>>> These questions came to mind while reading draft-ietf-snac-simple, as it
>>> would seem reasonable to want the SCAC router to obtain a ULA prefix from
>>> the delegating router and not a GUA prefix, especially in the scenario
>>> described in A.3. However, similar questions exist for downstream RFC7084
>>> or PD-per-device in a multi-prefix environment.
>>>
>>> Thanks.
>>> --
>>> ===============================================
>>> David Farmer               Email:farmer@umn.edu
>>> Networking & Telecommunication Services
>>> Office of Information Technology
>>> University of Minnesota
>>> 2218 University Ave SE        Phone: 612-626-0815
>>> Minneapolis, MN 55414-3029   Cell: 612-812-9952
>>> ===============================================
>>> _______________________________________________
>>> v6ops mailing list -- v6ops@ietf.org
>>> To unsubscribe send an email to v6ops-leave@ietf.org
>>>
>>
>
> --
> ===============================================
> David Farmer               Email:farmer@umn.edu
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: 612-626-0815
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================
>