Networking Working GroupInternet Engineering Task Force (IETF) JP. VasseurInternet-DraftRequest for Comments: 7102 Cisco Systems,Inc Intended status:Inc. Category: InformationalSeptember 30, 2013 Expires: March 31,January 2014 ISSN: 2070-1721 TermsusedUsed inRutingRouting forLow power AndLow-Power and Lossy Networksdraft-ietf-roll-terminology-13.txtAbstractThe documentsThis document provides a glossary of terminology used in routing requirements and solutions for networks referred to asLow powerLow-Power and Lossy Networks(LLN).(LLNs). An LLN is typically composed of many embedded devices with limited power, memory, and processing resources interconnected by a variety of links. There is a wide scope of application areas for LLNs, including industrial monitoring, building automation(e.g. Heating, Ventilating, Air Conditioning,(e.g., heating, ventilation, air conditioning, lighting, access control, fire), connected home,healthcare,health care, environmental monitoring, urban sensor networks, energy management, assets tracking, and refrigeration. Status of This Memo ThisInternet-Draftdocument issubmitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documentsnot an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF).Note that other groups may also distribute working documents as Internet-Drafts. The listIt represents the consensus ofcurrent Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents validthe IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are amaximumcandidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status ofsix monthsthis document, any errata, and how to provide feedback on it may beupdated, replaced, or obsoleted by other documentsobtained atany time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on March 31, 2014.http://www.rfc-editor.org/info/rfc7102. Copyright Notice Copyright (c)20132014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . 2....................................................2 2. Terminology. . . . . . . . . . . . . . . . . . . . . . . . . 3.....................................................3 3.IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4.Security Considerations. . . . . . . . . . . . . . . . . . . 7 5..........................................7 4. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . 7 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 6.1. Normative References . . . . . . . . . . . . . . . . . . 7 6.2.................................................7 5. Informative References. . . . . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7..........................................7 1. IntroductionThe documentsThis document provides a glossary of terminology used in routing requirements and solutions for networks referred to asLow powerLow-Power and Lossy Networks(LLN). Low power and Lossy networks (LLNs)(LLNs). LLNs are typically composed of many embedded devices with limited power, memory, and processing resources interconnected by a variety of links, such as IEEE802.15.4, Low Power WiFi.802.15.4 or low-power Wi-Fi. There is a wide scope of application areas for LLNs, including industrial monitoring, building automation(HVAC,(heating, ventilation, air conditioning, lighting, access control, fire), connected home,healthcare,health care, environmental monitoring, urban sensor networks, energy management, assetstrackingtracking, and refrigeration. Since these applications are usually highly specific (forexample Industrial Automation, Building Automation, ...),example, industrial automation, building automation, etc.), it is not uncommon to see a number of disparate terms used to describe the same device or functionality.ThusThus, in order to avoid confusion or discrepancies, this document specifies the common terminology to be used in all ROLLWorking Groupworking group documents. The terms defined in this document are used in[RFC5548],[RFC5673], [RFC5826][RFC5548], [RFC5673], [RFC5826], and [RFC5867]. Terminology specific to a particular applicationareis out of the scope of this document. It is expected that all routingrequirementsdocuments defining requirements or specifyingroutingsolutions for LLN will use the common terminology specified in this document. This document should be listed as an informative reference. 2. Terminology Actuator:aA field device that controls a set of equipment. For example, an actuator might control and/or modulate the flow of a gas or liquid, control electricity distribution, perform a mechanical operation,...etc. AMI: Advanced MeteringInfrastructure that makesInfrastructure. Makes use of Smart Grid technologies. A canonical Smart Grid application issmart-metering.smart- metering. Channel: Radio frequency sub-band used to transmit a modulated signal carrying packets. Channel Hopping: A procedure by which field devices synchronously change channels during operation. Commissioning Tool: Any physical or logical device temporarily added to the network for the express purpose of setting up the network and device operational parameters. Thecommisioningcommissioning tool can also be temporarily added to the LLN for scheduled or unscheduled maintenance. Closed Loop Control: A procedure whereby a device controller controls an actuator based on input information sensed by one or more field devices. Controller: A field device that can receive sensor input and automatically change the environment in the facility by manipulating digital or analog actuators. DA: DistributionAutomation, partAutomation. Part of Smart Grid. Encompasses technologies for maintenance and management of electrical distribution systems. DAG: Directed AcyclicGraph:Graph. A directed graph with no directed cycles (a graph formed by a collection of vertices and directed edges where each edge connects one vertex to another, such that there is no way to start at some vertex v and follow a sequence of edges that eventually loops back tothe edgevertex vagain)again). Data sink: A device that collects data from nodes in an LLN. Downstream: Data direction traveling from outside of the LLN(e.g.(e.g., traffic coming from a LAN,WANWAN, or the Internet) viaa LBR,an LLN Border Router (LBR), or ingeneralgeneral, "deeper" in the Directed Acyclic Graph computed by the routing protocol. Field Device: A field device is a physical device placed in the network's operating environment(e.g.(e.g., plant, urban area, or home). Field devices includesensors,sensors and actuators as well as routers andLow powerLow-Power and Lossy Network BorderRouter (LBR).Routers (LBRs). A field device is usually (but not always) a device with constrained CPU, memory footprint, storage capacity,bandwidthbandwidth, and sometimes power (battery operated). At the time of writing, for the sake of illustration, a typical sensor or actuator would have a fewKBytesKilobytes of RAM, a few dozens ofKBytesKilobytes of ROM/Flash memory, a8/16/32 bit microcontroller8-/16-/32-bit microcontroller, and communication capabilities ranging from a fewKbits/skbits/s to a fewhundreds of KBits/s.hundred kbits/s. Althoughit is expected to seecontinuousimprovementsimprovement of hardware and softwaretechnologies,technologies is expected, such devices will likely continue to be seen asresource constrainedresource-constrained devices comparedcomparedto computers and routers used in the rest of the Internet. Flashmemory:Memory: non-volatile memory that can be re-programmed. FMS: Facility Management System. A global term applied across all the vertical designations within abuilding including, Heating, Ventilating,building, including heating, ventilation, andAir Conditioning alsoair conditioning (also referred to asHVAC, Fire, Security, LightingHVAC), fire, security, lighting, andElevatorelevator control. HART:"HighwayHighway Addressable RemoteTransducer", aTransducer. A group of specifications for industrial process and control devices administered by the HART Foundation (see [HART]). The latest version for the specifications isHART7HART7, which includes the additions for WirelessHART. HVAC: Heating,VentilationVentilation, and Air Conditioning. A term applied to mechanisms used to maintain the comfort level of an internal space. ISA:"InternationalInternational Society ofAutomation". ISA is anAutomation. An ANSI accredited standards-making society. ISA100 is an ISA committee whose charter includes defining a family of standards for industrial automation. [ISA100.11a] is a working group within ISA100 that is working on a standard for monitoring and non-criticalprocessprocess- control applications. LAN: Local Area Network. LBR:Low powerLow-Power and Lossy Network Border Router.The LBR is aA device that connects theLow powerLow-Power and Lossy Network to another routing domain such as aLocal Area Network (LAN), Wide Area Network (WAN)LAN, a WAN, or the Internet where apossiblydifferent routing protocolismay be in operation. The LBR acts as a routing device and may possibly host other functions such as data collector or aggregator. LLN:Low powerLow-Power and Lossynetworks (LLNs) are typicallyNetwork. Typically composed of many embedded devices with limited power, memory, and processing resources interconnected by a variety of links, such as IEEE 802.15.4 orLow Power WiFi.low-power Wi-Fi. There is a wide scope of application areas for LLNs, including industrial monitoring, building automation (HVAC, lighting, access control, fire), connected home,healthcare,health care, environmental monitoring, urban sensor networks, energy management, assetstrackingtracking, andrefrigeration..refrigeration. MP2P:Multipoint-to-Point is usedMultipoint-to-Point. Used to describe a particular traffic pattern(e.g.(e.g., MP2P flows collecting information from many nodes flowing upstream towards a collecting sink or an LBR). MAC: Medium Access Control. Refers to algorithms and procedures used by the data link layer to coordinate use of the physical layer.Non-sleepyNon-Sleepy Node: Anon-sleepy node is anode that always remains in a fullypowered onpowered-on state(i.e.(i.e., always awake) where it has the capability to perform communication. Open Loop Control: A process whereby a plant operator manually manipulates an actuator over the network where the decision is influenced by information sensed by field devices. PER: Packet Error Rate. A ratio of the number of unusable packets (not received atall,all or received inerror-error, even after any applicable error correction has been applied) to the total number of packets that would have beenbeenreceived in the absence of errors. P2P: Point To Point.This refersRefers to traffic exchanged between two nodes (regardless of the number of hops between the two nodes). P2MP:Point-to-Multipoint traffic refersPoint-to-Multipoint. Refers to traffic between one node and a set of nodes. This is similar to the P2MP concept in Multicast or MPLS Traffic Engineering ([RFC4461]and [RFC4875]). A commonRPLuse case for the Routing Protocol for Low-Power and Lossy Networks (RPL) involves P2MP flows from or through a DAG root outward towards other nodes contained in the DAG. RAM: Random Access Memory.The RAM is aA volatile memory. RFID: Radio Frequency IDentification. ROM:Read OnlyRead-Only Memory. ROLL: Routing OverLow powerLow-Power and Lossynetworks.Networks. RPL: An IPv6 Routing Protocol for Low-Power and Lossy Networks that provides a mechanism whereby multipoint-to-point traffic from devices inside the LLN towards a central control point as well aspoint-to- multipointpoint-to-multipoint traffic from the central control point to the devices inside the LLN are supported. RPL alsosupport point-to-pointsupports point-to- point traffic between anyarbitratry nodearbitrary nodes in the LLN. RPL Domain: ARPL routing domain is acollection of RPL routers under the control of a single administration. The boundaries of routing domains are defined by network management by setting some links to be exterior, orinter-domain,inter- domain, links. Schedule: An agreed execution, wake-up, transmission, reception, etc.,time-tabletimetable between two or more field devices. Sensor: Asensor is adevice that measures a physical quantity and converts it to an analog or digital signal that can be read by a program or a user. Sensed data can be of many types: electromagnetic(e.g.(e.g., current, voltage, power,resistance, ...) ,or resistance), mechanical(e.g.(e.g., pressure, flow, liquid density,humidity, ...),or humidity), chemical(e.g. oxygen,(e.g., oxygen or carbonmonoxide, ...),monoxide), acoustic(e.g. noise,(e.g., noise or ultrasound),...etc. Sleepy Node: Asleepy node is anode that may sometimes go into a sleep mode(i.e.(i.e., go into alow powerlow-power state to conserve power) and temporarily suspend protocol communication. Whennonot inasleep mode, the sleepy node is in a fullypowered onpowered-on state where it has the capability to perform communication. Smart Grid: ASmart Grid is abroad class of applications to network and automate utility infrastructure. Timeslot: ATimeslot is afixed time interval that may be used for the transmission or reception of a packet between two field devices. A timeslot used for communications is associated with aslotted-linkslotted-link. Upstream: Data direction traveling from the LLN via the LBR to outside of the LLN (LAN, WAN, or Internet) orgeneralgenerally closer to the root of theDirected Acyclic GraphDAG computed by the routing protocol. WAN: Wide Area Network. 3.IANA Considerations This document includes no request for IANA action. 4.Security Considerations Since this document specifies terminology and does not specify newprocedureprocedures or protocols, it raises no new securityissue. 5.issues. 4. Acknowledgements The authors would like to thank Christian Jacquenet, Tim Winter, Pieter De Mil, David Meyer, MukulGoyalGoyal, and Abdussalam Baryun for their valuablefeed-back. 6. References 6.1.feedback. 5. Informative References [HART] HART CommunicationFoundation (http://www.hartcomm.org)Foundation, <http://www.hartcomm.org>. [ISA100.11a] ISA, "Wireless systems for industrial automation: Process control and related applications", ISA 100.11a, May 2008, <http://www.isa.org/Community/ SP100WirelessSystemsforAutomation>. [RFC4461] Yasukawa, S., Ed., "Signaling Requirements for Point-to- Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)", RFC 4461, April 2006. [RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. Yasukawa, Ed., "Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)", RFC 4875, May 2007. [RFC5548] Dohler, M., Ed., Watteyne, T., Ed., Winter, T., Ed., and D. Barthel, Ed., "Routing Requirements for Urban Low-Power and Lossy Networks", RFC 5548, May 2009. [RFC5673] Pister, K., Ed., Thubert, P., Ed., Dwars, S., and T. Phinney, "Industrial Routing Requirements in Low-Power and Lossy Networks", RFC 5673, October 2009. [RFC5826] Brandt, A., Buron, J., and G. Porcu, "Home Automation Routing Requirements in Low-Power and Lossy Networks", RFC 5826, April 2010. [RFC5867] Martocci, J., Ed., De Mil, P., Riou, N., and W. Vermeylen, "Building Automation Routing Requirements in Low-Power and Lossy Networks", RFC 5867, June 2010. Author's AddressJPJP. Vasseur Cisco Systems,IncInc. 1414 Massachusetts Avenue Boxborough, MA 01719USA Email:US EMail: jpv@cisco.com