Connecting Stub Networks to Existing Infrastructure
draft-lemon-stub-networks-02

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02

Internet Engineering Task Force                                 T. Lemon
Internet-Draft                                                Apple Inc.
Intended status: Best Current Practice                      2 March 2021
Expires: 3 September 2021

          Connecting Stub Networks to Existing Infrastructure
                      draft-lemon-stub-networks-02

Abstract

   This document describes a set of practices for connecting stub
   networks to adjacent infrastructure networks, as well as to larger
   network fabrics.  This is applicable in cases such as constrained
   (Internet of Things) networks where there is a need to provide
   functional parity of service discovery and reachability between
   devices on the stub network and devices on an adjacent infrastructure
   link (for example, a home network).

   The stub networks use case is intended to fully address the need to
   attach a single network link to an infrastructure network, where the
   attached link provides no through routing and in cases where
   integration to the infrastructure routing fabric (if any) is not
   available.

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 3 September 2021.

Copyright Notice

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

Lemon                   Expires 3 September 2021                [Page 1]
Internet-Draft          Connecting Stub Networks              March 2021

   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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Support for adjacent infrastructure links . . . . . . . . . .   4
     3.1.  Managing addressability on the adjacent infrastructure
           link  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  IP addressability already present on adjacent
               infrastructure link . . . . . . . . . . . . . . . . .   4
       3.1.2.  IP addressability not present on adjacent
               infrastructure link . . . . . . . . . . . . . . . . .   6
       3.1.3.  Resolving contention over which prefix to
               deprecate . . . . . . . . . . . . . . . . . . . . . .   6
       3.1.4.  Handling the presence of multiple stub routers  . . .   7
     3.2.  Managing addressability on the stub network . . . . . . .   7
       3.2.1.  Maintenance across stub router restarts . . . . . . .   8
       3.2.2.  Generating a ULA prefix to provide addressability . .   9
     3.3.  Managing reachability on the adjacent infrastructure
           link  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     3.4.  Managing reachability on the stub network . . . . . . . .   9
     3.5.  Providing discoverability of stub network hosts on the
           adjacent infrastructure link  . . . . . . . . . . . . . .  10
     3.6.  Providing discoverability of adjacent infrastructure hosts
           on the stub network . . . . . . . . . . . . . . . . . . .  12
   4.  Providing reachability to IPv4 services to the stub
           network . . . . . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  NAT64 provided by infrastructure  . . . . . . . . . . . .  12
     4.2.  NAT64 provided by stub router(s)  . . . . . . . . . . . .  13
   5.  Handling partitioning events on a stub network  . . . . . . .  14
   6.  Support for non-adjacent links  . . . . . . . . . . . . . . .  14
     6.1.  Acquiring an off-stub-network-routable prefix for the stub
           network . . . . . . . . . . . . . . . . . . . . . . . . .  15
     6.2.  Arranging for routing to a stub network's off-stub-network
           routable prefix . . . . . . . . . . . . . . . . . . . . .  16
     6.3.  Making service advertisements available on non-adjacent