IPv6 Prefix Delegation for Hosts
draft-templin-v6ops-pdhost-05

Document Type Active Internet-Draft (individual)
Last updated 2017-03-27
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                    F. Templin, Ed.
Internet-Draft                              Boeing Research & Technology
Intended status: Informational                            March 27, 2017
Expires: September 28, 2017

                    IPv6 Prefix Delegation for Hosts
                   draft-templin-v6ops-pdhost-05.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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 28, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Templin                Expires September 28, 2017               [Page 1]
Internet-Draft         Prefix Delegation for Hosts            March 2017

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Multi-Addressing Considerations . . . . . . . . . . . . . . .   5
   4.  Multi-Addressing Alternatives for Delegated Prefixes  . . . .   5
   5.  MLD/DAD Implications  . . . . . . . . . . . . . . . . . . . .   6
   6.  IPv6 Neighbor Discovery Implications  . . . . . . . . . . . .   7
   7.  "Mixed Mode" Implications . . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     11.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   IPv6 Prefix Delegation (PD) entails 1) the communication of a prefix
   from a delegating authority to a requesting node, 2) a representation
   of the prefix in the routing system, and 3) a control messaging
   service to maintain delegated prefix lifetimes.  Following
   delegation, the prefix is available for the requesting node's
   exclusive use and is not shared with any other nodes.  An example
   IPv6 PD service is DHCPv6 PD [RFC3315][RFC3633].

   Using services such as DHCPv6 PD, a Delegating Router 'D' delegates a
   prefix 'P' to a Requesting Node 'R'' as shown in Figure 1:

Templin                Expires September 28, 2017               [Page 2]
Internet-Draft         Prefix Delegation for Hosts            March 2017

                        +---------------------+
                        |Delegating Router 'D'|
                        |   (Delegate 'P')    |
                        +----------+----------+
                                   |
                             .-(::::::::)
Show full document text