Self-configuring Stub Networks: Problem Statement
draft-lemon-stub-networks-ps-00

Document Type Active Internet-Draft (individual)
Last updated 2020-07-09
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)
Network Working Group                                           T. Lemon
Internet-Draft                                               Apple, Inc.
Intended status: Informational                              July 8, 2020
Expires: January 9, 2021

           Self-configuring Stub Networks: Problem Statement
                    draft-lemon-stub-networks-ps-00

Abstract

   IETF currently provides protocols for automatically connecting single
   hosts to existing network infrastructure.  This document describes a
   related problem: the problem of connecting a stub network (a
   collection of hosts behind a router) automatically to existing
   network infrastructure in the same manner.

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 January 9, 2021.

Copyright Notice

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

Lemon                    Expires January 9, 2021                [Page 1]
Internet-Draft       Stub Networks Problem Statement           July 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Interoperability Goals  . . . . . . . . . . . . . . . . .   4
     1.2.  Usability Goals . . . . . . . . . . . . . . . . . . . . .   5
     1.3.  State of the Art  . . . . . . . . . . . . . . . . . . . .   5
   2.  Possible Approaches . . . . . . . . . . . . . . . . . . . . .   6
     2.1.  Proxy ND  . . . . . . . . . . . . . . . . . . . . . . . .   6
       2.1.1.  Reachability  . . . . . . . . . . . . . . . . . . . .   6
       2.1.2.  Addressability  . . . . . . . . . . . . . . . . . . .   7
       2.1.3.  Discoverability . . . . . . . . . . . . . . . . . . .   7
       2.1.4.  Requirements  . . . . . . . . . . . . . . . . . . . .   7
       2.1.5.  Observations  . . . . . . . . . . . . . . . . . . . .   7
     2.2.  Stub reachability using RA  . . . . . . . . . . . . . . .   8
       2.2.1.  Reachability  . . . . . . . . . . . . . . . . . . . .   8
       2.2.2.  Addressability  . . . . . . . . . . . . . . . . . . .   8
       2.2.3.  Discoverability . . . . . . . . . . . . . . . . . . .   8
       2.2.4.  Requirements  . . . . . . . . . . . . . . . . . . . .   8
       2.2.5.  Observations  . . . . . . . . . . . . . . . . . . . .   8
     2.3.  Global reachability . . . . . . . . . . . . . . . . . . .   9
       2.3.1.  Reachability  . . . . . . . . . . . . . . . . . . . .   9
       2.3.2.  Addressability  . . . . . . . . . . . . . . . . . . .   9
       2.3.3.  Discoverability . . . . . . . . . . . . . . . . . . .  10
       2.3.4.  Requirements  . . . . . . . . . . . . . . . . . . . .  10
       2.3.5.  Observations  . . . . . . . . . . . . . . . . . . . .  10
     2.4.  Support for IPv4  . . . . . . . . . . . . . . . . . . . .  10
       2.4.1.  Reachability  . . . . . . . . . . . . . . . . . . . .  10
       2.4.2.  Addressability  . . . . . . . . . . . . . . . . . . .  11
       2.4.3.  Discoverability . . . . . . . . . . . . . . . . . . .  11
       2.4.4.  Requirements  . . . . . . . . . . . . . . . . . . . .  12
       2.4.5.  Observations  . . . . . . . . . . . . . . . . . . . .  12
   3.  Discoverability Options . . . . . . . . . . . . . . . . . . .  12
   4.  Multiple Egress, Multiple Link  . . . . . . . . . . . . . . .  13
   5.  Management Considerations . . . . . . . . . . . . . . . . . .  13
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  13
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   8.  IANA considerations . . . . . . . . . . . . . . . . . . . . .  14
   9.  Informative References  . . . . . . . . . . . . . . . . . . .  14
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction
Show full document text