Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-per-device-03
Jen Linkova <furry13@gmail.com> Tue, 10 October 2023 20:07 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 3423BC151082 for <v6ops@ietfa.amsl.com>; Tue, 10 Oct 2023 13:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.856
X-Spam-Level:
X-Spam-Status: No, score=-1.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_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 7rORnKZdJ3XN for <v6ops@ietfa.amsl.com>; Tue, 10 Oct 2023 13:07:05 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 B4774C15107E for <v6ops@ietf.org>; Tue, 10 Oct 2023 13:07:05 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2c12ae20a5cso70723821fa.2 for <v6ops@ietf.org>; Tue, 10 Oct 2023 13:07:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696968424; x=1697573224; 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=F/T81Fq5YaZUbWLOb44kcedQ3dk/WMFxGC2teXXFRck=; b=kFm9StVKXYgBWxaZZYH5t5pVUQm6gc+9CEQ+hCPPKInruW20lipYmYcFNMgMnJJB89 9PZao5PzXaSw9sEHO6/zC4BY9FT+wFlzHW9J9ys8HFO+LAaOL7zV7lmmtoFuRL+ws8PY TQl2m8uH59Q0x3T8QMguyN7aqOczUApQuY/c2KUTf48THBBHb/C3Y8B/UGnZy8Uzvp4X YundDiwaqviCkBSU5se4JkTvoBCZ+foH4o3pytptwHY3PbK0mnWSxH0IbirJ7SsRiOhd WL9p5Vw2Tsi81qnYwUMzClD6J0sCEGFdgKgh4pdr9C7/Q8MiR9Q+KE7v6hNjdcPJWg/G LGNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696968424; x=1697573224; 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=F/T81Fq5YaZUbWLOb44kcedQ3dk/WMFxGC2teXXFRck=; b=J08JguuOeyICMx44qOSUeyF3FVvwDgfAOSVVSyTpV/qAyfwQwubmxhfp55g6uMveQu nQl0NRyBkgdDq00Et06FP5ZjKFVD5Ax2bYN43/chrq+CeCtZq/Vo8iuL8YJAQdMH8mtr +Yq+WDguB76fKNMWaRJ0Y4YLWYAcscDMtw+8hpbqU9+0us1xFm5R+kWBJdlRnuyVOHqw Yq9iIWAU0JyGl/woOYtBOdPfcHUaJ2CVTAGOs64HZriJFj7EhYCIYgQ/Be5y+WWoL/LT QDtD946qYmgr6Eojb2wFUBxO9Sn5Zao7gT1C3XXqNIXqzcnOxu3lxauYzFmDD/6aSPbP GRrA==
X-Gm-Message-State: AOJu0Yzgs1YL3NiLAlKcLOlPTn21vQtzj49KveWXIwH3VYUAylhEIN8g dU16UBfQFWvfFb+ft5Tw5PZJAS+m7esqefp8whg=
X-Google-Smtp-Source: AGHT+IEMW4gRoNAh/mX9auGIkzEnvWZCGzQqGvtlewpWSehqsAw6mEfp11wQHrg6Prk+xnK9JldP0IIV4PaTOIQBCXc=
X-Received: by 2002:a2e:9b15:0:b0:2b6:decf:5cbd with SMTP id u21-20020a2e9b15000000b002b6decf5cbdmr15010442lji.36.1696968423512; Tue, 10 Oct 2023 13:07:03 -0700 (PDT)
MIME-Version: 1.0
References: <169660647031.23597.13067349132781805398@ietfa.amsl.com> <CAFU7BATORG5sruy19XMAXsfvqumOB7wL=G1EbNo-zUrtzoddNg@mail.gmail.com> <64e6fcde-ffd6-1051-415b-4326802842ff@joelhalpern.com> <CAFU7BASyWh_qf925EpUVe09_n4jqmqf+o3QV3zRKH3u47EAyQA@mail.gmail.com> <fec33501-2906-8ab3-f21f-4abaed72e072@joelhalpern.com> <CAFU7BAQyZsDqqBMG_io_6-=ZSeuQ+HtbPjoTGRpShjDVw9ufNA@mail.gmail.com> <f184ea58-2355-f720-5de5-096a4eafa21d@joelhalpern.com>
In-Reply-To: <f184ea58-2355-f720-5de5-096a4eafa21d@joelhalpern.com>
From: Jen Linkova <furry13@gmail.com>
Date: Tue, 10 Oct 2023 13:06:52 -0700
Message-ID: <CAFU7BAQNE+HCC2Or-t30aXBh9OC6H2Q9QESJSsWOLyuN4e_NoQ@mail.gmail.com>
To: Joel Halpern <jmh@joelhalpern.com>
Cc: V6 Ops List <v6ops@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/jTdk3hV0C7PYDhzgrCHMpbBgVkA>
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: Tue, 10 Oct 2023 20:07:10 -0000
On Tue, Oct 10, 2023 at 7:02 AM Joel Halpern <jmh@joelhalpern.com> wrote: > > "For example, it can form addresses as described in [RFC7084] > > requirement WAA-7"? > <Jmh>Yes, that would help. It would remove the part that confused me > and leave a reasonable reference. </jmh> > > Actually I believe the draft says (Section 6.2, the first-hop router > > requirements) > > > > "With the first-hop routers performing DHCPv6 relay functions, the > > proposed design neither requires any subsequent relays in the path nor > > introduce any requirements to such relays, if they are deployed." > > > > Do you think we shall explicitly say smth like "requirements (like snooping)"? > <jmh>Clearly, I did not read carefully enough. It is there. Still, I > think adding the parenthetical would help. </jmh> Great, I've just sent a github PR, the proposed changes will appear in -04. > >>> On Fri, Oct 6, 2023 at 9:05 AM Joel Halpern <jmh@joelhalpern.com> wrote: > >>>> Thank you. The introduction now seems to me quite clear, and lays out > >>>> the case for the procedures the draft introduces. I also appreciate the > >>>> caveats and clarifications in the Applicability and Limitations section (5). > >>> Thanks a lot for review and feedback, Joel! > >>> I'd like to confirm if you think that the current version of the draft > >>> is ready to complete the WGLC? > >>>> Joel > >>>> > >>>> On 10/6/2023 11:48 AM, Jen Linkova wrote: > >>>>> 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 > > > > -- SY, Jen Linkova aka Furry
- [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-per-… internet-drafts
- [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-per-d… Jen Linkova
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Joel Halpern
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Brian E Carpenter
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Jen Linkova
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Chongfeng Xie
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Brian E Carpenter
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Jen Linkova
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Joel Halpern
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Ole Troan
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Lorenzo Colitti
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Jen Linkova
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Vasilenko Eduard
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Ole Troan
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Ole Troan
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Brian E Carpenter
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Jen Linkova
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Joel Halpern
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Jen Linkova
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Jen Linkova
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Jen Linkova
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Ole Troan
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Chongfeng Xie
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Lorenzo Colitti
- Re: [v6ops] Continuing WGLC: ietf-v6ops-dhcp-pd-p… Jen Linkova