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

David Farmer <farmer@umn.edu> Wed, 24 July 2024 03:10 UTC

Return-Path: <farmer@umn.edu>
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 C9B5AC19330B for <v6ops@ietfa.amsl.com>; Tue, 23 Jul 2024 20:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=umn.edu
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 2HWtL6ikpf5M for <v6ops@ietfa.amsl.com>; Tue, 23 Jul 2024 20:10:20 -0700 (PDT)
Received: from mta-p5.oit.umn.edu (mta-p5.oit.umn.edu [134.84.196.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8541C15108A for <v6ops@ietf.org>; Tue, 23 Jul 2024 20:10:18 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p5.oit.umn.edu (Postfix) with ESMTP id 4WTJt154Fcz9vYnR for <v6ops@ietf.org>; Wed, 24 Jul 2024 03:10:17 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p5.oit.umn.edu ([127.0.0.1]) by localhost (mta-p5.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MnIglbJZVhXK for <v6ops@ietf.org>; Tue, 23 Jul 2024 22:10:17 -0500 (CDT)
Received: from mail-lj1-f197.google.com (mail-lj1-f197.google.com [209.85.208.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p5.oit.umn.edu (Postfix) with ESMTPS id 4WTJt10ytRz9vYnL for <v6ops@ietf.org>; Tue, 23 Jul 2024 22:10:17 -0500 (CDT)
DMARC-Filter: OpenDMARC Filter v1.3.2 mta-p5.oit.umn.edu 4WTJt10ytRz9vYnL
DKIM-Filter: OpenDKIM Filter v2.11.0 mta-p5.oit.umn.edu 4WTJt10ytRz9vYnL
Received: by mail-lj1-f197.google.com with SMTP id 38308e7fff4ca-2ef233fb86bso43273361fa.1 for <v6ops@ietf.org>; Tue, 23 Jul 2024 20:10:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; t=1721790614; x=1722395414; 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=OHFsge5Qy5QB9FRFdX4p2N2BA8MqQgBBkkRc3B1E8Wg=; b=TlSVDRVAbYoY/ZW03VaGoi5EAY50PX3L8j4HC846vchmnhUEAmT8m6q3uUEAjsqT/u 6llYDcuhY7gkR+ypcJJI0te8oXNg8p7LAa4UijPyR6YtPPUdm8YktW8vhhRwgJSl6WSn jsdz67UAvXnZjl3yQHwMlr7CL999JbJN9LSfXW1YIntp+LbrumKGkfwGbu/xse6Yk145 PLh6XnBgWKje9AH6K+i8dCFqwiLvRttu35QoDYT4Pubzo0ARPwOkkCyB8tBAxTPY4QCU 0pp2lImYCYPJl8xWY94KjsRNCrm2ZypTBO6tWgVfJoBnRdeuvKmCKFsEyIeM5+2qDIPw W66g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721790614; x=1722395414; 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=OHFsge5Qy5QB9FRFdX4p2N2BA8MqQgBBkkRc3B1E8Wg=; b=DPhWbPf8EeSfm/E6aNQ+M4yyJ270m+bNIl4fy1kVSqy9THVaVmbs4mmukndNEeFiPb CRUzEnWvSSryTjviR5D6drZCUBuicvJwvGVwDv83Hdn9MaCJefSzdeqm6P7GLWUhOStl 30ij4MNqzIDaKPsM+8b0QZ4Fgn04HC4x/zga5tL8gk/EAuE9inNqawJo82dqmBlJqlyh +Xpi2R6O9/X641cQ4Z88ZRIW7JzoZBSxYF8Dh4txfBTIRvP/uVZTlfVPKgHGtQL9MqMF uXRZjTse+3OMsw1ZElR7tos3Qu91xdbDJM0xFFj2Ms0w8tqJlyZrBp5T4WcjjJ1bXSaC GdXQ==
X-Gm-Message-State: AOJu0YySwQ0SBoA81O07dbwWZRoPlrzo5NelIca0T3/BTvDugwjVj09i vO2Iqv/K8Wde24khCyMM/emoCWItWzZ7TmTvkNBfvHFYOnQX+vl1nfzh1O8KDJ3RftdLEvhllmi f4ZPQv+qSIhocdYiqTRbtChTpkMKWQ7Ylj1j8tD96rqJOQEhgiOaxMTuagbxZV9L1ONXI9qMHgM a8JcH1nPZDKeqdoICvtn0LI/J/2yzOiw==
X-Received: by 2002:a2e:9103:0:b0:2ef:2ba5:d214 with SMTP id 38308e7fff4ca-2f02b6f96eemr13333361fa.4.1721790614485; Tue, 23 Jul 2024 20:10:14 -0700 (PDT)
X-Google-Smtp-Source: AGHT+IHi9r/cg5n1T9f5/A8cXIMeS3K1116pE5YxcAwBk52F6rg8x5dx+o/cXkxthZJv6aMGLLqzZwxZbFPeIFKwNas=
X-Received: by 2002:a2e:9103:0:b0:2ef:2ba5:d214 with SMTP id 38308e7fff4ca-2f02b6f96eemr13333211fa.4.1721790613998; Tue, 23 Jul 2024 20:10:13 -0700 (PDT)
MIME-Version: 1.0
References: <CAN-Dau1tRp02p58O8RKcCAVeXKqnkJt_b14KM5iCcDTm4JmnGQ@mail.gmail.com> <CAPt1N1ntZmL47HH-zkryVey6NmzEenKfBzZ90hcUQaduZV3sLw@mail.gmail.com> <CAN-Dau1udnxJTWWknwwTjzTa7cQejoE0qcVk94u5ijd3RaBXrw@mail.gmail.com> <CAPt1N1mEPLo6BN6=xLd7r+WJ7PiNhjW3GtUboZtTBZeU6dy-0Q@mail.gmail.com>
In-Reply-To: <CAPt1N1mEPLo6BN6=xLd7r+WJ7PiNhjW3GtUboZtTBZeU6dy-0Q@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Tue, 23 Jul 2024 22:09:57 -0500
Message-ID: <CAN-Dau0icgiM5+9_KYhEiaKwfRD2tUcA9qSpC=R5sVgSecRcGQ@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="000000000000ecf082061df59da6"
Message-ID-Hash: WJUQZZTJXCVVZEOOR33LFXC3BHHJD7OE
X-Message-ID-Hash: WJUQZZTJXCVVZEOOR33LFXC3BHHJD7OE
X-MailFrom: farmer@umn.edu
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/EedTqR7WpBEIBFa8Bibr4mXeH7I>
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>

So, are you saying the SNAC router should use a GUA prefix in all cases and
expose the IOT devices to the Global Internet?

On Tue, Jul 23, 2024 at 9:55 PM Ted Lemon <mellon@fugue.com> wrote:

> 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
>> ===============================================
>>
>

-- 
===============================================
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
===============================================