| rfc9696v2.txt | rfc9696.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) Y. Wei, Ed. | Internet Engineering Task Force (IETF) Y. Wei, Ed. | |||
| Request for Comments: 9696 Z. Zhang | Request for Comments: 9696 Z. Zhang | |||
| Category: Informational ZTE Corporation | Category: Informational ZTE Corporation | |||
| ISSN: 2070-1721 D. Afanasiev | ISSN: 2070-1721 D. Afanasiev | |||
| Yandex | Yandex | |||
| P. Thubert | P. Thubert | |||
| Individual | Individual | |||
| T. Przygienda | T. Przygienda | |||
| Juniper Networks | Juniper Networks | |||
| December 2024 | March 2025 | |||
| Routing in Fat Trees (RIFT) Applicability and Operational Considerations | Routing in Fat Trees (RIFT) Applicability and Operational Considerations | |||
| Abstract | Abstract | |||
| This document discusses the properties, applicability, and | This document discusses the properties, applicability, and | |||
| operational considerations of Routing in Fat Trees (RIFT) in | operational considerations of Routing in Fat Trees (RIFT) in | |||
| different network scenarios with the intention of providing a rough | different network scenarios with the intention of providing a rough | |||
| guide on how RIFT can be deployed to simplify routing operations in | guide on how RIFT can be deployed to simplify routing operations in | |||
| Clos topologies and their variations. | Clos topologies and their variations. | |||
| skipping to change at line 41 ¶ | skipping to change at line 41 ¶ | |||
| Internet Engineering Steering Group (IESG). Not all documents | Internet Engineering Steering Group (IESG). Not all documents | |||
| approved by the IESG are candidates for any level of Internet | approved by the IESG are candidates for any level of Internet | |||
| Standard; see Section 2 of RFC 7841. | Standard; see Section 2 of RFC 7841. | |||
| Information about the current status of this document, any errata, | Information about the current status of this document, any errata, | |||
| and how to provide feedback on it may be obtained at | and how to provide feedback on it may be obtained at | |||
| https://www.rfc-editor.org/info/rfc9696. | https://www.rfc-editor.org/info/rfc9696. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2024 IETF Trust and the persons identified as the | Copyright (c) 2025 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Revised BSD License text as described in Section 4.e of the | include Revised BSD License text as described in Section 4.e of the | |||
| Trust Legal Provisions and are provided without warranty as described | Trust Legal Provisions and are provided without warranty as described | |||
| skipping to change at line 1568 ¶ | skipping to change at line 1568 ¶ | |||
| <https://www.rfc-editor.org/info/rfc8655>. | <https://www.rfc-editor.org/info/rfc8655>. | |||
| [RFC8950] Litkowski, S., Agrawal, S., Ananthamurthy, K., and K. | [RFC8950] Litkowski, S., Agrawal, S., Ananthamurthy, K., and K. | |||
| Patel, "Advertising IPv4 Network Layer Reachability | Patel, "Advertising IPv4 Network Layer Reachability | |||
| Information (NLRI) with an IPv6 Next Hop", RFC 8950, | Information (NLRI) with an IPv6 Next Hop", RFC 8950, | |||
| DOI 10.17487/RFC8950, November 2020, | DOI 10.17487/RFC8950, November 2020, | |||
| <https://www.rfc-editor.org/info/rfc8950>. | <https://www.rfc-editor.org/info/rfc8950>. | |||
| [RFC9692] Przygienda, T., Ed., Head, J., Ed., Sharma, A., Thubert, | [RFC9692] Przygienda, T., Ed., Head, J., Ed., Sharma, A., Thubert, | |||
| P., Rijsman, B., and D. Afanasiev, "RIFT: Routing in Fat | P., Rijsman, B., and D. Afanasiev, "RIFT: Routing in Fat | |||
| Trees", RFC 9692, DOI 10.17487/RFC9692, December 2024, | Trees", RFC 9692, DOI 10.17487/RFC9692, March 2025, | |||
| <https://www.rfc-editor.org/info/rfc9692>. | <https://www.rfc-editor.org/info/rfc9692>. | |||
| [TR-384] Broadband Forum Technical Report, "TR-384: Cloud Central | [TR-384] Broadband Forum Technical Report, "TR-384: Cloud Central | |||
| Office Reference Architectural Framework", TR-384, Issue | Office Reference Architectural Framework", TR-384, Issue | |||
| 1, January 2018, | 1, January 2018, | |||
| <https://www.broadband-forum.org/pdfs/tr-384-1-0-0.pdf>. | <https://www.broadband-forum.org/pdfs/tr-384-1-0-0.pdf>. | |||
| 8.2. Informative References | 8.2. Informative References | |||
| [CLOS] Yuan, X., "On Nonblocking Folded-Clos Networks in Computer | [CLOS] Yuan, X., "On Nonblocking Folded-Clos Networks in Computer | |||
| End of changes. 3 change blocks. | ||||
| 3 lines changed or deleted | 3 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||