idnits 2.17.1 draft-ietf-roll-terminology-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. 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 (May 7, 2009) is 5461 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'HART' is mentioned on line 164, but not defined == Unused Reference: 'I-D.ietf-roll-home-routing-reqs' is defined on line 261, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-roll-indus-routing-reqs' is defined on line 267, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-roll-urban-routing-reqs' is defined on line 273, but no explicit reference was found in the text == Unused Reference: 'I-D.martocci-roll-building-routing-reqs' is defined on line 280, but no explicit reference was found in the text == Outdated reference: A later version (-11) exists of draft-ietf-roll-home-routing-reqs-06 == Outdated reference: A later version (-06) exists of draft-ietf-roll-indus-routing-reqs-05 Summary: 1 error (**), 0 flaws (~~), 9 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 May 7, 2009 4 Expires: November 8, 2009 6 Terminology in Low power And Lossy Networks 7 draft-ietf-roll-terminology-01.txt 9 Status of this Memo 11 This Internet-Draft is submitted to IETF in full conformance with the 12 provisions of BCP 78 and BCP 79. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt. 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 This Internet-Draft will expire on November 8, 2009. 32 Copyright Notice 34 Copyright (c) 2009 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents in effect on the date of 39 publication of this document (http://trustee.ietf.org/license-info). 40 Please review these documents carefully, as they describe your rights 41 and restrictions with respect to this document. 43 Abstract 45 The documents defines a terminology for discussing routing 46 requirements and solutions for networks referred to as Low power and 47 Lossy Networks (LLN). A LLN is typically composed of many embedded 48 devices with limited power, memory, and processing resources 49 interconnected by a variety of links. There is a wide scope of 50 application areas for LLNs, including industrial monitoring, building 51 automation (e.g. Heating, Ventilating, Air Conditioning, lighting, 52 access control, fire), connected home, healthcare, environmental 53 monitoring, urban sensor networks, energy management, assets 54 tracking, refrigeration. 56 Requirements Language 58 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 59 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 60 document are to be interpreted as described in RFC 2119 [RFC2119]. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 67 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 68 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 69 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 71 6.2. Informative References . . . . . . . . . . . . . . . . . . 7 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 74 1. Introduction 76 This document defines a terminology for discussing routing 77 requirements and solutions for networks referred to as Low power and 78 Lossy Networks (LLN). 80 Low power and Lossy networks (LLNs) are typically composed of many 81 embedded devices with limited power, memory, and processing resources 82 interconnected by a variety of links, such as IEEE 802.15.4, Low 83 Power WiFi. There is a wide scope of application areas for LLNs, 84 including industrial monitoring, building automation (HVAC, lighting, 85 access control, fire), connected home, healthcare, environmental 86 monitoring, urban sensor networks, energy management, assets tracking 87 and refrigeration. 89 Since these applications are usually highly specific (for example 90 Industrial Automation, Building Automation, ...), it is not uncommon 91 to see a number of disparate terms to describe the same device or 92 functionality. Thus in order to avoid confusion or discrepancies, 93 this document specifies the common terminology to be used in all ROLL 94 Working Group documents. Terminology specific to a particular 95 application are out of the scope of this document. 97 It is expected that all routing requirements documents defining 98 requirements or specifying routing solutions for LLN will use the 99 common terminology specified in this document. This document should 100 be listed as an informative reference. 102 2. Terminology 104 Actuator: a field device that controls a set of equipment. For 105 example, an actuator might control and/or modulates the flow of a gas 106 or liquid, control electricity distribution, perform a mechanical 107 operation, ... 109 AMI: Advanced Metering Infrastructure that makes use of Smart Grid 110 technologies. A canonical Smart Grid application is smart-metering. 112 Channel: Radio frequency sub-band used to transmit a modulated signal 113 carrying packets. 115 Channel Hopping: A procedure by which field devices synchronously 116 change channels during operation. 118 Commissioning Tool: Any physical or logical device temporarily added 119 to the network for the expressed purpose of setting up the network 120 and device operational parameters. The commisioning tool can also be 121 temporarily added to the LLN for scheduled or unscheduled 122 maintenance. 124 Closed Loop Control: A process whereby a device controller controls 125 an actuator based on information sensed by one or more field devices. 127 Controller: A field device that can receive sensor input and 128 automatically change the environment in the facility by manipulating 129 digital or analog actuators. 131 DA: Distribution Automation, part of Smart Grid. Encompasses 132 technologies for maintenance and management of electrical 133 distribution systems. 135 Data sink: A device that collects data from nodes in a LLN. 137 Downstream: Data direction traveling from outside of the LLN (e.g. 138 traffic coming from a LAN, WAN or the Internet) via a LBR. 140 Field Device: A field deviced is a physical device placed in the 141 network's operating environment (e.g. plant, urban or home). Field 142 devices include sensors, actuators as well as routers and Low power 143 and Lossy Network Border Router (including LBR). A field device is 144 usually (but not always) a device with constrained CPU, memory 145 footprint, storage capacity, bandwidth and sometimes power (battery 146 operated). At the time of writing, for the sake of illustration, a 147 typical sensor or actuator would have a few KBytes of RAM, a few 148 dozens of KBytes of ROM/Flash memory, a 8/16/32 bit microcontroller 149 and communication capabilities ranging from a few Kbits/s to a few 150 hundreds of KBits/s. Although it is expected to see continuous 151 improvements of hardware and software technologies, such devices will 152 likely continue to be seen as resource constrained devices compared 153 to computers and routers used in the Internet. 155 Flash memory: non-volatile memory that can be re-programmed. 157 FMS: Facility Management System. A global term applied across all 158 the vertical designations within a building including, Heating, 159 Ventilating, and Air Conditioning also referred to as HVAC, Fire, 160 Security, Lighting and Elevator control. 162 HART: "Highway Addressable Remote Transducer", a group of 163 specifications for industrial process and control devices 164 administered by the HART Foundation (see [HART]). The latest version 165 for the specifications is HART7 which includes the additions for 166 WirelessHART. 168 HVAC: Heating, Ventilation and Air Conditioning. A term applied to 169 the comfort level of an internal space. 171 ISA: "International Society of Automation". ISA is an ANSI 172 accredited standards-making society. ISA100 is an ISA committee 173 whose charter includes defining a family of standards for industrial 174 automation. [ISA100.11a] is a working group within ISA100 that is 175 working on a standard for monitoring and non-critical process control 176 applications. 178 LAN: Local Area Network. 180 LBR: Low power and lossy network Border Router. The LBR is a device 181 that connects the Low power and Lossy Network to another routing 182 domain such as a Local Area Network (LAN), Wide Area Network (WAN) or 183 the Internet where a possibly different routing protocol is in 184 operation. The LBR acts as a routing device and may possibly host 185 other functions such as data collector or aggregator. 187 LLN: Low power and Lossy networks (LLNs) are typically composed of 188 many embedded devices with limited power, memory, and processing 189 resources interconnected by a variety of links, such as IEEE 802.15.4 190 or Low Power WiFi. There is a wide scope of application areas for 191 LLNs, including industrial monitoring, building automation (HVAC, 192 lighting, access control, fire), connected home, healthcare, 193 environmental monitoring, urban sensor networks, energy management, 194 assets tracking and refrigeration.. 196 MAC: Medium Access Control. Refers to algorithms and procedures used 197 by the data link layer to coordinate use of the physical layer. 199 Open Loop Control: A process whereby a plant operator manually 200 manipulates an actuator over the network where the decision is 201 influenced by information sensed by field devices. 203 PER: Packet Error Rate. A ratio of the number of unusable packets 204 (not received at all, or received in error- even after any applicable 205 error correction has been applied) to the total number of packets 206 that would have been been received in the absence of errors. 208 RAM: Random Access Memory. The RAM is a volatile memory. 210 RFID: Radio Frequency IDentification. 212 ROM: Read Only Memory. 214 ROLL: Routing Over Low power and Lossy networks. 216 Schedule: An agreed execution, wake-up, transmission, reception, 217 etc., time-table between two or more field devices. 219 Sensor: A sensor is a device that measures a physical quantity and 220 converts it to a analog or digital signal that can be read by a 221 program or a user. Sensed data can be of many types: electromagnetic 222 (e.g. current, voltage, power, resistance, ...) , mechanical (e.g. 223 pressure, flow, liquid density, humidity, ...), chemical (e.g. 224 oxygen, carbon monoxide, ...), acoustic (e.g. noise, ultrasound), ... 226 Smart Grid: A Smart Grid is a broad class of applications to network 227 and automate utility infrastructure. 229 Timeslot: A Timeslot is a fixed time interval that may be used for 230 the transmission or reception of a packet between two field devices. 231 A timeslot used for communications is associated with a slotted-link 233 Upstream: Data direction traveling from the LLN via the LBR to 234 outside of the LLN (LAN, WAN, Internet). 236 WAN: Wide Area Network. 238 3. IANA Considerations 240 This document includes no request for IANA action. 242 4. Security Considerations 244 Since this document specifies terminology and does not specify new 245 procedure or protocols, it raises no new security issue. 247 5. Acknowledgements 249 The authors would like to thank Christian Jacquenet, Tim Winter, 250 Pieter De Mil and David Meyer for their valuable feed-back. 252 6. References 254 6.1. Normative References 256 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 257 Requirement Levels", BCP 14, RFC 2119, March 1997. 259 6.2. Informative References 261 [I-D.ietf-roll-home-routing-reqs] 262 Porcu, G., "Home Automation Routing Requirements in Low 263 Power and Lossy Networks", 264 draft-ietf-roll-home-routing-reqs-06 (work in progress), 265 November 2008. 267 [I-D.ietf-roll-indus-routing-reqs] 268 Networks, D., Thubert, P., Dwars, S., and T. Phinney, 269 "Industrial Routing Requirements in Low Power and Lossy 270 Networks", draft-ietf-roll-indus-routing-reqs-05 (work in 271 progress), April 2009. 273 [I-D.ietf-roll-urban-routing-reqs] 274 Dohler, M., Watteyne, T., Winter, T., Barthel, D., 275 Jacquenet, C., Madhusudan, G., and G. Chegaray, "Urban 276 WSNs Routing Requirements in Low Power and Lossy 277 Networks", draft-ietf-roll-urban-routing-reqs-05 (work in 278 progress), March 2009. 280 [I-D.martocci-roll-building-routing-reqs] 281 Martocci, J., Riou, N., Mil, P., and W. Vermeylen, 282 "Building Automation Routing Requirements in Low Power and 283 Lossy Networks", 284 draft-martocci-roll-building-routing-reqs-01 (work in 285 progress), October 2008. 287 Author's Address 289 JP Vasseur 290 Cisco Systems, Inc 291 1414 Massachusetts Avenue 292 Boxborough, MA 01719 293 USA 295 Email: jpv@cisco.com