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

Document Type Active Internet-Draft (individual)
Last updated 2018-06-10
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                                  S. Jiang
Expires: December 13, 2018                  Huawei Technologies Co., Ltd
                                                           June 11, 2018

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

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.  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 December 13, 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

Carpenter & Jiang       Expires December 13, 2018               [Page 1]
Internet-Draft               Limited Domains                   June 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.  Examples of Limited Domain Requirements . . . . . . . . . . .   3
   3.  Examples of Limited Domain Solutions  . . . . . . . . . . . .   5
   4.  Common Aspects of Limited Domains . . . . . . . . . . . . . .   7
   5.  The Need to Define a Limited Domain Boundary  . . . . . . . .   8
   6.  Defining Protocol Scope . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   10. Informative References  . . . . . . . . . . . . . . . . . . .   8
   Appendix A.  Change log [RFC Editor: Please remove] . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

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,
   but drawn together by a single virtual network over the Internet, or
   a single physical network running partially in parallel with the
   Internet.  We expand on these possibilities below.  To capture the
   topic, this document refers to such networks as "limited domains".

   The phrase "Balkanization of the Internet" has often been used to
   criticise mechanisms that block the free flow of information across
   the network.  That is not the topic of this document, which does not
   discuss filtering mechanisms and does not apply to protocols that are
   designed for use across the whole Internet.

   The requirements of limited domains will be different in different
   scenarios.  Policies, default parameters, and the options supported
   may vary.  Also, the style of network management may vary, between a
   completely unmanaged network, one with fully autonomic management,
Show full document text