SLAAC with prefixes of arbitrary length in PIO (Variable SLAAC) - A Problem Statement
draft-mishra-v6ops-variable-slaac-problem-stmt-01

Document Type Active Internet-Draft (individual)
Authors Gyan Mishra  , Alexandre Petrescu  , Naveen Kottapalli  , Dusan Mudric  , Dmytro Shytyi 
Last updated 2020-10-30
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
6MAN Working Group                                             G. Mishra
Internet-Draft                                              Verizon Inc.
Intended status: Informational                               A. Petrescu
Expires: May 3, 2021                                           CEA, LIST
                                                           N. Kottapalli
                                                           Benu Networks
                                                               D. Mudric
                                                                   Ciena
                                                               D. Shytyi
                                                                     SFR
                                                        October 30, 2020

  SLAAC with prefixes of arbitrary length in PIO (Variable SLAAC) - A
                           Problem Statement
           draft-mishra-v6ops-variable-slaac-problem-stmt-01

Abstract

   In the past, various IPv6 addressing models have been proposed based
   on a subnet hierarchy embedding a 64-bit prefix.  The last remnant of
   IPv6 classful addressing is a inflexible interface identifier
   boundary at /64.  This document details the 64-bit boundary problem
   statement.

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 May 3, 2021.

Copyright Notice

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

Mishra, et al.             Expires May 3, 2021                  [Page 1]
Internet-Draft               Variable SLAAC                 October 2020

   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.

Table of Contents

   1.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Variable SLAAC Use Cases  . . . . . . . . . . . . . . . . . .   5
     4.1.  Permission-less Extension of the Network  . . . . . . . .   5
     4.2.  Private Networks  . . . . . . . . . . . . . . . . . . . .   6
     4.3.  Mobile IPv6 . . . . . . . . . . . . . . . . . . . . . . .   6
     4.4.  Home and SOHO . . . . . . . . . . . . . . . . . . . . . .   7
     4.5.  3GPP V2I and V2V networking . . . . . . . . . . . . . . .   7
     4.6.  Smart Traffic Lights  . . . . . . . . . . . . . . . . . .   8
     4.7.  6lo . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.8.  Large ISP's backbone POP  . . . . . . . . . . . . . . . .   9
     4.9.  Permission-less extension of the Network  . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  ChangeLog  . . . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  Introduction

   From the beginning, the IPv6 addressing plan was based on a 128 bit
   address format made up of 8 hextets which were broken down into a 64
   bit four hextet prefix and 64 bit four hextet interface identifier.
Show full document text