draft-ietf-roll-terminology-05.txt   draft-ietf-roll-terminology-06.txt 
Networking Working Group JP. Vasseur Networking Working Group JP. Vasseur
Internet-Draft Cisco Systems, Inc Internet-Draft Cisco Systems, Inc
Intended status: Informational March 14, 2011 Intended status: Informational September 14, 2011
Expires: September 15, 2011 Expires: March 17, 2012
Terminology in Low power And Lossy Networks Terminology in Low power And Lossy Networks
draft-ietf-roll-terminology-05.txt draft-ietf-roll-terminology-06.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 44 skipping to change at page 1, line 44
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 September 15, 2011. This Internet-Draft will expire on March 17, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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 . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . 7
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 26 skipping to change at page 3, line 26
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. The terms defined in this document are used Working Group documents. The terms defined in this document are used
in [RFC5548],[I-D.ietf-roll-indus-routing-reqs], in [RFC5548],[RFC5673], [RFC5826] and[RFC5867].
[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 Terminology specific to a particular application are out of the scope
of this document. 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
skipping to change at page 7, line 20 skipping to change at page 7, line 19
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-09
(work in progress), January 2010.
[I-D.ietf-roll-home-routing-reqs]
Brandt, A. and J. Buron, "Home Automation Routing
Requirements in Low Power and Lossy Networks",
draft-ietf-roll-home-routing-reqs-11 (work in progress),
January 2010.
[I-D.ietf-roll-indus-routing-reqs]
Networks, D., Thubert, P., Dwars, S., and T. Phinney,
"Industrial Routing Requirements in Low Power and Lossy
Networks", draft-ietf-roll-indus-routing-reqs-06 (work in
progress), June 2009.
[RFC4461] Yasukawa, S., "Signaling Requirements for Point-to- [RFC4461] Yasukawa, S., "Signaling Requirements for Point-to-
Multipoint Traffic-Engineered MPLS Label Switched Paths Multipoint Traffic-Engineered MPLS Label Switched Paths
(LSPs)", RFC 4461, April 2006. (LSPs)", RFC 4461, April 2006.
[RFC4875] Aggarwal, R., Papadimitriou, D., and S. Yasukawa, [RFC4875] Aggarwal, R., Papadimitriou, D., and S. Yasukawa,
"Extensions to Resource Reservation Protocol - Traffic "Extensions to Resource Reservation Protocol - Traffic
Engineering (RSVP-TE) for Point-to-Multipoint TE Label Engineering (RSVP-TE) for Point-to-Multipoint TE Label
Switched Paths (LSPs)", RFC 4875, May 2007. Switched Paths (LSPs)", RFC 4875, May 2007.
[RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel, [RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel,
"Routing Requirements for Urban Low-Power and Lossy "Routing Requirements for Urban Low-Power and Lossy
Networks", RFC 5548, May 2009. Networks", RFC 5548, May 2009.
[RFC5673] Pister, K., Thubert, P., 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., De Mil, P., Riou, N., and W. Vermeylen,
"Building Automation Routing Requirements in Low-Power and
Lossy Networks", RFC 5867, June 2010.
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. 7 change blocks. 
26 lines changed or deleted 18 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/