| Internet-Draft | BGP-LS Extensions for IS-IS FR | October 2021 |
| Head & Przygienda | Expires 24 April 2022 | [Page] |
This document defines new BGP-LS (BGP Link-State) TLVs in order to carry IS-IS Flood Reflection information.¶
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 24 April 2022.¶
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.¶
BGP Link-State RFC7752 [RFC7752] defines mechanisms to advertise information about the underlying IGP in BGP NLRI to an external entity (e.g. a controller). New BGP-LS TLVs are required in order to faciliate IS-IS Flood Reflection [IS-IS-FR] extensions.¶
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].¶
This document defines the following BGP-LS TLV code point value in accordance with RFC7752 rules:¶
| TLV Code Point | Description | IS-IS TLV |
|---|---|---|
| TBD1 | Flood Reflection TLV | TBD1 (161) [IS-IS-FR] |
TLV formats are described in detail in subsequent subsections.¶
This TLV advertises Flood Reflector details. The semantics and values of the fields in the TLV are described in [IS-IS-FR].¶
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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
where:¶
This section requests entries from the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs" registry for the following TLVs:¶
| TLV Code Point | Description |
|---|---|
| TBD1 | Flood Reflection TLV |
Procedures and protocol extensions defined in this document do not affect the BGP security model. See the "Security Considerations" section of [RFC4271] for a discussion of BGP security. Also, refer to [RFC4272] and [RFC6952] for analyses of BGP security issues. Security considerations for acquiring and distributing BGP-LS information are discussed in [RFC7752].¶
The TLVs introduced in this document are used to propagate IS-IS Flood Reflection TLVs defined in [IS-IS-FR]. These TLVs represent IS-IS Flood Reflector state and are therefore assumed to support any/all of the required security and authentication mechanisms as described in [IS-IS-FR] to prevent any security issues when propagating the TLVs into BGP-LS.¶