2. Core Terminology
There are two important aspects to scaling within the Internet of Things:
-
scaling up Internet technologies to a large number [FIFTY-BILLION] of inexpensive nodes, while
-
scaling down the characteristics of each of these nodes and of the networks being built out of them, to make this scaling up economically and physically viable.
The need for scaling down the characteristics of nodes leads to "constrained nodes".
2.1. Constrained Nodes
The term "constrained node" is best defined by contrasting the characteristics of a constrained node with certain widely held expectations on more familiar Internet nodes:
Constrained Node: A node where some of the characteristics that are otherwise pretty much taken for granted for Internet nodes at the time of writing are not attainable, often due to cost constraints and/or physical constraints on characteristics such as size, weight, and available power and energy. The tight limits on power, memory, and processing resources lead to hard upper bounds on state, code space, and processing cycles, making optimization of energy and network bandwidth usage a dominating consideration in all design requirements. Also, some layer-2 services such as full connectivity and broadcast/multicast may be lacking.
While this is not a rigorous definition, it is grounded in the state of the art and clearly sets apart constrained nodes from server systems, desktop or laptop computers, powerful mobile devices such as smartphones, etc. There may be many design considerations that lead to these constraints, including cost, size, weight, and other scaling factors.
(An alternative term, when the properties as a network node are not in focus, is "constrained device".)
There are multiple facets to the constraints on nodes, often applying in combination, for example:
-
constraints on the maximum code complexity (ROM/Flash),
-
constraints on the size of state and buffers (RAM),
-
constraints on the amount of computation feasible in a period of time ("processing power"),
-
constraints on the available power, and
-
constraints on user interface and accessibility in deployment (ability to set keys, update software, etc.).
Section 3 defines a small number of interesting classes ("class-N" for N = 0, 1, 2) of constrained nodes focusing on relevant combinations of the first two constraints. With respect to available power, [RFC6606] distinguishes "power-affluent" nodes (mains-powered or regularly recharged) from "power-constrained nodes" (battery-powered or energy-harvesting).
The use of constrained nodes in networks often also leads to constraints on the networks themselves. However, there may also be constraints on networks that are largely independent of those of the nodes. We therefore distinguish "constrained networks" from "constrained-node networks".
2.2. Constrained Networks
We define "constrained network" in a similar way:
Constrained Network: A network where some of the characteristics pretty much taken for granted with link layers in common use in the Internet at the time of writing are not attainable.
Constraints may include:
-
low achievable bitrate/throughput (including limits on duty cycle),
-
high packet loss and high variability of packet loss (delivery rate),
-
highly asymmetric link characteristics,
-
severe penalties for using larger packets (e.g., high packet loss due to link-layer fragmentation),
-
limits on reachability over time (a substantial number of devices may power off at any point in time but periodically "wake up" for brief periods of time),
-
lack of (or severe constraints on) advanced services such as IP multicast.
More generally, we speak of constrained networks whenever at least some of the nodes involved in the network exhibit these characteristics.
Again, there may be several reasons for this:
-
cost constraints on the network,
-
constraints of the nodes (for constrained-node networks),
-
physical constraints (e.g., power constraints, environmental constraints, media constraints such as underwater operation, limited spectrum for very high density, electromagnetic compatibility),
-
regulatory constraints, such as very limited spectrum availability (including limits on effective radiated power and duty cycle) or explosion safety,
-
technology constraints, such as older and lower-speed technologies that are still operational and may need to stay in use for some more time.
2.2.1. Challenged Networks
A constrained network is not necessarily a "challenged network" [FALL]:
Challenged Network: A network that has serious trouble maintaining what an application would today expect of the end-to-end IP model, e.g., by:
-
not being able to offer end-to-end IP connectivity at all,
-
exhibiting serious interruptions in end-to-end IP connectivity, or
-
exhibiting delay well beyond the Maximum Segment Lifetime (MSL) defined by TCP [RFC0793].
All challenged networks are constrained networks in some sense, but not all constrained networks are challenged networks. There is no well-defined boundary between the two, though. Delay-Tolerant Networking (DTN) has been designed to cope with challenged networks [RFC4838].
2.3. Constrained-Node Networks
Constrained-Node Network: A network whose characteristics are influenced by being composed of a significant portion of constrained nodes.
A constrained-node network always is a constrained network because of the network constraints stemming from the node constraints, but it may also have other constraints that already make it a constrained network.
The rest of this subsection introduces two additional terms that are in active use in the areas of work that are the focus of this document; their meanings are not well defined in the documents that use them.
2.3.1. LLN
A related term that has been used to describe the focus of the IETF ROLL working group is "Low-Power and Lossy Network (LLN)". The ROLL (Routing Over Low-Power and Lossy) terminology document [RFC7102] defines LLNs as follows:
LLN: Low-Power and Lossy Network. Typically composed of many embedded devices with limited power, memory, and processing resources interconnected by a variety of links, such as IEEE 802.15.4 or low-power Wi-Fi. There is a wide scope of application areas for LLNs, including industrial monitoring, building automation (heating, ventilation, and air conditioning (HVAC), lighting, access control, fire), connected home, health care, environmental monitoring, urban sensor networks, energy management, assets tracking, and refrigeration.
Beyond that, LLNs often exhibit considerable loss at the physical layer, with significant variability of the delivery rate, and some short-term unreliability, coupled with some medium-term stability that makes it worthwhile to both construct directed acyclic graphs that are medium-term stable for routing and do measurements on the edges such as Expected Transmission Count (ETX) [RFC6551]. Not all LLNs comprise low-power nodes [RPL-DEPLOYMENT].
LLNs typically are composed of constrained nodes; this leads to the design of operation modes such as the "non-storing mode" defined by RPL (the IPv6 Routing Protocol for Low-Power and Lossy Networks [RFC6550]). So, in the terminology of the present document, an LLN is a constrained-node network with certain network characteristics, which include constraints on the network as well.
2.3.2. LoWPAN, 6LoWPAN
One interesting class of a constrained network often used as a constrained-node network is "LoWPAN" [RFC4919], a term inspired from the name of an IEEE 802.15.4 working group (low-rate wireless personal area networks (LR-WPANs)). The expansion of the LoWPAN acronym, "Low-Power Wireless Personal Area Network", contains a hard-to-justify "Personal" that is due to the history of task group naming in IEEE 802 more than due to an orientation of LoWPANs around a single person. Actually, LoWPANs have been suggested for urban monitoring, control of large buildings, and industrial control applications, so the "Personal" can only be considered a vestige. Occasionally, the term is read as "Low-Power Wireless Area Networks" [WEI]. Originally focused on IEEE 802.15.4, "LoWPAN" (or when used for IPv6, "6LoWPAN") also refers to networks built from similarly constrained link-layer technologies [V6-BTLE] [V6-DECT-ULE] [V6-G9959].