| < draft-ietf-idr-bgp-bfd-strict-mode-02.txt | draft-ietf-idr-bgp-bfd-strict-mode-03.txt > | |||
|---|---|---|---|---|
| IDR Workgroup M. Zheng | IDR Workgroup M. Zheng | |||
| Internet-Draft Individual Contributor | Internet-Draft Ciena | |||
| Intended status: Standards Track A. Lindem | Intended status: Standards Track A. Lindem | |||
| Expires: May 7, 2020 Cisco Systems | Expires: November 8, 2020 Cisco Systems | |||
| J. Haas | J. Haas | |||
| Juniper Networks, Inc. | Juniper Networks, Inc. | |||
| A. Fu | A. Fu | |||
| Bloomberg L.P. | Bloomberg L.P. | |||
| November 4, 2019 | May 7, 2020 | |||
| BGP BFD Strict-Mode | BGP BFD Strict-Mode | |||
| draft-ietf-idr-bgp-bfd-strict-mode-02 | draft-ietf-idr-bgp-bfd-strict-mode-03 | |||
| Abstract | Abstract | |||
| This document specifies extensions to RFC4271 BGP-4 that enable a BGP | This document specifies extensions to RFC4271 BGP-4 that enable a BGP | |||
| speaker to negotiate additional Bidirectional Forwarding Detection | speaker to negotiate additional Bidirectional Forwarding Detection | |||
| (BFD) extensions using a BGP capability. This BFD capability enables | (BFD) extensions using a BGP capability. This BFD capability enables | |||
| a BGP speaker to prevent a BGP session from being established until a | a BGP speaker to prevent a BGP session from being established until a | |||
| BFD session is established. It is referred to as BGP BFD "strict- | BFD session is established. It is referred to as BGP BFD "strict- | |||
| mode". BGP BFD strict-mode will be supported when both the local | mode". BGP BFD strict-mode will be supported when both the local | |||
| speaker and its remote peer are BFD strict-mode capable. | speaker and its remote peer are BFD strict-mode capable. | |||
| skipping to change at page 1, line 41 ¶ | skipping to change at page 1, line 41 ¶ | |||
| 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 May 7, 2020. | This Internet-Draft will expire on November 8, 2020. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2020 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 Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| skipping to change at page 5, line 37 ¶ | skipping to change at page 5, line 37 ¶ | |||
| DOI 10.17487/RFC5882, June 2010, | DOI 10.17487/RFC5882, June 2010, | |||
| <https://www.rfc-editor.org/info/rfc5882>. | <https://www.rfc-editor.org/info/rfc5882>. | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
| May 2017, <https://www.rfc-editor.org/info/rfc8174>. | May 2017, <https://www.rfc-editor.org/info/rfc8174>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Mercia Zheng | Mercia Zheng | |||
| Individual Contributor | Ciena | |||
| 3939 N. 1st Street | ||||
| San Jose, CA 95134 | ||||
| UNITED STATES | ||||
| Email: merciaz.ietf@gmail.com | Email: merciaz.ietf@gmail.com | |||
| Acee Lindem | Acee Lindem | |||
| Cisco Systems | Cisco Systems | |||
| 301 Midenhall Way | 301 Midenhall Way | |||
| GARY, NC 27513 | GARY, NC 27513 | |||
| UNITED STATES | UNITED STATES | |||
| Email: acee@cisco.com | Email: acee@cisco.com | |||
| End of changes. 7 change blocks. | ||||
| 7 lines changed or deleted | 10 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/ | ||||