Prefix and Address Assignment in a Home Network
draft-pfister-homenet-prefix-assignment-02
Document | Type |
Replaced Internet-Draft
(homenet WG)
Expired & archived
|
|
---|---|---|---|
Authors | Pierre Pfister , Benjamin Paterson , Jari Arkko | ||
Last updated | 2014-09-03 (Latest revision 2014-06-30) | ||
Replaced by | draft-ietf-homenet-prefix-assignment | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-homenet-prefix-assignment | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Pierre Pfister
Benjamin Paterson
Jari Arkko
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)