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

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

       Multi-Addressing Considerations for IPv6 Prefix Delegation
                   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.

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 December 16, 2018.

Copyright Notice

   Copyright (c) 2018 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

Templin                 Expires December 16, 2018               [Page 1]
Internet-Draft Multi-Addressing for IPv6 Prefix Delegation     June 2018

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Multi-Addressing Considerations . . . . . . . . . . . . . . .   6
   4.  Multi-Addressing Alternatives for Delegated Prefixes  . . . .   7
   5.  Address Autoconfiguration Considerations  . . . . . . . . . .   8
   6.  MLD/DAD Implications  . . . . . . . . . . . . . . . . . . . .   8
   7.  Dynamic Routing Protocol Implications . . . . . . . . . . . .   8
   8.  IPv6 Neighbor Discovery Implications  . . . . . . . . . . . .   9
   9.  ICMPv6 Implications . . . . . . . . . . . . . . . . . . . . .   9
   10. Prefix Delegation Services  . . . . . . . . . . . . . . . . .  10
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   12. Security Considerations . . . . . . . . . . . . . . . . . . .  10
   13. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     14.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     14.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .  13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   IPv6 Prefix Delegation (PD) entails 1) the communication of a prefix
   from a server to a requesting router, 2) a representation of the
   prefix in the network's Routing Information Base (RIB) and the first-
   hop router's forwarding information base (FIB), and 3) a control
   messaging service 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 multi-addressing considerations for requesting nodes that
   acts as a router on behalf of any downstream networks and/or as a
   host on behalf of its local applications.

   For nodes that connect downstream-attached networks (e.g., a
   cellphone that connects a "tethered" Internet of Things (IoT), a
   laptop computer with a complex internal network of virtual machines,
   etc.), the classic routing model applies as shown in Figure 1:

Templin                 Expires December 16, 2018               [Page 2]
Internet-Draft Multi-Addressing for IPv6 Prefix Delegation     June 2018

                               .---------.
Show full document text