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

Chongfeng Xie <chongfeng.xie@foxmail.com> Sun, 08 October 2023 04:04 UTC

Return-Path: <chongfeng.xie@foxmail.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 36E8AC15198E for <v6ops@ietfa.amsl.com>; Sat, 7 Oct 2023 21:04:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.829
X-Spam-Level: *
X-Spam-Status: No, score=1.829 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_FROM=0.001, FREEMAIL_REPLY=1, HELO_DYNAMIC_IPADDR=1.951, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, 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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.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 y80oKl7iNkxh for <v6ops@ietfa.amsl.com>; Sat, 7 Oct 2023 21:04:20 -0700 (PDT)
Received: from out203-205-221-191.mail.qq.com (out203-205-221-191.mail.qq.com [203.205.221.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8495AC15107F for <v6ops@ietf.org>; Sat, 7 Oct 2023 21:04:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1696737855; bh=BN/7j4+2jeMJlakm2KqXjuIslqqqGvH1tAz8qt+NsoI=; h=Date:From:To:Subject:References; b=rF4WN8ypLJ8XkbZ2n7VxE4gA+zEFTbvDsZJxar00hli7+ZUsJMvy+8vXcCzOZ/I6w Ga7Ye8gJKxfYcwuT1DAzJK6/VLcjJp2BGyGn5t74AYS9ZjA88QYwQ/kg8SwglqORab 1uxYDK8jWXZC3dlcQzwaDvld2/ek63zs2ZE8Ae44=
Received: from DESKTOP-48H476U ([219.142.69.75]) by newxmesmtplogicsvrszc5-0.qq.com (NewEsmtp) with SMTP id 10E330E1; Sun, 08 Oct 2023 12:04:14 +0800
X-QQ-mid: xmsmtpt1696737854tj9zvai5j
Message-ID: <tencent_BE90399FE81A0DD08DE3D64C3EB6AC72B705@qq.com>
X-QQ-XMAILINFO: MyIXMys/8kCtM/ppar++8yE/GJ/XgfIh3uks2YTzQXC8FjwqwRuRCB7TsGJR5I OsoCjn5K0yHqYyjBfmOlC60vIDe58efAKDC979KhQWeX/b5q2kKjtRJMHXVLH4LFITehlUlo+Oy+ zhJxygxUp6WbvXT0N2skNZfVhu9J2rEGkemIm4JO8G7da/83An7spZa0lhPviAbmu904IvqXzK/b T0w8/i1STKvwwZUShA6k4vDHtNNOZLjbkzAqpefm/LRIvGJ1Uh5szVuVs7Gg02hC8ny0yYBkN1pm IaLzq056kyEPW6geWEquY076xSF/WGZdyx31LipI5GGzp36C13sVCZeXZFohrvfKEiBvEfitgjBA o9gFu64bFT1NMhNqRZryF1F+fclI1rkLNIh92sBJ8CDNLJZ5i7EXTWeeAPV9rhPlmrYZrzt9YUNK OVgagz/16bLbOTn8b8LOfh0MiEmxhvpn4JGNpKKHV+EGt7dSFK9cnbx95tbZKMST2VLqleawi9BT Cfyp2K8puN2G9gNL/sHXQx+LvsDfF9z+UytJGFNHE40hPzQDf5mWiQag6HyNkQzJWv9v3hHDRfEK /rjn7ZrUNsqNNvSYCuv7Nc8C97D03yVibB6Zq4MyFC0U3Xz/Qa4v/EbfDz8vDcvhQaNW1i6RYinM h1RU8K4UFC5xEKTI4xhGPejRTujy7y58tH0Yz7zDm77PqU9OCUJKfdP9JYkKMbqh/y5cOdxyiAbT t+a1fC/p+r2HTg+FHNV8bq6ZQkdWyBET89NLkGfLLtfxKRm096Lf3Pul0gSxIzEKQOqkpswlgEJO zFeu3HVgb0AZv+UoSC3enZXhmKMfM+ytvrXSKpulEEN4FMNdUfWObDOzHduqGoAcMQ52B8cnmywX r0zLiM3aaHCjlXlaKpLCHgs2yWclteaTLqcHyAEwm58qbcnTxRZFEKV46MwEt/rPRznfOniTQ1lO mBzDQ7RX5ZCaypBiJ3tLXFIY2cJtM6MN83MIc8WebX8y21ZwMHRg==
X-QQ-XMRINFO: Nq+8W0+stu50PRdwbJxPCL0=
Date: Sun, 08 Oct 2023 12:04:15 +0800
From: Chongfeng Xie <chongfeng.xie@foxmail.com>
To: Jen Linkova <furry13@gmail.com>, list <v6ops@ietf.org>
References: <169660647031.23597.13067349132781805398@ietfa.amsl.com>, <CAFU7BATORG5sruy19XMAXsfvqumOB7wL=G1EbNo-zUrtzoddNg@mail.gmail.com>
X-Priority: 3
X-GUID: 8D0AE3F0-C22F-409E-A381-40E07676E694
X-Has-Attach: no
X-Mailer: Foxmail 7.2.24.96[cn]
Mime-Version: 1.0
X-OQ-MSGID: <202310081204146762563@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart885186475152_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/vKT83k3WkuZim7OBgjsJP_XFWy8>
Subject: Re: [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: Sun, 08 Oct 2023 04:04:24 -0000

Hi folks,
I support the progress of this draft and hope that it will eventually pass the last call. Nevertheless,I have the following suggestions:
1) This draft is about using DHCPv6 PD to Allocate Unique IPv6 Prefix to Client, the approache is described mainly in text. In order to help readers, especially those outside the v6ops community, understand it more quickly, it is recommended to add an diagram to show the overall architecture and the inter-relationships between the entities in it.
2) Regarding to the scenario of virtual host, in reality, the implementation of virtual host can be divided into multiple methods, some methods do not require the address obtained by the underlying physical host to assign an address to the upper layer virtual host. For example, in a cloud system, a dedicated cloud management platform is generally used to configure addresses for tenants' DHCP servers, rather than being assigned by physical hosts. Therefore, I hope to provide an explanation of the application scope of this solution in virtual hosts.
3) In addition, this draft mentions considerations or requirements for components, such as First-Hop Router and DHCPv6-PD Server. Should it also mention requirements or considerations for clients?
4)The following Nits shoule be fixed
   section 7: Thsi-->This
   Section 9:conenctivity--->connectivity

Best regards
Chongfeng



xiechf@chinatelecom.cn
 
From: 【外部账号】Jen Linkova
Date: 2023-10-06 23:48
To: V6 Ops List
CC: Vasilenko Eduard
Subject: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-per-device-03
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
 
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops