IS-IS Routing for Spine-Leaf Topology
draft-ietf-lsr-isis-spine-leaf-ext-02
Networking Working Group N. Shen
Internet-Draft L. Ginsberg
Intended status: Standards Track Cisco Systems
Expires: March 5, 2020 S. Thyamagundalu
September 2, 2019
IS-IS Routing for Spine-Leaf Topology
draft-ietf-lsr-isis-spine-leaf-ext-02
Abstract
This document describes a mechanism for routers and switches in a
Spine-Leaf type topology to have non-reciprocal Intermediate System
to Intermediate System (IS-IS) routing relationships between the
leafs and spines. The leaf nodes do not need to have the topology
information of other nodes and exact prefixes in the network. This
extension also has application in the Internet of Things (IoT).
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 5, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Shen, et al. Expires March 5, 2020 [Page 1]
Internet-Draft IS-IS SL Extension September 2019
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Spine-Leaf (SL) Extension . . . . . . . . . . . . . . . . . . 4
3.1. Topology Examples . . . . . . . . . . . . . . . . . . . . 4
3.2. Applicability Statement . . . . . . . . . . . . . . . . . 5
3.3. Spine-Leaf TLVs . . . . . . . . . . . . . . . . . . . . . 6
3.3.1. Spine-Leaf TLV . . . . . . . . . . . . . . . . . . . 6
3.3.2. Leaf-Set TLV . . . . . . . . . . . . . . . . . . . . 7
3.3.2.1. Leaf-Set Sub-TLVs . . . . . . . . . . . . . . . . 7
3.3.3. Advertising IPv4/IPv6 Reachability . . . . . . . . . 8
3.3.4. Advertising Connection to RF-Leaf Node . . . . . . . 8
3.4. Mechanism . . . . . . . . . . . . . . . . . . . . . . . . 9
3.4.1. Pure CLOS Topology . . . . . . . . . . . . . . . . . 10
3.5. Implementation and Operation . . . . . . . . . . . . . . 11
3.5.1. CSNP PDU . . . . . . . . . . . . . . . . . . . . . . 11
3.5.2. Leaf to Leaf connection . . . . . . . . . . . . . . . 12
3.5.2.1. Local traffic only . . . . . . . . . . . . . . . 12
3.5.2.2. Transit traffic allowed . . . . . . . . . . . . . 12
3.5.3. Spine Node Hostname . . . . . . . . . . . . . . . . . 13
3.5.4. IS-IS Reverse Metric . . . . . . . . . . . . . . . . 13
3.5.5. Spine-Leaf Traffic Engineering . . . . . . . . . . . 13
3.5.6. Other End-to-End Services . . . . . . . . . . . . . . 13
3.5.7. Address Family and Topology . . . . . . . . . . . . . 14
3.5.8. Migration . . . . . . . . . . . . . . . . . . . . . . 14
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
5. Security Considerations . . . . . . . . . . . . . . . . . . . 15
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. Normative References . . . . . . . . . . . . . . . . . . 15
7.2. Informative References . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction
The IS-IS routing protocol defined by [ISO10589] has been widely
deployed in provider networks, data centers and enterprise campus
environments. In the data center and enterprise switching networks,
Show full document text