IS-IS Topology-Transparent Zone
draft-chen-isis-ttz-12
Internet Engineering Task Force H. Chen
Internet-Draft R. Li
Intended status: Standards Track Futurewei
Expires: February 19, 2021 Y. Yang
IBM
A. Kumar S N
RtBrick
Y. Fan
Casa Systems
N. So
V. Liu
M. Toy
Verizon
L. Liu
Fujitsu
K. Makhijani
Futurewei
August 18, 2020
IS-IS Topology-Transparent Zone
draft-chen-isis-ttz-12.txt
Abstract
This document presents a topology-transparent zone in an area. A
zone is a block/piece of an area, which comprises a group of routers
and a number of circuits connecting them. It is abstracted as a
virtual entity such as a single virtual node or zone edges mesh. Any
router outside of the zone is not aware of the zone. The information
about the circuits and routers inside the zone is not distributed to
any router outside of the zone.
Status of This Memo
This Internet-Draft is submitted to IETF 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
Chen, et al. Expires February 19, 2021 [Page 1]
Internet-Draft IS-IS TTZ August 2020
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 February 19, 2021.
Copyright Notice
Copyright (c) 2020 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Zone Abstraction . . . . . . . . . . . . . . . . . . . . . . 4
4. Topology-Transparent Zone . . . . . . . . . . . . . . . . . . 5
4.1. Zone as a Single Node . . . . . . . . . . . . . . . . . . 5
4.1.1. An Example of Zone as a Single Node . . . . . . . . . 5
4.1.2. Zone Leader Election . . . . . . . . . . . . . . . . 7
4.1.3. LS Generation for Zone as a Single Node . . . . . . . 8
4.1.4. Adjacency Establishment and Termination . . . . . . . 8
4.1.5. Computation of Routes . . . . . . . . . . . . . . . . 10
4.1.6. Extensions to Protocols . . . . . . . . . . . . . . . 11
4.2. Zone as Edges Full Mesh . . . . . . . . . . . . . . . . . 14
4.2.1. Extensions to IS-IS . . . . . . . . . . . . . . . . . 14
4.3. Advertisement of LSs . . . . . . . . . . . . . . . . . . 15
4.3.1. Advertisement of LSs within Zone . . . . . . . . . . 15
4.3.2. Advertisement of LSs through Zone . . . . . . . . . . 16
5. Seamless Migration . . . . . . . . . . . . . . . . . . . . . 16
5.1. Transfer Zone to a Single Node . . . . . . . . . . . . . 16
5.2. Roll Back from Zone as a Single Node . . . . . . . . . . 16
6. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . 19
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
Show full document text