| < draft-ietf-idr-bgp-ls-sbfd-extensions-05.txt | draft-ietf-idr-bgp-ls-sbfd-extensions-06.txt > | |||
|---|---|---|---|---|
| Inter-Domain Routing Z. Li | Inter-Domain Routing Z. Li | |||
| Internet-Draft S. Zhuang | Internet-Draft S. Zhuang | |||
| Intended status: Standards Track Huawei | Intended status: Standards Track Huawei | |||
| Expires: September 9, 2021 K. Talaulikar, Ed. | Expires: April 25, 2022 K. Talaulikar, Ed. | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| S. Aldrin | S. Aldrin | |||
| Google, Inc | Google, Inc | |||
| J. Tantsura | J. Tantsura | |||
| Apstra | Microsoft | |||
| G. Mirsky | G. Mirsky | |||
| ZTE Corp. | Ericsson | |||
| March 8, 2021 | October 22, 2021 | |||
| BGP Link-State Extensions for Seamless BFD | BGP Link-State Extensions for Seamless BFD | |||
| draft-ietf-idr-bgp-ls-sbfd-extensions-05 | draft-ietf-idr-bgp-ls-sbfd-extensions-06 | |||
| Abstract | Abstract | |||
| Seamless Bidirectional Forwarding Detection (S-BFD) defines a | Seamless Bidirectional Forwarding Detection (S-BFD) defines a | |||
| simplified mechanism to use Bidirectional Forwarding Detection (BFD) | simplified mechanism to use Bidirectional Forwarding Detection (BFD) | |||
| with large portions of negotiation aspects eliminated, thus providing | with large portions of negotiation aspects eliminated, thus providing | |||
| benefits such as quick provisioning as well as improved control and | benefits such as quick provisioning as well as improved control and | |||
| flexibility to network nodes initiating the path monitoring. The | flexibility to network nodes initiating the path monitoring. The | |||
| link-state routing protocols (IS-IS and OSPF) have been extended to | link-state routing protocols (IS-IS and OSPF) have been extended to | |||
| advertise the Seamless BFD (S-BFD) Discriminators. | advertise the Seamless BFD (S-BFD) Discriminators. | |||
| skipping to change at page 1, line 47 ¶ | skipping to change at page 1, line 47 ¶ | |||
| 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 September 9, 2021. | This Internet-Draft will expire on April 25, 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 IETF Trust and the persons identified as the | Copyright (c) 2021 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 | |||
| skipping to change at page 7, line 8 ¶ | skipping to change at page 7, line 8 ¶ | |||
| administrative domain. | administrative domain. | |||
| Advertising the S-BFD Discriminators via BGP-LS makes it possible for | Advertising the S-BFD Discriminators via BGP-LS makes it possible for | |||
| attackers to initiate S-BFD sessions using the advertised | attackers to initiate S-BFD sessions using the advertised | |||
| information. The vulnerabilities this poses and how to mitigate them | information. The vulnerabilities this poses and how to mitigate them | |||
| are discussed in [RFC7752]. | are discussed in [RFC7752]. | |||
| 8. Acknowledgements | 8. Acknowledgements | |||
| The authors would like to thank Nan Wu for his contributions to this | The authors would like to thank Nan Wu for his contributions to this | |||
| work and Gunter Van De Velde for his review. | work and Gunter Van De Velde for his review. The authors would also | |||
| like to thank Jeff Haas for his shepherd review of this document. | ||||
| 9. References | 9. References | |||
| 9.1. Normative References | 9.1. Normative References | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| skipping to change at page 8, line 8 ¶ | skipping to change at page 8, line 8 ¶ | |||
| 9.2. Informative References | 9.2. Informative References | |||
| [I-D.ietf-mpls-seamless-mpls] | [I-D.ietf-mpls-seamless-mpls] | |||
| Leymann, N., Decraene, B., Filsfils, C., Konstantynowicz, | Leymann, N., Decraene, B., Filsfils, C., Konstantynowicz, | |||
| M., and D. Steinberg, "Seamless MPLS Architecture", draft- | M., and D. Steinberg, "Seamless MPLS Architecture", draft- | |||
| ietf-mpls-seamless-mpls-07 (work in progress), June 2014. | ietf-mpls-seamless-mpls-07 (work in progress), June 2014. | |||
| [I-D.ietf-spring-segment-routing-policy] | [I-D.ietf-spring-segment-routing-policy] | |||
| Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and | Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and | |||
| P. Mattes, "Segment Routing Policy Architecture", draft- | P. Mattes, "Segment Routing Policy Architecture", draft- | |||
| ietf-spring-segment-routing-policy-09 (work in progress), | ietf-spring-segment-routing-policy-13 (work in progress), | |||
| November 2020. | May 2021. | |||
| [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route | [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route | |||
| Reflection: An Alternative to Full Mesh Internal BGP | Reflection: An Alternative to Full Mesh Internal BGP | |||
| (IBGP)", RFC 4456, DOI 10.17487/RFC4456, April 2006, | (IBGP)", RFC 4456, DOI 10.17487/RFC4456, April 2006, | |||
| <https://www.rfc-editor.org/info/rfc4456>. | <https://www.rfc-editor.org/info/rfc4456>. | |||
| [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation | [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation | |||
| Element (PCE)-Based Architecture", RFC 4655, | Element (PCE)-Based Architecture", RFC 4655, | |||
| DOI 10.17487/RFC4655, August 2006, | DOI 10.17487/RFC4655, August 2006, | |||
| <https://www.rfc-editor.org/info/rfc4655>. | <https://www.rfc-editor.org/info/rfc4655>. | |||
| skipping to change at page 9, line 8 ¶ | skipping to change at page 9, line 8 ¶ | |||
| Huawei | Huawei | |||
| Huawei Bld., No.156 Beiqing Rd. | Huawei Bld., No.156 Beiqing Rd. | |||
| Beijing 100095 | Beijing 100095 | |||
| China | China | |||
| Email: zhuangshunwan@huawei.com | Email: zhuangshunwan@huawei.com | |||
| Ketan Talaulikar (editor) | Ketan Talaulikar (editor) | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| India | India | |||
| Email: ketant@cisco.com | Email: ketant.ietf@gmail.com | |||
| Sam Aldrin | Sam Aldrin | |||
| Google, Inc | Google, Inc | |||
| Email: aldrin.ietf@gmail.com | Email: aldrin.ietf@gmail.com | |||
| Jeff Tantsura | Jeff Tantsura | |||
| Apstra | Microsoft | |||
| Email: jefftant.ietf@gmail.com | Email: jefftant.ietf@gmail.com | |||
| Greg Mirsky | Greg Mirsky | |||
| ZTE Corp. | Ericsson | |||
| Email: gregimirsky@gmail.com | Email: gregimirsky@gmail.com | |||
| End of changes. 10 change blocks. | ||||
| 12 lines changed or deleted | 13 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/ | ||||