idnits 2.17.1 draft-ietf-roll-terminology-13.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 30, 2013) is 3854 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Networking Working Group JP. Vasseur 3 Internet-Draft Cisco Systems, Inc 4 Intended status: Informational September 30, 2013 5 Expires: March 31, 2014 7 Terms used in Ruting for Low power And Lossy Networks 8 draft-ietf-roll-terminology-13.txt 10 Abstract 12 The documents provides a glossary of terminology used in routing 13 requirements and solutions for networks referred to as Low power and 14 Lossy Networks (LLN). An LLN is typically composed of many embedded 15 devices with limited power, memory, and processing resources 16 interconnected by a variety of links. There is a wide scope of 17 application areas for LLNs, including industrial monitoring, building 18 automation (e.g. Heating, Ventilating, Air Conditioning, lighting, 19 access control, fire), connected home, healthcare, environmental 20 monitoring, urban sensor networks, energy management, assets 21 tracking, refrigeration. 23 Status of This Memo 25 This Internet-Draft is submitted to IETF in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on March 31, 2014. 40 Copyright Notice 41 Copyright (c) 2013 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal Provisions 45 Relating to IETF Documents (http://trustee.ietf.org/license-info) 46 in effect on the date of publication of this document. Please 47 review these documents carefully, as they describe your rights 48 and restrictions with respect to this document. Code Components 49 extracted from this document must include Simplified BSD License 50 text as described in Section 4.e of the Trust Legal Provisions 51 and are provided without warranty as described in the Simplified 52 BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 59 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 60 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 61 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 62 6.1. Normative References . . . . . . . . . . . . . . . . . . 7 63 6.2. Informative References . . . . . . . . . . . . . . . . . 7 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 66 1. Introduction 68 The documents provides a glossary of terminology used in routing 69 requirements solutions for networks referred to as Low power and Lossy 70 Networks (LLN). 72 Low power and Lossy networks (LLNs) are typically composed of many 73 embedded devices with limited power, memory, and processing resources 74 interconnected by a variety of links, such as IEEE 802.15.4, Low 75 Power WiFi. There is a wide scope of application areas for LLNs, 76 including industrial monitoring, building automation (HVAC, lighting, 77 access control, fire), connected home, healthcare, environmental 78 monitoring, urban sensor networks, energy management, assets tracking 79 and refrigeration. 81 Since these applications are usually highly specific (for example 82 Industrial Automation, Building Automation, ...), it is not uncommon 83 to see a number of disparate terms to describe the same device or 84 functionality. Thus in order to avoid confusion or discrepancies, 85 this document specifies the common terminology to be used in all ROLL 86 Working Group documents. The terms defined in this document are used 87 in [RFC5548],[RFC5673], [RFC5826] and [RFC5867]. 89 Terminology specific to a particular application are out of the scope 90 of this document. 92 It is expected that all routing requirements documents defining 93 requirements or specifying routing solutions for LLN will use the 94 common terminology specified in this document. This document should 95 be listed as an informative reference. 97 2. Terminology 99 Actuator: a field device that controls a set of equipment. For 100 example, an actuator might control and/or modulate the flow of a gas 101 or liquid, control electricity distribution, perform a mechanical 102 operation, ... 104 AMI: Advanced Metering Infrastructure that makes use of Smart Grid 105 technologies. A canonical Smart Grid application is smart-metering. 107 Channel: Radio frequency sub-band used to transmit a modulated signal 108 carrying packets. 110 Channel Hopping: A procedure by which field devices synchronously 111 change channels during operation. 113 Commissioning Tool: Any physical or logical device temporarily added 114 to the network for the express purpose of setting up the network and 115 device operational parameters. The commisioning tool can also be 116 temporarily added to the LLN for scheduled or unscheduled 117 maintenance. 119 Closed Loop Control: A procedure whereby a device controller controls 120 an actuator based on input information sensed by one or more field 121 devices. 123 Controller: A field device that can receive sensor input and 124 automatically change the environment in the facility by manipulating 125 digital or analog actuators. 127 DA: Distribution Automation, part of Smart Grid. Encompasses 128 technologies for maintenance and management of electrical 129 distribution systems. 131 Directed Acyclic Graph: A directed graph with no directed cycles (a 132 graph formed by a collection of vertices and directed edges where 133 each edge connects one vertex to another, such that there is no way 134 to start at some vertex v and follow a sequence of edges that 135 eventually loops back to the edge v again) 137 Data sink: A device that collects data from nodes in an LLN. 139 Downstream: Data direction traveling from outside of the LLN (e.g. 140 traffic coming from a LAN, WAN or the Internet) via a LBR, or in 141 general "deeper" in the Directed Acyclic Graph computed by the 142 routing protocol. 144 Field Device: A field device is a physical device placed in the 145 network's operating environment (e.g. plant, urban or home). Field 146 devices include sensors, actuators as well as routers and Low power 147 and Lossy Network Border Router (LBR). A field device is usually 148 (but not always) a device with constrained CPU, memory footprint, 149 storage capacity, bandwidth and sometimes power (battery operated). 150 At the time of writing, for the sake of illustration, a typical 151 sensor or actuator would have a few KBytes of RAM, a few dozens of 152 KBytes of ROM/Flash memory, a 8/16/32 bit microcontroller and 153 communication capabilities ranging from a few Kbits/s to a few 154 hundreds of KBits/s. Although it is expected to see continuous 155 improvements of hardware and software technologies, such devices will 156 likely continue to be seen as resource constrained devices compared 157 compared to computers and routers used in the rest of the Internet. 159 Flash memory: non-volatile memory that can be re-programmed. 161 FMS: Facility Management System. A global term applied across all 162 the vertical designations within a building including, Heating, 163 Ventilating, and Air Conditioning also referred to as HVAC, Fire, 164 Security, Lighting and Elevator control. 166 HART: "Highway Addressable Remote Transducer", a group of 167 specifications for industrial process and control devices 168 administered by the HART Foundation (see [HART]). The latest version 169 for the specifications is HART7 which includes the additions for 170 WirelessHART. 172 HVAC: Heating, Ventilation and Air Conditioning. A term applied to 173 the comfort level of an internal space. 175 ISA: "International Society of Automation". ISA is an ANSI 176 accredited standards-making society. ISA100 is an ISA committee 177 whose charter includes defining a family of standards for industrial 178 automation. [ISA100.11a] is a working group within ISA100 that is 179 working on a standard for monitoring and non-critical process control 180 applications. 182 LAN: Local Area Network. 184 LBR: Low power and Lossy Network Border Router. The LBR is a device 185 that connects the Low power and Lossy Network to another routing 186 domain such as a Local Area Network (LAN), Wide Area Network (WAN) or 187 the Internet where a possibly different routing protocol is in 188 operation. The LBR acts as a routing device and may possibly host 189 other functions such as data collector or aggregator. 191 LLN: Low power and Lossy networks (LLNs) are typically composed of 192 many embedded devices with limited power, memory, and processing 193 resources interconnected by a variety of links, such as IEEE 802.15.4 194 or Low Power WiFi. There is a wide scope of application areas for 195 LLNs, including industrial monitoring, building automation (HVAC, 196 lighting, access control, fire), connected home, healthcare, 197 environmental monitoring, urban sensor networks, energy management, 198 assets tracking and refrigeration.. 200 MP2P: Multipoint-to-Point is used to describe a particular traffic 201 pattern (e.g. MP2P flows collecting information from many nodes 202 flowing upstream towards a collecting sink or an LBR). 204 MAC: Medium Access Control. Refers to algorithms and procedures used 205 by the data link layer to coordinate use of the physical layer. 207 Non-sleepy Node: A non-sleepy node is a node that always remains in a 208 fully powered on state (i.e. always awake) where it has the 209 capability to perform communication. 211 Open Loop Control: A process whereby a plant operator manually 212 manipulates an actuator over the network where the decision is 213 influenced by information sensed by field devices. 215 PER: Packet Error Rate. A ratio of the number of unusable packets 216 (not received at all, or received in error- even after any applicable 217 error correction has been applied) to the total number of packets 218 that would have been been received in the absence of errors. 220 P2P: Point To Point. This refers to traffic exchanged between two 221 nodes (regardless of the number of hops between the two nodes). 223 P2MP: Point-to-Multipoint traffic refers to traffic between one node 224 and a set of nodes. This is similar to the P2MP concept in Multicast 225 or MPLS Traffic Engineering ([RFC4461]and [RFC4875]). A common RPL 226 use case involves P2MP flows from or through a DAG root outward 227 towards other nodes contained in the DAG. 229 RAM: Random Access Memory. The RAM is a volatile memory. 231 RFID: Radio Frequency IDentification. 233 ROM: Read Only Memory. 235 ROLL: Routing Over Low power and Lossy networks. 237 RPL: An IPv6 Routing Protocol for Low-Power and Lossy Networks that 238 provides a mechanism whereby multipoint-to-point traffic from devices 239 inside the LLN towards a central control point as well as point-to- 240 multipoint traffic from the central control point to the devices 241 inside the LLN are supported. RPL also support point-to-point 242 traffic between any arbitratry node in the LLN. 244 RPL Domain: A RPL routing domain is a collection of RPL routers under 245 the control of a single administration. The boundaries of routing 246 domains are defined by network management by setting some links to be 247 exterior, or inter-domain, links. 249 Schedule: An agreed execution, wake-up, transmission, reception, 250 etc., time-table between two or more field devices. 252 Sensor: A sensor is a device that measures a physical quantity and 253 converts it to an analog or digital signal that can be read by a 254 program or a user. Sensed data can be of many types: electromagnetic 255 (e.g. current, voltage, power, resistance, ...) , mechanical (e.g. 256 pressure, flow, liquid density, humidity, ...), chemical (e.g. 257 oxygen, carbon monoxide, ...), acoustic (e.g. noise, ultrasound), 258 ... 260 Sleepy Node: A sleepy node is a node that may sometimes go into a 261 sleep mode (i.e. go into a low power state to conserve power) and 262 temporarily suspend protocol communication. When no in a sleep mode, 263 the sleepy node is in a fully powered on state where it has the 264 capability to perform communication. 266 Smart Grid: A Smart Grid is a broad class of applications to network 267 and automate utility infrastructure. 269 Timeslot: A Timeslot is a fixed time interval that may be used for 270 the transmission or reception of a packet between two field devices. 271 A timeslot used for communications is associated with a slotted-link 273 Upstream: Data direction traveling from the LLN via the LBR to 274 outside of the LLN (LAN, WAN, Internet) or general closer to the root 275 of the Directed Acyclic Graph computed by the routing protocol. 277 WAN: Wide Area Network. 279 3. IANA Considerations 281 This document includes no request for IANA action. 283 4. Security Considerations 285 Since this document specifies terminology and does not specify new 286 procedure or protocols, it raises no new security issue. 288 5. Acknowledgements 290 The authors would like to thank Christian Jacquenet, Tim Winter, 291 Pieter De Mil, David Meyer, Mukul Goyal and Abdussalam Baryun for 292 their valuable feed-back. 294 6. References 296 6.1. Informative References 298 [HART] HART Communication Foundation (http://www.hartcomm.org) 300 [RFC4461] Yasukawa, S., "Signaling Requirements for Point-to- 301 Multipoint Traffic-Engineered MPLS Label Switched Paths 302 (LSPs)", RFC 4461, April 2006. 304 [RFC4875] Aggarwal, R., Papadimitriou, D., and S. Yasukawa, 305 "Extensions to Resource Reservation Protocol - Traffic 306 Engineering (RSVP-TE) for Point-to-Multipoint TE Label 307 Switched Paths (LSPs)", RFC 4875, May 2007. 309 [RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel, 310 "Routing Requirements for Urban Low-Power and Lossy 311 Networks", RFC 5548, May 2009. 313 [RFC5673] Pister, K., Thubert, P., Dwars, S., and T. Phinney, 314 "Industrial Routing Requirements in Low-Power and Lossy 315 Networks", RFC 5673, October 2009. 317 [RFC5826] Brandt, A., Buron, J., and G. Porcu, "Home Automation 318 Routing Requirements in Low-Power and Lossy Networks", RFC 319 5826, April 2010. 321 [RFC5867] Martocci, J., De Mil, P., Riou, N., and W. Vermeylen, 322 "Building Automation Routing Requirements in Low-Power and 323 Lossy Networks", RFC 5867, June 2010. 325 Author's Address 326 JP Vasseur 327 Cisco Systems, Inc 328 1414 Massachusetts Avenue 329 Boxborough, MA 01719 330 USA 332 Email: jpv@cisco.com