idnits 2.17.00 (12 Aug 2021) /tmp/idnits64167/draft-vasseur-roll-terminology-00.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 289. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 300. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 307. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 313. 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 11, 2008) is 4999 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'HART' is mentioned on line 152, but not defined == Unused Reference: 'I-D.ietf-roll-home-routing-reqs' is defined on line 240, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-roll-indus-routing-reqs' is defined on line 246, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-roll-urban-routing-reqs' is defined on line 252, but no explicit reference was found in the text == Unused Reference: 'I-D.martocci-roll-building-routing-reqs' is defined on line 259, 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 11, 2008 4 Expires: March 15, 2009 6 Terminology in Low power And Lossy Networks 7 draft-vasseur-roll-terminology-00.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 15, 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 (HVAC, lighting, access control, fire), connected home, 43 healthcare, environmental monitoring, urban sensor networks, energy 44 management, assets tracking, refrigeration. 46 Requirements Language 48 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 49 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 50 document are to be interpreted as described in RFC 2119 [RFC2119]. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 57 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 58 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 59 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 60 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 61 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 63 Intellectual Property and Copyright Statements . . . . . . . . . . 8 65 1. Introduction 67 The documents defines a terminology for discussing routing 68 requirements and solutions for networks referred to as Low power and 69 Lossy Networks (LLN). 71 Low power and Lossy networks (LLNs) are typically composed of many 72 embedded devices with limited power, memory, and processing resources 73 interconnected by a variety of links, such as IEEE 802.15.4, Low 74 Power WiFi. There is a wide scope of application areas for LLNs, 75 including industrial monitoring, building automation (HVAC, lighting, 76 access control, fire), connected home, healthcare, environmental 77 monitoring, urban sensor networks, energy management, assets 78 tracking, refrigeration. 80 Since these applications are usually highly specific (Industrial 81 Automation, Building Automation, ...), it is not uncommon to see a 82 number of disparate terms to describe the same device of 83 functionality. Thus it was needed to specify common terms for all 84 LLNs to avoid confusion and discrepancies. Terminology specific to a 85 particular application are out of the scope of this document. 87 It is expected that all routing requirements documents defining 88 requirements or specifying routing solutions for LLN will use the 89 common terminology specified in this document. 91 2. Terminology 93 Actuator: a field device that moves or controls an equipment. An 94 actuator can control and/or modulates the flow of a gas or liquid, 95 control electricity distribution, perform a mechanical operation, ... 97 AMI: Advanced Metering Infrastructure, part of Smart Grid. 98 Encompasses smart-metering applications. 100 BAS: Building Automation System. This term is synonymous with 101 Facility Management System (FMS). 103 BMS: Building Automation System. This term is synonymous with 104 Facility Management System (FMS) 106 Channel: Radio frequency sub-band used to transmit a modulated signal 107 carrying packets. 109 Channel Hopping An algorithm by which field devices synchronously 110 change channels during operation 111 Commissioning Tool: Any physical or logical device temporarily added 112 to the network for the expressed purpose of setting up the network 113 and device operational parameters 115 Closed Loop Control: A process whereby a device controller controls 116 an actuator based on information sensed by one or more field devices. 118 Controller: A field device that can receive sensor input and 119 automatically change the environment in the facility by manipulating 120 digital or analog actuators. 122 DA: Distribution Automation, part of Smart Grid. Encompasses 123 technologies for maintenance and management of electrical 124 distribution systems. 126 Downstream: Data direction traveling from outside of the LLN (LAN, 127 WAN, Internet) via the LBR to the LLN. 129 Field Device: physical devices placed in the network's operating 130 environment (plant, urban, home, ...). Field devices include 131 sensors, actuators as well as routers and Lowe power and lossy 132 network Border Router (LBR). A field device is most of the time a 133 constrained device with limited CPU, memory footprint, storage 134 capacity, bandwidth and sometimes power constrained (battery 135 operated). At the time of writing, for the sake of illustration, a 136 typicaly sensor or actuator would have a few KBytes of RAM, a few 137 dozens of KBytes of ROM/Flash memory, a 8/16/32 bit microcontroller 138 and communication capabilities ranging from a few Kbits/s to a few 139 hundreds of KBits/s. With the dramatic imrpovments of hardware and 140 software technologies it is expected to see continous improvments but 141 such devices will likely continue to be seen as constrained devices 142 compared to computers and routers used in the Internet. 144 Flash memory: non-volatile memory that can be re-programmed. 146 FMS: Facility Management System. A global term applied across all 147 the vertical designations within a building including, HVAC, Fire, 148 Security, Lighting and Elevator control. 150 HART: "Highway Addressable Remote Transducer", a group of 151 specifications for industrial process and control devices 152 administered by the HART Foundation (see [HART]). The latest version 153 for the specifications is HART7 which includes the additions for 154 WirelessHART. 156 HVAC: Heating, Ventilation and Air Conditioning. A term applied to 157 the comfort level of an internal space. 159 ISA: "International Society of Automation". ISA is an ANSI 160 accredited standards-making society. ISA100 is an ISA committee 161 whose charter includes defining a family of standards for industrial 162 automation. [ISA100.11a] is a working group within ISA100 that is 163 working on a standard for monitoring and non-critical process control 164 applications. 166 LAN: Local Area Network. 168 LBR: Low power and loosy network Border Router. The LBR is a device 169 that connects the low power and lossy network to another routing 170 domain such as a Local Area Network (LAN), Wide Area Network (WAN) or 171 the Internet where a possibly different routing protocol is in 172 operation. The LBR acts as a routing device and may possibly host 173 other functions such as data collector or aggregator, which is fairly 174 typical in LLN. 176 LLN: Low power and Lossy networks (LLNs) are typically composed of 177 many embedded devices with limited power, memory, and processing 178 resources interconnected by a variety of links, such as IEEE 179 802.15.4, Low Power WiFi. There is a wide scope of application areas 180 for LLNs, including industrial monitoring, building automation (HVAC, 181 lighting, access control, fire), connected home, healthcare, 182 environmental monitoring, urban sensor networks, energy management, 183 assets tracking, refrigeration.. 185 Open Loop Control: A process whereby a plant operator manually 186 manipulates an actuator over the network where the decision is 187 influenced by information sensed by field devices. 189 RAM: Random Access Memory. The RAM is a volatile memory. 191 ROM: Read Only Memory. 193 ROLL: Routing Over Low power and Lossy networks. 195 Schedule: An agreed execution, wake-up, transmission, reception, 196 etc., time-table between two or more field devices. 198 Sensor: device that measures a physical quantity and convert it to a 199 analog or digital signal that can be read by a program or a user. 200 Sensed data can be of many types: electromagnetic (current, voltage, 201 power, resistance) , mechanical (pressure, flow, liquid density, 202 humidity, ...), chemical (oxygen, carbon monoxide, ...), acoustic 203 (noise, ultrasound), ... 205 Smart Grid: a broad class of applications to network and automate 206 utility infrastructure. 208 Timeslot: A fixed time interval that may be used for the transmission 209 or reception of a packet between two field devices. A timeslot used 210 for communications is associated with a slotted-link 212 Uptream: Data direction traveling from the LLN via the LBR to outside 213 of the LLN (LAN, WAN, Internet). 215 WAN: Wide Area Network. 217 3. IANA Considerations 219 This document includes no request for IANA action. 221 4. Security Considerations 223 Since this document specifies terminology and does not specify new 224 procedure or protocols, there are no security issues associated with 225 it. 227 5. Acknowledgements 229 The authors would like to thank ... 231 6. References 233 6.1. Normative References 235 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 236 Requirement Levels", BCP 14, RFC 2119, March 1997. 238 6.2. Informative References 240 [I-D.ietf-roll-home-routing-reqs] 241 Brandt, A. and G. Porcu, "Home Automation Routing 242 Requirement in Low Power and Lossy Networks", 243 draft-ietf-roll-home-routing-reqs-02 (work in progress), 244 July 2008. 246 [I-D.ietf-roll-indus-routing-reqs] 247 Networks, D., Thubert, P., Dwars, S., and T. Phinney, 248 "Industrial Routing Requirements in Low Power and Lossy 249 Networks", draft-ietf-roll-indus-routing-reqs-01 (work in 250 progress), July 2008. 252 [I-D.ietf-roll-urban-routing-reqs] 253 Dohler, M., Watteyne, T., Winter, T., Jacquenet, C., 254 Madhusudan, G., Chegaray, G., and D. Barthel, "Urban WSNs 255 Routing Requirements in Low Power and Lossy Networks", 256 draft-ietf-roll-urban-routing-reqs-01 (work in progress), 257 July 2008. 259 [I-D.martocci-roll-building-routing-reqs] 260 Martocci, J., Riou, N., Mil, P., and W. Vermeylen, 261 "Commercial Routing Requirements in Low Power and Lossy 262 Networks", draft-martocci-roll-building-routing-reqs-00 263 (work in progress), September 2008. 265 Author's Address 267 JP Vasseur 268 Cisco Systems, Inc 269 1414 Massachusetts Avenue 270 Boxborough, MA 01719 271 USA 273 Email: jpv@cisco.com 275 Full Copyright Statement 277 Copyright (C) The IETF Trust (2008). 279 This document is subject to the rights, licenses and restrictions 280 contained in BCP 78, and except as set forth therein, the authors 281 retain all their rights. 283 This document and the information contained herein are provided on an 284 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 285 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 286 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 287 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 288 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 289 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 291 Intellectual Property 293 The IETF takes no position regarding the validity or scope of any 294 Intellectual Property Rights or other rights that might be claimed to 295 pertain to the implementation or use of the technology described in 296 this document or the extent to which any license under such rights 297 might or might not be available; nor does it represent that it has 298 made any independent effort to identify any such rights. Information 299 on the procedures with respect to rights in RFC documents can be 300 found in BCP 78 and BCP 79. 302 Copies of IPR disclosures made to the IETF Secretariat and any 303 assurances of licenses to be made available, or the result of an 304 attempt made to obtain a general license or permission for the use of 305 such proprietary rights by implementers or users of this 306 specification can be obtained from the IETF on-line IPR repository at 307 http://www.ietf.org/ipr. 309 The IETF invites any interested party to bring to its attention any 310 copyrights, patents or patent applications, or other proprietary 311 rights that may cover technology that may be required to implement 312 this standard. Please address the information to the IETF at 313 ietf-ipr@ietf.org.