Subject: [Casm] Fwd: Last Call: <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> (Unique IPv6 Prefix Per Host) to Best Current Practice

From: "Marc Blanchet" <[email-masked]>
Date: Tue, 23 May 2017 15:51:53 -0400

hello,
  this could really benefit from CASM architecture, IMHO.

Marc.

Forwarded message:

> From: The IESG <[email-masked]>
> To: IETF-Announce <[email-masked]>
> Cc: [email-masked], [email-masked], 
> [email-masked], 
> [email-masked], 
> [email-masked]
> Subject: Last Call: 
> <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> (Unique IPv6 
> Prefix Per Host) to Best Current Practice
> Date: Tue, 23 May 2017 12:41:43 -0700
>
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'Unique IPv6 Prefix Per Host'
>   <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> as Best 
> Current
> Practice
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> [email-masked] mailing lists by 2017-06-06. Exceptionally, comments may 
> be
> sent to [email-masked] instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> 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 file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-per-host/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-per-host/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> The document contains these normative downward references.
> See RFC 3967 for additional information:
>     rfc6106: IPv6 Router Advertisement Options for DNS Configuration 
> (Proposed Standard - IETF stream)
>     rfc4941: Privacy Extensions for Stateless Address 
> Autoconfiguration in IPv6 (Draft Standard - IETF stream)
>     rfc4862: IPv6 Stateless Address Autoconfiguration (Draft Standard 
> - IETF stream)
>     rfc3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) 
> (Proposed Standard - IETF stream)