draft-ietf-roll-terminology-01.txt   draft-ietf-roll-terminology-02.txt 
Networking Working Group JP. Vasseur Networking Working Group JP. Vasseur
Internet-Draft Cisco Systems, Inc Internet-Draft Cisco Systems, Inc
Intended status: Informational May 7, 2009 Intended status: Informational October 8, 2009
Expires: November 8, 2009 Expires: April 11, 2010
Terminology in Low power And Lossy Networks Terminology in Low power And Lossy Networks
draft-ietf-roll-terminology-01.txt draft-ietf-roll-terminology-02.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
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 November 8, 2009. This Internet-Draft will expire on April 11, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 24 skipping to change at page 2, line 24
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
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 6.1. Normative References . . . . . . . . . . . . . . . . . . . 7
6.2. Informative References . . . . . . . . . . . . . . . . . . 7 6.2. Informative References . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
This document 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
skipping to change at page 3, line 25 skipping to change at page 3, line 25
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 tracking monitoring, urban sensor networks, energy management, assets tracking
and refrigeration. and refrigeration.
Since these applications are usually highly specific (for example Since these applications are usually highly specific (for example
Industrial Automation, Building Automation, ...), it is not uncommon Industrial Automation, Building Automation, ...), it is not uncommon
to see a number of disparate terms to describe the same device or to see a number of disparate terms to describe the same device or
functionality. Thus in order to avoid confusion or discrepancies, functionality. Thus in order to avoid confusion or discrepancies,
this document specifies the common terminology to be used in all ROLL this document specifies the common terminology to be used in all ROLL
Working Group documents. Terminology specific to a particular Working Group documents. The terms defined in this document are used
application are out of the scope of this document. in [RFC5548],[I-D.ietf-roll-indus-routing-reqs],
[I-D.ietf-roll-home-routing-reqs] and
[I-D.ietf-roll-building-routing-reqs].
Terminology specific to a 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. This document should common terminology specified in this document. This document should
be listed as an informative reference. be listed as an informative reference.
2. Terminology 2. Terminology
Actuator: a field device that controls a set of equipment. For Actuator: a field device that controls a set of equipment. For
example, an actuator might control and/or modulates the flow of a gas example, an actuator might control and/or modulates the flow of a gas
skipping to change at page 5, line 31 skipping to change at page 5, line 36
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 802.15.4 resources interconnected by a variety of links, such as IEEE 802.15.4
or Low Power WiFi. There is a wide scope of application areas for or Low Power WiFi. There is a wide scope of application areas for
LLNs, including industrial monitoring, building automation (HVAC, 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 and refrigeration.. assets tracking and refrigeration..
MP2P: Multipoint-to-Point is used to describe a particular traffic
pattern (e.g. MP2P flows collecting information from many nodes
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.
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
nodes (regardless of the number of hops between the two nodes).
P2MP: Point-to-Multipoint traffic 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 common RPL
use case involves P2MP flows from or through a DAG root outward
towards other nodes contained in the DAG.
RAM: Random Access Memory. The RAM is a volatile memory. RAM: Random Access Memory. The RAM is a volatile memory.
RFID: Radio Frequency IDentification. RFID: Radio Frequency IDentification.
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.
skipping to change at page 7, line 7 skipping to change at page 7, line 20
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-building-routing-reqs]
Martocci, J., Riou, N., Mil, P., and W. Vermeylen,
"Building Automation Routing Requirements in Low Power and
Lossy Networks", draft-ietf-roll-building-routing-reqs-07
(work in progress), September 2009.
[I-D.ietf-roll-home-routing-reqs] [I-D.ietf-roll-home-routing-reqs]
Porcu, G., "Home Automation Routing Requirements in Low Brandt, A., Buron, J., and G. Porcu, "Home Automation
Power and Lossy Networks", Routing Requirements in Low Power and Lossy Networks",
draft-ietf-roll-home-routing-reqs-06 (work in progress), draft-ietf-roll-home-routing-reqs-08 (work in progress),
November 2008. September 2009.
[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-05 (work in Networks", draft-ietf-roll-indus-routing-reqs-06 (work in
progress), April 2009. progress), June 2009.
[I-D.ietf-roll-urban-routing-reqs] [RFC4461] Yasukawa, S., "Signaling Requirements for Point-to-
Dohler, M., Watteyne, T., Winter, T., Barthel, D., Multipoint Traffic-Engineered MPLS Label Switched Paths
Jacquenet, C., Madhusudan, G., and G. Chegaray, "Urban (LSPs)", RFC 4461, April 2006.
WSNs Routing Requirements in Low Power and Lossy
Networks", draft-ietf-roll-urban-routing-reqs-05 (work in
progress), March 2009.
[I-D.martocci-roll-building-routing-reqs] [RFC4875] Aggarwal, R., Papadimitriou, D., and S. Yasukawa,
Martocci, J., Riou, N., Mil, P., and W. Vermeylen, "Extensions to Resource Reservation Protocol - Traffic
"Building Automation Routing Requirements in Low Power and Engineering (RSVP-TE) for Point-to-Multipoint TE Label
Lossy Networks", Switched Paths (LSPs)", RFC 4875, May 2007.
draft-martocci-roll-building-routing-reqs-01 (work in
progress), October 2008. [RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel,
"Routing Requirements for Urban Low-Power and Lossy
Networks", RFC 5548, May 2009.
Author's Address Author's Address
JP Vasseur JP Vasseur
Cisco Systems, Inc Cisco Systems, Inc
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Email: jpv@cisco.com Email: jpv@cisco.com
 End of changes. 13 change blocks. 
28 lines changed or deleted 51 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/