Re: [Snac] I-D Action: draft-ietf-snac-simple-00.txt

Florian Obser <florian+ietf@narrans.de> Mon, 20 February 2023 12:06 UTC

Return-Path: <florian+ietf@narrans.de>
X-Original-To: snac@ietfa.amsl.com
Delivered-To: snac@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C201C1595FE for <snac@ietfa.amsl.com>; Mon, 20 Feb 2023 04:06:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 wlLmtxZNuQFd for <snac@ietfa.amsl.com>; Mon, 20 Feb 2023 04:06:13 -0800 (PST)
Received: from imap.narrans.de (michelangelo.narrans.de [IPv6:2001:19f0:6c01:821:5400:1ff:fe33:a36d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA512) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8135DC1595E5 for <snac@ietf.org>; Mon, 20 Feb 2023 04:06:12 -0800 (PST)
Received: from pinkunicorn (2001-1c00-270d-e800-8570-5b09-1239-3bd4.cable.dynamic.v6.ziggo.nl [2001:1c00:270d:e800:8570:5b09:1239:3bd4]) by michelangelo.narrans.de (OpenSMTPD) with ESMTPSA id f434654a (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for <snac@ietf.org>; Mon, 20 Feb 2023 13:06:07 +0100 (CET)
From: Florian Obser <florian+ietf@narrans.de>
To: snac@ietf.org
References: <167631700481.44401.16650680728729430437@ietfa.amsl.com>
Date: Mon, 20 Feb 2023 13:06:06 +0100
In-Reply-To: <167631700481.44401.16650680728729430437@ietfa.amsl.com> (internet-drafts@ietf.org's message of "Mon, 13 Feb 2023 11:36:44 -0800")
Message-ID: <m1pma4sfrl.fsf@narrans.de>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (darwin)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/snac/sEoT5x0TkxQ8EqlwWMYRV8ePXTU>
Subject: Re: [Snac] I-D Action: draft-ietf-snac-simple-00.txt
X-BeenThere: snac@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Mailing list for discussing problems relating to the automatic connection of stub networks to existing infrastructure networks. " <snac.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/snac>, <mailto:snac-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/snac/>
List-Post: <mailto:snac@ietf.org>
List-Help: <mailto:snac-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/snac>, <mailto:snac-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2023 12:06:16 -0000

5.2.2 states:
|   If IPv6 prefix delegation is available, which implies that IPv6
|   service is also available on the infrastructure link, then the stub
|   router MAY use IPv6 prefix delegation to acquire a prefix to
|   advertise on the stub network, rather than allocating one out of its
|   ULA prefix.

and 5.2.3:
|   Therefore, when DHCPv6-PD is available, the stub router MUST use DHCPv6
|   PD rather than its own prefix.

That's contradictory, I suppose 5.2.2 should say:
|   If IPv6 prefix delegation is available, which implies that IPv6
|   service is also available on the infrastructure link, then the stub
|   router MUST use IPv6 prefix delegation to acquire a prefix to
|   advertise on the stub network, rather than allocating one out of its
|   ULA prefix.

Or maybe just drop the last paragraph from 5.2.2 entirely.

-- 
In my defence, I have been left unsupervised.