IPv6 Prefix Delegation Models
draft-templin-v6ops-pdhost-17

Document Type Active Internet-Draft (individual)
Last updated 2017-12-14
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                         December 14, 2017
Expires: June 17, 2018

                     IPv6 Prefix Delegation Models
                   draft-templin-v6ops-pdhost-17.txt

Abstract

   IPv6 prefixes are typically delegated to requesting routers which
   then use them to number their downstream-attached links and networks.
   This document considers prefix delegation models according to whether
   the requesting router acts as a router on behalf of any downstream
   networks, as host on behalf of its local applications or as both.

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 https://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 June 17, 2018.

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
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   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.

Templin                   Expires June 17, 2018                 [Page 1]
Internet-Draft      IPv6 Prefix Delegation for Hosts       December 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Multi-Addressing Considerations . . . . . . . . . . . . . . .   6
   4.  Multi-Addressing Alternatives for Delegated Prefixes  . . . .   7
   5.  Address Autoconfiguration Considerations  . . . . . . . . . .   7
   6.  MLD/DAD Implications  . . . . . . . . . . . . . . . . . . . .   8
   7.  Dynamic Routing Protocol Implications . . . . . . . . . . . .   8
   8.  IPv6 Neighbor Discovery Implications  . . . . . . . . . . . .   8
   9.  ICMPv6 Implications . . . . . . . . . . . . . . . . . . . . .   9
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   11. Security Considerations . . . . . . . . . . . . . . . . . . .   9
   12. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     13.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .  13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   IPv6 Prefix Delegation (PD) entails 1) the communication of a prefix
   from a Delegating Router to a Requesting Router, 2) a representation
   of the prefix in the Delegating Router's routing table, and 3) a
   control messaging service between the Delegating and Requesting
   Routers to maintain prefix lifetimes.  Following delegation, the
   prefix is available for the Requesting Router's exclusive use and is
   not shared with any other nodes.  This document considers prefix
   delegation models where the Requesting Router is a node that acts as
   a router on behalf of any downstream networks, as host on behalf of
   its local applications or as both.

   The Requesting Router explcitly requests prefix delegations via an
   on-link Delegating Router.  The Delegating Router may host the prefix
   delegation service locally, or it may forward prefix delegation
   requests to supporting infrastructure located elsewhere in the
   operator's network (e.g. as in the DHCPv6 relay agent model
   [RFC3315][RFC3633]).  Regardless of where the actual prefix
   delegation server resides, however, the Delegating Router provides
   the Requesting Router's first-hop interface to the service.  The
   following paragraphs present prefix delegation models.

   For nodes that connect downstream-attached networks (e.g., a
   cellphone that connects a "tethered" Internet of Things (IoT)
   network, a server that hosts a complex internal network of virtual
Show full document text