draft-ietf-mpls-rmr-03.txt		draft-ietf-mpls-rmr-04.txt
	MPLS WG K. Kompella		MPLS WG K. Kompella
	Internet-Draft Juniper Networks, Inc.		Internet-Draft Juniper Networks, Inc.
	Intended status: Standards Track L. Contreras		Intended status: Standards Track L. Contreras
	Expires: May 3, 2017 Telefonica		Expires: September 12, 2017 Telefonica
	October 30, 2016		March 11, 2017
	Resilient MPLS Rings		Resilient MPLS Rings
	draft-ietf-mpls-rmr-03		draft-ietf-mpls-rmr-04
	Abstract		Abstract
	This document describes the use of the MPLS control and data planes		This document describes the use of the MPLS control and data planes
	on ring topologies. It describes the special nature of rings, and		on ring topologies. It describes the special nature of rings, and
	proceeds to show how MPLS can be effectively used in such topologies.		proceeds to show how MPLS can be effectively used in such topologies.
	It describes how MPLS rings are configured, auto-discovered and		It describes how MPLS rings are configured, auto-discovered and
	signaled, as well as how the data plane works. Companion documents		signaled, as well as how the data plane works. Companion documents
	describe the details of discovery and signaling for specific		describe the details of discovery and signaling for specific
	protocols.		protocols.
	skipping to change at page 1, line 43 ¶		skipping to change at page 1, line 43 ¶
	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 May 3, 2017.		This Internet-Draft will expire on September 12, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2017 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
	skipping to change at page 7, line 38 ¶		skipping to change at page 7, line 38 ¶
	and AL_jk to R_j+1. R_j also receives two labels: CL_j+1,k from		and AL_jk to R_j+1. R_j also receives two labels: CL_j+1,k from
	R_j+1, and AL_j-1,k from R_j-1. R_j can now set up the forwarding		R_j+1, and AL_j-1,k from R_j-1. R_j can now set up the forwarding
	entries for RL_k. In the CW direction, R_j swaps incoming label		entries for RL_k. In the CW direction, R_j swaps incoming label
	CL_jk with CL_j+1,k with next hop R_j+1; these allow R_j to act as		CL_jk with CL_j+1,k with next hop R_j+1; these allow R_j to act as
	LSR for RL_k. R_j also installs an LFIB entry to push CL_j+1,k with		LSR for RL_k. R_j also installs an LFIB entry to push CL_j+1,k with
	next hop R_j+1 to act as ingress for RL_k. Similarly, in the AC		next hop R_j+1 to act as ingress for RL_k. Similarly, in the AC
	direction, R_j swaps incoming label AL_jk with AL_j-1,k with next hop		direction, R_j swaps incoming label AL_jk with AL_j-1,k with next hop
	R_j-1 (as LSR), and an entry to push AL_j-1,k with next hop R_j-1 (as		R_j-1 (as LSR), and an entry to push AL_j-1,k with next hop R_j-1 (as
	ingress).		ingress).
	Clearly, R_k does not act as ingress for its own LSPs. However, if		Clearly, R_k does not act as ingress for its own LSPs. However, R_k
	these LSPs use UHP, then R_k installs LFIB entries to pop CL_k,k for		can send OAM messages, for example, an MPLS ping or traceroute
	packets received from R_k-1 and to pop AL_k,k for packets received		([I-D.ietf-mpls-rfc4379bis]), using labels CL_k,k+1 and AL_k-1,k, to
	from R_k+1.		test the entire ring LSP anchored at R_k in both directions.
			Furthermore, if these LSPs use UHP, then R_k installs LFIB entries to
			pop CL_k,k for packets received from R_k-1 and to pop AL_k,k for
			packets received from R_k+1.
	3.6. Installing FRR LFIB Entries		3.6. Installing FRR LFIB Entries
	At the same time that R_j sets up its primary CW and AC LFIB entries,		At the same time that R_j sets up its primary CW and AC LFIB entries,
	it can also set up the protection forwarding entries for RL_k. In		it can also set up the protection forwarding entries for RL_k. In
	the CW direction, R_j sets up an FRR LFIB entry to swap incoming		the CW direction, R_j sets up an FRR LFIB entry to swap incoming
	label CL_jk with AL_j-1,k with next hop R_j-1. In the AC direction,		label CL_jk with AL_j-1,k with next hop R_j-1. In the AC direction,
	R_j sets up an FRR LFIB entry to swap incoming label AL_jk with		R_j sets up an FRR LFIB entry to swap incoming label AL_jk with
	CL_j+1,k with next hop R_j+1. Again, R_k does not install FRR LFIB		CL_j+1,k with next hop R_j+1. Again, R_k does not install FRR LFIB
	entries in this manner.		entries in this manner.
	skipping to change at page 13, line 16 ¶		skipping to change at page 13, line 16 ¶
	10.1. Normative References		10.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,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
	10.2. Informative References		10.2. Informative References
			[I-D.ietf-mpls-rfc4379bis]
			Kompella, K., Swallow, G., Pignataro, C., Kumar, N.,
			Aldrin, S., and M. Chen, "Detecting Multi-Protocol Label
			Switched (MPLS) Data Plane Failures", draft-ietf-mpls-
			rfc4379bis-09 (work in progress), October 2016.
	[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,		[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
	and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP		and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
	Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,		Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
	<http://www.rfc-editor.org/info/rfc3209>.		<http://www.rfc-editor.org/info/rfc3209>.
	[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering		[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
	(TE) Extensions to OSPF Version 2", RFC 3630,		(TE) Extensions to OSPF Version 2", RFC 3630,
	DOI 10.17487/RFC3630, September 2003,		DOI 10.17487/RFC3630, September 2003,
	<http://www.rfc-editor.org/info/rfc3630>.		<http://www.rfc-editor.org/info/rfc3630>.
End of changes. 6 change blocks.
	9 lines changed or deleted		18 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/