idnits 2.17.1 draft-ietf-roll-terminology-09.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (January 17, 2013) is 4088 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'HART' is mentioned on line 166, but not defined Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Networking Working Group JP. Vasseur 2 Internet-Draft Cisco Systems, Inc 3 Intended status: Informational January 17, 2013 4 Expires: July 21, 2013 6 Terminology in Low power And Lossy Networks 7 draft-ietf-roll-terminology-09.txt 9 Abstract 11 The documents defines a terminology for discussing routing 12 requirements and solutions for networks referred to as Low power and 13 Lossy Networks (LLN). A LLN is typically composed of many embedded 14 devices with limited power, memory, and processing resources 15 interconnected by a variety of links. There is a wide scope of 16 application areas for LLNs, including industrial monitoring, building 17 automation (e.g. Heating, Ventilating, Air Conditioning, lighting, 18 access control, fire), connected home, healthcare, environmental 19 monitoring, urban sensor networks, energy management, assets 20 tracking, refrigeration. 22 Requirements Language 24 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 25 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 26 document are to be interpreted as described in RFC 2119 [RFC2119]. 28 Status of this Memo 30 This Internet-Draft is submitted to IETF in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on July 21, 2013. 45 Copyright Notice 47 Copyright (c) 2013 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 65 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 66 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 67 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 68 6.1. Normative References . . . . . . . . . . . . . . . . . . . 7 69 6.2. Informative References . . . . . . . . . . . . . . . . . . 7 70 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 72 1. Introduction 74 This document defines a terminology for discussing routing 75 requirements and solutions for networks referred to as Low power and 76 Lossy Networks (LLN). 78 Low power and Lossy networks (LLNs) are typically composed of many 79 embedded devices with limited power, memory, and processing resources 80 interconnected by a variety of links, such as IEEE 802.15.4, Low 81 Power WiFi. There is a wide scope of application areas for LLNs, 82 including industrial monitoring, building automation (HVAC, lighting, 83 access control, fire), connected home, healthcare, environmental 84 monitoring, urban sensor networks, energy management, assets tracking 85 and refrigeration. 87 Since these applications are usually highly specific (for example 88 Industrial Automation, Building Automation, ...), it is not uncommon 89 to see a number of disparate terms to describe the same device or 90 functionality. Thus in order to avoid confusion or discrepancies, 91 this document specifies the common terminology to be used in all ROLL 92 Working Group documents. The terms defined in this document are used 93 in [RFC5548],[RFC5673], [RFC5826] and [RFC5867]. 95 Terminology specific to a particular application are out of the scope 96 of this document. 98 It is expected that all routing requirements documents defining 99 requirements or specifying routing solutions for LLN will use the 100 common terminology specified in this document. This document should 101 be listed as an informative reference. 103 2. Terminology 105 Actuator: a field device that controls a set of equipment. For 106 example, an actuator might control and/or modulates the flow of a gas 107 or liquid, control electricity distribution, perform a mechanical 108 operation, ... 110 AMI: Advanced Metering Infrastructure that makes use of Smart Grid 111 technologies. A canonical Smart Grid application is smart-metering. 113 Channel: Radio frequency sub-band used to transmit a modulated signal 114 carrying packets. 116 Channel Hopping: A procedure by which field devices synchronously 117 change channels during operation. 119 Commissioning Tool: Any physical or logical device temporarily added 120 to the network for the expressed purpose of setting up the network 121 and device operational parameters. The commisioning tool can also be 122 temporarily added to the LLN for scheduled or unscheduled 123 maintenance. 125 Closed Loop Control: A procedure whereby a device controller controls 126 an actuator based on input information sensed by one or more field 127 devices. 129 Controller: A field device that can receive sensor input and 130 automatically change the environment in the facility by manipulating 131 digital or analog actuators. 133 DA: Distribution Automation, part of Smart Grid. Encompasses 134 technologies for maintenance and management of electrical 135 distribution systems. 137 Data sink: A device that collects data from nodes in a 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. 142 Field Device: A field deviced is a physical device placed in the 143 network's operating environment (e.g. plant, urban or home). Field 144 devices include sensors, actuators as well as routers and Low power 145 and Lossy Network Border Router (including LBR). A field device is 146 usually (but not always) a device with constrained CPU, memory 147 footprint, storage capacity, bandwidth and sometimes power (battery 148 operated). At the time of writing, for the sake of illustration, a 149 typical sensor or actuator would have a few KBytes of RAM, a few 150 dozens of KBytes of ROM/Flash memory, a 8/16/32 bit microcontroller 151 and communication capabilities ranging from a few Kbits/s to a few 152 hundreds of KBits/s. Although it is expected to see continuous 153 improvements of hardware and software technologies, such devices will 154 likely continue to be seen as resource constrained devices compared 155 to computers and routers used in the Internet. 157 Flash memory: non-volatile memory that can be re-programmed. 159 FMS: Facility Management System. A global term applied across all 160 the vertical designations within a building including, Heating, 161 Ventilating, and Air Conditioning also referred to as HVAC, Fire, 162 Security, Lighting and Elevator control. 164 HART: "Highway Addressable Remote Transducer", a group of 165 specifications for industrial process and control devices 166 administered by the HART Foundation (see [HART]). The latest version 167 for the specifications is HART7 which includes the additions for 168 WirelessHART. 170 HVAC: Heating, Ventilation and Air Conditioning. A term applied to 171 the comfort level of an internal space. 173 ISA: "International Society of Automation". ISA is an ANSI 174 accredited standards-making society. ISA100 is an ISA committee 175 whose charter includes defining a family of standards for industrial 176 automation. [ISA100.11a] is a working group within ISA100 that is 177 working on a standard for monitoring and non-critical process control 178 applications. 180 LAN: Local Area Network. 182 LBR: Low power and lossy network Border Router. The LBR is a device 183 that connects the Low power and Lossy Network to another routing 184 domain such as a Local Area Network (LAN), Wide Area Network (WAN) or 185 the Internet where a possibly different routing protocol is in 186 operation. The LBR acts as a routing device and may possibly host 187 other functions such as data collector or aggregator. 189 LLN: Low power and Lossy networks (LLNs) are typically composed of 190 many embedded devices with limited power, memory, and processing 191 resources interconnected by a variety of links, such as IEEE 802.15.4 192 or Low Power WiFi. There is a wide scope of application areas for 193 LLNs, including industrial monitoring, building automation (HVAC, 194 lighting, access control, fire), connected home, healthcare, 195 environmental monitoring, urban sensor networks, energy management, 196 assets tracking and refrigeration.. 198 MP2P: Multipoint-to-Point is used to describe a particular traffic 199 pattern (e.g. MP2P flows collecting information from many nodes 200 flowing inwards towards a collecting sink or an LBR). 202 MAC: Medium Access Control. Refers to algorithms and procedures used 203 by the data link layer to coordinate use of the physical layer. 205 Open Loop Control: A process whereby a plant operator manually 206 manipulates an actuator over the network where the decision is 207 influenced by information sensed by field devices. 209 PER: Packet Error Rate. A ratio of the number of unusable packets 210 (not received at all, or received in error- even after any applicable 211 error correction has been applied) to the total number of packets 212 that would have been been received in the absence of errors. 214 P2P: Point To Point. This refers to traffic exchanged between two 215 nodes (regardless of the number of hops between the two nodes). 217 P2MP: Point-to-Multipoint traffic refers to traffic between one node 218 and a set of nodes. This is similar to the P2MP concept in Multicast 219 or MPLS Traffic Engineering ([RFC4461]and [RFC4875]). A common RPL 220 use case involves P2MP flows from or through a DAG root outward 221 towards other nodes contained in the DAG. 223 RAM: Random Access Memory. The RAM is a volatile memory. 225 RFID: Radio Frequency IDentification. 227 ROM: Read Only Memory. 229 ROLL: Routing Over Low power and Lossy networks. 231 RPL Domain: A RPL routing domain is a collection of RPL routers under 232 the control of a single administration. The boundaries of routing 233 domains are defined by network management by setting some links to be 234 exterior, or inter-domain, links. 236 Schedule: An agreed execution, wake-up, transmission, reception, 237 etc., time-table between two or more field devices. 239 Sensor: A sensor is a device that measures a physical quantity and 240 converts it to a analog or digital signal that can be read by a 241 program or a user. Sensed data can be of many types: electromagnetic 242 (e.g. current, voltage, power, resistance, ...) , mechanical (e.g. 243 pressure, flow, liquid density, humidity, ...), chemical (e.g. 244 oxygen, carbon monoxide, ...), acoustic (e.g. noise, ultrasound), ... 246 Smart Grid: A Smart Grid is a broad class of applications to network 247 and automate utility infrastructure. 249 Timeslot: A Timeslot is a fixed time interval that may be used for 250 the transmission or reception of a packet between two field devices. 251 A timeslot used for communications is associated with a slotted-link 253 Upstream: Data direction traveling from the LLN via the LBR to 254 outside of the LLN (LAN, WAN, Internet). 256 WAN: Wide Area Network. 258 3. IANA Considerations 260 This document includes no request for IANA action. 262 4. Security Considerations 264 Since this document specifies terminology and does not specify new 265 procedure or protocols, it raises no new security issue. 267 5. Acknowledgements 269 The authors would like to thank Christian Jacquenet, Tim Winter, 270 Pieter De Mil, David Meyer, Mukul Goyal and Abdussalam Baryun for 271 their valuable feed-back. 273 6. References 275 6.1. Normative References 277 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 278 Requirement Levels", BCP 14, RFC 2119, March 1997. 280 6.2. Informative References 282 [RFC4461] Yasukawa, S., "Signaling Requirements for Point-to- 283 Multipoint Traffic-Engineered MPLS Label Switched Paths 284 (LSPs)", RFC 4461, April 2006. 286 [RFC4875] Aggarwal, R., Papadimitriou, D., and S. Yasukawa, 287 "Extensions to Resource Reservation Protocol - Traffic 288 Engineering (RSVP-TE) for Point-to-Multipoint TE Label 289 Switched Paths (LSPs)", RFC 4875, May 2007. 291 [RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel, 292 "Routing Requirements for Urban Low-Power and Lossy 293 Networks", RFC 5548, May 2009. 295 [RFC5673] Pister, K., Thubert, P., Dwars, S., and T. Phinney, 296 "Industrial Routing Requirements in Low-Power and Lossy 297 Networks", RFC 5673, October 2009. 299 [RFC5826] Brandt, A., Buron, J., and G. Porcu, "Home Automation 300 Routing Requirements in Low-Power and Lossy Networks", 301 RFC 5826, April 2010. 303 [RFC5867] Martocci, J., De Mil, P., Riou, N., and W. Vermeylen, 304 "Building Automation Routing Requirements in Low-Power and 305 Lossy Networks", RFC 5867, June 2010. 307 Author's Address 309 JP Vasseur 310 Cisco Systems, Inc 311 1414 Massachusetts Avenue 312 Boxborough, MA 01719 313 USA 315 Email: jpv@cisco.com