< draft-ietf-roll-terminology-00.txt		draft-ietf-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 October 9, 2008		Intended status: Informational May 7, 2009
	Expires: April 12, 2009		Expires: November 8, 2009
	Terminology in Low power And Lossy Networks		Terminology in Low power And Lossy Networks
	draft-ietf-roll-terminology-00.txt		draft-ietf-roll-terminology-01.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		This Internet-Draft is submitted to IETF in full conformance with the
	applicable patent or other IPR claims of which he or she is aware		provisions of BCP 78 and BCP 79.
	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.
	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.
	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."
	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 April 12, 2009.		This Internet-Draft will expire on November 8, 2009.
			Copyright Notice
			Copyright (c) 2009 IETF Trust and the persons identified as the
			document authors. All rights reserved.
			This document is subject to BCP 78 and the IETF Trust's Legal
			Provisions Relating to IETF Documents in effect on the date of
			publication of this document (http://trustee.ietf.org/license-info).
			Please review these documents carefully, as they describe your rights
			and restrictions with respect to this document.
	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 2, line 20 ¶		skipping to change at page 2, line 27 ¶
	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 . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . 7
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
	Intellectual Property and Copyright Statements . . . . . . . . . . 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 30 ¶		skipping to change at page 3, line 30 ¶
	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. Terminology specific to a particular
	application are out of the scope of this document.		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. This document should
			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
	or liquid, control electricity distribution, perform a mechanical		or liquid, control electricity distribution, perform a mechanical
	operation, ...		operation, ...
	AMI: Advanced Metering Infrastructure that makes use of Smart Grid		AMI: Advanced Metering Infrastructure that makes use of Smart Grid
	technologies. A canonical Smart Grid application is smart-metering.		technologies. A canonical Smart Grid application is smart-metering.
	skipping to change at page 4, line 17 ¶		skipping to change at page 4, line 18 ¶
	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.
			Data sink: A device that collects data from nodes in a LLN.
	Downstream: Data direction traveling from outside of the LLN (e.g.		Downstream: Data direction traveling from outside of the LLN (e.g.
	traffic coming from a LAN, WAN or the Internet) via a LBR.		traffic coming from a LAN, WAN or the Internet) via a LBR.
	Field Device: A field deviced is a physical device placed in the		Field Device: A field deviced is a physical device placed in the
	network's operating environment (e.g. plant, urban or home). Field		network's operating environment (e.g. plant, urban or home). Field
	devices include sensors, actuators as well as routers and Low power		devices include sensors, actuators as well as routers and Low power
	and Lossy Network Border Router (including LBR). A field device is		and Lossy Network Border Router (including LBR). A field device is
	usually (but not always) a device with constrained CPU, memory		usually (but not always) a device with constrained CPU, memory
	footprint, storage capacity, bandwidth and sometimes power (battery		footprint, storage capacity, bandwidth and sometimes power (battery
	operated). At the time of writing, for the sake of illustration, a		operated). At the time of writing, for the sake of illustration, a
	skipping to change at page 5, line 28 ¶		skipping to change at page 5, line 31 ¶
	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..
			MAC: Medium Access Control. Refers to algorithms and procedures used
			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
			(not received at all, or received in error- even after any applicable
			error correction has been applied) to the total number of packets
			that would have been been received in the absence of errors.
	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 6, line 38 ¶		skipping to change at page 7, line 8 ¶
	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., Buron, J., and G. Porcu, "Home Automation		Porcu, G., "Home Automation Routing Requirements in Low
	Routing Requirement in Low Power and Lossy Networks",		Power and Lossy Networks",
	draft-ietf-roll-home-routing-reqs-03 (work in progress),		draft-ietf-roll-home-routing-reqs-06 (work in progress),
	September 2008.		November 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-05 (work in
	progress), July 2008.		progress), April 2009.
	[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., Barthel, D.,
	Madhusudan, G., Chegaray, G., and D. Barthel, "Urban WSNs		Jacquenet, C., Madhusudan, G., and G. Chegaray, "Urban
	Routing Requirements in Low Power and Lossy Networks",		WSNs Routing Requirements in Low Power and Lossy
	draft-ietf-roll-urban-routing-reqs-01 (work in progress),		Networks", draft-ietf-roll-urban-routing-reqs-05 (work in
	July 2008.		progress), March 2009.
	[I-D.martocci-roll-building-routing-reqs]		[I-D.martocci-roll-building-routing-reqs]
	Martocci, J., Riou, N., Mil, P., and W. Vermeylen,		Martocci, J., Riou, N., Mil, P., and W. Vermeylen,
	"Commercial Routing Requirements in Low Power and Lossy		"Building Automation Routing Requirements in Low Power and
	Networks", draft-martocci-roll-building-routing-reqs-00		Lossy Networks",
	(work in progress), September 2008.		draft-martocci-roll-building-routing-reqs-01 (work in
			progress), October 2008.
	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
	Full Copyright Statement
	Copyright (C) The IETF Trust (2008).
	This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.
	This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
	THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Intellectual Property
	The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.
	Copies of IPR disclosures made to the IETF Secretariat and any
	assurances of licenses to be made available, or the result of an
	attempt made to obtain a general license or permission for the use of
	such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.
End of changes. 15 change blocks.
	25 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/