| draft-ietf-bfd-unsolicited-01.txt | draft-ietf-bfd-unsolicited-02.txt | |||
|---|---|---|---|---|
| Network Working Group E. Chen | Network Working Group E. Chen | |||
| Internet-Draft N. Shen | Internet-Draft Cisco Systems | |||
| Intended status: Standards Track Cisco Systems | Intended status: Standards Track N. Shen | |||
| Expires: December 30, 2019 R. Raszuk | Expires: January 29, 2021 Zededa | |||
| R. Raszuk | ||||
| Bloomberg LP | Bloomberg LP | |||
| R. Rahman | R. Rahman | |||
| Cisco Systems | Cisco Systems | |||
| June 28, 2019 | July 28, 2020 | |||
| Unsolicited BFD for Sessionless Applications | Unsolicited BFD for Sessionless Applications | |||
| draft-ietf-bfd-unsolicited-01 | draft-ietf-bfd-unsolicited-02 | |||
| Abstract | Abstract | |||
| For operational simplification of "sessionless" applications using | For operational simplification of "sessionless" applications using | |||
| BFD, in this document we present procedures for "unsolicited BFD" | BFD, in this document we present procedures for "unsolicited BFD" | |||
| that allow a BFD session to be initiated by only one side, and be | that allow a BFD session to be initiated by only one side, and be | |||
| established without explicit per-session configuration or | established without explicit per-session configuration or | |||
| registration by the other side (subject to certain per-interface or | registration by the other side (subject to certain per-interface or | |||
| per-router policies). | per-router policies). | |||
| skipping to change at page 1, line 47 ¶ | 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 December 30, 2019. | This Internet-Draft will expire on January 29, 2021. | |||
| 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 10, line 39 ¶ | skipping to change at page 10, line 39 ¶ | |||
| /routing/control-plane-protocols/control-plane-protocol/bfd/ip-sh | /routing/control-plane-protocols/control-plane-protocol/bfd/ip-sh | |||
| /sessions/session/unsolicited: access to this information discloses | /sessions/session/unsolicited: access to this information discloses | |||
| the role of the local system in the creation of the unsolicited BFD | the role of the local system in the creation of the unsolicited BFD | |||
| session. | session. | |||
| 6. References | 6. References | |||
| 6.1. Normative References | 6.1. Normative References | |||
| [I-D.ietf-bfd-yang] | [I-D.ietf-bfd-yang] | |||
| Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and | Rahman, R., Zheng, L., Jethanandani, M., Pallagatti, S., | |||
| G. Mirsky, "YANG Data Model for Bidirectional Forwarding | and G. Mirsky, "YANG Data Model for Bidirectional | |||
| Detection (BFD)", draft-ietf-bfd-yang-17 (work in | Forwarding Detection (BFD)", draft-ietf-bfd-yang-17 (work | |||
| progress), August 2018. | in progress), August 2018. | |||
| [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>. | |||
| [RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., Ed., and C. | [RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., Ed., and C. | |||
| Pignataro, "The Generalized TTL Security Mechanism | Pignataro, "The Generalized TTL Security Mechanism | |||
| (GTSM)", RFC 5082, DOI 10.17487/RFC5082, October 2007, | (GTSM)", RFC 5082, DOI 10.17487/RFC5082, October 2007, | |||
| <https://www.rfc-editor.org/info/rfc5082>. | <https://www.rfc-editor.org/info/rfc5082>. | |||
| skipping to change at page 11, line 46 ¶ | skipping to change at page 11, line 46 ¶ | |||
| [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>. | |||
| 6.2. Informative References | 6.2. Informative References | |||
| [I-D.ietf-idr-rs-bfd] | [I-D.ietf-idr-rs-bfd] | |||
| Bush, R., Haas, J., Scudder, J., Nipper, A., and C. | Bush, R., Haas, J., Scudder, J., Nipper, A., and C. | |||
| Dietzel, "Making Route Servers Aware of Data Link Failures | Dietzel, "Making Route Servers Aware of Data Link Failures | |||
| at IXPs", draft-ietf-idr-rs-bfd-07 (work in progress), | at IXPs", draft-ietf-idr-rs-bfd-08 (work in progress), | |||
| March 2019. | September 2019. | |||
| [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A | [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A | |||
| Border Gateway Protocol 4 (BGP-4)", RFC 4271, | Border Gateway Protocol 4 (BGP-4)", RFC 4271, | |||
| DOI 10.17487/RFC4271, January 2006, | DOI 10.17487/RFC4271, January 2006, | |||
| <https://www.rfc-editor.org/info/rfc4271>. | <https://www.rfc-editor.org/info/rfc4271>. | |||
| [RFC7880] Pignataro, C., Ward, D., Akiya, N., Bhatia, M., and S. | [RFC7880] Pignataro, C., Ward, D., Akiya, N., Bhatia, M., and S. | |||
| Pallagatti, "Seamless Bidirectional Forwarding Detection | Pallagatti, "Seamless Bidirectional Forwarding Detection | |||
| (S-BFD)", RFC 7880, DOI 10.17487/RFC7880, July 2016, | (S-BFD)", RFC 7880, DOI 10.17487/RFC7880, July 2016, | |||
| <https://www.rfc-editor.org/info/rfc7880>. | <https://www.rfc-editor.org/info/rfc7880>. | |||
| skipping to change at page 12, line 31 ¶ | skipping to change at page 12, line 31 ¶ | |||
| Enke Chen | Enke Chen | |||
| Cisco Systems | Cisco Systems | |||
| 560 McCarthy Blvd. | 560 McCarthy Blvd. | |||
| Milpitas, CA 95035 | Milpitas, CA 95035 | |||
| USA | USA | |||
| Email: enkechen@cisco.com | Email: enkechen@cisco.com | |||
| Naiming Shen | Naiming Shen | |||
| Cisco Systems | Zededa | |||
| 560 McCarthy Blvd. | ||||
| Milpitas, CA 95035 | ||||
| USA | ||||
| Email: naiming@cisco.com | Email: naiming@zededa.com | |||
| Robert Raszuk | Robert Raszuk | |||
| Bloomberg LP | Bloomberg LP | |||
| 731 Lexington Ave | 731 Lexington Ave | |||
| New York City, NY 10022 | New York City, NY 10022 | |||
| USA | USA | |||
| Email: robert@raszuk.net | Email: robert@raszuk.net | |||
| Reshad Rahman | Reshad Rahman | |||
| Cisco Systems | Cisco Systems | |||
| 2000 Innovation Drive | 2000 Innovation Drive | |||
| Kanata, Ontario K2K 3E8 | Kanata, Ontario K2K 3E8 | |||
| Canada | Canada | |||
| Email: rrahman@cisco.com | Email: rrahman@cisco.com | |||
| End of changes. 10 change blocks. | ||||
| 18 lines changed or deleted | 17 lines changed or added | |||
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||