draft-ietf-bfd-unsolicited-08.txt   draft-ietf-bfd-unsolicited-09.txt 
Network Working Group E. Chen Network Working Group E. Chen
Internet-Draft Palo Alto Networks Internet-Draft Palo Alto Networks
Intended status: Standards Track N. Shen Intended status: Standards Track N. Shen
Expires: 30 May 2022 Zededa Expires: 6 June 2022 Zededa
R. Raszuk R. Raszuk
NTT Network Innovations NTT Network Innovations
R. Rahman R. Rahman
26 November 2021 3 December 2021
Unsolicited BFD for Sessionless Applications Unsolicited BFD for Sessionless Applications
draft-ietf-bfd-unsolicited-08 draft-ietf-bfd-unsolicited-09
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 2, line 4 skipping to change at page 2, line 4
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 30 May 2022. This Internet-Draft will expire on 6 June 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 (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
skipping to change at page 2, line 31 skipping to change at page 2, line 31
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Procedures for Unsolicited BFD . . . . . . . . . . . . . . . 3 2. Procedures for Unsolicited BFD . . . . . . . . . . . . . . . 3
3. State Variables . . . . . . . . . . . . . . . . . . . . . . . 4 3. State Variables . . . . . . . . . . . . . . . . . . . . . . . 4
4. YANG Data Model . . . . . . . . . . . . . . . . . . . . . . . 5 4. YANG Data Model . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Unsolicited BFD Hierarchy . . . . . . . . . . . . . . . . 5 4.1. Unsolicited BFD Hierarchy . . . . . . . . . . . . . . . . 5
4.2. Unsolicited BFD Module . . . . . . . . . . . . . . . . . 6 4.2. Unsolicited BFD Module . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7.1. BFD Protocol Security Considerations . . . . . . . . . . 10 7.1. BFD Protocol Security Considerations . . . . . . . . . . 11
7.2. YANG Module Security Considerations . . . . . . . . . . . 11 7.2. YANG Module Security Considerations . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . 13 8.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
The current implementation and deployment practice for BFD ([RFC5880] The current implementation and deployment practice for BFD ([RFC5880]
and [RFC5881]) usually requires BFD sessions be explicitly configured and [RFC5881]) usually requires BFD sessions be explicitly configured
or registered on both sides. This requirement is not an issue when or registered on both sides. This requirement is not an issue when
an application like BGP [RFC4271] has the concept of a "session" that an application like BGP [RFC4271] has the concept of a "session" that
involves both sides for its establishment. However, this requirement involves both sides for its establishment. However, this requirement
can be operationally challenging when the prerequisite "session" does can be operationally challenging when the prerequisite "session" does
skipping to change at page 6, line 21 skipping to change at page 6, line 22
+--rw (interval-config-type)? +--rw (interval-config-type)?
+--:(tx-rx-intervals) +--:(tx-rx-intervals)
| +--rw desired-min-tx-interval? uint32 | +--rw desired-min-tx-interval? uint32
| +--rw required-min-rx-interval? uint32 | +--rw required-min-rx-interval? uint32
+--:(single-interval) {single-minimum-interval}? +--:(single-interval) {single-minimum-interval}?
+--rw min-interval? uint32 +--rw min-interval? uint32
augment /rt:routing/rt:control-plane-protocols augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/bfd:bfd/bfd-ip-sh:ip-sh /rt:control-plane-protocol/bfd:bfd/bfd-ip-sh:ip-sh
/bfd-ip-sh:interfaces: /bfd-ip-sh:interfaces:
+--rw unsolicited {bfd-unsol:unsolicited-params-per-interface}? +--rw unsolicited {bfd-unsol:unsolicited-params-per-interface}?
+--rw enabled boolean +--rw enabled? boolean
+--rw local-multiplier? multiplier +--rw local-multiplier? multiplier
+--rw (interval-config-type)? +--rw (interval-config-type)?
+--:(tx-rx-intervals) +--:(tx-rx-intervals)
| +--rw desired-min-tx-interval? uint32 | +--rw desired-min-tx-interval? uint32
| +--rw required-min-rx-interval? uint32 | +--rw required-min-rx-interval? uint32
+--:(single-interval) {single-minimum-interval}? +--:(single-interval) {single-minimum-interval}?
+--rw min-interval? uint32 +--rw min-interval? uint32
augment /rt:routing/rt:control-plane-protocols augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/bfd:bfd/bfd-ip-sh:ip-sh /rt:control-plane-protocol/bfd:bfd/bfd-ip-sh:ip-sh
/bfd-ip-sh:sessions/bfd-ip-sh:session: /bfd-ip-sh:sessions/bfd-ip-sh:session:
 End of changes. 7 change blocks. 
7 lines changed or deleted 7 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/