| < draft-ietf-spring-bfd-02.txt | draft-ietf-spring-bfd-03.txt > | |||
|---|---|---|---|---|
| SPRING Working Group G. Mirsky | SPRING Working Group G. Mirsky | |||
| Internet-Draft Ericsson | Internet-Draft Ericsson | |||
| Intended status: Standards Track J. Tantsura | Intended status: Standards Track J. Tantsura | |||
| Expires: 27 March 2022 Juniper Networks | Expires: 28 September 2022 Microsoft | |||
| I. Varlashkin | I. Varlashkin | |||
| M. Chen | M. Chen | |||
| Huawei | Huawei | |||
| J. Wenying | J. Wenying | |||
| CMCC | CMCC | |||
| 23 September 2021 | 27 March 2022 | |||
| Bidirectional Forwarding Detection (BFD) in Segment Routing Networks | Bidirectional Forwarding Detection (BFD) in Segment Routing Networks | |||
| Using MPLS Dataplane | Using MPLS Dataplane | |||
| draft-ietf-spring-bfd-02 | draft-ietf-spring-bfd-03 | |||
| Abstract | Abstract | |||
| Segment Routing (SR) architecture leverages the paradigm of source | Segment Routing (SR) architecture leverages the paradigm of source | |||
| routing. It can be realized in the Multiprotocol Label Switching | routing. It can be realized in the Multiprotocol Label Switching | |||
| (MPLS) network without any change to the data plane. A segment is | (MPLS) network without any change to the data plane. A segment is | |||
| encoded as an MPLS label, and an ordered list of segments is encoded | encoded as an MPLS label, and an ordered list of segments is encoded | |||
| as a stack of labels. Bidirectional Forwarding Detection (BFD) is | as a stack of labels. Bidirectional Forwarding Detection (BFD) is | |||
| expected to monitor any existing path between systems. This document | expected to monitor any existing path between systems. This document | |||
| defines how to use Label Switched Path Ping to bootstrap a BFD | defines how to use Label Switched Path Ping to bootstrap a BFD | |||
| skipping to change at page 1, line 48 ¶ | skipping to change at page 1, line 48 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on 27 March 2022. | This Internet-Draft will expire on 28 September 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 IETF Trust and the persons identified as the | Copyright (c) 2022 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 (https://trustee.ietf.org/ | Provisions Relating to IETF Documents (https://trustee.ietf.org/ | |||
| license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
| Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
| and restrictions with respect to this document. Code Components | and restrictions with respect to this document. Code Components | |||
| extracted from this document must include Simplified BSD License text | extracted from this document must include Revised BSD License text as | |||
| as described in Section 4.e of the Trust Legal Provisions and are | described in Section 4.e of the Trust Legal Provisions and are | |||
| provided without warranty as described in the Simplified BSD License. | provided without warranty as described in the Revised BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 | 1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 3 | 1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 1.1.2. Requirements Language . . . . . . . . . . . . . . . . 4 | 1.1.2. Requirements Language . . . . . . . . . . . . . . . . 4 | |||
| 2. Bootstrapping BFD Session over Segment Routed Tunnel with MPLS | 2. Bootstrapping BFD Session over Segment Routed Tunnel with MPLS | |||
| Data Plane . . . . . . . . . . . . . . . . . . . . . . . 4 | Data Plane . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 3. Use BFD Reverse Path TLV over Segment Routed MPLS Tunnel . . 5 | 3. Use BFD Reverse Path TLV over Segment Routed MPLS Tunnel . . 5 | |||
| skipping to change at page 12, line 21 ¶ | skipping to change at page 12, line 21 ¶ | |||
| information about the implementation of this specification. | information about the implementation of this specification. | |||
| 14. References | 14. References | |||
| 14.1. Normative References | 14.1. Normative References | |||
| [I-D.ietf-mpls-bfd-directed] | [I-D.ietf-mpls-bfd-directed] | |||
| Mirsky, G., Tantsura, J., Varlashkin, I., and M. Chen, | Mirsky, G., Tantsura, J., Varlashkin, I., and M. Chen, | |||
| "Bidirectional Forwarding Detection (BFD) Directed Return | "Bidirectional Forwarding Detection (BFD) Directed Return | |||
| Path for MPLS Label Switched Paths (LSPs)", Work in | Path for MPLS Label Switched Paths (LSPs)", Work in | |||
| Progress, Internet-Draft, draft-ietf-mpls-bfd-directed-18, | Progress, Internet-Draft, draft-ietf-mpls-bfd-directed-19, | |||
| 20 August 2021, <https://datatracker.ietf.org/doc/html/ | 14 February 2022, <https://datatracker.ietf.org/doc/html/ | |||
| draft-ietf-mpls-bfd-directed-18>. | draft-ietf-mpls-bfd-directed-19>. | |||
| [I-D.mirsky-bfd-mpls-demand] | [I-D.mirsky-bfd-mpls-demand] | |||
| Mirsky, G., "BFD in Demand Mode over Point-to-Point MPLS | Mirsky, G., "BFD in Demand Mode over Point-to-Point MPLS | |||
| LSP", Work in Progress, Internet-Draft, draft-mirsky-bfd- | LSP", Work in Progress, Internet-Draft, draft-mirsky-bfd- | |||
| mpls-demand-09, 30 March 2021, | mpls-demand-11, 7 March 2022, | |||
| <https://datatracker.ietf.org/doc/html/draft-mirsky-bfd- | <https://datatracker.ietf.org/doc/html/draft-mirsky-bfd- | |||
| mpls-demand-09>. | mpls-demand-11>. | |||
| [I-D.voyer-spring-sr-p2mp-policy] | [I-D.voyer-spring-sr-p2mp-policy] | |||
| Voyer, D., Filsfils, C., Parekh, R., Bidgoli, H., and Z. | Voyer, D., Filsfils, C., Parekh, R., Bidgoli, H., and Z. | |||
| Zhang, "SR Replication Policy for P2MP Service Delivery", | Zhang, "SR Replication Policy for P2MP Service Delivery", | |||
| Work in Progress, Internet-Draft, draft-voyer-spring-sr- | Work in Progress, Internet-Draft, draft-voyer-spring-sr- | |||
| p2mp-policy-03, 2 July 2019, | p2mp-policy-03, 2 July 2019, | |||
| <https://datatracker.ietf.org/doc/html/draft-voyer-spring- | <https://datatracker.ietf.org/doc/html/draft-voyer-spring- | |||
| sr-p2mp-policy-03>. | sr-p2mp-policy-03>. | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| skipping to change at page 14, line 28 ¶ | skipping to change at page 14, line 28 ¶ | |||
| DOI 10.17487/RFC8660, December 2019, | DOI 10.17487/RFC8660, December 2019, | |||
| <https://www.rfc-editor.org/info/rfc8660>. | <https://www.rfc-editor.org/info/rfc8660>. | |||
| 14.2. Informative References | 14.2. Informative References | |||
| [I-D.ietf-pim-bfd-p2mp-use-case] | [I-D.ietf-pim-bfd-p2mp-use-case] | |||
| Mirsky, G. and J. Xiaoli, "Fast Failover in Protocol | Mirsky, G. and J. Xiaoli, "Fast Failover in Protocol | |||
| Independent Multicast - Sparse Mode (PIM-SM) Using | Independent Multicast - Sparse Mode (PIM-SM) Using | |||
| Bidirectional Forwarding Detection (BFD) for Multipoint | Bidirectional Forwarding Detection (BFD) for Multipoint | |||
| Networks", Work in Progress, Internet-Draft, draft-ietf- | Networks", Work in Progress, Internet-Draft, draft-ietf- | |||
| pim-bfd-p2mp-use-case-07, 10 September 2021, | pim-bfd-p2mp-use-case-10, 9 December 2021, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-pim-bfd- | <https://datatracker.ietf.org/doc/html/draft-ietf-pim-bfd- | |||
| p2mp-use-case-07>. | p2mp-use-case-10>. | |||
| [I-D.ietf-spring-mpls-anycast-segments] | [I-D.ietf-spring-mpls-anycast-segments] | |||
| Sarkar, P., Gredler, H., Filsfils, C., Previdi, S., | Sarkar, P., Gredler, H., Filsfils, C., Previdi, S., | |||
| Decraene, B., and M. Horneffer, "Anycast Segments in MPLS | Decraene, B., and M. Horneffer, "Anycast Segments in MPLS | |||
| based Segment Routing", Work in Progress, Internet-Draft, | based Segment Routing", Work in Progress, Internet-Draft, | |||
| draft-ietf-spring-mpls-anycast-segments-03, 27 April 2020, | draft-ietf-spring-mpls-anycast-segments-03, 27 April 2020, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-spring- | <https://datatracker.ietf.org/doc/html/draft-ietf-spring- | |||
| mpls-anycast-segments-03>. | mpls-anycast-segments-03>. | |||
| [RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and | [RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and | |||
| skipping to change at page 15, line 6 ¶ | skipping to change at page 15, line 6 ¶ | |||
| <https://www.rfc-editor.org/info/rfc6790>. | <https://www.rfc-editor.org/info/rfc6790>. | |||
| [RFC9026] Morin, T., Ed., Kebler, R., Ed., and G. Mirsky, Ed., | [RFC9026] Morin, T., Ed., Kebler, R., Ed., and G. Mirsky, Ed., | |||
| "Multicast VPN Fast Upstream Failover", RFC 9026, | "Multicast VPN Fast Upstream Failover", RFC 9026, | |||
| DOI 10.17487/RFC9026, April 2021, | DOI 10.17487/RFC9026, April 2021, | |||
| <https://www.rfc-editor.org/info/rfc9026>. | <https://www.rfc-editor.org/info/rfc9026>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Greg Mirsky | Greg Mirsky | |||
| Ericsson | Ericsson | |||
| Email: gregimirsky@gmail.com | Email: gregimirsky@gmail.com | |||
| Jeff Tantsura | Jeff Tantsura | |||
| Juniper Networks | Microsoft | |||
| Email: jefftant.ietf@gmail.com | Email: jefftant.ietf@gmail.com | |||
| Ilya Varlashkin | Ilya Varlashkin | |||
| Email: Ilya@nobulus.com | Email: Ilya@nobulus.com | |||
| Mach(Guoyi) Chen | Mach(Guoyi) Chen | |||
| Huawei | Huawei | |||
| Email: mach.chen@huawei.com | Email: mach.chen@huawei.com | |||
| Jiang Wenying | Jiang Wenying | |||
| CMCC | CMCC | |||
| Email: jiangwenying@chinamobile.com | Email: jiangwenying@chinamobile.com | |||
| End of changes. 16 change blocks. | ||||
| 21 lines changed or deleted | 16 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/ | ||||