< draft-ietf-mpls-forwarding-07.txt		draft-ietf-mpls-forwarding-08.txt >
	skipping to change at page 1, line 16 ¶		skipping to change at page 1, line 16 ¶
	Expires: August 16, 2014 Juniper Networks		Expires: August 16, 2014 Juniper Networks
	S. Amante		S. Amante
	Apple Inc.		Apple Inc.
	A. Malis		A. Malis
	Huawei		Huawei
	C. Pignataro		C. Pignataro
	Cisco		Cisco
	February 12, 2014		February 12, 2014
	MPLS Forwarding Compliance and Performance Requirements		MPLS Forwarding Compliance and Performance Requirements
	draft-ietf-mpls-forwarding-07		draft-ietf-mpls-forwarding-08
	Abstract		Abstract
	This document provides guidelines for implementers regarding MPLS		This document provides guidelines for implementers regarding MPLS
	forwarding and a basis for evaluations of forwarding implementations.		forwarding and a basis for evaluations of forwarding implementations.
	Guidelines cover many aspects of MPLS forwarding. Topics are		Guidelines cover many aspects of MPLS forwarding. Topics are
	highlighted where implementers might otherwise overlook practical		highlighted where implementers might otherwise overlook practical
	requirements which are unstated or under emphasized or are optional		requirements which are unstated or under emphasized or are optional
	for conformance to RFCs but are often considered mandatory by		for conformance to RFCs but are often considered mandatory by
	providers.		providers.
	skipping to change at page 12, line 26 ¶		skipping to change at page 12, line 26 ¶
	the labels to a general purpose CPU or other highly programmable		the labels to a general purpose CPU or other highly programmable
	hardware. For example, ELI will only be sent to LSR which have		hardware. For example, ELI will only be sent to LSR which have
	signaled support for [RFC6790] and high OAM packet rate must be		signaled support for [RFC6790] and high OAM packet rate must be
	negotiated among endpoints.		negotiated among endpoints.
	[RFC3429] reserves a label for ITU-T Y.1711, however Y.1711 does not		[RFC3429] reserves a label for ITU-T Y.1711, however Y.1711 does not
	work with multipath and its use is strongly discouraged.		work with multipath and its use is strongly discouraged.
	The current list of special purpose labels can be found on the		The current list of special purpose labels can be found on the
	"Multiprotocol Label Switching Architecture (MPLS) Label Values"		"Multiprotocol Label Switching Architecture (MPLS) Label Values"
	registry reachable at IANA's pages at [1].		registry reachable at IANA's pages at http://www.iana.org.
	[I-D.ietf-mpls-special-purpose-labels] introduces an IANA "Extended		[I-D.ietf-mpls-special-purpose-labels] introduces an IANA "Extended
	Special Purpose MPLS Label Values" registry and makes use of the		Special Purpose MPLS Label Values" registry and makes use of the
	"extension" label, label 15, to indicate that the next label is an		"extension" label, label 15, to indicate that the next label is an
	extended special purpose label and requires special handling. The		extended special purpose label and requires special handling. The
	range of only 16 values for special purpose labels allows a table to		range of only 16 values for special purpose labels allows a table to
	be used. The range of extended special purpose labels with 20 bits		be used. The range of extended special purpose labels with 20 bits
	available for use may have to be handled in some other way in the		available for use may have to be handled in some other way in the
	unlikely event that in the future the range of currently reserved		unlikely event that in the future the range of currently reserved
	values 256-1048575 are used. If only the standards action range,		values 256-1048575 are used. If only the standards action range,
End of changes. 2 change blocks.
	2 lines changed or deleted		2 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/