IS-IS Multi Topology Deployment Considerations
draft-chunduri-lsr-isis-mt-deployment-cons-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-05-19
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
LSR Working Group U. Chunduri
Internet-Draft Huawei USA
Intended status: Informational J. Tantsura
Expires: November 20, 2019 Apstra, Inc.
S. Hegde
Juniper Networks
May 19, 2019
IS-IS Multi Topology Deployment Considerations
draft-chunduri-lsr-isis-mt-deployment-cons-02
Abstract
This document analyzes IS-IS Multi Topology (MT) applicability in
various deployments (Core/Mobile Backhaul/Data Center underlays).
This document explores the nuances around the terminology and usage
of various IS-IS address families, topologies with different
considerations, for choosing the right combination for a specific
deployment scenario.
This document also discusses various ways one can deploy IPv6 only
IS-IS topology.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [RFC2119],
RFC8174 [RFC8174] when, and only when they appear in all capitals, as
shown here.
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 November 20, 2019.
Chunduri, et al. Expires November 20, 2019 [Page 1]
Internet-DrafIS-IS Multi Topology Deployment Considerations May 2019
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
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Need for MT in IS-IS networks . . . . . . . . . . . . . . . . 3
3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Topologies and Address Families . . . . . . . . . . . . . . . 4
4.1. Single Topology Mode and Multiple Address Families . . . 4
4.2. Multiple Topology Mode and Multiple Address Families . . 5
4.2.1. Transition Mode . . . . . . . . . . . . . . . . . . . 6
4.3. IPv6 Only Topology . . . . . . . . . . . . . . . . . . . 6
5. IS-IS MT and LFA . . . . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
ISIS originally developed for OSI [ISO.10589.1992] and extensions
have been made available to support IPv4 [RFC1195]. A method for
exchanging IPv6 routing information using the IS-IS routing protocol
is specified in [RFC5308]. How to run a set of independent IP
topologies with topology specific adjacencies, within a single IS-IS
domain has been defined in IS-IS MT [RFC5120].
Multiple mobile backhaul network user plane proposals like
[I-D.ietf-dmm-srv6-mobile-uplane] and [I-D.herbert-ila-mobile] use
IPv6 only solution using source routing, address transformation
respectively. It is possible to conceive, various parts of the
backhaul networks use IPv4 and appropriate migration strategy needed
Show full document text