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

Ted Lemon <mellon@fugue.com> Wed, 24 July 2024 14:40 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 F2F57C180B50 for <v6ops@ietfa.amsl.com>; Wed, 24 Jul 2024 07:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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 LkekZqChCVaj for <v6ops@ietfa.amsl.com>; Wed, 24 Jul 2024 07:40:29 -0700 (PDT)
Received: from mail-oa1-x2b.google.com (mail-oa1-x2b.google.com [IPv6:2001:4860:4864:20::2b]) (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 730CEC169431 for <v6ops@ietf.org>; Wed, 24 Jul 2024 07:40:29 -0700 (PDT)
Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-250ca14422aso3621891fac.0 for <v6ops@ietf.org>; Wed, 24 Jul 2024 07:40:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20230601.gappssmtp.com; s=20230601; t=1721832028; x=1722436828; 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=CtkC1wWkyv8AugeiY2gTiNz55dgUEvQtom1lgJOWSxg=; b=yvbfUWMR4KMmlbR7iHDhp2BO3wvJZoWwufEIJFXSB1qhPfk0VYsL6BIQFK9ZGyEcHe 6gtq5HdpYTDgfG7ocFAE79gcvoGHe6YB/8hT6Iuz8fUhQQZCZEbxUe1sUYbtQpuvPlC2 5fjdfHqzZamZBzbFBpjnbuWXEdhqvtka9BZmR5c65jC7CAJYJ/Ee7HoT5hX4fnNsBUQU L+kTafXSiBsAfclILQONJ8LVIoL0GsROVlDk+7O5KtGxB4CQ9RNPn8HWG9eHnYjPSSAn TWPaT4ipKGQJ9Wczlu4hLLmzdW6LXlLycB7+FHhMLn7UIPNRMyur10hmClP8z2Mwcrby 5tcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721832028; x=1722436828; 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=CtkC1wWkyv8AugeiY2gTiNz55dgUEvQtom1lgJOWSxg=; b=mJ+/YshZbATJVDRTu9KF/OoldV6FGYMmFQtFOWINOuLwnl/Lja1CqDyCSm961E1dUT nBmCBO0yo9PC/3M81C5Zl71qp/6Cxxj+8wf6mdvfB3C1J2ED5QUw1aQYgRzAKzxCI+zl I7ljwa2tmGjOAfglo8NDGgVxxKx754fqltDCqP3Qs02csEMuv1DxGY9bO+9RSxAU+sPi T3YczbWnHZFHB+4vCRJfeDepMxoiI5vVWCsSE18JRSEVMdaPVPNOD7XQB1nlFtpf3FCW LKgG/6I2PYHDqsZ0+5ZFbrIqn2BJ5JBahsUC5LGTa0B6x91RuAUtC3iKDYBNQcUWa8Qs OmXg==
X-Forwarded-Encrypted: i=1; AJvYcCVI0PXJ18ERTOXLsrIhlGPrKWNU2nybMcJ7wrKeUlz1ufoLxvcZNeMP/dcz2u6S4nCi/JtigwJ4clTX1KmRBQ==
X-Gm-Message-State: AOJu0YxekH44e2W1LKqtKIUsCD1Y8PwKxD4fJl7kN4euyC4GPLoZoCQb dn7mGCAOfmltMvkQRpvpof8yZAd807RlGtJ0qxI0fJdhqJRytTTy7QUhwAC/0sbu4Zeky81yX5M Qxlpbvnl/+rQKLKYSeipAxkIp8oMg53aLz96J0Q==
X-Google-Smtp-Source: AGHT+IGBTk6weMGUKLFmOqiECY+IW36lDz6cgRCyVJ9P7s4ivI4SOAcRHE6XzZiWD/Bsc1KPQNE6mFkcnifVJq1+4AA=
X-Received: by 2002:a05:6871:825:b0:25e:19fe:f240 with SMTP id 586e51a60fabf-2648c9c4df5mr2529287fac.9.1721832028648; Wed, 24 Jul 2024 07:40:28 -0700 (PDT)
MIME-Version: 1.0
References: <CAPt1N1kEDabn4gWU4Nt2esWnS-ni4oEqfUOQE2EiNwAtJon3iQ@mail.gmail.com> <DCD8C19A-1E56-46F7-934A-7C12814A4768@employees.org>
In-Reply-To: <DCD8C19A-1E56-46F7-934A-7C12814A4768@employees.org>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 24 Jul 2024 07:40:18 -0700
Message-ID: <CAPt1N1mWWeoz9yCfDL97SSSMotEGEiXV9hk9ib4pEzrxCQXRww@mail.gmail.com>
To: Ole Trøan <otroan@employees.org>
Content-Type: multipart/alternative; boundary="0000000000006e590c061dff4256"
Message-ID-Hash: N6HLUU7OEE2DDSEYNT3U6HSWMXO4ROPU
X-Message-ID-Hash: N6HLUU7OEE2DDSEYNT3U6HSWMXO4ROPU
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/TL7riqeVkpH2LXflP2_O2mpE894>
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>

The SNAC draft does speak of stub networks, in the sense that a stub router
might have more than one. In such a situation I would expect it to request
one /64 per stub network. We should definitely say this explicitly in the
document.

However, I don’t know what the use case would be for this—it seems like the
primary motivation for doing stub routers (incompatible layer 2s) doesn’t
really support this configuration.

So as a practical matter I don’t think we need to worry about it.

Op wo 24 jul 2024 om 07:33 schreef Ole Trøan <otroan@employees.org>

>
>
> > On 24 Jul 2024, at 16:00, Ted Lemon <mellon@fugue.com> wrote:
> >
> > SNAC and PD-per-device are unrelated. You asked me a question about
> SNAC, which I answered. SNAC routers will pay no attention at all to the P
> bit.
>
> Slightly tangential, and possibly something that should be on the snac
> list.
>
> Not quite sure what Dave is asking, cause this is mostly up to network
> policy.
>
> E.g If the infrastructure network was numbered with a GUA and a ULA prefix
> I would expect a SNAC router asking for a singe IAID IA_PD to get an IA_PD
> back with two prefixes. One ULA and one GUA. But again, that’s up to the
> network.
>
> The tangential question, that I didn’t find in snac-simple, does a snac
> router ever need to number more than a single interface? If so PD allows
> the SNAC router to use a separate IA_PD for each interface, allowing for a
> more efficient allocation. Eg for 3 interfaces a single prefix would be a
> /62, while for 3 PDs it would be 3x/64. (In spirit with the flat model in
> cpe-lan-pd).
>
> Is this choice and recommendation worth including in snac-simple?
>
> O.
>
>