| rfc9085v2.txt | rfc9085.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) S. Previdi | Internet Engineering Task Force (IETF) S. Previdi | |||
| Request for Comments: 9085 Huawei Technologies | Request for Comments: 9085 Huawei Technologies | |||
| Category: Standards Track K. Talaulikar, Ed. | Category: Standards Track K. Talaulikar, Ed. | |||
| ISSN: 2070-1721 C. Filsfils | ISSN: 2070-1721 C. Filsfils | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| H. Gredler | H. Gredler | |||
| RtBrick Inc. | RtBrick Inc. | |||
| M. Chen | M. Chen | |||
| Huawei Technologies | Huawei Technologies | |||
| July 2021 | August 2021 | |||
| Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment | |||
| Routing | Routing | |||
| Abstract | Abstract | |||
| Segment Routing (SR) allows for a flexible definition of end-to-end | Segment Routing (SR) allows for a flexible definition of end-to-end | |||
| paths by encoding paths as sequences of topological subpaths, called | paths by encoding paths as sequences of topological subpaths, called | |||
| "segments". These segments are advertised by routing protocols, | "segments". These segments are advertised by routing protocols, | |||
| e.g., by the link-state routing protocols (IS-IS, OSPFv2, and OSPFv3) | e.g., by the link-state routing protocols (IS-IS, OSPFv2, and OSPFv3) | |||
| skipping to change at line 1321 ¶ | skipping to change at line 1321 ¶ | |||
| DOI 10.17487/RFC8667, December 2019, | DOI 10.17487/RFC8667, December 2019, | |||
| <https://www.rfc-editor.org/info/rfc8667>. | <https://www.rfc-editor.org/info/rfc8667>. | |||
| [RFC8668] Ginsberg, L., Ed., Bashandy, A., Filsfils, C., Nanduri, | [RFC8668] Ginsberg, L., Ed., Bashandy, A., Filsfils, C., Nanduri, | |||
| M., and E. Aries, "Advertising Layer 2 Bundle Member Link | M., and E. Aries, "Advertising Layer 2 Bundle Member Link | |||
| Attributes in IS-IS", RFC 8668, DOI 10.17487/RFC8668, | Attributes in IS-IS", RFC 8668, DOI 10.17487/RFC8668, | |||
| December 2019, <https://www.rfc-editor.org/info/rfc8668>. | December 2019, <https://www.rfc-editor.org/info/rfc8668>. | |||
| [RFC9084] Wang, A., Lindem, A., Dong, J., Psenak, P., and K. | [RFC9084] Wang, A., Lindem, A., Dong, J., Psenak, P., and K. | |||
| Talaulikar, Ed., "OSPF Prefix Originator Extensions", | Talaulikar, Ed., "OSPF Prefix Originator Extensions", | |||
| RFC 9084, DOI 10.17487/RFC9084, July 2021, | RFC 9084, DOI 10.17487/RFC9084, August 2021, | |||
| <https://www.rfc-editor.org/info/rfc9084>. | <https://www.rfc-editor.org/info/rfc9084>. | |||
| 6.2. Informative References | 6.2. Informative References | |||
| [ISIS-SR-YANG] | [ISIS-SR-YANG] | |||
| Litkowski, S., Qu, Y., Sarkar, P., Chen, I., and J. | Litkowski, S., Qu, Y., Sarkar, P., Chen, I., and J. | |||
| Tantsura, "YANG Data Model for IS-IS Segment Routing", | Tantsura, "YANG Data Model for IS-IS Segment Routing", | |||
| Work in Progress, Internet-Draft, draft-ietf-isis-sr-yang- | Work in Progress, Internet-Draft, draft-ietf-isis-sr-yang- | |||
| 10, 21 February 2021, | 10, 21 February 2021, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-isis-sr- | <https://datatracker.ietf.org/doc/html/draft-ietf-isis-sr- | |||
| End of changes. 2 change blocks. | ||||
| 2 lines changed or deleted | 2 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||