BFD Stability
draft-ietf-bfd-stability-12
Document | Type | Active Internet-Draft (bfd WG) | |
---|---|---|---|
Authors | Ashesh Mishra , Mahesh Jethanandani , Ankur Saxena , Santosh Pallagatti , Mach Chen , Peng Fan | ||
Last updated | 2024-01-31 | ||
Replaces | draft-ashesh-bfd-stability | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Proposed Standard | ||
Formats | |||
Yang Validation | 0 errors, 0 warnings | ||
Reviews |
YANGDOCTORS Last Call review
(of
-08)
by Ebben Aries
Ready w/nits
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | Held by WG | |
Document shepherd | Reshad Rahman | ||
Shepherd write-up | Show Last changed 2020-07-23 | ||
IESG | IESG state | I-D Exists | |
Consensus boilerplate | Yes | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | Reshad Rahman <rrahman@cisco.com> |
draft-ietf-bfd-stability-12
quot;; } description "Augment the 'bfd' container to add attributes related to BFD stability."; } augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/bfd:bfd/bfd-lag:lag/" + "bfd-lag:sessions/bfd-lag:session/bfd-lag:member-links/" + "bfd-lag:micro-bfd-ipv4/bfd-lag:session-statistics" { leaf lost-packet-count { type yang:counter32; description "Number of BFD packets that were lost without bringing the session down. This counter should be present only if stability is configured."; } description "Augment the 'bfd' container to add attributes related to BFD stability."; } augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/bfd:bfd/bfd-mpls:mpls/" + "bfd-mpls:session-groups/bfd-mpls:session-group/" + "bfd-mpls:sessions/bfd-mpls:session-statistics" { leaf lost-packet-count { type yang:counter32; description "Number of BFD packets that were lost without bringing the session down. This counter should be present only if stability is configured."; Mishra, et al. Expires 3 August 2024 [Page 10] Internet-Draft BFD Stability January 2024 } description "Augment the 'bfd' container to add attributes related to BFD stability."; } } <CODE ENDS> 7. IANA Considerations 7.1. The "IETF XML" Registry This document registers one URIs in the "ns" subregistry of the "IETF XML" registry [RFC3688]. Following the format in [RFC3688], the following registration is requested: URI: urn:ietf:params:xml:ns:yang:ietf-bfd-stability Registrant Contact: The IESG XML: N/A, the requested URI is an XML namespace. 7.2. The "YANG Module Names" Registry This document registers one YANG modules in the "YANG Module Names" registry [RFC6020]. Following the format in [RFC6020], the following registrations are requested: name: ietf-bfd-stability namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-stability prefix: bfds reference: RFC XXXX 8. Security Consideration The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446]. The NETCONF Access Control Model (NACM) [RFC8341] provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. The YANG module does not define any writeable/creatable/deletable data nodes that can have an adverse impact on a BFD session. Mishra, et al. Expires 3 August 2024 [Page 11] Internet-Draft BFD Stability January 2024 The only readable data nodes in YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. The model defines a read-only variables to indicate the number of packets that were lost. Access to this information may allow a malicious user information on which links are experiencing issues. The YANG module does not define any RPC operations. 9. Contributors The authors of this document would like to acknowledge Jeff Haas as a contributor to this document. Jeff played a role not only as a shepherd but also actively contributed to the improvement of the document. In addition, Manav Bhatia also contributed to this document. 10. Acknowledgements Authors would like to thank Nobo Akiya, Jeffery Haas, Dileep Singh, Basil Saji, Sagar Soni, Albert Fu and Mallik Mudigonda who also contributed to this document. 11. Normative References [I-D.ietf-bfd-optimizing-authentication] Jethanandani, M., Mishra, A., Saxena, A., and M. Bhatia, "Optimizing BFD Authentication", Work in Progress, Internet-Draft, draft-ietf-bfd-optimizing-authentication- 13, 1 August 2021, <https://datatracker.ietf.org/doc/html/ draft-ietf-bfd-optimizing-authentication-13>. [I-D.ietf-bfd-secure-sequence-numbers] DeKok, A., Jethanandani, M., Agarwal, S., Mishra, A., and A. Saxena, "Secure BFD Sequence Numbers", Work in Progress, Internet-Draft, draft-ietf-bfd-secure-sequence- numbers-12, 29 November 2023, <https://datatracker.ietf.org/doc/html/draft-ietf-bfd- secure-sequence-numbers-12>. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>. Mishra, et al. Expires 3 August 2024 [Page 12] Internet-Draft BFD Stability January 2024 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-editor.org/info/rfc3688>. [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, <https://www.rfc-editor.org/info/rfc5880>. [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, <https://www.rfc-editor.org/info/rfc6020>. [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, <https://www.rfc-editor.org/info/rfc6241>. [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, <https://www.rfc-editor.org/info/rfc6242>. [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, <https://www.rfc-editor.org/info/rfc6991>. [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, <https://www.rfc-editor.org/info/rfc8040>. [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>. [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration Access Control Model", STD 91, RFC 8341, DOI 10.17487/RFC8341, March 2018, <https://www.rfc-editor.org/info/rfc8341>. [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for Routing Management (NMDA Version)", RFC 8349, DOI 10.17487/RFC8349, March 2018, <https://www.rfc-editor.org/info/rfc8349>. [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, <https://www.rfc-editor.org/info/rfc8446>. Mishra, et al. Expires 3 August 2024 [Page 13] Internet-Draft BFD Stability January 2024 [RFC9314] Jethanandani, M., Ed., Rahman, R., Ed., Zheng, L., Ed., Pallagatti, S., and G. Mirsky, "YANG Data Model for Bidirectional Forwarding Detection (BFD)", RFC 9314, DOI 10.17487/RFC9314, September 2022, <https://www.rfc-editor.org/info/rfc9314>. Appendix A. Examples This section tries to show some examples in how the model can be configured for stability. A.1. Single Hop BFD Configuration This example demonstrates how a Single Hop BFD session can be configured to enable monitoring of a session for stability. =============== NOTE: '\' line wrapping per RFC 8792 =============== <?xml version="1.0" encoding="UTF-8"?> <key-chains xmlns="urn:ietf:params:xml:ns:yang:ietf-key-chain" xmlns:kc="urn:ietf:params:xml:ns:yang:ietf-key-chain"> <key-chain> <name>bfd-stability-config</name> <description>"An example for BFD Stabalized configuration."</de\ scription> <key> <key-id>55</key-id> <lifetime> <send-lifetime> <start-date-time>2017-01-01T00:00:00Z</start-date-time> <end-date-time>2017-02-01T00:00:00Z</end-date-time> </send-lifetime> <accept-lifetime> <start-date-time>2016-12-31T23:59:55Z</start-date-time> <end-date-time>2017-02-01T00:00:05Z</end-date-time> </accept-lifetime> </lifetime> <crypto-algorithm>kc:sha-1</crypto-algorithm> </key> </key-chain> </key-chains> <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns:if-type="urn:ietf:params:xml:ns:yang:iana-if-type"> <interface> <name>eth0</name> <type>if-type:ethernetCsmacd</type> Mishra, et al. Expires 3 August 2024 [Page 14] Internet-Draft BFD Stability January 2024 </interface> </interfaces> <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing" xmlns:bfd-types="urn:ietf:params:xml:ns:yang:ietf-bfd-types" xmlns:stability="urn:ietf:params:xml:ns:yang:ietf-bfd-stability\ "> <control-plane-protocols> <control-plane-protocol> <type>bfd-types:bfdv1</type> <name>name:BFD</name> <bfd xmlns="urn:ietf:params:xml:ns:yang:ietf-bfd"> <ip-sh xmlns="urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh"> <sessions> <session> <interface>eth0</interface> <dest-addr>2001:db8:0:113::101</dest-addr> <desired-min-tx-interval>10000</desired-min-tx-interv\ al> <required-min-rx-interval> 10000 </required-min-rx-interval> <stability:stability>true</stability:stability> <authentication> <key-chain>bfd-stability-config</key-chain> <meticulous>true</meticulous> </authentication> </session> </sessions> </ip-sh> </bfd> </control-plane-protocol> </control-plane-protocols> </routing> Authors' Addresses Ashesh Mishra Aalyria Technologies Email: ashesh@aalyria.com Mahesh Jethanandani Kloud Services CA United States of America Email: mjethanandani@gmail.com Mishra, et al. Expires 3 August 2024 [Page 15] Internet-Draft BFD Stability January 2024 Ankur Saxena Ciena Corporation 3939 North 1st Street San Jose, CA 95134 United States of America Email: ankurpsaxena@gmail.com URI: www.ciena.com Santosh Pallagatti VMware Bangalore 560103 Karnataka India Email: santosh.pallagatti@gmail.com Mach Chen Huawei Email: mach.chen@huawei.com Peng Fan China Mobile 32 Xuanwumen West Street Beijing Beijing, China Email: fanp08@gmail.com Mishra, et al. Expires 3 August 2024 [Page 16]