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

Jen Linkova <furry13@gmail.com> Sat, 07 October 2023 12:31 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 126D9C14CF15 for <v6ops@ietfa.amsl.com>; Sat, 7 Oct 2023 05:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level:
X-Spam-Status: No, score=-1.855 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_BLOCKED=0.001, 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 Wub8BPwtnL89 for <v6ops@ietfa.amsl.com>; Sat, 7 Oct 2023 05:30:58 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 3F871C14F749 for <v6ops@ietf.org>; Sat, 7 Oct 2023 05:30:58 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id 38308e7fff4ca-2c3c424d502so17894381fa.1 for <v6ops@ietf.org>; Sat, 07 Oct 2023 05:30:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696681856; x=1697286656; 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=UNnfcnztRsMffNm6Uz4FpgGcmMDYn96IGyf6A223OQM=; b=Nml+p/RrRxcnr4YZ6NErtqDimC+xjzS7CWpemKZw7uDDCR4i0BaqQlWmmQkLeYlrah 5fGVDPTg6PrykuGc4GZZjW/vi4dU3SpML1yvpFggRL05nV04TZYuiFBbeAR+P96sIdpr ZdEXK7IcBVavuUjxcrPyhgGNLV1xLQi3kC7ipVs47xWfmRBC1egM9tZ3VTF46FPGkRZQ l0jXBD+ew43PU9mPf+H8bU84mpEGV+VdOcdximR4Fy1PA5VLVTVJa0sleMjrjZLNmon0 UHXXkMJVpqzdOtExikWt+0i+dVE7Zwvnc8aYP7vbn4vlem780B6R5S2abAM7NvFPvoTU mSOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696681856; x=1697286656; 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=UNnfcnztRsMffNm6Uz4FpgGcmMDYn96IGyf6A223OQM=; b=I1KUoKruOsRSUgbESW5M5HOhcc2HMBQfHLo5++EISVgiQNxSeoh1SbOiorAJlOqojY LHdQznoLsWDNgAdQWhId3UmWgV5dVrkHP4XMVEpC5ZM8yWD5ij2yrCSyai4A0kbpo4Yn REY8Dx06MCSXb6EXbDFOZh2DWuip5Xb8byMyJRCS3biwx8CC0wDJYuKlG5bWS9gdLt4T bHr9Id+MbUWTcf+IjbynAUoj7Vx4gzr+Iq+LpnN2SZjvKnDuqii73f4SEhYsK2sbVJ/w 4V/tlvXk9ssY/YQ99lI74GeTLXlYcgLsUEyjaMwfQ9vc0Zc8ESYsvi1I2omwG9Ntp3vq vU+w==
X-Gm-Message-State: AOJu0YyvmKdmJy1BXWzmK+9KDNg/DUrmIrWQ87kpgCJci4lK3CFmefzA swymJS6lXdHg9XB0uM4LmLDCO3eRoUY+uuvwCsA=
X-Google-Smtp-Source: AGHT+IE4BFmMOdnS5Of921jb7KGW3zEk2bvYUH9txJ4lw/OPRR1sa4wIolXNLsHuGkjyBzW1vh+ZzJak6aI5YTmXpTE=
X-Received: by 2002:ac2:4da7:0:b0:500:daec:2817 with SMTP id h7-20020ac24da7000000b00500daec2817mr8463223lfe.54.1696681856129; Sat, 07 Oct 2023 05:30:56 -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> <016d23ac-02d5-d21a-256f-0ed605e377d2@gmail.com>
In-Reply-To: <016d23ac-02d5-d21a-256f-0ed605e377d2@gmail.com>
From: Jen Linkova <furry13@gmail.com>
Date: Sat, 07 Oct 2023 05:30:44 -0700
Message-ID: <CAFU7BASvqGW2dBtAkd4rH7t=xi978Kz7wZSPbAQPLomwZ8Wwzw@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Joel Halpern <jmh@joelhalpern.com>, V6 Ops List <v6ops@ietf.org>, Lorenzo Colitti <lorenzo@google.com>, Pascal Thubert <pascal.thubert@gmail.com>, Vasilenko Eduard <vasilenko.eduard@huawei.com>, Ole Troan <otroan@employees.org>, oselists@gmail.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Y7-L0KeK5om21dO6n52pQtsoWCY>
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: Sat, 07 Oct 2023 12:31:02 -0000

On Fri, Oct 6, 2023 at 2:57 PM Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> Agreed, this is all much clearer now.

Thank you for your review, Brian!
So what do you think about the WGLC status? Do you think the draft is
ready to be advanced?

> A minor remark (not really suggesting a change):
>
> >  6.1. Prefix Pool Allocation
> ...
> > Other deployment models, such as prefix pools shared over multiple links or routers, are possible, but not described in this document.
>
> This would in fact be a very obvious application for RFC 8992, a bit similar to the scenario in appendix A.2 thereof.

Oh interesting, thanks for the reference. I've not been following
ANI-related work, to be honest - will read RFC 8992.

> On 07-Oct-23 05:04, Joel Halpern 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).
> >
> > Yours,
> >
> > 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