Multi-Addressing Considerations for IPv6 Prefix Delegation
draft-templin-v6ops-pdhost-21

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2018-12-16 (latest revision 2018-06-14)
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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-templin-v6ops-pdhost-21.txt

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

Fred Templin (fltemplin@acm.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)