[v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-per-device-03

Jen Linkova <furry13@gmail.com> Fri, 06 October 2023 15:48 UTC

Return-Path: <furry13@gmail.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 7AB2EC15C261 for <v6ops@ietfa.amsl.com>; Fri, 6 Oct 2023 08:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.856
X-Spam-Level:
X-Spam-Status: No, score=-6.856 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 esj_b0s_TxRl for <v6ops@ietfa.amsl.com>; Fri, 6 Oct 2023 08:48:43 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 79C49C15C263 for <v6ops@ietf.org>; Fri, 6 Oct 2023 08:48:43 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-5041335fb9cso2922336e87.0 for <v6ops@ietf.org>; Fri, 06 Oct 2023 08:48:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696607321; x=1697212121; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=aqVXMz+eT9qacJh96hW+1rxBgR9Miar0OhNcAubOWas=; b=UVIpajgBe6OYwdZ3CdAVfNCJcqxhVav1PSSOLm45cFwLQUthw6kkRopMNyukGSjIaf T6ewYFqDnRXc5u5pNW+W5tzr4ey5N6KNEdxRSMUgEV4bBYrRiZEFMIfG+DuYYywXIkQH btiOWQCpe08V3/dw45XuqJFdrmt1wt4yktehMh4N6S5IBdLsNdpsHg8NfgfUIvADJ510 +ItvtBVZNYinrkYjMReAzCm0qYQN7Z5D/r7i5kJERFp+kxMobfGP30LC0mIn4qyFLA5l HIhgqqYkW+uBpGhmkdxBSqdpIRhRqKrNxxrOWHguYP7LlIA5Vg+P4RxMqwCoL9lXKWX8 kThg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696607321; x=1697212121; h=content-transfer-encoding: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=aqVXMz+eT9qacJh96hW+1rxBgR9Miar0OhNcAubOWas=; b=lYL47rdDTvr2y64JheIdNXHEhZz9ZnoSvg84M85QctJn8vGlBswH4WllbiOIF7QgzH K9yfSLIz189Z8fo6njqM2jPG/6SzM8+574bkuJ/gwJSFqytOk04pXSj8OLv4eEPLEXeQ +ZjzVk34MbFMxzvb+jbAjiU0y/xSM6XA62vnuNs/2zaIaaqLkE0Mu/35549L/wkiMDnw GSECWixkHm3ea3zsZoctBxtckmtn0cx1nxUMlgZ4cNGjEL1nxWi/3PQsuxelBwZNG2+7 ptU3Ut6prf6Gvj0hAtGNOzhyBbMOqGZ161Xj29PtGhz1L4+tKIiPSGx6VE/bpoDQ857E FLfA==
X-Gm-Message-State: AOJu0YySpF26Zm7N+7H94SEz7r+s5WQYw9uzoBYZeyZJf1gtqYgrhpOL BRKp4G0W4c1jqxdY0Os5nkrQWAvrn4QSg8PI25X++qrw1Rgs0g==
X-Google-Smtp-Source: AGHT+IF2D/3OEhJ758ifo61LR/L9E09AUyU4kxFOQULu7tpC6ud7y7CCPfogO7GOByebVnK4g6EbTpIjoqtWPHQ2Kcc=
X-Received: by 2002:a05:6512:e96:b0:500:b3fe:916e with SMTP id bi22-20020a0565120e9600b00500b3fe916emr9141988lfb.2.1696607320956; Fri, 06 Oct 2023 08:48:40 -0700 (PDT)
MIME-Version: 1.0
References: <169660647031.23597.13067349132781805398@ietfa.amsl.com>
In-Reply-To: <169660647031.23597.13067349132781805398@ietfa.amsl.com>
From: Jen Linkova <furry13@gmail.com>
Date: Fri, 06 Oct 2023 08:48:29 -0700
Message-ID: <CAFU7BATORG5sruy19XMAXsfvqumOB7wL=G1EbNo-zUrtzoddNg@mail.gmail.com>
To: V6 Ops List <v6ops@ietf.org>
Cc: Lorenzo Colitti <lorenzo@google.com>, Pascal Thubert <pascal.thubert@gmail.com>, Vasilenko Eduard <vasilenko.eduard=40huawei.com@dmarc.ietf.org>, Ole Troan <otroan@employees.org>, "Joel M. Halpern" <jmh@joelhalpern.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, oselists@gmail.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/G2xK3UqfHPjOYjW9KpTnynkIsf0>
Subject: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-per-device-03
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Oct 2023 15:48:44 -0000

Dear v6ops WG,

We have just submitted the -03 version for
ietf-v6ops-dhcp-pd-per-device - thank you very much to everyone who
provided feedback!
Please review and let us know if the draft is ready to progress.

The main changes:
- Introduction is rewritten (much shorter and, hopefully, more clear)
- some text about multiple addresses use cases moved to Appendix.
- The Applicability and Limitation section is moved up, so it's in the
beginning - hopefully it would help the readers to understand what
scenarios are in scope and what are not.
- Client Mobility section added to discuss what happens when a client
moves between network attachment points.
- the draft is now explicit that it focuses on "a pool per link"
scenario, which also drastically simplifies the routing and relay
requirements (the routing section is updated as well).
- the draft now suggests Active Leasequery as one of the mechanisms to
keep the relay state in sync with the server.
- The Prefix Consideration section has been updated and states that
the endpoints are not required to use SLAAC - it's just the network
allows them to do that, if they need to.
- various changes to address other comments received during the WGLC so far.

I'd like to ask everyone who has expressed concerns during this WGLC
(you are in Cc: - hopefully I didn't miss anyone) to review the new
version and let the author know if you still have concerns.

Thank you!

On Fri, Oct 6, 2023 at 8:35 AM <internet-drafts@ietf.org> wrote:
>
> Internet-Draft draft-ietf-v6ops-dhcp-pd-per-device-03.txt is now available. It
> is a work item of the IPv6 Operations (V6OPS) WG of the IETF.
>
>    Title:   Using DHCPv6-PD to Allocate Unique IPv6 Prefix per Client in Large Broadcast Networks
>    Authors: Lorenzo Colitti
>             Jen Linkova
>             Xiao Ma
>    Name:    draft-ietf-v6ops-dhcp-pd-per-device-03.txt
>    Pages:   18
>    Dates:   2023-10-06
>
> Abstract:
>
>    This document discusses an IPv6 deployment scenario when individual
>    clients connected to large broadcast networks (such as enterprise
>    networks or public Wi-Fi networks) are allocated unique prefixes via
>    DHCPv6 Prefix Delegation (DHCPv6-PD).
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-dhcp-pd-per-device/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-v6ops-dhcp-pd-per-device-03.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-v6ops-dhcp-pd-per-device-03
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



-- 
SY, Jen Linkova aka Furry