From lorenzo@google.com Mon Nov 6 05:26:25 2023 Return-Path: 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 6D385C0A856D for ; Mon, 6 Nov 2023 05:26:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -22.606 X-Spam-Level: X-Spam-Status: No, score=-22.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=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_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 thCLc6IRNKEE for ; Mon, 6 Nov 2023 05:26:24 -0800 (PST) Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (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 AD4D5C17DBF1 for ; Mon, 6 Nov 2023 05:26:24 -0800 (PST) Received: by mail-qv1-xf2b.google.com with SMTP id 6a1803df08f44-66d17bdabe1so31861856d6.0 for ; Mon, 06 Nov 2023 05:26:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1699277183; x=1699881983; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DN7b3UHqNJMwxBhhobTDaOD0Y724ij6gTFs0IXmyeb4=; b=TT91BOwl+Pe1+B4wqp/SMtoqYXMi76E8cKMSQqdNsQ85Cs7qdeyRSsxVrB3KiVgxE1 Eh0V539D1mBxQFLRIrtoeglZ7710g9PI1YcN/b9f2OD2rbG1owgHbCGQ192UX0sBjrbj kJCbmAJ6m/+bnAVXcmFZImymoD02CDit26PTYKnwMfD/0zHuyBMEktSvP92/+a385ZHA smIxEGQ63XIaEECff00KXm+xW9qUIIO29Dn2ZtZiOR5IH9EA++W2YB1OlQFI/utpnG6P +uCUh5AeARbd2cyto7gyHLuVxmTazb4V79ho/GP/1nOVckZ4YsQVm3L6SVh0AhejSpNN hadw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699277183; x=1699881983; h=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=DN7b3UHqNJMwxBhhobTDaOD0Y724ij6gTFs0IXmyeb4=; b=I6fqq/acXxrHZbbPdnC/tlDIKMH/V1TLCARZCqntniLOaD3uozIkTaLZY7Vrep8fRC CaqFTJIgFu07OeazyumSUCWVVLzVMOTRnqEnaqgaSNFUmCrd9bQMKhB1Ceww64pjKscL L8XybUbPYf9qgK9UfR5/8zZ2w42QD0iBed9ClF42Ksv3uTiBmDp40JVyG+XJz8HadYvN AePR2mAB6XKFcmP7dn5HakF9uoCsXs8kZ4oOjvxMQHW7wKnmzrFb1+5NSDDLRgNql9nQ P8c3kUJVUjjeJtcytMiHYoNrmrpuuYaudA83ghgZadvb1rITseL2HrHb6zVnsv0GKYB2 YGlw== X-Gm-Message-State: AOJu0YytM2Dbzc2IJ7kYcAreA9/87C8h+h62o6IjzALVIZMIfejBQ0Y7 xEPrcbaDunMvFEfHx5VXh29ADhnQsJyU2I+bYziBHbXEjKOxe1pZzqz6qo9S X-Google-Smtp-Source: AGHT+IFDEvTl2Pvofb5dQTxfu4EffbV9p1XfY0jYKWxC59mCfbLTvwNjNgAdEKY0XpTHQxLWmCCTcWnCflin40XfSac= X-Received: by 2002:ad4:5f89:0:b0:670:fa29:eb51 with SMTP id jp9-20020ad45f89000000b00670fa29eb51mr31514505qvb.12.1699277183428; Mon, 06 Nov 2023 05:26:23 -0800 (PST) MIME-Version: 1.0 References: <169919966581.36738.5162400304409089286@ietfa.amsl.com> In-Reply-To: From: Lorenzo Colitti Date: Mon, 6 Nov 2023 13:26:07 +0000 Message-ID: To: Alexandre Petrescu Cc: v6ops@ietf.org Content-Type: multipart/alternative; boundary="000000000000e5016f06097bcc87" Archived-At: Subject: Re: [v6ops] New Version Notification for draft-ietf-v6ops-dhcp-pd-per-device-05.txt X-BeenThere: v6ops@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: v6ops discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Nov 2023 13:26:25 -0000 --000000000000e5016f06097bcc87 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks! That will be fixed in the next revision. On Mon, Nov 6, 2023 at 12:49=E2=80=AFPM Alexandre Petrescu < alexandre.petrescu@gmail.com> wrote: > Nit: in Figure 1 this address needs an additional ':' or 3 other hextets: > > 2001:db8:ddd0:2:6666 > > Alex > > Le 05/11/2023 =C3=A0 17:17, Jen Linkova a =C3=A9crit : > > Hello, > > > > Following the conclusion of the WGLC (thanks to everyone who > > commented!), we've submitted a -05 version with the following changes: > > 1. Making it more clear that the draft requires the network to > > delegate a SLAAC-suitable prefix, and /64 is currently required for > > SLAAC to work - but it doesn't have to be like that in the future. > > Examples also use /64. Brian, does it address your comment? > > 2. To address most of Ole's comments: > > 2.1 Making it explicit that the draft only covers the network > > behavior, while host requirements are out of scope. > > 2.2 Clarifying that the network can support both flat and > > hierarchical models - it's up to the host to specify the hint. > > 3. Rewriting examples in the prefix length consideration section to > > make it clearer that the proposal does not require an excessive amount > > of IPv6 space. > > > > > > > > On Sun, Nov 5, 2023 at 4:54=E2=80=AFPM wrote= : > >> A new version of Internet-Draft > draft-ietf-v6ops-dhcp-pd-per-device-05.txt has > >> been successfully submitted by Jen Linkova and posted to the > >> IETF repository. > >> > >> Name: draft-ietf-v6ops-dhcp-pd-per-device > >> Revision: 05 > >> Title: Using DHCPv6-PD to Allocate Unique IPv6 Prefix per Client in > Large Broadcast Networks > >> Date: 2023-11-05 > >> Group: v6ops > >> Pages: 20 > >> URL: > https://www.ietf.org/archive/id/draft-ietf-v6ops-dhcp-pd-per-device-05.tx= t > >> Status: > https://datatracker.ietf.org/doc/draft-ietf-v6ops-dhcp-pd-per-device/ > >> HTML: > https://www.ietf.org/archive/id/draft-ietf-v6ops-dhcp-pd-per-device-05.ht= ml > >> HTMLized: > https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-dhcp-pd-per-device > >> Diff: > https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-v6ops-dhcp-pd-per-= device-05 > >> > >> Abstract: > >> > >> This document discusses an IPv6 deployment scenario when individua= l > >> clients connected to large broadcast networks (such as enterprise > >> networks or public Wi-Fi networks) are allocated unique prefixes v= ia > >> DHCPv6 Prefix Delegation (DHCPv6-PD). > >> > >> > >> > >> The IETF Secretariat > >> > >> > > > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops > --000000000000e5016f06097bcc87 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks! That will be fixed in the next revision.
=
On Mon= , Nov 6, 2023 at 12:49=E2=80=AFPM Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
Nit: in Figure 1 = this address needs an additional ':' or 3 other hextets:

2001:db8:ddd0:2:6666

Alex

Le 05/11/2023 =C3=A0 17:17, Jen Linkova a =C3=A9crit=C2=A0:
> Hello,
>
> Following the conclusion of the WGLC (thanks to everyone who
> commented!), we've submitted a -05 version with the following chan= ges:
> 1. Making it more clear that the draft requires the network to
> delegate a SLAAC-suitable prefix, and /64 is currently required for > SLAAC to work - but it=C2=A0 doesn't have to be like that in the f= uture.
> Examples also use /64. Brian, does it address your comment?
> 2. To address most of Ole's comments:
>=C2=A0 =C2=A0 2.1 Making it explicit that the draft only covers the net= work
> behavior, while host requirements are out of scope.
>=C2=A0 =C2=A0 2.2 Clarifying that the network can support both flat and=
> hierarchical models - it's up to the host to specify the hint.
> 3. Rewriting examples in the prefix length consideration section to > make it clearer that the proposal does not require an excessive amount=
> of IPv6 space.
>
>
>
> On Sun, Nov 5, 2023 at 4:54=E2=80=AFPM <internet-drafts@ietf.org> wrote:<= br> >> A new version of Internet-Draft draft-ietf-v6ops-dhcp-pd-per-devic= e-05.txt has
>> been successfully submitted by Jen Linkova and posted to the
>> IETF repository.
>>
>> Name:=C2=A0 =C2=A0 =C2=A0draft-ietf-v6ops-dhcp-pd-per-device
>> Revision: 05
>> Title:=C2=A0 =C2=A0 Using DHCPv6-PD to Allocate Unique IPv6 Prefix= per Client in Large Broadcast Networks
>> Date:=C2=A0 =C2=A0 =C2=A02023-11-05
>> Group:=C2=A0 =C2=A0 v6ops
>> Pages:=C2=A0 =C2=A0 20
>> URL:=C2=A0 =C2=A0 =C2=A0 https://www.ietf.org/archive/id/draft-ietf-v6ops-dhcp-pd-per-device= -05.txt
>> Status:=C2=A0 =C2=A0ht= tps://datatracker.ietf.org/doc/draft-ietf-v6ops-dhcp-pd-per-device/
>> HTML:=C2=A0 =C2=A0 =C2=A0https://www.ietf.org/archive/id/draft-ietf-v6ops-dhcp-pd-per-devic= e-05.html
>> HTMLized: https://= datatracker.ietf.org/doc/html/draft-ietf-v6ops-dhcp-pd-per-device
>> Diff:=C2=A0 =C2=A0 =C2=A0https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-v6op= s-dhcp-pd-per-device-05
>>
>> Abstract:
>>
>>=C2=A0 =C2=A0 =C2=A0This document discusses an IPv6 deployment scen= ario when individual
>>=C2=A0 =C2=A0 =C2=A0clients connected to large broadcast networks (= such as enterprise
>>=C2=A0 =C2=A0 =C2=A0networks or public Wi-Fi networks) are allocate= d unique prefixes via
>>=C2=A0 =C2=A0 =C2=A0DHCPv6 Prefix Delegation (DHCPv6-PD).
>>
>>
>>
>> The IETF Secretariat
>>
>>
>

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops
--000000000000e5016f06097bcc87--