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