Re: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-per-device-00.txt

On 19-May-23 03:59, Vasilenko Eduard wrote:
> Section 4 is still misleading people that SLAAC (and /64 as a consequence) are mandatory.

The draft says:

     because all IPv6 nodes are required to support SLAAC.

This is not quite true. BCP 220 (RFC 8504) says:

    Hosts MUST support IPv6 Stateless Address Autoconfiguration.

In the context of this draft, that discrepancy is unimportant.

Of course, sites MAY choose to deploy DHCPv6 instead of SLAAC, but that doesn't remove the MUST for hosts.

     Brian

> In fact, section 4 assumes some special "complex host" that has a virtual router inside. Is it still a host? Does the virtual router need additional specifications?
> Albeit, in the majority of cases, a normal host would not have a virtual router inside.
> Moreover, even virtualized host (with many VMs or Containers) would have a virtual switch inside, not a router.
> Hence, for the great majority of cases, SLAAC is not relevant.
> Section 4 is still misleading.
> 
> Nothing in the draft is about the possibility to use prefixes different from /64.
> 
> The draft is still targeted for one corner case (with a virtual router inside the host),
> Discarding the possibility to use the solution on a much broader set of use cases.
> 
> Ed/
> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Thursday, May 18, 2023 6:35 PM
> To: i-d-announce@ietf.org
> Cc: v6ops@ietf.org
> Subject: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-per-device-00.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the IPv6 Operations (V6OPS) WG of the IETF.
> 
>     Title           : Using DHCP-PD to Allocate Unique IPv6 Prefix per Device in Broadcast Networks
>     Authors         : Lorenzo Colitti
>                       Jen Linkova
>                       Xiao Ma
>     Filename        : draft-ietf-v6ops-dhcp-pd-per-device-00.txt
>     Pages           : 14
>     Date            : 2023-05-18
> 
> Abstract:
>     This document discusses the IPv6 deployment scenario when individual
>     devices connected to broadcast networks (like WiFi hotspots or
>     enterprise networks) are allocated unique prefixes via DHCP-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-00.html
> 
> 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
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops