draft-ietf-roll-terminology-10.txt		draft-ietf-roll-terminology-11.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 31, 2013		Intended status: Informational February 16, 2013
	Expires: August 4, 2013		Expires: August 20, 2013
	Terminology in Low power And Lossy Networks		Terminology in Low power And Lossy Networks
	draft-ietf-roll-terminology-10.txt		draft-ietf-roll-terminology-11.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 August 4, 2013.		This Internet-Draft will expire on August 20, 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
	skipping to change at page 7, line 33		skipping to change at page 7, line 33
	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
			[HART] HART Communication Foundation (http://www.hartcomm.org)
	[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,
End of changes. 4 change blocks.
	4 lines changed or deleted		6 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/