[homenet] Fwd: New Version Notification for draft-ietf-homenet-prefix-assignment-01.txt

[Pierre Pfister <[e-mail]>]

Hello group,

I updated version -01 of the Homenet prefix assignment draft.

Changes since -00 are:
- Add a paragraph specifying that Route Information Options must be included in router advertisements, providing in-home prefixes information.
- Lost Delegated Prefixes are advertised up to 2 hours (In agreement with SLAAC and RFC7084).
- Deprecated Delegated Prefixes (preferred lifetime = 0) are not used for new assignments (Unless configuration states otherwise or no other prefix is available).
- New **proposal** for autonomously generated ULAs. If no IPv6 prefix is available, ULA generation is a ‘SHOULD’. The proposition also deals with network splits.

Please notice that the change concerning the ULA generation is a hot topic. 
This is a proposal, trying to provide a solution to the different concerns expressed on the dedicated thread:

Comments are welcome.

Regards,

- Pierre


> 
> A new version of I-D, draft-ietf-homenet-prefix-assignment-01.txt
> has been successfully submitted by Pierre Pfister and posted to the
> IETF repository.
> 
> Name:		draft-ietf-homenet-prefix-assignment
> Revision:	01
> Title:		Prefix and Address Assignment in a Home Network
> Document date:	2014-10-24
> Group:		homenet
> Pages:		32
> URL:            http://www.ietf.org/internet-drafts/draft-ietf-homenet-prefix-assignment-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-homenet-prefix-assignment/
> Htmlized:       http://tools.ietf.org/html/draft-ietf-homenet-prefix-assignment-01
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-prefix-assignment-01
> 
> Abstract:
>   This memo describes a home network prefix and address assignment
>   algorithm running on top of any 'flooding protocol' that fulfills the
>   specified requirements.  It is expected that home border routers are
>   allocated one or multiple IPv6 prefixes through DHCPv6 Prefix
>   Delegation (PD) or that prefixes are made available through other
>   means.  An IPv4 address can also be assigned and private addresses be
>   used with NAT to provide IPv4 connectivity.  In both cases, provided
>   prefixes need to be efficiently divided among the multiple links, and
>   routers need to obtain addresses.  This document describes a
>   distributed algorithm for IPv4 and IPv6 prefixes division, assignment
>   and router's address assignment, and specifies how hosts can be given
>   addresses and configuration options using DHCP or SLAAC.
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat
>