idnits 2.17.1 draft-ietf-roll-terminology-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) 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 29, 2010) is 5134 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'HART' is mentioned on line 173, but not defined Summary: 1 error (**), 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 29, 2010 4 Expires: September 30, 2010 6 Terminology in Low power And Lossy Networks 7 draft-ietf-roll-terminology-03.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), its areas, and its working groups. Note that 35 other groups may also distribute working documents as Internet- 36 Drafts. 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 The list of current Internet-Drafts can be accessed at 44 http://www.ietf.org/ietf/1id-abstracts.txt. 46 The list of Internet-Draft Shadow Directories can be accessed at 47 http://www.ietf.org/shadow.html. 49 This Internet-Draft will expire on September 30, 2010. 51 Copyright Notice 53 Copyright (c) 2010 IETF Trust and the persons identified as the 54 document authors. All rights reserved. 56 This document is subject to BCP 78 and the IETF Trust's Legal 57 Provisions Relating to IETF Documents 58 (http://trustee.ietf.org/license-info) in effect on the date of 59 publication of this document. Please review these documents 60 carefully, as they describe your rights and restrictions with respect 61 to this document. Code Components extracted from this document must 62 include Simplified BSD License text as described in Section 4.e of 63 the Trust Legal Provisions and are provided without warranty as 64 described in the BSD License. 66 Table of Contents 68 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 69 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 70 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 71 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 72 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 73 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 74 6.1. Normative References . . . . . . . . . . . . . . . . . . . 7 75 6.2. Informative References . . . . . . . . . . . . . . . . . . 7 76 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 78 1. Introduction 80 This document defines a terminology for discussing routing 81 requirements and solutions for networks referred to as Low power and 82 Lossy Networks (LLN). 84 Low power and Lossy networks (LLNs) are typically composed of many 85 embedded devices with limited power, memory, and processing resources 86 interconnected by a variety of links, such as IEEE 802.15.4, Low 87 Power WiFi. There is a wide scope of application areas for LLNs, 88 including industrial monitoring, building automation (HVAC, lighting, 89 access control, fire), connected home, healthcare, environmental 90 monitoring, urban sensor networks, energy management, assets tracking 91 and refrigeration. 93 Since these applications are usually highly specific (for example 94 Industrial Automation, Building Automation, ...), it is not uncommon 95 to see a number of disparate terms to describe the same device or 96 functionality. Thus in order to avoid confusion or discrepancies, 97 this document specifies the common terminology to be used in all ROLL 98 Working Group documents. The terms defined in this document are used 99 in [RFC5548],[I-D.ietf-roll-indus-routing-reqs], 100 [I-D.ietf-roll-home-routing-reqs] and 101 [I-D.ietf-roll-building-routing-reqs]. 103 Terminology specific to a particular application are out of the scope 104 of this document. 106 It is expected that all routing requirements documents defining 107 requirements or specifying routing solutions for LLN will use the 108 common terminology specified in this document. This document should 109 be listed as an informative reference. 111 2. Terminology 113 Actuator: a field device that controls a set of equipment. For 114 example, an actuator might control and/or modulates the flow of a gas 115 or liquid, control electricity distribution, perform a mechanical 116 operation, ... 118 AMI: Advanced Metering Infrastructure that makes use of Smart Grid 119 technologies. A canonical Smart Grid application is smart-metering. 121 Channel: Radio frequency sub-band used to transmit a modulated signal 122 carrying packets. 124 Channel Hopping: A procedure by which field devices synchronously 125 change channels during operation. 127 Commissioning Tool: Any physical or logical device temporarily added 128 to the network for the expressed purpose of setting up the network 129 and device operational parameters. The commisioning tool can also be 130 temporarily added to the LLN for scheduled or unscheduled 131 maintenance. 133 Closed Loop Control: A process whereby a device controller controls 134 an actuator based on information sensed by one or more field devices. 136 Controller: A field device that can receive sensor input and 137 automatically change the environment in the facility by manipulating 138 digital or analog actuators. 140 DA: Distribution Automation, part of Smart Grid. Encompasses 141 technologies for maintenance and management of electrical 142 distribution systems. 144 Data sink: A device that collects data from nodes in a LLN. 146 Downstream: Data direction traveling from outside of the LLN (e.g. 147 traffic coming from a LAN, WAN or the Internet) via a LBR. 149 Field Device: A field deviced is a physical device placed in the 150 network's operating environment (e.g. plant, urban or home). Field 151 devices include sensors, actuators as well as routers and Low power 152 and Lossy Network Border Router (including LBR). A field device is 153 usually (but not always) a device with constrained CPU, memory 154 footprint, storage capacity, bandwidth and sometimes power (battery 155 operated). At the time of writing, for the sake of illustration, a 156 typical sensor or actuator would have a few KBytes of RAM, a few 157 dozens of KBytes of ROM/Flash memory, a 8/16/32 bit microcontroller 158 and communication capabilities ranging from a few Kbits/s to a few 159 hundreds of KBits/s. Although it is expected to see continuous 160 improvements of hardware and software technologies, such devices will 161 likely continue to be seen as resource constrained devices compared 162 to computers and routers used in the Internet. 164 Flash memory: non-volatile memory that can be re-programmed. 166 FMS: Facility Management System. A global term applied across all 167 the vertical designations within a building including, Heating, 168 Ventilating, and Air Conditioning also referred to as HVAC, Fire, 169 Security, Lighting and Elevator control. 171 HART: "Highway Addressable Remote Transducer", a group of 172 specifications for industrial process and control devices 173 administered by the HART Foundation (see [HART]). The latest version 174 for the specifications is HART7 which includes the additions for 175 WirelessHART. 177 HVAC: Heating, Ventilation and Air Conditioning. A term applied to 178 the comfort level of an internal space. 180 ISA: "International Society of Automation". ISA is an ANSI 181 accredited standards-making society. ISA100 is an ISA committee 182 whose charter includes defining a family of standards for industrial 183 automation. [ISA100.11a] is a working group within ISA100 that is 184 working on a standard for monitoring and non-critical process control 185 applications. 187 LAN: Local Area Network. 189 LBR: Low power and lossy network Border Router. The LBR is a device 190 that connects the Low power and Lossy Network to another routing 191 domain such as a Local Area Network (LAN), Wide Area Network (WAN) or 192 the Internet where a possibly different routing protocol is in 193 operation. The LBR acts as a routing device and may possibly host 194 other functions such as data collector or aggregator. 196 LLN: Low power and Lossy networks (LLNs) are typically composed of 197 many embedded devices with limited power, memory, and processing 198 resources interconnected by a variety of links, such as IEEE 802.15.4 199 or Low Power WiFi. There is a wide scope of application areas for 200 LLNs, including industrial monitoring, building automation (HVAC, 201 lighting, access control, fire), connected home, healthcare, 202 environmental monitoring, urban sensor networks, energy management, 203 assets tracking and refrigeration.. 205 MP2P: Multipoint-to-Point is used to describe a particular traffic 206 pattern (e.g. MP2P flows collecting information from many nodes 207 flowing inwards towards a collecting sink or an LBR). 209 MAC: Medium Access Control. Refers to algorithms and procedures used 210 by the data link layer to coordinate use of the physical layer. 212 Open Loop Control: A process whereby a plant operator manually 213 manipulates an actuator over the network where the decision is 214 influenced by information sensed by field devices. 216 PER: Packet Error Rate. A ratio of the number of unusable packets 217 (not received at all, or received in error- even after any applicable 218 error correction has been applied) to the total number of packets 219 that would have been been received in the absence of errors. 221 P2P: Point To Point. This refers to traffic exchanged between two 222 nodes (regardless of the number of hops between the two nodes). 224 P2MP: Point-to-Multipoint traffic refers to traffic between one node 225 and a set of nodes. This is similar to the P2MP concept in Multicast 226 or MPLS Traffic Engineering ([RFC4461]and [RFC4875]). A common RPL 227 use case involves P2MP flows from or through a DAG root outward 228 towards other nodes contained in the DAG. 230 RAM: Random Access Memory. The RAM is a volatile memory. 232 RFID: Radio Frequency IDentification. 234 ROM: Read Only Memory. 236 ROLL: Routing Over Low power and Lossy networks. 238 Schedule: An agreed execution, wake-up, transmission, reception, 239 etc., time-table between two or more field devices. 241 Sensor: A sensor is a device that measures a physical quantity and 242 converts it to a analog or digital signal that can be read by a 243 program or a user. Sensed data can be of many types: electromagnetic 244 (e.g. current, voltage, power, resistance, ...) , mechanical (e.g. 245 pressure, flow, liquid density, humidity, ...), chemical (e.g. 246 oxygen, carbon monoxide, ...), acoustic (e.g. noise, ultrasound), ... 248 Smart Grid: A Smart Grid is a broad class of applications to network 249 and automate utility infrastructure. 251 Timeslot: A Timeslot is a fixed time interval that may be used for 252 the transmission or reception of a packet between two field devices. 253 A timeslot used for communications is associated with a slotted-link 255 Upstream: Data direction traveling from the LLN via the LBR to 256 outside of the LLN (LAN, WAN, Internet). 258 WAN: Wide Area Network. 260 3. IANA Considerations 262 This document includes no request for IANA action. 264 4. Security Considerations 266 Since this document specifies terminology and does not specify new 267 procedure or protocols, it raises no new security issue. 269 5. Acknowledgements 271 The authors would like to thank Christian Jacquenet, Tim Winter, 272 Pieter De Mil and David Meyer for their valuable feed-back. 274 6. References 276 6.1. Normative References 278 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 279 Requirement Levels", BCP 14, RFC 2119, March 1997. 281 6.2. Informative References 283 [I-D.ietf-roll-building-routing-reqs] 284 Martocci, J., Riou, N., Mil, P., and W. Vermeylen, 285 "Building Automation Routing Requirements in Low Power and 286 Lossy Networks", draft-ietf-roll-building-routing-reqs-09 287 (work in progress), January 2010. 289 [I-D.ietf-roll-home-routing-reqs] 290 Brandt, A. and J. Buron, "Home Automation Routing 291 Requirements in Low Power and Lossy Networks", 292 draft-ietf-roll-home-routing-reqs-11 (work in progress), 293 January 2010. 295 [I-D.ietf-roll-indus-routing-reqs] 296 Networks, D., Thubert, P., Dwars, S., and T. Phinney, 297 "Industrial Routing Requirements in Low Power and Lossy 298 Networks", draft-ietf-roll-indus-routing-reqs-06 (work in 299 progress), June 2009. 301 [RFC4461] Yasukawa, S., "Signaling Requirements for Point-to- 302 Multipoint Traffic-Engineered MPLS Label Switched Paths 303 (LSPs)", RFC 4461, April 2006. 305 [RFC4875] Aggarwal, R., Papadimitriou, D., and S. Yasukawa, 306 "Extensions to Resource Reservation Protocol - Traffic 307 Engineering (RSVP-TE) for Point-to-Multipoint TE Label 308 Switched Paths (LSPs)", RFC 4875, May 2007. 310 [RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel, 311 "Routing Requirements for Urban Low-Power and Lossy 312 Networks", RFC 5548, May 2009. 314 Author's Address 316 JP Vasseur 317 Cisco Systems, Inc 318 1414 Massachusetts Avenue 319 Boxborough, MA 01719 320 USA 322 Email: jpv@cisco.com