IPv6 Prefix Delegation for Hosts
draft-templin-v6ops-pdhost-04
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (individual) | |
| Last updated | 2017-02-19 (latest revision 2016-08-18) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-templin-v6ops-pdhost-04.txt
Abstract
IPv6 prefixes are typically delegated to requesting routers which then use them to number their downstream-attached links and networks. The requesting router then acts as a router between the downstream- attached hosts and the upstream Internetwork, and can also act as a host under the weak end system model. This document considers the case when the "requesting router" is actually a simple host which receives a delegated prefix that it can use solely for its own internal multi-addressing purposes under the strong end system model. This method can be applied in a wide variety of use cases to allow ample address availability without impacting link performance.
Authors
Fred Templin (fltemplin@acm.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)