Terminology for Constrained-Node Networks
draft-bormann-lwig-7228bis-03

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

• Versions
• 00
• 01
• 02
• 03

LWIG Working Group                                            C. Bormann
Internet-Draft                                   Universitaet Bremen TZI
Intended status: Informational                                  M. Ersue
Expires: January 3, 2019                    Nokia Solutions and Networks
                                                              A. Keranen
                                                                Ericsson
                                                                C. Gomez
                                                               UPC/i2CAT
                                                           July 02, 2018

               Terminology for Constrained-Node Networks
                     draft-bormann-lwig-7228bis-03

Abstract

   The Internet Protocol Suite is increasingly used on small devices
   with severe constraints on power, memory, and processing resources,
   creating constrained-node networks.  This document provides a number
   of basic terms that have been useful in the standardization work for
   constrained-node networks.

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 3, 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

Bormann, et al.          Expires January 3, 2019                [Page 1]
Internet-Draft               CNN Terminology                   July 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.  Core Terminology  . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Constrained Nodes . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Constrained Networks  . . . . . . . . . . . . . . . . . .   5
       2.2.1.  Challenged Networks . . . . . . . . . . . . . . . . .   6
     2.3.  Constrained-Node Networks . . . . . . . . . . . . . . . .   6
       2.3.1.  LLN . . . . . . . . . . . . . . . . . . . . . . . . .   7
       2.3.2.  LoWPAN, 6LoWPAN . . . . . . . . . . . . . . . . . . .   7
   3.  Classes of Constrained Devices  . . . . . . . . . . . . . . .   8
   4.  Power Terminology . . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  Scaling Properties  . . . . . . . . . . . . . . . . . . .  11
     4.2.  Classes of Energy Limitation  . . . . . . . . . . . . . .  12
     4.3.  Strategies for Using Power for Communication  . . . . . .  13
   5.  Classes of Networks . . . . . . . . . . . . . . . . . . . . .  15
     5.1.  Classes of link layer MTU size  . . . . . . . . . . . . .  15
     5.2.  Class of Internet Integration . . . . . . . . . . . . . .  16
     5.3.  Classes of physical layer bit rate  . . . . . . . . . . .  16
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   8.  Informative References  . . . . . . . . . . . . . . . . . . .  18
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  22
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Introduction

   Small devices with limited CPU, memory, and power resources, so-
   called "constrained devices" (often used as sensors/actuators, smart
   objects, or smart devices) can form a network, becoming "constrained
   nodes" in that network.  Such a network may itself exhibit
   constraints, e.g., with unreliable or lossy channels, limited and
   unpredictable bandwidth, and a highly dynamic topology.

   Constrained devices might be in charge of gathering information in
   diverse settings, including natural ecosystems, buildings, and
   factories, and sending the information to one or more server
   stations.  They might also act on information, by performing some
   physical action, including displaying it.  Constrained devices may