Limited Domains and Internet Protocols
draft-carpenter-limited-domains-03

Document Type Active Internet-Draft (individual)
Last updated 2018-09-11
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                                       B. Carpenter
Internet-Draft                                         Univ. of Auckland
Intended status: Informational                                    B. Liu
Expires: March 16, 2019                              Huawei Technologies
                                                      September 12, 2018

                 Limited Domains and Internet Protocols
                   draft-carpenter-limited-domains-03

Abstract

   There is a noticeable trend towards network requirements, behaviours
   and semantics that are specific to a limited region of the Internet
   and a particular set of requirements.  Policies, default parameters,
   the options supported, the style of network management and security
   requirements may vary.  This document reviews examples of such
   limited domains and emerging solutions, and develops a related
   taxonomy.  It shows the needs for a precise definition of a limited
   domain boundary and for a corresponding protocol to allow nodes to
   discover where such a boundary exists.

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 March 16, 2019.

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

Carpenter & Liu          Expires March 16, 2019                 [Page 1]
Internet-Draft               Limited Domains              September 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Failure Modes in Today's Internet . . . . . . . . . . . . . .   3
   3.  Examples of Limited Domain Requirements . . . . . . . . . . .   4
   4.  Examples of Limited Domain Solutions  . . . . . . . . . . . .   6
   5.  Taxonomy of Limited Domains . . . . . . . . . . . . . . . . .   9
     5.1.  The Domain as a Whole . . . . . . . . . . . . . . . . . .   9
     5.2.  Individual Nodes  . . . . . . . . . . . . . . . . . . . .  10
     5.3.  The Domain Boundary . . . . . . . . . . . . . . . . . . .  10
     5.4.  Topology  . . . . . . . . . . . . . . . . . . . . . . . .  10
     5.5.  Technology  . . . . . . . . . . . . . . . . . . . . . . .  11
     5.6.  Connection to the Internet  . . . . . . . . . . . . . . .  11
     5.7.  Security, Trust and Privacy Model . . . . . . . . . . . .  11
     5.8.  Operations  . . . . . . . . . . . . . . . . . . . . . . .  12
   6.  Common Features of Limited Domains  . . . . . . . . . . . . .  12
   7.  Defining a Limited Domain Boundary  . . . . . . . . . . . . .  13
   8.  Defining Protocol Scope . . . . . . . . . . . . . . . . . . .  13
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   11. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  13
   12. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   13. Informative References  . . . . . . . . . . . . . . . . . . .  14
   Appendix A.  Change log [RFC Editor: Please remove] . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   As the Internet continues to grow and diversify, with a realistic
   prospect of tens of billions of nodes being connected directly and
   indirectly, there is a noticeable trend towards local requirements,
   behaviours and semantics.  The word "local" should be understood in a
   special sense, however.  In some cases it may refer to geographical
   and physical locality - all the nodes in a single building, on a
   single campus, or in a given vehicle.  In other cases it may refer to
   a defined set of users or nodes distributed over a much wider area,
Show full document text