Juniper Networks

1137 Innovation Way Sunnyvale CA USA jhead@juniper.net

Juniper Networks

1137 Innovation Way Sunnyvale CA USA prz@juniper.net

Routing Area Inter-Domain Routing IS-IS Flood Reflection is a mechanism that allows flat, single-area IS-IS topologies to scale beyond their traditional limitations. This document defines new BGP-LS (BGP Link-State) TLVs in order to carry IS-IS Flood Reflection information.

Introduction IS-IS Flood Reflection is a mechanism that allows flat, single-area IS-IS topologies to scale beyond their existing limitations. Flood Reflection topologies are broken into clusters. The participating nodes must convey their unique Cluster ID signifying their membership in a particular topology as well as their role (e.g. Flood Reflector or Client). BGP Link-State RFC7752 defines mechanisms to advertise information about the underlying IGP in BGP NLRI to an external entity (e.g. a controller). A new BGP-LS TLV is required in order to describe IS-IS Flood Reflection node and link details. This document defines that TLV.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

BGP-LS Extensions for IS-IS Flood Reflection Controllers may need to compute traffic engineered paths across Flood Reflection clusters. This requires that they be aware of Flood Reflection state (be it operational or configured), such as Cluster ID, C-bit (which indicates Flood Reflector or Client), and any applicable sub-TLVs. The IS-IS Flood Reflection TLV can be advertised in BGP-LS as either a Node attribute or a Link attribute. When describing a node, values are derived from the IS-IS Flood Reflection Discovery Sub-TLV. When describing a link, values are derived from the IS-IS Adjacency Sub-TLV. The semantics of any fields within the TLV/sub-TLVs are described in . This document defines the following BGP-LS TLVs for use with IS-IS Flood Reflection.

IS-IS Flood Reflection TLV 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |C| RESERVED | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flood Reflection Cluster ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sub-TLVs ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

IS-IS Flood Reflection TLV This section defines a BGP-LS Attribute that corresponds to IS-IS Flood Reflection TLVs/sub-TLVs as described in where:

• Type:

  TBD1 (1047)

  Length:

  variable

Design Considerations It is typical that a BGP-LS extension mirror its IGP counterpart. IS-IS Flood Reflection defines an optional "Flood Reflection Discovery Tunnel Type Sub-Sub-TLV" that is capable of facilitating the creation of "L1 Shortcuts" between nodes in a Flood Reflection cluster. This document intentionally excludes a BGP-LS extension of this capability for the following reasons. For example, shortcuts could be point-to-point IS-IS tunnels or be encapsulated by other means. In deployments where the tunnels are IS-IS based, no additional BGP-LS extension is required as the existing BGP-LS extensions for IS-IS will suffice. However, for deployments where tunnels are encapsulated by other means it is not desirable for BGP-LS to carry that information as it is tunnel state and not IGP state. Other existing or new BGP-LS extensions that correspond to the particular tunnel type should be used to fulfill any BGP-LS requirements.

IANA Considerations This section requests the following (suggested) values from the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs" registry for the following TLVs:

Suggested TLV Entries Suggested TLV Entries

TLV Code Point	Description	IS-IS TLV/Sub-TLV	Reference
TBD1 (1047)	IS-IS Flood Reflection	(22|23|25|141|222|223|242)/161	This document.

Security Considerations Procedures and protocol extensions defined in this document do not affect the BGP security model. See the "Security Considerations" section of for a discussion of BGP security. Also, refer to and for analyses of BGP security issues. Security considerations for acquiring and distributing BGP-LS information are discussed in . The TLVs introduced in this document are used to propagate IS-IS Flood Reflection TLVs defined in . These TLVs represent IS-IS Flood Reflection state and are therefore assumed to support any/all of the required security and authentication mechanisms as described in to prevent any security issues when propagating the TLVs into BGP-LS.

Acknowledgements The authors would like to thank Ketan Talaulikar for several iterations of review and practical suggestions.

References Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.