< draft-ietf-isis-mrt-01.txt		draft-ietf-isis-mrt-02.txt >
	Network Working Group Z. Li		Network Working Group Z. Li
	Internet-Draft N. Wu		Internet-Draft N. Wu
	Intended status: Standards Track Q. Zhao		Intended status: Standards Track Q. Zhao
	Expires: April 21, 2016 Huawei Technologies		Expires: November 19, 2016 Huawei Technologies
	A. Atlas		A. Atlas
	C. Bowers		C. Bowers
	Juniper Networks		Juniper Networks
	J. Tantsura		J. Tantsura
	Ericsson		Individual
	October 19, 2015		May 18, 2016
	Intermediate System to Intermediate System (IS-IS) Extensions for		Intermediate System to Intermediate System (IS-IS) Extensions for
	Maximally Redundant Trees (MRT)		Maximally Redundant Trees (MRT)
	draft-ietf-isis-mrt-01		draft-ietf-isis-mrt-02
	Abstract		Abstract
	This document describes extensions to IS-IS to support the		This document describes extensions to IS-IS to support the
	distributed computation of Maximally Redundant Trees (MRT). Example		distributed computation of Maximally Redundant Trees (MRT). Example
	uses of MRT include IP/LDP Fast-Reroute and global protection or		uses of MRT include IP/LDP Fast-Reroute and global protection or
	live-live for multicast traffic. The extensions indicate what MRT		live-live for multicast traffic. The extensions indicate what MRT
	profile(s) each router supports. Different MRT profiles can be		profile(s) each router supports. Different MRT profiles can be
	defined to support different uses and to allow transition of		defined to support different uses and to allow transition of
	capabilities. An extension is introduced to flood MRT-Ineligible		capabilities. An extension is introduced to flood MRT-Ineligible
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	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 April 21, 2016.		This Internet-Draft will expire on November 19, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2016 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 8, line 12 ¶		skipping to change at page 8, line 12 ¶
	NOT be used in the MRT calculation for the default topology for all		NOT be used in the MRT calculation for the default topology for all
	profiles.		profiles.
	5.3. A Note on Multi-Topology Routing		5.3. A Note on Multi-Topology Routing
	[RFC5120] specifies how to support multi-topology routing in IS-IS.		[RFC5120] specifies how to support multi-topology routing in IS-IS.
	The current document specifies how to signal support for MRT in the		The current document specifies how to signal support for MRT in the
	default routing topology only. The format of the extensions in this		default routing topology only. The format of the extensions in this
	document allows the MRT Profile sub-TLV and the MRT-Ineligible Link		document allows the MRT Profile sub-TLV and the MRT-Ineligible Link
	sub-TLV to be scoped to topologies with non-zero MT-ID at some point		sub-TLV to be scoped to topologies with non-zero MT-ID at some point
	in future. However, this document restricts these extensions to		in the future. However, this document restricts these extensions to
	apply only to the default topology. The MRT Profile sub-TLV is		apply only to the default topology. The MRT Profile sub-TLV is
	restricting by explicitly requiring the MT-ID field to be set to		restricted by explicitly requiring the MT-ID field to be set to zero.
	zero. The MRT-Ineligible Link sub-TLV is restricted by only allowing		The MRT-Ineligible Link sub-TLV is restricted by only allowing it to
	it to be included in the Extended IS Reachability TLV (TLV#22) which		be included in the Extended IS Reachability TLV (TLV#22) which is
	is scoped to the default topology, and not allowing it to appear		scoped to the default topology, and not allowing it to appear TLV#222
	TLV#222 (the topology-scoped version of the Extended IS Reachability		(the topology-scoped version of the Extended IS Reachability TLV).
	TLV).
	Lifting these restrictions is for further study. Note that the MRT		Lifting these restrictions is for further study. Note that the MRT
	signalling extensions in this document can co-exist with IS-IS multi-		signalling extensions in this document can co-exist with IS-IS multi-
	topology routing, with the limitation that MRT Red and Blue		topology routing, with the limitation that MRT Red and Blue
	forwarding trees can only be built for the default topology.		forwarding trees can only be built for the default topology.
	The format of the Controlled Convergence sub-TLV (discussed below)		The format of the Controlled Convergence sub-TLV (discussed below)
	also contains an MT-ID field, allowing a Controlled Convergence sub-		also contains an MT-ID field, allowing a Controlled Convergence sub-
	TLV to be scoped to a particular topology. This document does not		TLV to be scoped to a particular topology. This document does not
	place restrictions on the MT-ID field in the Controlled Convergence		place restrictions on the MT-ID field in the Controlled Convergence
	skipping to change at page 14, line 27 ¶		skipping to change at page 14, line 27 ¶
	Chris Bowers		Chris Bowers
	Juniper Networks		Juniper Networks
	1194 N. Mathilda Ave.		1194 N. Mathilda Ave.
	Sunnyvale, CA 94089		Sunnyvale, CA 94089
	USA		USA
	Email: cbowers@juniper.net		Email: cbowers@juniper.net
	Jeff Tantsura		Jeff Tantsura
	Ericsson		Individual
	300 Holger Way
	San Jose, CA 95134
	USA		USA
	Email: jeff.tantsura@ericsson.com		Email: jefftant.ietf@gmail.com
End of changes. 9 change blocks.
	16 lines changed or deleted		13 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/