Multi-Addressing Considerations for IPv6 Prefix Delegation
draft-templin-v6ops-pdhost-21
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Author | Fred Templin | ||
Last updated | 2018-12-16 (Latest revision 2018-06-14) | ||
RFC stream | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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
IPv6 prefixes are typically delegated to requesting routers which assign them to their downstream-attached links and networks. The requesting node can provision the prefix according to whether it acts as a router on behalf of any downstream networks and/or as a host on behalf of its local applications. In the latter case, the requesting node can use portions of the delegated prefix for its own multi- addressing purposes. This document therefore considers prefix delegation consideations for both the classic routing and various multi-addressing use cases.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)