Browse Prior Art Database

IS-IS Flooding Scope Link State PDUs (LSPs) (RFC7356)

IP.com Disclosure Number: IPCOM000238528D
Original Publication Date: 2014-Sep-01
Included in the Prior Art Database: 2014-Sep-03
Document File: 46 page(s) / 46K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Ginsberg: AUTHOR [+3]

Abstract

The Update Process, as defined by [IS-IS], provides reliable and efficient flooding of information to all routers in a given flooding scope. Currently, the protocol supports two flooding scopes and associated PDUs. Level 1 (L1) Link State PDUs (LSPs) are flooded to all routers in an area. Level 2 (L2) LSPs are flooded to all routers in the Level 2 subdomain. The basic operation of the Update Process can be applied to any subset of the routers in a given topology so long as that topology is not partitioned. It is, therefore, possible to introduce new PDUs in support of other flooding scopes and utilize the same Update Process machinery to provide the same reliability and efficiency that the Update Process currently provides for L1 and L2 scopes. This document defines these new PDUs and the modified Update Process rules that are to be used in supporting new flooding scopes.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

Internet Engineering Task Force (IETF)                       L. Ginsberg Request for Comments: 7356                                    S. Previdi Category: Standards Track                                        Y. Yang ISSN: 2070-1721                                            Cisco Systems                                                           September 2014

               IS-IS Flooding Scope Link State PDUs (LSPs)

Abstract

   Intermediate System to Intermediate System (IS-IS) provides efficient    and reliable flooding of information to its peers; however, the    current flooding scopes are limited to either area scope or domain    scope.  There are existing use cases where support of other flooding    scopes is desirable.  This document defines new Protocol Data Units    (PDUs) that provide support for new flooding scopes as well as    additional space for advertising information targeted for the    currently supported flooding scopes.  This document also defines    extended Type-Length-Values (TLVs) and sub-TLVs that are encoded    using 16-bit fields for Type and Length.

   The protocol extensions defined in this document are not backwards    compatible with existing implementations and so must be deployed with    care.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7356.

 Ginsberg, et al.             Standards Track                    [Page 1]
 RFC 7356                IS-IS Flooding Scope LSPs         September 2014

 Copyright Notice

   Copyright (c) 2014 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    (http://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   ...