idnits 2.17.1 draft-ietf-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 291. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 302. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 309. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 315. 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 (October 9, 2008) is 5671 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'HART' is mentioned on line 153, but not defined == Unused Reference: 'I-D.ietf-roll-home-routing-reqs' is defined on line 242, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-roll-indus-routing-reqs' is defined on line 248, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-roll-urban-routing-reqs' is defined on line 254, but no explicit reference was found in the text == Unused Reference: 'I-D.martocci-roll-building-routing-reqs' is defined on line 261, but no explicit reference was found in the text == Outdated reference: A later version (-11) exists of draft-ietf-roll-home-routing-reqs-03 == Outdated reference: A later version (-06) exists of draft-ietf-roll-indus-routing-reqs-01 == Outdated reference: A later version (-05) exists of draft-ietf-roll-urban-routing-reqs-01 == 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 October 9, 2008 4 Expires: April 12, 2009 6 Terminology in Low power And Lossy Networks 7 draft-ietf-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 April 12, 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 (e.g. Heating, Ventilating, Air Conditioning, lighting, 43 access control, fire), connected home, healthcare, environmental 44 monitoring, urban sensor networks, energy management, assets 45 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 (for example 82 Industrial Automation, Building Automation, ...), it is not uncommon 83 to see a number of disparate terms to describe the same device or 84 functionality. Thus in order to avoid confusion or discrepancies, 85 this document specifies the common terminology to be used in all ROLL 86 Working Group documents. Terminology specific to a particular 87 application are out of the scope of this document. 89 It is expected that all routing requirements documents defining 90 requirements or specifying routing solutions for LLN will use the 91 common terminology specified in this document. 93 2. Terminology 95 Actuator: a field device that controls a set of equipment. For 96 example, an actuator might control and/or modulates the flow of a gas 97 or liquid, control electricity distribution, perform a mechanical 98 operation, ... 100 AMI: Advanced Metering Infrastructure that makes use of Smart Grid 101 technologies. A canonical Smart Grid application is smart-metering. 103 Channel: Radio frequency sub-band used to transmit a modulated signal 104 carrying packets. 106 Channel Hopping: A procedure by which field devices synchronously 107 change channels during operation. 109 Commissioning Tool: Any physical or logical device temporarily added 110 to the network for the expressed purpose of setting up the network 111 and device operational parameters. The commisioning tool can also be 112 temporarily added to the LLN for scheduled or unscheduled 113 maintenance. 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 (e.g. 127 traffic coming from a LAN, WAN or the Internet) via a LBR. 129 Field Device: A field deviced is a physical device placed in the 130 network's operating environment (e.g. plant, urban or home). Field 131 devices include sensors, actuators as well as routers and Low power 132 and Lossy Network Border Router (including LBR). A field device is 133 usually (but not always) a device with constrained CPU, memory 134 footprint, storage capacity, bandwidth and sometimes power (battery 135 operated). At the time of writing, for the sake of illustration, a 136 typical 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. Although it is expected to see continuous 140 improvements of hardware and software technologies, such devices will 141 likely continue to be seen as resource constrained devices compared 142 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, Heating, 148 Ventilating, and Air Conditioning also referred to as HVAC, Fire, 149 Security, Lighting and Elevator control. 151 HART: "Highway Addressable Remote Transducer", a group of 152 specifications for industrial process and control devices 153 administered by the HART Foundation (see [HART]). The latest version 154 for the specifications is HART7 which includes the additions for 155 WirelessHART. 157 HVAC: Heating, Ventilation and Air Conditioning. A term applied to 158 the comfort level of an internal space. 160 ISA: "International Society of Automation". ISA is an ANSI 161 accredited standards-making society. ISA100 is an ISA committee 162 whose charter includes defining a family of standards for industrial 163 automation. [ISA100.11a] is a working group within ISA100 that is 164 working on a standard for monitoring and non-critical process control 165 applications. 167 LAN: Local Area Network. 169 LBR: Low power and lossy network Border Router. The LBR is a device 170 that connects the Low power and Lossy Network to another routing 171 domain such as a Local Area Network (LAN), Wide Area Network (WAN) or 172 the Internet where a possibly different routing protocol is in 173 operation. The LBR acts as a routing device and may possibly host 174 other functions such as data collector or aggregator. 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 802.15.4 179 or Low Power WiFi. There is a wide scope of application areas for 180 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 and 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 RFID: Radio Frequency IDentification. 193 ROM: Read Only Memory. 195 ROLL: Routing Over Low power and Lossy networks. 197 Schedule: An agreed execution, wake-up, transmission, reception, 198 etc., time-table between two or more field devices. 200 Sensor: A sensor is a device that measures a physical quantity and 201 converts it to a analog or digital signal that can be read by a 202 program or a user. Sensed data can be of many types: electromagnetic 203 (e.g. current, voltage, power, resistance, ...) , mechanical (e.g. 204 pressure, flow, liquid density, humidity, ...), chemical (e.g. 205 oxygen, carbon monoxide, ...), acoustic (e.g. noise, ultrasound), ... 207 Smart Grid: A Smart Grid is a broad class of applications to network 208 and automate utility infrastructure. 210 Timeslot: A Timeslot is a fixed time interval that may be used for 211 the transmission or reception of a packet between two field devices. 212 A timeslot used for communications is associated with a slotted-link 214 Upstream: Data direction traveling from the LLN via the LBR to 215 outside of the LLN (LAN, WAN, Internet). 217 WAN: Wide Area Network. 219 3. IANA Considerations 221 This document includes no request for IANA action. 223 4. Security Considerations 225 Since this document specifies terminology and does not specify new 226 procedure or protocols, it raises no new security issue. 228 5. Acknowledgements 230 The authors would like to thank Christian Jacquenet, Tim Winter, 231 Pieter De Mil and David Meyer for their valuable feed-back. 233 6. References 235 6.1. Normative References 237 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 238 Requirement Levels", BCP 14, RFC 2119, March 1997. 240 6.2. Informative References 242 [I-D.ietf-roll-home-routing-reqs] 243 Brandt, A., Buron, J., and G. Porcu, "Home Automation 244 Routing Requirement in Low Power and Lossy Networks", 245 draft-ietf-roll-home-routing-reqs-03 (work in progress), 246 September 2008. 248 [I-D.ietf-roll-indus-routing-reqs] 249 Networks, D., Thubert, P., Dwars, S., and T. Phinney, 250 "Industrial Routing Requirements in Low Power and Lossy 251 Networks", draft-ietf-roll-indus-routing-reqs-01 (work in 252 progress), July 2008. 254 [I-D.ietf-roll-urban-routing-reqs] 255 Dohler, M., Watteyne, T., Winter, T., Jacquenet, C., 256 Madhusudan, G., Chegaray, G., and D. Barthel, "Urban WSNs 257 Routing Requirements in Low Power and Lossy Networks", 258 draft-ietf-roll-urban-routing-reqs-01 (work in progress), 259 July 2008. 261 [I-D.martocci-roll-building-routing-reqs] 262 Martocci, J., Riou, N., Mil, P., and W. Vermeylen, 263 "Commercial Routing Requirements in Low Power and Lossy 264 Networks", draft-martocci-roll-building-routing-reqs-00 265 (work in progress), September 2008. 267 Author's Address 269 JP Vasseur 270 Cisco Systems, Inc 271 1414 Massachusetts Avenue 272 Boxborough, MA 01719 273 USA 275 Email: jpv@cisco.com 277 Full Copyright Statement 279 Copyright (C) The IETF Trust (2008). 281 This document is subject to the rights, licenses and restrictions 282 contained in BCP 78, and except as set forth therein, the authors 283 retain all their rights. 285 This document and the information contained herein are provided on an 286 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 287 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 288 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 289 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 290 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 291 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 293 Intellectual Property 295 The IETF takes no position regarding the validity or scope of any 296 Intellectual Property Rights or other rights that might be claimed to 297 pertain to the implementation or use of the technology described in 298 this document or the extent to which any license under such rights 299 might or might not be available; nor does it represent that it has 300 made any independent effort to identify any such rights. Information 301 on the procedures with respect to rights in RFC documents can be 302 found in BCP 78 and BCP 79. 304 Copies of IPR disclosures made to the IETF Secretariat and any 305 assurances of licenses to be made available, or the result of an 306 attempt made to obtain a general license or permission for the use of 307 such proprietary rights by implementers or users of this 308 specification can be obtained from the IETF on-line IPR repository at 309 http://www.ietf.org/ipr. 311 The IETF invites any interested party to bring to its attention any 312 copyrights, patents or patent applications, or other proprietary 313 rights that may cover technology that may be required to implement 314 this standard. Please address the information to the IETF at 315 ietf-ipr@ietf.org.