| < draft-vasseur-roll-terminology-00.txt | draft-vasseur-roll-terminology-01.txt > | |||
|---|---|---|---|---|
| Networking Working Group JP. Vasseur | Networking Working Group JP. Vasseur | |||
| Internet-Draft Cisco Systems, Inc | Internet-Draft Cisco Systems, Inc | |||
| Intended status: Informational September 11, 2008 | Intended status: Informational September 15, 2008 | |||
| Expires: March 15, 2009 | Expires: March 19, 2009 | |||
| Terminology in Low power And Lossy Networks | Terminology in Low power And Lossy Networks | |||
| draft-vasseur-roll-terminology-00.txt | draft-vasseur-roll-terminology-01.txt | |||
| Status of this Memo | Status of this Memo | |||
| By submitting this Internet-Draft, each author represents that any | By submitting this Internet-Draft, each author represents that any | |||
| applicable patent or other IPR claims of which he or she is aware | applicable patent or other IPR claims of which he or she is aware | |||
| have been or will be disclosed, and any of which he or she becomes | have been or will be disclosed, and any of which he or she becomes | |||
| aware will be disclosed, in accordance with Section 6 of BCP 79. | aware will be disclosed, in accordance with Section 6 of BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
| skipping to change at page 1, line 34 ¶ | skipping to change at page 1, line 34 ¶ | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
| This Internet-Draft will expire on March 15, 2009. | This Internet-Draft will expire on March 19, 2009. | |||
| Abstract | Abstract | |||
| The documents defines a terminology for discussing routing | The documents defines a terminology for discussing routing | |||
| requirements and solutions for networks referred to as Low power and | requirements and solutions for networks referred to as Low power and | |||
| Lossy Networks (LLN). A LLN is typically composed of many embedded | Lossy Networks (LLN). A LLN is typically composed of many embedded | |||
| devices with limited power, memory, and processing resources | devices with limited power, memory, and processing resources | |||
| interconnected by a variety of links. There is a wide scope of | interconnected by a variety of links. There is a wide scope of | |||
| application areas for LLNs, including industrial monitoring, building | application areas for LLNs, including industrial monitoring, building | |||
| automation (HVAC, lighting, access control, fire), connected home, | automation (Heating, Ventilating, and Air Conditioning also referred | |||
| to as HVAC, lighting, access control, fire), connected home, | ||||
| healthcare, environmental monitoring, urban sensor networks, energy | healthcare, environmental monitoring, urban sensor networks, energy | |||
| management, assets tracking, refrigeration. | management, assets tracking, refrigeration. | |||
| Requirements Language | Requirements Language | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | |||
| document are to be interpreted as described in RFC 2119 [RFC2119]. | document are to be interpreted as described in RFC 2119 [RFC2119]. | |||
| Table of Contents | Table of Contents | |||
| skipping to change at page 3, line 7 ¶ | skipping to change at page 3, line 7 ¶ | |||
| 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 | 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 | |||
| 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 | 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 | 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 | 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 | |||
| 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 | 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 | |||
| Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 | Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
| Intellectual Property and Copyright Statements . . . . . . . . . . 8 | Intellectual Property and Copyright Statements . . . . . . . . . . 8 | |||
| 1. Introduction | 1. Introduction | |||
| The documents defines a terminology for discussing routing | This document defines a terminology for discussing routing | |||
| requirements and solutions for networks referred to as Low power and | requirements and solutions for networks referred to as Low power and | |||
| Lossy Networks (LLN). | Lossy Networks (LLN). | |||
| Low power and Lossy networks (LLNs) are typically composed of many | Low power and Lossy networks (LLNs) are typically composed of many | |||
| embedded devices with limited power, memory, and processing resources | embedded devices with limited power, memory, and processing resources | |||
| interconnected by a variety of links, such as IEEE 802.15.4, Low | interconnected by a variety of links, such as IEEE 802.15.4, Low | |||
| Power WiFi. There is a wide scope of application areas for LLNs, | Power WiFi. There is a wide scope of application areas for LLNs, | |||
| including industrial monitoring, building automation (HVAC, lighting, | including industrial monitoring, building automation (HVAC, lighting, | |||
| access control, fire), connected home, healthcare, environmental | access control, fire), connected home, healthcare, environmental | |||
| monitoring, urban sensor networks, energy management, assets | monitoring, urban sensor networks, energy management, assets tracking | |||
| tracking, refrigeration. | and refrigeration. | |||
| Since these applications are usually highly specific (Industrial | Since these applications are usually highly specific (Industrial | |||
| Automation, Building Automation, ...), it is not uncommon to see a | Automation, Building Automation, ...), it is not uncommon to see a | |||
| number of disparate terms to describe the same device of | number of disparate terms to describe the same device or | |||
| functionality. Thus it was needed to specify common terms for all | functionality. Thus it was needed to specify common terms for all | |||
| LLNs to avoid confusion and discrepancies. Terminology specific to a | LLNs to avoid confusion and discrepancies. Terminology specific to a | |||
| particular application are out of the scope of this document. | particular application are out of the scope of this document. | |||
| It is expected that all routing requirements documents defining | It is expected that all routing requirements documents defining | |||
| requirements or specifying routing solutions for LLN will use the | requirements or specifying routing solutions for LLN will use the | |||
| common terminology specified in this document. | common terminology specified in this document. | |||
| 2. Terminology | 2. Terminology | |||
| Actuator: a field device that moves or controls an equipment. An | Actuator: a field device that controls a set of equipments. An | |||
| actuator can control and/or modulates the flow of a gas or liquid, | actuator can control and/or modulates the flow of a gas or liquid, | |||
| control electricity distribution, perform a mechanical operation, ... | control electricity distribution, perform a mechanical operation, ... | |||
| AMI: Advanced Metering Infrastructure, part of Smart Grid. | AMI: Advanced Metering Infrastructure that makes use of Smart Grid | |||
| Encompasses smart-metering applications. | technologies. Encompasses smart-metering applications. | |||
| BAS: Building Automation System. This term is synonymous with | ||||
| Facility Management System (FMS). | ||||
| BMS: Building Automation System. This term is synonymous with | ||||
| Facility Management System (FMS) | ||||
| Channel: Radio frequency sub-band used to transmit a modulated signal | Channel: Radio frequency sub-band used to transmit a modulated signal | |||
| carrying packets. | carrying packets. | |||
| Channel Hopping An algorithm by which field devices synchronously | Channel Hopping: A procedure by which field devices synchronously | |||
| change channels during operation | change channels during operation. | |||
| Commissioning Tool: Any physical or logical device temporarily added | Commissioning Tool: Any physical or logical device temporarily added | |||
| to the network for the expressed purpose of setting up the network | to the network for the expressed purpose of setting up the network | |||
| and device operational parameters | and device operational parameters. The commision tool can also be | |||
| temporarily added for scheduled or unscheduled maintenance. | ||||
| Closed Loop Control: A process whereby a device controller controls | Closed Loop Control: A process whereby a device controller controls | |||
| an actuator based on information sensed by one or more field devices. | an actuator based on information sensed by one or more field devices. | |||
| Controller: A field device that can receive sensor input and | Controller: A field device that can receive sensor input and | |||
| automatically change the environment in the facility by manipulating | automatically change the environment in the facility by manipulating | |||
| digital or analog actuators. | digital or analog actuators. | |||
| DA: Distribution Automation, part of Smart Grid. Encompasses | DA: Distribution Automation, part of Smart Grid. Encompasses | |||
| technologies for maintenance and management of electrical | technologies for maintenance and management of electrical | |||
| distribution systems. | distribution systems. | |||
| Downstream: Data direction traveling from outside of the LLN (LAN, | Downstream: Data direction traveling from outside of the LLN (e.g. | |||
| WAN, Internet) via the LBR to the LLN. | traffic coming from a LAN, WAN or the Internet) via a LBR. | |||
| Field Device: physical devices placed in the network's operating | Field Device: physical devices placed in the network's operating | |||
| environment (plant, urban, home, ...). Field devices include | environment (plant, urban, home, ...). Field devices include | |||
| sensors, actuators as well as routers and Lowe power and lossy | sensors, actuators as well as routers and Low power and lossy network | |||
| network Border Router (LBR). A field device is most of the time a | Border Router (including LBR). A field device is most of the time | |||
| constrained device with limited CPU, memory footprint, storage | (but not always) a constrained device with limited CPU, memory | |||
| capacity, bandwidth and sometimes power constrained (battery | footprint, storage capacity, bandwidth and sometimes power | |||
| operated). At the time of writing, for the sake of illustration, a | constrained (battery operated). At the time of writing, for the sake | |||
| typicaly sensor or actuator would have a few KBytes of RAM, a few | of illustration, a typicaly sensor or actuator would have a few | |||
| dozens of KBytes of ROM/Flash memory, a 8/16/32 bit microcontroller | KBytes of RAM, a few dozens of KBytes of ROM/Flash memory, a 8/16/32 | |||
| and communication capabilities ranging from a few Kbits/s to a few | bit microcontroller and communication capabilities ranging from a few | |||
| hundreds of KBits/s. With the dramatic imrpovments of hardware and | Kbits/s to a few hundreds of KBits/s. Altough it is expected to see | |||
| software technologies it is expected to see continous improvments but | comtinuous improvements of hardware and software technologies, such | |||
| such devices will likely continue to be seen as constrained devices | devices will likely continue to be seen as constrained devices | |||
| compared to computers and routers used in the Internet. | compared to computers and routers used in the Internet. | |||
| Flash memory: non-volatile memory that can be re-programmed. | Flash memory: non-volatile memory that can be re-programmed. | |||
| FMS: Facility Management System. A global term applied across all | FMS: Facility Management System. A global term applied across all | |||
| the vertical designations within a building including, HVAC, Fire, | the vertical designations within a building including, Heating, | |||
| Ventilating, and Air Conditioning also referred to as HVAC, Fire, | ||||
| Security, Lighting and Elevator control. | Security, Lighting and Elevator control. | |||
| HART: "Highway Addressable Remote Transducer", a group of | HART: "Highway Addressable Remote Transducer", a group of | |||
| specifications for industrial process and control devices | specifications for industrial process and control devices | |||
| administered by the HART Foundation (see [HART]). The latest version | administered by the HART Foundation (see [HART]). The latest version | |||
| for the specifications is HART7 which includes the additions for | for the specifications is HART7 which includes the additions for | |||
| WirelessHART. | WirelessHART. | |||
| HVAC: Heating, Ventilation and Air Conditioning. A term applied to | HVAC: Heating, Ventilation and Air Conditioning. A term applied to | |||
| the comfort level of an internal space. | the comfort level of an internal space. | |||
| ISA: "International Society of Automation". ISA is an ANSI | ISA: "International Society of Automation". ISA is an ANSI | |||
| accredited standards-making society. ISA100 is an ISA committee | accredited standards-making society. ISA100 is an ISA committee | |||
| whose charter includes defining a family of standards for industrial | whose charter includes defining a family of standards for industrial | |||
| automation. [ISA100.11a] is a working group within ISA100 that is | automation. [ISA100.11a] is a working group within ISA100 that is | |||
| working on a standard for monitoring and non-critical process control | working on a standard for monitoring and non-critical process control | |||
| applications. | applications. | |||
| LAN: Local Area Network. | LAN: Local Area Network. | |||
| LBR: Low power and loosy network Border Router. The LBR is a device | LBR: Low power and lossy network Border Router. The LBR is a device | |||
| that connects the low power and lossy network to another routing | that connects the low power and lossy network to another routing | |||
| domain such as a Local Area Network (LAN), Wide Area Network (WAN) or | domain such as a Local Area Network (LAN), Wide Area Network (WAN) or | |||
| the Internet where a possibly different routing protocol is in | the Internet where a possibly different routing protocol is in | |||
| operation. The LBR acts as a routing device and may possibly host | operation. The LBR acts as a routing device and may possibly host | |||
| other functions such as data collector or aggregator, which is fairly | other functions such as data collector or aggregator. | |||
| typical in LLN. | ||||
| LLN: Low power and Lossy networks (LLNs) are typically composed of | LLN: Low power and Lossy networks (LLNs) are typically composed of | |||
| many embedded devices with limited power, memory, and processing | many embedded devices with limited power, memory, and processing | |||
| resources interconnected by a variety of links, such as IEEE | resources interconnected by a variety of links, such as IEEE | |||
| 802.15.4, Low Power WiFi. There is a wide scope of application areas | 802.15.4, Low Power WiFi. There is a wide scope of application areas | |||
| for LLNs, including industrial monitoring, building automation (HVAC, | for LLNs, including industrial monitoring, building automation (HVAC, | |||
| lighting, access control, fire), connected home, healthcare, | lighting, access control, fire), connected home, healthcare, | |||
| environmental monitoring, urban sensor networks, energy management, | environmental monitoring, urban sensor networks, energy management, | |||
| assets tracking, refrigeration.. | assets tracking and refrigeration.. | |||
| Open Loop Control: A process whereby a plant operator manually | Open Loop Control: A process whereby a plant operator manually | |||
| manipulates an actuator over the network where the decision is | manipulates an actuator over the network where the decision is | |||
| influenced by information sensed by field devices. | influenced by information sensed by field devices. | |||
| RAM: Random Access Memory. The RAM is a volatile memory. | RAM: Random Access Memory. The RAM is a volatile memory. | |||
| ROM: Read Only Memory. | ROM: Read Only Memory. | |||
| ROLL: Routing Over Low power and Lossy networks. | ROLL: Routing Over Low power and Lossy networks. | |||
| Schedule: An agreed execution, wake-up, transmission, reception, | Schedule: An agreed execution, wake-up, transmission, reception, | |||
| etc., time-table between two or more field devices. | etc., time-table between two or more field devices. | |||
| Sensor: device that measures a physical quantity and convert it to a | Sensor: device that measures a physical quantity and converts it to a | |||
| analog or digital signal that can be read by a program or a user. | analog or digital signal that can be read by a program or a user. | |||
| Sensed data can be of many types: electromagnetic (current, voltage, | Sensed data can be of many types: electromagnetic (current, voltage, | |||
| power, resistance) , mechanical (pressure, flow, liquid density, | power, resistance) , mechanical (pressure, flow, liquid density, | |||
| humidity, ...), chemical (oxygen, carbon monoxide, ...), acoustic | humidity, ...), chemical (oxygen, carbon monoxide, ...), acoustic | |||
| (noise, ultrasound), ... | (noise, ultrasound), ... | |||
| Smart Grid: a broad class of applications to network and automate | Smart Grid: a broad class of applications to network and automate | |||
| utility infrastructure. | utility infrastructure. | |||
| Timeslot: A fixed time interval that may be used for the transmission | Timeslot: A fixed time interval that may be used for the transmission | |||
| or reception of a packet between two field devices. A timeslot used | or reception of a packet between two field devices. A timeslot used | |||
| for communications is associated with a slotted-link | for communications is associated with a slotted-link | |||
| Upstream: Data direction traveling from the LLN via the LBR to | ||||
| Uptream: Data direction traveling from the LLN via the LBR to outside | outside of the LLN (LAN, WAN, Internet). | |||
| of the LLN (LAN, WAN, Internet). | ||||
| WAN: Wide Area Network. | WAN: Wide Area Network. | |||
| 3. IANA Considerations | 3. IANA Considerations | |||
| This document includes no request for IANA action. | This document includes no request for IANA action. | |||
| 4. Security Considerations | 4. Security Considerations | |||
| Since this document specifies terminology and does not specify new | Since this document specifies terminology and does not specify new | |||
| procedure or protocols, there are no security issues associated with | procedure or protocols, there are no security issues associated with | |||
| it. | it. | |||
| 5. Acknowledgements | 5. Acknowledgements | |||
| The authors would like to thank ... | The authors would like to thank Christian Jacquenet, Tim Winter and | |||
| Pieter De Mil for their valuable feed-back. | ||||
| 6. References | 6. References | |||
| 6.1. Normative References | 6.1. Normative References | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
| 6.2. Informative References | 6.2. Informative References | |||
| [I-D.ietf-roll-home-routing-reqs] | [I-D.ietf-roll-home-routing-reqs] | |||
| Brandt, A. and G. Porcu, "Home Automation Routing | Brandt, A., Buron, J., and G. Porcu, "Home Automation | |||
| Requirement in Low Power and Lossy Networks", | Routing Requirement in Low Power and Lossy Networks", | |||
| draft-ietf-roll-home-routing-reqs-02 (work in progress), | draft-ietf-roll-home-routing-reqs-03 (work in progress), | |||
| July 2008. | September 2008. | |||
| [I-D.ietf-roll-indus-routing-reqs] | [I-D.ietf-roll-indus-routing-reqs] | |||
| Networks, D., Thubert, P., Dwars, S., and T. Phinney, | Networks, D., Thubert, P., Dwars, S., and T. Phinney, | |||
| "Industrial Routing Requirements in Low Power and Lossy | "Industrial Routing Requirements in Low Power and Lossy | |||
| Networks", draft-ietf-roll-indus-routing-reqs-01 (work in | Networks", draft-ietf-roll-indus-routing-reqs-01 (work in | |||
| progress), July 2008. | progress), July 2008. | |||
| [I-D.ietf-roll-urban-routing-reqs] | [I-D.ietf-roll-urban-routing-reqs] | |||
| Dohler, M., Watteyne, T., Winter, T., Jacquenet, C., | Dohler, M., Watteyne, T., Winter, T., Jacquenet, C., | |||
| Madhusudan, G., Chegaray, G., and D. Barthel, "Urban WSNs | Madhusudan, G., Chegaray, G., and D. Barthel, "Urban WSNs | |||
| End of changes. 21 change blocks. | ||||
| 48 lines changed or deleted | 45 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||