1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
|
<pre>Internet Engineering Task Force (IETF) JP. Vasseur
Request for Comments: 7102 Cisco Systems, Inc.
Category: Informational January 2014
ISSN: 2070-1721
<span class="h1">Terms Used in Routing for Low-Power and Lossy Networks</span>
Abstract
This document provides a glossary of terminology used in routing
requirements and solutions for networks referred to as Low-Power and
Lossy Networks (LLNs). An LLN is typically composed of many embedded
devices with limited power, memory, and processing resources
interconnected by a variety of links. There is a wide scope of
application areas for LLNs, including industrial monitoring, building
automation (e.g., heating, ventilation, air conditioning, lighting,
access control, fire), connected home, health care, environmental
monitoring, urban sensor networks, energy management, assets
tracking, and refrigeration.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7102">http://www.rfc-editor.org/info/rfc7102</a>.
<span class="grey">Vasseur Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7102">RFC 7102</a> LLN Routing Terms January 2014</span>
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Security Considerations .........................................<a href="#page-7">7</a>
<a href="#section-4">4</a>. Acknowledgements ................................................<a href="#page-7">7</a>
<a href="#section-5">5</a>. Informative References ..........................................<a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document provides a glossary of terminology used in routing
requirements and solutions for networks referred to as Low-Power and
Lossy Networks (LLNs).
LLNs are 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, air conditioning,
lighting, access control, fire), connected home, health care,
environmental monitoring, urban sensor networks, energy management,
assets tracking, and refrigeration.
Since these applications are usually highly specific (for example,
industrial automation, building automation, etc.), it is not uncommon
to see a number of disparate terms used to describe the same device
or functionality. Thus, in order to avoid confusion or
discrepancies, this document specifies the common terminology to be
used in all ROLL working group documents. The terms defined in this
document are used in [<a href="./rfc5548" title=""Routing Requirements for Urban Low-Power and Lossy Networks"">RFC5548</a>], [<a href="./rfc5673" title=""Industrial Routing Requirements in Low-Power and Lossy Networks"">RFC5673</a>], [<a href="./rfc5826" title=""Home Automation Routing Requirements in Low-Power and Lossy Networks"">RFC5826</a>], and [<a href="./rfc5867" title=""Building Automation Routing Requirements in Low-Power and Lossy Networks"">RFC5867</a>].
Terminology specific to a particular application is out of the scope
of this document.
<span class="grey">Vasseur Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7102">RFC 7102</a> LLN Routing Terms January 2014</span>
It is expected that all routing documents defining requirements or
specifying solutions for LLN will use the common terminology
specified in this document. This document should be listed as an
informative reference.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
Actuator: A field device that controls a set of equipment. For
example, an actuator might control and/or modulate the flow of a
gas or liquid, control electricity distribution, perform a
mechanical operation, etc.
AMI: Advanced Metering Infrastructure. Makes use of Smart Grid
technologies. A canonical Smart Grid application is smart-
metering.
Channel: Radio frequency sub-band used to transmit a modulated signal
carrying packets.
Channel Hopping: A procedure by which field devices synchronously
change channels during operation.
Commissioning Tool: Any physical or logical device temporarily added
to the network for the express purpose of setting up the network
and device operational parameters. The commissioning tool can
also be temporarily added to the LLN for scheduled or unscheduled
maintenance.
Closed Loop Control: A procedure whereby a device controller controls
an actuator based on input information sensed by one or more field
devices.
Controller: A field device that can receive sensor input and
automatically change the environment in the facility by
manipulating digital or analog actuators.
DA: Distribution Automation. Part of Smart Grid. Encompasses
technologies for maintenance and management of electrical
distribution systems.
DAG: Directed Acyclic Graph. A directed graph with no directed
cycles (a graph formed by a collection of vertices and directed
edges where each edge connects one vertex to another, such that
there is no way to start at some vertex v and follow a sequence of
edges that eventually loops back to vertex v again).
Data sink: A device that collects data from nodes in an LLN.
<span class="grey">Vasseur Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7102">RFC 7102</a> LLN Routing Terms January 2014</span>
Downstream: Data direction traveling from outside of the LLN (e.g.,
traffic coming from a LAN, WAN, or the Internet) via an LLN Border
Router (LBR), or in general, "deeper" in the Directed Acyclic
Graph computed by the routing protocol.
Field Device: A field device is a physical device placed in the
network's operating environment (e.g., plant, urban area, or
home). Field devices include sensors and actuators as well as
routers and Low-Power and Lossy Network Border Routers (LBRs). A
field device is usually (but not always) a device with constrained
CPU, memory footprint, storage capacity, bandwidth, and sometimes
power (battery operated). At the time of writing, for the sake of
illustration, a typical sensor or actuator would have a few
Kilobytes of RAM, a few dozens of Kilobytes of ROM/Flash memory, a
8-/16-/32-bit microcontroller, and communication capabilities
ranging from a few kbits/s to a few hundred kbits/s. Although
continuous improvement of hardware and software technologies is
expected, such devices will likely continue to be seen as
resource-constrained devices compared to computers and routers
used in the rest of the Internet.
Flash Memory: non-volatile memory that can be re-programmed.
FMS: Facility Management System. A global term applied across all
the vertical designations within a building, including heating,
ventilation, and air conditioning (also referred to as HVAC),
fire, security, lighting, and elevator control.
HART: Highway Addressable Remote Transducer. A group of
specifications for industrial process and control devices
administered by the HART Foundation (see [<a href="#ref-HART">HART</a>]). The latest
version for the specifications is HART7, which includes the
additions for WirelessHART.
HVAC: Heating, Ventilation, and Air Conditioning. A term applied to
mechanisms used to maintain the comfort level of an internal
space.
ISA: International Society of Automation. An ANSI accredited
standards-making society. ISA100 is an ISA committee whose
charter includes defining a family of standards for industrial
automation. [<a href="#ref-ISA100.11a">ISA100.11a</a>] is a working group within ISA100 that is
working on a standard for monitoring and non-critical process-
control applications.
LAN: Local Area Network.
<span class="grey">Vasseur Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7102">RFC 7102</a> LLN Routing Terms January 2014</span>
LBR: Low-Power and Lossy Network Border Router. A device that
connects the Low-Power and Lossy Network to another routing domain
such as a LAN, a WAN, or the Internet where a different routing
protocol may be in operation. The LBR acts as a routing device
and may possibly host other functions such as data collector or
aggregator.
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 (HVAC, lighting, access control, fire), connected home,
health care, environmental monitoring, urban sensor networks,
energy management, assets tracking, and refrigeration.
MP2P: Multipoint-to-Point. Used to describe a particular traffic
pattern (e.g., MP2P flows collecting information from many nodes
flowing upstream towards a collecting sink or an LBR).
MAC: Medium Access Control. Refers to algorithms and procedures used
by the data link layer to coordinate use of the physical layer.
Non-Sleepy Node: A node that always remains in a fully powered-on
state (i.e., always awake) where it has the capability to perform
communication.
Open Loop Control: A process whereby a plant operator manually
manipulates an actuator over the network where the decision is
influenced by information sensed by field devices.
PER: Packet Error Rate. A ratio of the number of unusable packets
(not received at all or received in error, even after any
applicable error correction has been applied) to the total number
of packets that would have been received in the absence of errors.
P2P: Point To Point. Refers to traffic exchanged between two nodes
(regardless of the number of hops between the two nodes).
P2MP: Point-to-Multipoint. Refers to traffic between one node and a
set of nodes. This is similar to the P2MP concept in Multicast or
MPLS Traffic Engineering ([<a href="./rfc4461" title=""Signaling Requirements for Point-to- Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)"">RFC4461</a>]and [<a href="./rfc4875" title=""Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)"">RFC4875</a>]). A common use
case for the Routing Protocol for Low-Power and Lossy Networks
(RPL) involves P2MP flows from or through a DAG root outward
towards other nodes contained in the DAG.
RAM: Random Access Memory. A volatile memory.
<span class="grey">Vasseur Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7102">RFC 7102</a> LLN Routing Terms January 2014</span>
RFID: Radio Frequency IDentification.
ROM: Read-Only Memory.
ROLL: Routing Over Low-Power and Lossy Networks.
RPL: An IPv6 Routing Protocol for Low-Power and Lossy Networks that
provides a mechanism whereby multipoint-to-point traffic from
devices inside the LLN towards a central control point as well as
point-to-multipoint traffic from the central control point to the
devices inside the LLN are supported. RPL also supports point-to-
point traffic between any arbitrary nodes in the LLN.
RPL Domain: A collection of RPL routers under the control of a single
administration. The boundaries of routing domains are defined by
network management by setting some links to be exterior, or inter-
domain, links.
Schedule: An agreed execution, wake-up, transmission, reception,
etc., timetable between two or more field devices.
Sensor: A device that measures a physical quantity and converts it to
an analog or digital signal that can be read by a program or a
user. Sensed data can be of many types: electromagnetic (e.g.,
current, voltage, power, or resistance), mechanical (e.g.,
pressure, flow, liquid density, or humidity), chemical (e.g.,
oxygen or carbon monoxide), acoustic (e.g., noise or ultrasound),
etc.
Sleepy Node: A node that may sometimes go into a sleep mode (i.e., go
into a low-power state to conserve power) and temporarily suspend
protocol communication. When not in sleep mode, the sleepy node
is in a fully powered-on state where it has the capability to
perform communication.
Smart Grid: A broad class of applications to network and automate
utility infrastructure.
Timeslot: A fixed time interval that may be used for the transmission
or reception of a packet between two field devices. A timeslot
used for communications is associated with a slotted-link.
Upstream: Data direction traveling from the LLN via the LBR to
outside of the LLN (LAN, WAN, or Internet) or generally closer to
the root of the DAG computed by the routing protocol.
WAN: Wide Area Network.
<span class="grey">Vasseur Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7102">RFC 7102</a> LLN Routing Terms January 2014</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
Since this document specifies terminology and does not specify new
procedures or protocols, it raises no new security issues.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Acknowledgements</span>
The authors would like to thank Christian Jacquenet, Tim Winter,
Pieter De Mil, David Meyer, Mukul Goyal, and Abdussalam Baryun for
their valuable feedback.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Informative References</span>
[<a id="ref-HART">HART</a>] HART Communication Foundation, <<a href="http://www.hartcomm.org">http://www.hartcomm.org</a>>.
[<a id="ref-ISA100.11a">ISA100.11a</a>]
ISA, "Wireless systems for industrial automation: Process
control and related applications", ISA 100.11a, May 2008,
<<a href="http://www.isa.org/Community/SP100WirelessSystemsforAutomation">http://www.isa.org/Community/</a>
<a href="http://www.isa.org/Community/SP100WirelessSystemsforAutomation">SP100WirelessSystemsforAutomation</a>>.
[<a id="ref-RFC4461">RFC4461</a>] Yasukawa, S., Ed., "Signaling Requirements for Point-to-
Multipoint Traffic-Engineered MPLS Label Switched Paths
(LSPs)", <a href="./rfc4461">RFC 4461</a>, April 2006.
[<a id="ref-RFC4875">RFC4875</a>] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. Yasukawa,
Ed., "Extensions to Resource Reservation Protocol - Traffic
Engineering (RSVP-TE) for Point-to-Multipoint TE Label
Switched Paths (LSPs)", <a href="./rfc4875">RFC 4875</a>, May 2007.
[<a id="ref-RFC5548">RFC5548</a>] Dohler, M., Ed., Watteyne, T., Ed., Winter, T., Ed., and D.
Barthel, Ed., "Routing Requirements for Urban Low-Power and
Lossy Networks", <a href="./rfc5548">RFC 5548</a>, May 2009.
[<a id="ref-RFC5673">RFC5673</a>] Pister, K., Ed., Thubert, P., Ed., Dwars, S., and T.
Phinney, "Industrial Routing Requirements in Low-Power and
Lossy Networks", <a href="./rfc5673">RFC 5673</a>, October 2009.
[<a id="ref-RFC5826">RFC5826</a>] Brandt, A., Buron, J., and G. Porcu, "Home Automation
Routing Requirements in Low-Power and Lossy Networks", <a href="./rfc5826">RFC</a>
<a href="./rfc5826">5826</a>, April 2010.
[<a id="ref-RFC5867">RFC5867</a>] Martocci, J., Ed., De Mil, P., Riou, N., and W. Vermeylen,
"Building Automation Routing Requirements in Low-Power and
Lossy Networks", <a href="./rfc5867">RFC 5867</a>, June 2010.
<span class="grey">Vasseur Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7102">RFC 7102</a> LLN Routing Terms January 2014</span>
Author's Address
JP. Vasseur
Cisco Systems, Inc.
1414 Massachusetts Avenue
Boxborough, MA 01719
US
EMail: jpv@cisco.com
Vasseur Informational [Page 8]
</pre>
|
