[IPv6]Re: Working Group Last Call for <draft-ietf-6man-pio-pflag>

Ole Troan <otroan@employees.org> Tue, 11 June 2024 08:29 UTC

Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2949FC14F6E9 for <ipv6@ietfa.amsl.com>; Tue, 11 Jun 2024 01:29:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 cWvVniUAs4sX for <ipv6@ietfa.amsl.com>; Tue, 11 Jun 2024 01:29:46 -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 36385C151068 for <ipv6@ietf.org>; Tue, 11 Jun 2024 01:29:46 -0700 (PDT)
Received: from proxmox01.kjsl.com (localhost.localdomain [127.0.0.1]) by proxmox01.kjsl.com (Proxmox) with ESMTP id 3A7D3E2B77; Tue, 11 Jun 2024 08:29:45 +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=NUkRs3V4KJn5kbdC RwEjG4nbStaPsztbAswdkftYnNM=; b=N3zrku3GTjTkaAbf0hZUs9tmOyYN1ksZ SzpFy98D+4RrWzDKv5obW5rqDgw46v3iY/Z+L19jrRqaEB7oscouS+hvBd/jnbVc nuRxlRtzXm5tq9s7JspocNmOD5aGFOOrW4rGPtGHoHaT7dpl1p+dxtUdmxQK2NeY gdrN4Hf3mPuNe8KiIOUUBoGX3kK0pdZHFol/SpU4NF89HuRUB0MRDuoLaMiucFZA RNBKeMq1LVVRTrXtGnAxzS3Fzgg14/pVuXGFo2QAdNE4RUJGVQHlx4e9cktT6qxF Affm/RCJUT//+Cj66+QF9Aukyb91bRe79DPt+NwTqKE1GnKiAk2aUw==
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 1872DE2B48; Tue, 11 Jun 2024 08:29:45 +0000 (UTC)
Received: from smtpclient.apple (ti0389q160-2783.bb.online.no [46.9.227.254]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 401C44E11AE1; Tue, 11 Jun 2024 08:29:44 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAFU7BAQGe0md8cqEF8UgeBfb7XE1TuO+p_yCyu06jA2Ft7Pb8g@mail.gmail.com>
Date: Tue, 11 Jun 2024 10:29:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <372FA47C-EABC-4236-A8B5-85F13B37FF5E@employees.org>
References: <18236.1717011844@obiwan.sandelman.ca> <2AD87DE1-075E-45E7-A682-8042F04EF59A@employees.org> <89dbde8c-82c9-4a2e-9cff-8d4fd2d8fbe6@gmail.com> <9E7BEA1C-4597-4142-A3AB-57211C436197@employees.org> <CAKD1Yr0iR+RZHvuquCGYfntiD+K7-PdkvGJzHLx1PLrFqJ=Z4Q@mail.gmail.com> <47BF97B8-2BEE-47CC-A965-C6BB112990AB@employees.org> <4bcfcd71-d295-433d-813f-1183c7da3cf3@gmail.com> <CAKD1Yr1CL_Jw4O-iETF6T1v8EL_Lj-fMi6EV=3MgPhN+M2tc8w@mail.gmail.com> <84f6e699-5587-4407-a566-b031c31e2cd5@gmail.com> <CAMGpriWqD99OzdOaJU7_nQTwvD=o1wsVxOQrbMqy5sH7sX7gwA@mail.gmail.com> <95dfd2e9-25da-4449-b740-724804a34735@gmail.com> <CAKr6gn12Vq9xJWGH+Na6xhDXXsW2XSDCnLegjXMRLN8KJ2CEZQ@mail.gmail.com> <CAKD1Yr24RyW_oxhY3iz5nEdXd0EZENy9cZBo7tfxLqLLMHOX_g@mail.gmail.com> <e2e406e1-1231-4c28-8163-c0e220da7453@lear.ch> <b8f85b39-0167-4040-a5d4-3a97f8819b99@gmail.com> <E50531BE-5867-472A-91FE-739341545D62@employees.org> <CAKD1Yr3uHmaSZ7A74X8TJrx6z39ed6DAbOgEXXnOkBiZtQ=WEw@mail.gmail.com> <CAN-Dau1hhR-nHGoR5KzHgwxyF-S5Q=VwnFmhJzeJDQfuaOUe+Q@mail.gmail.com> <CAKD1Yr34jwMdY=A+PCpjkMKb9v-bT9dr9TThv415tnka3MKeFg@mail.gmail.com> <CAN-Dau2yeRE=_XKz9Cx_h7N+NVwyn_c=HHh0HD0M4xnvYbMQkA@mail.gmail.com> <CAFU7BAQGe0md8cqEF8UgeBfb7XE1TuO+p_yCyu06jA2Ft7Pb8g@mail.gmail.com>
To: Jen Linkova <furry13@gmail.com>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: PPZXARYIJAFUFRSSCFRVNWDFR6J3I3AI
X-Message-ID-Hash: PPZXARYIJAFUFRSSCFRVNWDFR6J3I3AI
X-MailFrom: otroan@employees.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: David Farmer <farmer=40umn.edu@dmarc.ietf.org>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, 6man WG <ipv6@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [IPv6]Re: Working Group Last Call for <draft-ietf-6man-pio-pflag>
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/AjT9TnHXr4X3sA-FroCmrfbxJPs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

> IMHO the very important thing here is that the P flag indicates to the
> client that the client can request a prefix *short enough* for SLAAC.
> The goal is to prevent a client to ask for a short prefix if the
> network supports PD in general but doesn't have enough space for such
> clients.
> Clients which need long prefixes (/120../80 whatever) can just do it
> any time, I'm not sure there is any need for signalling support for an
> arbitrary long prefix.

On the other thread I saw quite a lot of support for not having that restriction.

The P-flag means, “don’t autoconfigure an address using this PIO if you can get addresses via PD instead”.
And for that use case, SLAAC is not used.

SLAAC could be used for network extensions. But only in very limited topologies, so cannot be an general solution.

Cheers,
Ole