< draft-ietf-rtgwg-cl-requirement-09.txt		draft-ietf-rtgwg-cl-requirement-10.txt >
	RTGWG C. Villamizar, Ed.		RTGWG C. Villamizar, Ed.
	Internet-Draft OCCNC, LLC		Internet-Draft OCCNC, LLC
	Intended status: Informational D. McDysan, Ed.		Intended status: Informational D. McDysan, Ed.
	Expires: August 9, 2013 Verizon		Expires: September 23, 2013 Verizon
	S. Ning		S. Ning
	Tata Communications		Tata Communications
	A. Malis		A. Malis
	Verizon		Verizon
	L. Yong		L. Yong
	Huawei USA		Huawei USA
	February 5, 2013		March 22, 2013
	Requirements for MPLS Over a Composite Link		Requirements for Composite Links in MPLS Networks
	draft-ietf-rtgwg-cl-requirement-09		draft-ietf-rtgwg-cl-requirement-10
	Abstract		Abstract
	There is often a need to provide large aggregates of bandwidth that		There is often a need to provide large aggregates of bandwidth that
	are best provided using parallel links between routers or MPLS LSR.		are best provided using parallel links between routers or MPLS LSR.
	In core networks there is often no alternative since the aggregate		In core networks there is often no alternative since the aggregate
	capacities of core networks today far exceed the capacity of a single		capacities of core networks today far exceed the capacity of a single
	physical link or single packet processing element.		physical link or single packet processing element.
	The presence of parallel links, with each link potentially comprised		The presence of parallel links, with each link potentially comprised
	of multiple layers has resulted in additional requirements. Certain		of multiple layers has resulted in additional requirements. Certain
	services may benefit from being restricted to a subset of the		services may benefit from being restricted to a subset of the
	component links or a specific component link, where component link		component links or a specific component link, where component link
	characteristics, such as latency, differ. Certain services require		characteristics, such as latency, differ. Certain services require
	that an LSP be treated as atomic and avoid reordering. Other		that an LSP be treated as atomic and avoid reordering. Other
	services will continue to require only that reordering not occur		services will continue to require only that reordering not occur
	within a microflow as is current practice.		within a microflow as is current practice.
	Current practice related to multipath is described briefly in an
	appendix.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted 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). 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 23, 2013.
	This Internet-Draft will expire on August 9, 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
End of changes. 5 change blocks.
	9 lines changed or deleted		5 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/