idnits 2.17.1 draft-ietf-roll-terminology-05.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 (March 14, 2011) is 4784 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'HART' is mentioned on line 167, 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 March 14, 2011 4 Expires: September 15, 2011 6 Terminology in Low power And Lossy Networks 7 draft-ietf-roll-terminology-05.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 September 15, 2011. 45 Copyright Notice 47 Copyright (c) 2011 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 . . . . . . . . . . . . . . . . . . . . 6 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],[I-D.ietf-roll-indus-routing-reqs], 94 [I-D.ietf-roll-home-routing-reqs] and 95 [I-D.ietf-roll-building-routing-reqs]. 97 Terminology specific to a particular application are out of the scope 98 of this document. 100 It is expected that all routing requirements documents defining 101 requirements or specifying routing solutions for LLN will use the 102 common terminology specified in this document. This document should 103 be listed as an informative reference. 105 2. Terminology 107 Actuator: a field device that controls a set of equipment. For 108 example, an actuator might control and/or modulates the flow of a gas 109 or liquid, control electricity distribution, perform a mechanical 110 operation, ... 112 AMI: Advanced Metering Infrastructure that makes use of Smart Grid 113 technologies. A canonical Smart Grid application is smart-metering. 115 Channel: Radio frequency sub-band used to transmit a modulated signal 116 carrying packets. 118 Channel Hopping: A procedure by which field devices synchronously 119 change channels during operation. 121 Commissioning Tool: Any physical or logical device temporarily added 122 to the network for the expressed purpose of setting up the network 123 and device operational parameters. The commisioning tool can also be 124 temporarily added to the LLN for scheduled or unscheduled 125 maintenance. 127 Closed Loop Control: A process whereby a device controller controls 128 an actuator based on information sensed by one or more field devices. 130 Controller: A field device that can receive sensor input and 131 automatically change the environment in the facility by manipulating 132 digital or analog actuators. 134 DA: Distribution Automation, part of Smart Grid. Encompasses 135 technologies for maintenance and management of electrical 136 distribution systems. 138 Data sink: A device that collects data from nodes in a LLN. 140 Downstream: Data direction traveling from outside of the LLN (e.g. 141 traffic coming from a LAN, WAN or the Internet) via a LBR. 143 Field Device: A field deviced is a physical device placed in the 144 network's operating environment (e.g. plant, urban or home). Field 145 devices include sensors, actuators as well as routers and Low power 146 and Lossy Network Border Router (including LBR). A field device is 147 usually (but not always) a device with constrained CPU, memory 148 footprint, storage capacity, bandwidth and sometimes power (battery 149 operated). At the time of writing, for the sake of illustration, a 150 typical sensor or actuator would have a few KBytes of RAM, a few 151 dozens of KBytes of ROM/Flash memory, a 8/16/32 bit microcontroller 152 and communication capabilities ranging from a few Kbits/s to a few 153 hundreds of KBits/s. Although it is expected to see continuous 154 improvements of hardware and software technologies, such devices will 155 likely continue to be seen as resource constrained devices compared 156 to computers and routers used in the Internet. 158 Flash memory: non-volatile memory that can be re-programmed. 160 FMS: Facility Management System. A global term applied across all 161 the vertical designations within a building including, Heating, 162 Ventilating, and Air Conditioning also referred to as HVAC, Fire, 163 Security, Lighting and Elevator control. 165 HART: "Highway Addressable Remote Transducer", a group of 166 specifications for industrial process and control devices 167 administered by the HART Foundation (see [HART]). The latest version 168 for the specifications is HART7 which includes the additions for 169 WirelessHART. 171 HVAC: Heating, Ventilation and Air Conditioning. A term applied to 172 the comfort level of an internal space. 174 ISA: "International Society of Automation". ISA is an ANSI 175 accredited standards-making society. ISA100 is an ISA committee 176 whose charter includes defining a family of standards for industrial 177 automation. [ISA100.11a] is a working group within ISA100 that is 178 working on a standard for monitoring and non-critical process control 179 applications. 181 LAN: Local Area Network. 183 LBR: Low power and lossy network Border Router. The LBR is a device 184 that connects the Low power and Lossy Network to another routing 185 domain such as a Local Area Network (LAN), Wide Area Network (WAN) or 186 the Internet where a possibly different routing protocol is in 187 operation. The LBR acts as a routing device and may possibly host 188 other functions such as data collector or aggregator. 190 LLN: Low power and Lossy networks (LLNs) are typically composed of 191 many embedded devices with limited power, memory, and processing 192 resources interconnected by a variety of links, such as IEEE 802.15.4 193 or Low Power WiFi. There is a wide scope of application areas for 194 LLNs, including industrial monitoring, building automation (HVAC, 195 lighting, access control, fire), connected home, healthcare, 196 environmental monitoring, urban sensor networks, energy management, 197 assets tracking and refrigeration.. 199 MP2P: Multipoint-to-Point is used to describe a particular traffic 200 pattern (e.g. MP2P flows collecting information from many nodes 201 flowing inwards towards a collecting sink or an LBR). 203 MAC: Medium Access Control. Refers to algorithms and procedures used 204 by the data link layer to coordinate use of the physical layer. 206 Open Loop Control: A process whereby a plant operator manually 207 manipulates an actuator over the network where the decision is 208 influenced by information sensed by field devices. 210 PER: Packet Error Rate. A ratio of the number of unusable packets 211 (not received at all, or received in error- even after any applicable 212 error correction has been applied) to the total number of packets 213 that would have been been received in the absence of errors. 215 P2P: Point To Point. This refers to traffic exchanged between two 216 nodes (regardless of the number of hops between the two nodes). 218 P2MP: Point-to-Multipoint traffic refers to traffic between one node 219 and a set of nodes. This is similar to the P2MP concept in Multicast 220 or MPLS Traffic Engineering ([RFC4461]and [RFC4875]). A common RPL 221 use case involves P2MP flows from or through a DAG root outward 222 towards other nodes contained in the DAG. 224 RAM: Random Access Memory. The RAM is a volatile memory. 226 RFID: Radio Frequency IDentification. 228 ROM: Read Only Memory. 230 ROLL: Routing Over Low power and Lossy networks. 232 Schedule: An agreed execution, wake-up, transmission, reception, 233 etc., time-table between two or more field devices. 235 Sensor: A sensor is a device that measures a physical quantity and 236 converts it to a analog or digital signal that can be read by a 237 program or a user. Sensed data can be of many types: electromagnetic 238 (e.g. current, voltage, power, resistance, ...) , mechanical (e.g. 239 pressure, flow, liquid density, humidity, ...), chemical (e.g. 240 oxygen, carbon monoxide, ...), acoustic (e.g. noise, ultrasound), ... 242 Smart Grid: A Smart Grid is a broad class of applications to network 243 and automate utility infrastructure. 245 Timeslot: A Timeslot is a fixed time interval that may be used for 246 the transmission or reception of a packet between two field devices. 247 A timeslot used for communications is associated with a slotted-link 249 Upstream: Data direction traveling from the LLN via the LBR to 250 outside of the LLN (LAN, WAN, Internet). 252 WAN: Wide Area Network. 254 3. IANA Considerations 256 This document includes no request for IANA action. 258 4. Security Considerations 260 Since this document specifies terminology and does not specify new 261 procedure or protocols, it raises no new security issue. 263 5. Acknowledgements 265 The authors would like to thank Christian Jacquenet, Tim Winter, 266 Pieter De Mil and David Meyer for their valuable feed-back. 268 6. References 270 6.1. Normative References 272 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 273 Requirement Levels", BCP 14, RFC 2119, March 1997. 275 6.2. Informative References 277 [I-D.ietf-roll-building-routing-reqs] 278 Martocci, J., Riou, N., Mil, P., and W. Vermeylen, 279 "Building Automation Routing Requirements in Low Power and 280 Lossy Networks", draft-ietf-roll-building-routing-reqs-09 281 (work in progress), January 2010. 283 [I-D.ietf-roll-home-routing-reqs] 284 Brandt, A. and J. Buron, "Home Automation Routing 285 Requirements in Low Power and Lossy Networks", 286 draft-ietf-roll-home-routing-reqs-11 (work in progress), 287 January 2010. 289 [I-D.ietf-roll-indus-routing-reqs] 290 Networks, D., Thubert, P., Dwars, S., and T. Phinney, 291 "Industrial Routing Requirements in Low Power and Lossy 292 Networks", draft-ietf-roll-indus-routing-reqs-06 (work in 293 progress), June 2009. 295 [RFC4461] Yasukawa, S., "Signaling Requirements for Point-to- 296 Multipoint Traffic-Engineered MPLS Label Switched Paths 297 (LSPs)", RFC 4461, April 2006. 299 [RFC4875] Aggarwal, R., Papadimitriou, D., and S. Yasukawa, 300 "Extensions to Resource Reservation Protocol - Traffic 301 Engineering (RSVP-TE) for Point-to-Multipoint TE Label 302 Switched Paths (LSPs)", RFC 4875, May 2007. 304 [RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel, 305 "Routing Requirements for Urban Low-Power and Lossy 306 Networks", RFC 5548, May 2009. 308 Author's Address 310 JP Vasseur 311 Cisco Systems, Inc 312 1414 Massachusetts Avenue 313 Boxborough, MA 01719 314 USA 316 Email: jpv@cisco.com