draft-ietf-roll-terminology-09.txt | draft-ietf-roll-terminology-10.txt | |||
---|---|---|---|---|
Networking Working Group JP. Vasseur | Networking Working Group JP. Vasseur | |||
Internet-Draft Cisco Systems, Inc | Internet-Draft Cisco Systems, Inc | |||
Intended status: Informational January 17, 2013 | Intended status: Informational January 31, 2013 | |||
Expires: July 21, 2013 | Expires: August 4, 2013 | |||
Terminology in Low power And Lossy Networks | Terminology in Low power And Lossy Networks | |||
draft-ietf-roll-terminology-09.txt | draft-ietf-roll-terminology-10.txt | |||
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 (e.g. Heating, Ventilating, Air Conditioning, lighting, | automation (e.g. Heating, Ventilating, Air Conditioning, lighting, | |||
skipping to change at page 1, line 45 | skipping to change at page 1, line 45 | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
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." | |||
This Internet-Draft will expire on July 21, 2013. | This Internet-Draft will expire on August 4, 2013. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2013 IETF Trust and the persons identified as the | Copyright (c) 2013 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
described in the Simplified BSD License. | described in the Simplified BSD License. | |||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 | 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 | |||
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 | 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 | |||
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 | 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 | 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
6.1. Normative References . . . . . . . . . . . . . . . . . . . 7 | 6.1. Normative References . . . . . . . . . . . . . . . . . . . 7 | |||
6.2. Informative References . . . . . . . . . . . . . . . . . . 7 | 6.2. Informative References . . . . . . . . . . . . . . . . . . 7 | |||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 | Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
1. Introduction | 1. Introduction | |||
This document defines a terminology for discussing routing | This document defines a terminology for discussing routing | |||
skipping to change at page 5, line 42 | skipping to change at page 5, line 42 | |||
environmental monitoring, urban sensor networks, energy management, | environmental monitoring, urban sensor networks, energy management, | |||
assets tracking and refrigeration.. | assets tracking and refrigeration.. | |||
MP2P: Multipoint-to-Point is used to describe a particular traffic | MP2P: Multipoint-to-Point is used to describe a particular traffic | |||
pattern (e.g. MP2P flows collecting information from many nodes | pattern (e.g. MP2P flows collecting information from many nodes | |||
flowing inwards towards a collecting sink or an LBR). | flowing inwards towards a collecting sink or an LBR). | |||
MAC: Medium Access Control. Refers to algorithms and procedures used | MAC: Medium Access Control. Refers to algorithms and procedures used | |||
by the data link layer to coordinate use of the physical layer. | by the data link layer to coordinate use of the physical layer. | |||
Non-sleepy Node: A non-sleepy node is a node that always remains in a | ||||
fully powered on state (i.e. always awake) where it has the | ||||
capability to perform RPL protocol communication. | ||||
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. | |||
PER: Packet Error Rate. A ratio of the number of unusable packets | PER: Packet Error Rate. A ratio of the number of unusable packets | |||
(not received at all, or received in error- even after any applicable | (not received at all, or received in error- even after any applicable | |||
error correction has been applied) to the total number of packets | error correction has been applied) to the total number of packets | |||
that would have been been received in the absence of errors. | that would have been been received in the absence of errors. | |||
P2P: Point To Point. This refers to traffic exchanged between two | P2P: Point To Point. This refers to traffic exchanged between two | |||
skipping to change at page 6, line 35 | skipping to change at page 6, line 39 | |||
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: A sensor is a device that measures a physical quantity and | Sensor: A sensor is a device that measures a physical quantity and | |||
converts it to a analog or digital signal that can be read by a | converts it to a analog or digital signal that can be read by a | |||
program or a user. Sensed data can be of many types: electromagnetic | program or a user. Sensed data can be of many types: electromagnetic | |||
(e.g. current, voltage, power, resistance, ...) , mechanical (e.g. | (e.g. current, voltage, power, resistance, ...) , mechanical (e.g. | |||
pressure, flow, liquid density, humidity, ...), chemical (e.g. | pressure, flow, liquid density, humidity, ...), chemical (e.g. | |||
oxygen, carbon monoxide, ...), acoustic (e.g. noise, ultrasound), ... | oxygen, carbon monoxide, ...), acoustic (e.g. noise, ultrasound), ... | |||
Sleepy Node: A sleepy node is a node that may sometimes go into a | ||||
sleep mode (i.e. go into a low power state to conserve power) and | ||||
temporarily suspend protocol communication. A sleepy node may also | ||||
sometimes remain in a fully powered on state where it has the | ||||
capability to perform RPL protocol communication. | ||||
Smart Grid: A Smart Grid is a broad class of applications to network | Smart Grid: A Smart Grid is a broad class of applications to network | |||
and automate utility infrastructure. | and automate utility infrastructure. | |||
Timeslot: A Timeslot is a fixed time interval that may be used for | Timeslot: A Timeslot is a fixed time interval that may be used for | |||
the transmission or reception of a packet between two field devices. | the transmission or reception of a packet between two field devices. | |||
A timeslot used for communications is associated with a slotted-link | A timeslot used for communications is associated with a slotted-link | |||
Upstream: Data direction traveling from the LLN via the LBR to | Upstream: Data direction traveling from the LLN via the LBR to | |||
outside of the LLN (LAN, WAN, Internet). | outside 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 | |||
End of changes. 7 change blocks. | ||||
6 lines changed or deleted | 15 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |