IETF Logo Mail Archive

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

Ole Trøan <otroan@employees.org> Wed, 24 July 2024 14:33 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 18046C17A743 for <v6ops@ietfa.amsl.com>; Wed, 24 Jul 2024 07:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 QrVbs1xi-bzK for <v6ops@ietfa.amsl.com>; Wed, 24 Jul 2024 07:33:31 -0700 (PDT)
Received: from proxmox01.kjsl.com (proxmox01.kjsl.com [IPv6:2607:7c80:54:6::6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 2801DC1654F2 for <v6ops@ietf.org>; Wed, 24 Jul 2024 07:33:31 -0700 (PDT)
Received: from proxmox01.kjsl.com (localhost.localdomain [127.0.0.1]) by proxmox01.kjsl.com (Proxmox) with ESMTP id 20730E2EF2; Wed, 24 Jul 2024 14:33:30 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=employees.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:from:from:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to; s=prox2023; bh=3ArtfkXViuOX7AhQ yA3HwlSv7dR9n41W3txoLAyqkPk=; b=eSZ44FuCVTy739Xf5RocvFxJdNb24xw0 ZgGUAbhQPIAHAGH33ub8WWbrY73JY3i24S6cYKo6ELri4l8kMr5VsqQO/X4qXT7I WSMOX1JTITz2b1os73TMMbTds9yGS9yLKCs2BoHRBGNcWO6NJQf8pf7UltpkI1Cd 3cFc7y9T1U/085h86yWaP9n3YsEwIOdY8P0GucV+FIbmNs1Mz7l43V3X9/wWEumm Rkh/ke6LE9rRigmbLOFq9JvQlKWhGkXO8Rs0gepqySEPevv1RwHGAvGNjwn+AbuS pUBTLv3e62jmRXzW3EQlkUkxdq1YH7dgMFg1Ai6wSY6ClQyTyHwTSA==
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by proxmox01.kjsl.com (Proxmox) with ESMTPS id F3DBDE2ECD; Wed, 24 Jul 2024 14:33:29 +0000 (UTC)
Received: from smtpclient.apple (unknown [IPv6:2001:4650:c3ed:37a:9e2a:f334:61dc:ff10]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id BA06C4E11ADD; Wed, 24 Jul 2024 14:33:29 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Ole Trøan <otroan@employees.org>
Mime-Version: 1.0 (1.0)
Date: Wed, 24 Jul 2024 16:33:17 +0200
Message-Id: <DCD8C19A-1E56-46F7-934A-7C12814A4768@employees.org>
References: <CAPt1N1kEDabn4gWU4Nt2esWnS-ni4oEqfUOQE2EiNwAtJon3iQ@mail.gmail.com>
In-Reply-To: <CAPt1N1kEDabn4gWU4Nt2esWnS-ni4oEqfUOQE2EiNwAtJon3iQ@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: iPhone Mail (21F90)
Message-ID-Hash: 5GMCKXHQ7YDVUFHEKSBEG2ZXNFAJVDQ3
X-Message-ID-Hash: 5GMCKXHQ7YDVUFHEKSBEG2ZXNFAJVDQ3
X-MailFrom: otroan@employees.org
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/ptddxRu3m2CnQaZE_C9QLM8_SIU>
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>


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

v2.36.0 | Report a Bug | By Email | System Status