draft-ietf-roll-terminology-08.txt   draft-ietf-roll-terminology-09.txt 
Networking Working Group JP. Vasseur Networking Working Group JP. Vasseur
Internet-Draft Cisco Systems, Inc Internet-Draft Cisco Systems, Inc
Intended status: Informational December 12, 2012 Intended status: Informational January 17, 2013
Expires: June 15, 2013 Expires: July 21, 2013
Terminology in Low power And Lossy Networks Terminology in Low power And Lossy Networks
draft-ietf-roll-terminology-08.txt draft-ietf-roll-terminology-09.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 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 June 15, 2013. This Internet-Draft will expire on July 21, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 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 . . . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . . . . . . . . . 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 6, line 20 skipping to change at page 6, line 20
towards other nodes contained in the DAG. 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.
RPL Domain: A RPL routing domain is a collection 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, or inter-domain, links.
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), ...
skipping to change at page 7, line 8 skipping to change at page 7, line 13
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, it raises no new security issue. procedure or protocols, it raises no new security issue.
5. Acknowledgements 5. Acknowledgements
The authors would like to thank Christian Jacquenet, Tim Winter, The authors would like to thank Christian Jacquenet, Tim Winter,
Pieter De Mil, David Meyer and Abdussalam Baryun for their valuable Pieter De Mil, David Meyer, Mukul Goyal and Abdussalam Baryun for
feed-back. 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
 End of changes. 9 change blocks. 
9 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/