IS-IS Multi-Flooding Instances
draft-wang-lsr-isis-mfi-00
Link State Routing Working Group Y. Wang
Internet-Draft Huawei
Intended status: Standards Track A. Wang
Expires: August 25, 2021 China Telecom
Z. Hu
T. Zhou
Huawei
February 21, 2021
IS-IS Multi-Flooding Instances
draft-wang-lsr-isis-mfi-00
Abstract
This document proposes a new IS-IS flooding mechanism which separates
multiple flooding instances for dissemination of routing information
and other types of application-specific information to minimizes the
impact of non-routing information flooding on the routing convergence
and stability. Due to different flooding information has different
requirements on the flooding rate, these multi-flooding instances
should be given various priorities and flooding parameters. An
encoding format for IS-IS Multi-Flooding Instance Identifier (MFI-ID)
TLV and Update Process are specified in this document.
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 RFC 2119 [RFC2119].
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 August 25, 2021.
Wang, et al. Expires August 25, 2021 [Page 1]
Internet-Draft draft-wang-lsr-isis-mfi-00 February 2021
Copyright Notice
Copyright (c) 2021 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. IS-IS Multi-Flooding Instances . . . . . . . . . . . . . . . 3
2.1. Multi-Flooding Instance Identifier . . . . . . . . . . . 4
2.2. Update Process Operation . . . . . . . . . . . . . . . . 4
2.3. Interoperability Considerations . . . . . . . . . . . . . 5
3. IS-IS Non-routing MFIs Omission of Routing Calculation . . . 5
4. Applicability of IS-IS Multi-Flooding Instances . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
[ISO10589] specifies the IS-IS protocol, in which each Intermediate
System (IS) (router) advertises one or more IS-IS Link State Protocol
Data Units (LSPs) with routing topology and Traffic Engineering (TE)
information. As the one-octet LSP Number field, there are limited
256 numbers of LSPs that may be assigned. However, with the
increasing amount of Topology information and TE information proposed
to be advertised, for example, advertisement of Virtual Transport
Networks (VTN) Topology, VTN Resource and VTN specific Data Plane
Identifiers [I-D.dong-lsr-sr-enhanced-vpn], there will be huge
consumption of LSPs. In addition, with the increasing use the same
mechanism for advertisement of application-specific information,
therefore, a mechanism should be defined for advertisement of
Show full document text