idnits 2.17.00 (12 Aug 2021) /tmp/idnits65479/draft-vasseur-roll-terminology-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 286. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 297. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 304. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 310. 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 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 (September 15, 2008) is 4995 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'HART' is mentioned on line 150, but not defined == Unused Reference: 'I-D.ietf-roll-home-routing-reqs' is defined on line 237, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-roll-indus-routing-reqs' is defined on line 243, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-roll-urban-routing-reqs' is defined on line 249, but no explicit reference was found in the text == Unused Reference: 'I-D.martocci-roll-building-routing-reqs' is defined on line 256, but no explicit reference was found in the text == 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 == Outdated reference: draft-ietf-roll-urban-routing-reqs has been published as RFC 5548 == Outdated reference: A later version (-01) exists of draft-martocci-roll-building-routing-reqs-00 Summary: 1 error (**), 0 flaws (~~), 11 warnings (==), 7 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 September 15, 2008 4 Expires: March 19, 2009 6 Terminology in Low power And Lossy Networks 7 draft-vasseur-roll-terminology-01.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on March 19, 2009. 34 Abstract 36 The documents defines a terminology for discussing routing 37 requirements and solutions for networks referred to as Low power and 38 Lossy Networks (LLN). A LLN is typically composed of many embedded 39 devices with limited power, memory, and processing resources 40 interconnected by a variety of links. There is a wide scope of 41 application areas for LLNs, including industrial monitoring, building 42 automation (Heating, Ventilating, and Air Conditioning also referred 43 to as HVAC, lighting, access control, fire), connected home, 44 healthcare, environmental monitoring, urban sensor networks, energy 45 management, assets tracking, refrigeration. 47 Requirements Language 49 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 50 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 51 document are to be interpreted as described in RFC 2119 [RFC2119]. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 58 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 59 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 60 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 61 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 62 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 64 Intellectual Property and Copyright Statements . . . . . . . . . . 8 66 1. Introduction 68 This document defines a terminology for discussing routing 69 requirements and solutions for networks referred to as Low power and 70 Lossy Networks (LLN). 72 Low power and Lossy networks (LLNs) are typically composed of many 73 embedded devices with limited power, memory, and processing resources 74 interconnected by a variety of links, such as IEEE 802.15.4, Low 75 Power WiFi. There is a wide scope of application areas for LLNs, 76 including industrial monitoring, building automation (HVAC, lighting, 77 access control, fire), connected home, healthcare, environmental 78 monitoring, urban sensor networks, energy management, assets tracking 79 and refrigeration. 81 Since these applications are usually highly specific (Industrial 82 Automation, Building Automation, ...), it is not uncommon to see a 83 number of disparate terms to describe the same device or 84 functionality. Thus it was needed to specify common terms for all 85 LLNs to avoid confusion and discrepancies. Terminology specific to a 86 particular application are out of the scope of this document. 88 It is expected that all routing requirements documents defining 89 requirements or specifying routing solutions for LLN will use the 90 common terminology specified in this document. 92 2. Terminology 94 Actuator: a field device that controls a set of equipments. An 95 actuator can control and/or modulates the flow of a gas or liquid, 96 control electricity distribution, perform a mechanical operation, ... 98 AMI: Advanced Metering Infrastructure that makes use of Smart Grid 99 technologies. Encompasses smart-metering applications. 101 Channel: Radio frequency sub-band used to transmit a modulated signal 102 carrying packets. 104 Channel Hopping: A procedure by which field devices synchronously 105 change channels during operation. 107 Commissioning Tool: Any physical or logical device temporarily added 108 to the network for the expressed purpose of setting up the network 109 and device operational parameters. The commision tool can also be 110 temporarily added for scheduled or unscheduled maintenance. 112 Closed Loop Control: A process whereby a device controller controls 113 an actuator based on information sensed by one or more field devices. 115 Controller: A field device that can receive sensor input and 116 automatically change the environment in the facility by manipulating 117 digital or analog actuators. 119 DA: Distribution Automation, part of Smart Grid. Encompasses 120 technologies for maintenance and management of electrical 121 distribution systems. 123 Downstream: Data direction traveling from outside of the LLN (e.g. 124 traffic coming from a LAN, WAN or the Internet) via a LBR. 126 Field Device: physical devices placed in the network's operating 127 environment (plant, urban, home, ...). Field devices include 128 sensors, actuators as well as routers and Low power and lossy network 129 Border Router (including LBR). A field device is most of the time 130 (but not always) a constrained device with limited CPU, memory 131 footprint, storage capacity, bandwidth and sometimes power 132 constrained (battery operated). At the time of writing, for the sake 133 of illustration, a typicaly sensor or actuator would have a few 134 KBytes of RAM, a few dozens of KBytes of ROM/Flash memory, a 8/16/32 135 bit microcontroller and communication capabilities ranging from a few 136 Kbits/s to a few hundreds of KBits/s. Altough it is expected to see 137 comtinuous improvements of hardware and software technologies, such 138 devices will likely continue to be seen as constrained devices 139 compared to computers and routers used in the Internet. 141 Flash memory: non-volatile memory that can be re-programmed. 143 FMS: Facility Management System. A global term applied across all 144 the vertical designations within a building including, Heating, 145 Ventilating, and Air Conditioning also referred to as HVAC, Fire, 146 Security, Lighting and Elevator control. 148 HART: "Highway Addressable Remote Transducer", a group of 149 specifications for industrial process and control devices 150 administered by the HART Foundation (see [HART]). The latest version 151 for the specifications is HART7 which includes the additions for 152 WirelessHART. 154 HVAC: Heating, Ventilation and Air Conditioning. A term applied to 155 the comfort level of an internal space. 157 ISA: "International Society of Automation". ISA is an ANSI 158 accredited standards-making society. ISA100 is an ISA committee 159 whose charter includes defining a family of standards for industrial 160 automation. [ISA100.11a] is a working group within ISA100 that is 161 working on a standard for monitoring and non-critical process control 162 applications. 164 LAN: Local Area Network. 166 LBR: Low power and lossy network Border Router. The LBR is a device 167 that connects the low power and lossy network to another routing 168 domain such as a Local Area Network (LAN), Wide Area Network (WAN) or 169 the Internet where a possibly different routing protocol is in 170 operation. The LBR acts as a routing device and may possibly host 171 other functions such as data collector or aggregator. 173 LLN: Low power and Lossy networks (LLNs) are typically composed of 174 many embedded devices with limited power, memory, and processing 175 resources interconnected by a variety of links, such as IEEE 176 802.15.4, Low Power WiFi. There is a wide scope of application areas 177 for LLNs, including industrial monitoring, building automation (HVAC, 178 lighting, access control, fire), connected home, healthcare, 179 environmental monitoring, urban sensor networks, energy management, 180 assets tracking and refrigeration.. 182 Open Loop Control: A process whereby a plant operator manually 183 manipulates an actuator over the network where the decision is 184 influenced by information sensed by field devices. 186 RAM: Random Access Memory. The RAM is a volatile memory. 188 ROM: Read Only Memory. 190 ROLL: Routing Over Low power and Lossy networks. 192 Schedule: An agreed execution, wake-up, transmission, reception, 193 etc., time-table between two or more field devices. 195 Sensor: device that measures a physical quantity and converts it to a 196 analog or digital signal that can be read by a program or a user. 197 Sensed data can be of many types: electromagnetic (current, voltage, 198 power, resistance) , mechanical (pressure, flow, liquid density, 199 humidity, ...), chemical (oxygen, carbon monoxide, ...), acoustic 200 (noise, ultrasound), ... 202 Smart Grid: a broad class of applications to network and automate 203 utility infrastructure. 205 Timeslot: A fixed time interval that may be used for the transmission 206 or reception of a packet between two field devices. A timeslot used 207 for communications is associated with a slotted-link 208 Upstream: Data direction traveling from the LLN via the LBR to 209 outside of the LLN (LAN, WAN, Internet). 211 WAN: Wide Area Network. 213 3. IANA Considerations 215 This document includes no request for IANA action. 217 4. Security Considerations 219 Since this document specifies terminology and does not specify new 220 procedure or protocols, there are no security issues associated with 221 it. 223 5. Acknowledgements 225 The authors would like to thank Christian Jacquenet, Tim Winter and 226 Pieter De Mil for their valuable feed-back. 228 6. References 230 6.1. Normative References 232 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 233 Requirement Levels", BCP 14, RFC 2119, March 1997. 235 6.2. Informative References 237 [I-D.ietf-roll-home-routing-reqs] 238 Brandt, A., Buron, J., and G. Porcu, "Home Automation 239 Routing Requirement in Low Power and Lossy Networks", 240 draft-ietf-roll-home-routing-reqs-03 (work in progress), 241 September 2008. 243 [I-D.ietf-roll-indus-routing-reqs] 244 Networks, D., Thubert, P., Dwars, S., and T. Phinney, 245 "Industrial Routing Requirements in Low Power and Lossy 246 Networks", draft-ietf-roll-indus-routing-reqs-01 (work in 247 progress), July 2008. 249 [I-D.ietf-roll-urban-routing-reqs] 250 Dohler, M., Watteyne, T., Winter, T., Jacquenet, C., 251 Madhusudan, G., Chegaray, G., and D. Barthel, "Urban WSNs 252 Routing Requirements in Low Power and Lossy Networks", 253 draft-ietf-roll-urban-routing-reqs-01 (work in progress), 254 July 2008. 256 [I-D.martocci-roll-building-routing-reqs] 257 Martocci, J., Riou, N., Mil, P., and W. Vermeylen, 258 "Commercial Routing Requirements in Low Power and Lossy 259 Networks", draft-martocci-roll-building-routing-reqs-00 260 (work in progress), September 2008. 262 Author's Address 264 JP Vasseur 265 Cisco Systems, Inc 266 1414 Massachusetts Avenue 267 Boxborough, MA 01719 268 USA 270 Email: jpv@cisco.com 272 Full Copyright Statement 274 Copyright (C) The IETF Trust (2008). 276 This document is subject to the rights, licenses and restrictions 277 contained in BCP 78, and except as set forth therein, the authors 278 retain all their rights. 280 This document and the information contained herein are provided on an 281 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 282 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 283 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 284 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 285 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 286 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 288 Intellectual Property 290 The IETF takes no position regarding the validity or scope of any 291 Intellectual Property Rights or other rights that might be claimed to 292 pertain to the implementation or use of the technology described in 293 this document or the extent to which any license under such rights 294 might or might not be available; nor does it represent that it has 295 made any independent effort to identify any such rights. Information 296 on the procedures with respect to rights in RFC documents can be 297 found in BCP 78 and BCP 79. 299 Copies of IPR disclosures made to the IETF Secretariat and any 300 assurances of licenses to be made available, or the result of an 301 attempt made to obtain a general license or permission for the use of 302 such proprietary rights by implementers or users of this 303 specification can be obtained from the IETF on-line IPR repository at 304 http://www.ietf.org/ipr. 306 The IETF invites any interested party to bring to its attention any 307 copyrights, patents or patent applications, or other proprietary 308 rights that may cover technology that may be required to implement 309 this standard. Please address the information to the IETF at 310 ietf-ipr@ietf.org.