< draft-shen-isis-spine-leaf-ext-00.txt		draft-shen-isis-spine-leaf-ext-01.txt >
	Networking Working Group N. Shen		Networking Working Group N. Shen
	Internet-Draft S. Thyamagundalu		Internet-Draft S. Thyamagundalu
	Intended status: Standards Track Cisco Systems		Intended status: Standards Track Cisco Systems
	Expires: May 5, 2016 November 2, 2015		Expires: October 27, 2016 April 25, 2016
	IS-IS Routing for Spine-Leaf Topology		IS-IS Routing for Spine-Leaf Topology
	draft-shen-isis-spine-leaf-ext-00		draft-shen-isis-spine-leaf-ext-01
	Abstract		Abstract
	This document describes a mechanism for routers and switches in		This document describes a mechanism for routers and switches in
	Spine-Leaf type topology to have non-reciprocal Intermediate System		Spine-Leaf type topology to have non-reciprocal Intermediate System
	to Intermediate System (IS-IS) routing relationships between the		to Intermediate System (IS-IS) routing relationships between the
	leafs and spines. The leaf nodes do not need to have the topology		leafs and spines. The leaf nodes do not need to have the topology
	information of other nodes and exact prefixes in the network. This		information of other nodes and exact prefixes in the network. This
	extension also has application in the Internet of Things (IoT).		extension also has application in the Internet of Things (IoT).
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	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 5, 2016.		This Internet-Draft will expire on October 27, 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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3		1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
	2. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Spine-Leaf (SL) Extension . . . . . . . . . . . . . . . . . . 3		3. Spine-Leaf (SL) Extension . . . . . . . . . . . . . . . . . . 4
	3.1. Topology Example . . . . . . . . . . . . . . . . . . . . 4		3.1. Topology Example . . . . . . . . . . . . . . . . . . . . 4
	3.2. Applicability Statement . . . . . . . . . . . . . . . . . 4		3.2. Applicability Statement . . . . . . . . . . . . . . . . . 4
	3.3. Extension Encoding . . . . . . . . . . . . . . . . . . . 5		3.3. Extension Encoding . . . . . . . . . . . . . . . . . . . 5
	3.4. Mechanism . . . . . . . . . . . . . . . . . . . . . . . . 6		3.4. Mechanism . . . . . . . . . . . . . . . . . . . . . . . . 6
	3.5. Implementation and Operation . . . . . . . . . . . . . . 7		3.5. Implementation and Operation . . . . . . . . . . . . . . 7
	3.5.1. CSNP PDU . . . . . . . . . . . . . . . . . . . . . . 7		3.5.1. CSNP PDU . . . . . . . . . . . . . . . . . . . . . . 7
	3.5.2. Leaf to Leaf connection . . . . . . . . . . . . . . . 8		3.5.2. Leaf to Leaf connection . . . . . . . . . . . . . . . 8
	3.5.3. Overload Bit . . . . . . . . . . . . . . . . . . . . 8		3.5.3. Overload Bit . . . . . . . . . . . . . . . . . . . . 8
	3.5.4. Spine Node Hostname . . . . . . . . . . . . . . . . . 8		3.5.4. Spine Node Hostname . . . . . . . . . . . . . . . . . 8
	3.5.5. Default Route Metric . . . . . . . . . . . . . . . . 8		3.5.5. Default Route Metric . . . . . . . . . . . . . . . . 8
	3.5.6. Other End-to-End Services . . . . . . . . . . . . . . 9		3.5.6. Other End-to-End Services . . . . . . . . . . . . . . 9
	3.5.7. Address Family and Topology . . . . . . . . . . . . . 9		3.5.7. Address Family and Topology . . . . . . . . . . . . . 9
	3.5.8. Migration . . . . . . . . . . . . . . . . . . . . . . 9		3.5.8. Migration . . . . . . . . . . . . . . . . . . . . . . 9
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 10		5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
	7. Document Change Log . . . . . . . . . . . . . . . . . . . . . 10		7. Document Change Log . . . . . . . . . . . . . . . . . . . . . 10
			7.1. Changes to draft-shen-isis-spine-leaf-ext-01.txt . . . . 10
			7.2. Changes to draft-shen-isis-spine-leaf-ext-00.txt . . . . 10
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
	8.1. Normative References . . . . . . . . . . . . . . . . . . 10		8.1. Normative References . . . . . . . . . . . . . . . . . . 11
	8.2. Informative References . . . . . . . . . . . . . . . . . 11		8.2. Informative References . . . . . . . . . . . . . . . . . 12
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
	1. Introduction		1. Introduction
	The IS-IS routing protocol defined by [ISO10589] has been widely		The IS-IS routing protocol defined by [ISO10589] has been widely
	deployed in provider networks, data centers and enterprise campus		deployed in provider networks, data centers and enterprise campus
	environments. In the data center and enterprise switching networks,		environments. In the data center and enterprise switching networks,
	Spine-Leaf topology is commonly used. This document describes the		Spine-Leaf topology is commonly used. This document describes the
	mechanism where IS-IS routing can be optimized to take the advantage		mechanism where IS-IS routing can be optimized to take the advantage
	of the unique Spine-Leaf topology.		of the unique Spine-Leaf topology.
	skipping to change at page 10, line 31 ¶		skipping to change at page 10, line 38 ¶
	Security concerns for IS-IS are addressed in [ISO10589], [RFC5304],		Security concerns for IS-IS are addressed in [ISO10589], [RFC5304],
	[RFC5310], and [RFC7602]. This extension does not raise additional		[RFC5310], and [RFC7602]. This extension does not raise additional
	security issues.		security issues.
	6. Acknowledgments		6. Acknowledgments
	TBD.		TBD.
	7. Document Change Log		7. Document Change Log
			7.1. Changes to draft-shen-isis-spine-leaf-ext-01.txt
			o Submitted April 2016.
			o No change. Refresh the draft version.
			7.2. Changes to draft-shen-isis-spine-leaf-ext-00.txt
	o Initial version of the draft is published in November 2015.		o Initial version of the draft is published in November 2015.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[ISO10589]		[ISO10589]
	ISO "International Organization for Standardization",		ISO "International Organization for Standardization",
	"Intermediate system to Intermediate system intra-domain		"Intermediate system to Intermediate system intra-domain
	routeing information exchange protocol for use in		routeing information exchange protocol for use in
	conjunction with the protocol for providing the		conjunction with the protocol for providing the
	connectionless-mode Network Service (ISO 8473), ISO/IEC		connectionless-mode Network Service (ISO 8473), ISO/IEC
	10589:2002, Second Edition.", Nov 2002.		10589:2002, Second Edition.", Nov 2002.
End of changes. 10 change blocks.
	9 lines changed or deleted		18 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/