Network Working Group X. Xu Internet-Draft China Mobile Intended status: Standards Track 22 November 2023 Expires: 25 May 2024 Flooding Reduction in CLOS Networks draft-xu-lsr-flooding-reduction-in-clos-00 Abstract For a given OSPF (or ISIS) router within the CLOS topology, it would receive multiple copies of exactly the same LSA (or LSP) from multiple OSPF (or ISIS) neighbors. In addition, two OSPF (or ISIS) neighbors may send each other the same LSA (or LSP) simultaneously. The unnecessary link-state information flooding wastes the precious process resource of OSPF (or ISIS) routers. This document proposes extensions to OSPF (or ISIS) so as to reduce the OSPF (or ISIS) flooding within such CLOS networks. The reduction of the OSPF (or ISIS) flooding is much beneficial to improve the scalability of CLOS networks. 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 25 May 2024. Xu Expires 25 May 2024 [Page 1] Internet-Draft Flooding Reduction in CLOS Networks November 2023 Copyright Notice Copyright (c) 2023 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Modifications to Legacy OSPF and ISIS Behaviors . . . . . . . 4 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction For a given OSPF (or ISIS) router within the CLOS topology, it would receive multiple copies of exactly the same LSA (or LSP) from multiple OSPF (or ISIS) neighbors. In addition, two OSPF (or ISIS) neighbors may send each other the same LSA (or LSP) simultaneously. The unnecessary link-state information flooding wastes the precious process resource of OSPF (or ISIS) routers. This document proposes extensions to OSPF (or ISIS) so as to reduce the OSPF (or ISIS) flooding within such CLOS networks. The reduction of the OSPF (or ISIS) flooding is much beneficial to improve the scalability of CLOS networks. As a result, some CLOS network operators had to choose BGP as the underlay routing protocol in their data centers [RFC7938]. However, with the emergence of high-performance Ethernet networks for AI and high performance computing (HPC), the visibility of the whole network topology, and even the link load information, is crucial for performing the end-to-end path load-balancing, also known as global load-balancing or adaptive routing. As a result, link-state routing protocols, such as OSPF (or ISIS), would have to be reconsidered as Xu Expires 25 May 2024 [Page 2] Internet-Draft Flooding Reduction in CLOS Networks November 2023 the routing protocol for large-scale AI and HPC Ethernet networks. Of course, the prerequisite is the scaling issue associated with link-state routing protocols as mentioned above could be well addressed. This document describes a pragmatic approach to the above scaling issue. The basic idea is to configure partial routers as non- reflectors for a given OSPF area (or a given ISIS level) which are not allowed to reflect the LSAs (or LSPs) received from neighbors in that OSPF area (or that ISIS level) to neighbors in the same OSPF area (or the same ISIS level). For a three-stage CLOS network (i.e., a leaf-spine network) as shown in Figure 1, all nodes are in OSPF area zero (or ISIS Level-2). All leaf nodes SHOULD be configured as non-reflectors. To further reduce the link-state flooding, all spine nodes except two of them COULD be configured as non-refletors as well. For a five-stage CLOS network (i.e., a leaf-spine-superspine network) as shown in Figure 2, each PoD consist of leaf nodes and spine nodes is configured as an OSPF non-zero area (or an ISIS Level-1 area), each PoD-interconnect plane consist of spine nodes and super-spine nodes is configured as an OSPF area zero (or an ISIS Level-2 area) . As such, spine nodes act as OSPF area border routers (or ISIS Level- 1-2 routers). All leaf nodes SHOULD be configured as non-reflectors. All spine nodes SHOULD be configured as non-reflectors for OSPF area zero (or ISIS Level-2). To further reduce the link-state flooding, all spine nodes of each pod except at least two of them are recommended to be configured as non-reflectors for the associated non-zero OSPF area (or ISIS Level-1 area), and all super-spine nodes of each PoD-interconnect plane except two of them COULD be configured as non-reflectors. +----+ +----+ +----+ +----+ | S1 | | S2 | | S3 | | S4 | (Spine) +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ | L1 | | L2 | | L3 | | L4 | | L5 | | L6 | | L7 | | L8 | (Leaf) +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ Figure 1 Xu Expires 25 May 2024 [Page 3] Internet-Draft Flooding Reduction in CLOS Networks November 2023 ========================================= # +----+ +----+ +----+ +----+ # # | L1 | | L2 | | L3 | | L4 | (Leaf) # # +----+ +----+ +----+ +----+ # # PoD-1 # # +----+ +----+ +----+ +----+ # # | S1 | | S2 | | S3 | | S4 | (Spine) # # +----+ +----+ +----+ +----+ # ========================================= =============================== =============================== # +----+ +----+ +----+ +----+ # # +----+ +----+ +----+ +----+ # # |SS1 | |SS2 | |SS3 | |SS4 | # # |SS1 | |SS2 | |SS3 | |SS4 | # # +----+ +----+ +----+ +----+ # # +----+ +----+ +----+ +----+ # # (Super-Spine@Plane-1) # # (Super-Spine@Plane-4) # #============================== ... =============================== ========================================= # +----+ +----+ +----+ +----+ # # | S1 | | S2 | | S3 | | S4 | (Spine) # # +----+ +----+ +----+ +----+ # # PoD-8 # # +----+ +----+ +----+ +----+ # # | L1 | | L2 | | L3 | | L4 | (Leaf) # # +----+ +----+ +----+ +----+ # ========================================= Figure 2 The above diagram does not contain the connections between nodes. The reader should assume that leaf nodes in a given PoD is connected to every spine node in that PoD while each spine node (e.g., S1) is connected to all super-spine nodes in the corresponding PoD- interconnect plane (e.g., Plane-1). 2. Terminology This memo makes use of the terms defined in [RFC2328]. 3. Modifications to Legacy OSPF and ISIS Behaviors Those OSPF (or ISIS) routers which are configured as non-reflectors for a given OSPF area (or a given ISIS level) SHOULD NOT reflect the LSAs (or LSPs) received from neighbors in that OSPF area (or that ISIS level) to neighbors in the same OSPF area (or the same ISIS level). Xu Expires 25 May 2024 [Page 4] Internet-Draft Flooding Reduction in CLOS Networks November 2023 4. Acknowledgements TBD. 5. IANA Considerations TBD. 6. Security Considerations TBD. 7. References 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, DOI 10.17487/RFC2328, April 1998, . [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, . 7.2. Informative References [RFC4136] Pillay-Esnault, P., "OSPF Refresh and Flooding Reduction in Stable Topologies", RFC 4136, DOI 10.17487/RFC4136, July 2005, . [RFC7938] Lapukhov, P., Premji, A., and J. Mitchell, Ed., "Use of BGP for Routing in Large-Scale Data Centers", RFC 7938, DOI 10.17487/RFC7938, August 2016, . Author's Address Xiaohu Xu China Mobile Email: xuxiaohu_ietf@hotmail.com Xu Expires 25 May 2024 [Page 5]