[v6ops] Fwd: I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt

In the 2nd para of Sec. 4, it reads:

"The Unique IPv6 prefix can be derived from a locally managed
   pool or aggregate IPv6 block assigned to the First Hop Provider
   Router or from a centrally allocated pool.”

In the case the prefix is assigned from a centrally allocated pool, does this scenario include the following cases?:

	o all prefixes assigned to devices on the same shared network may not be aggregatable into a single shorter prefix.
	o /64 prefixes may be assigned randomly to different devices on different share network.

---
DY

> Begin forwarded message:
> 
> From: internet-drafts@ietf.org
> Subject: [v6ops] I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt
> Date: 31 July 2017 at 16:00:57 GMT+9
> To: <i-d-announce@ietf.org>
> Cc: v6ops@ietf.org
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IPv6 Operations WG of the IETF.
> 
>        Title           : Unique IPv6 Prefix Per Host
>        Authors         : John Jason Brzozowski
>                          Gunter Van De Velde
> 	Filename        : draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt
> 	Pages           : 8
> 	Date            : 2017-07-31
> 
> Abstract:
>   In some IPv6 environments, the need has arisen for hosts to be able
>   to utilize a unique IPv6 prefix, even though the link or media may be
>   shared.  Typically hosts (subscribers) on a shared network, either
>   wired or wireless, such as Ethernet, WiFi, etc., will acquire unique
>   IPv6 addresses from a common IPv6 prefix that is allocated or
>   assigned for use on a specific link.
> 
>   In most deployments today, IPv6 address assignment from a single IPv6
>   prefix on a shared network is done by either using IPv6 stateless
>   address auto-configuration (SLAAC) and/or stateful DHCPv6.  While
>   this is still viable and operates as designed, there are some large
>   scale environments where this concept introduces significant
>   performance challenges and implications, specifically related to IPv6
>   router and neighbor discovery.
> 
>   This document outlines an approach utilising existing IPv6 protocols
>   to allow hosts to be assigned a unique IPv6 prefix (instead of a
>   unique IPv6 address from a shared IPv6 prefix).  Benefits of unique
>   IPv6 prefix over a unique IPv6 address from the service provider
>   include improved subscriber isolation and enhanced subscriber
>   management.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-per-host/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-v6ops-unique-ipv6-prefix-per-host-07
> https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-unique-ipv6-prefix-per-host-07
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-unique-ipv6-prefix-per-host-07
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops