Unsolicited BFD for Sessionless Applications

The current implementation and deployment practice for BFD ( and ) usually requires BFD sessions be explicitly configured or registered on both sides. This requirement is not an issue when an application like BGP has the concept of a "session" that involves both sides for its establishment. However, this requirement can be operationally challenging when the prerequisite "session" does not naturally exist between two endpoints in an application. Simultaneous configuration and coordination may be required on both sides for BFD to take effect. For example: When BFD is used to keep track of the "liveness" of the nexthop of static routes. Although only one side may need the BFD functionality, currently both sides need to be involved in specific configuration and coordination and in some cases static routes are created unnecessarily just for BFD. When BFD is used to keep track of the "liveness" of the third-pary nexthop of BGP routes received from the Route Server at an Internet Exchange Point (IXP). As the third-party nexthop is different from the peering address of the Route Server, for BFD to work, currently two routers peering with the Route Server need to have routes and nexthops from each other (although indirectly via the Route Server). Clearly it is beneficial and desirable to reduce or eliminate unnecessary configurations and coordination in these "sessionless" applications using BFD. In this document we present procedures for "unsolicited BFD" that allow a BFD session to be initiated by only one side, and established without explicit per-session configuration or registration by the other side (subject to certain per-interface or global policies). Unsolicited BFD impacts only the initiation of BFD sessions. There is no change to all the other procedures specified in such as, but not limited to, the Echo function and Demand mode. With "unsolicited BFD" there is potential risk for excessive resource usage by BFD from "unexpected" remote systems. To mitigate such risks, several mechanisms are recommended in the Security Considerations section. The procedure described in this document could be applied to BFD for Multihop paths . However, because of security risks, this document applies only to BFD for single IP hops . Compared to the "Seamless BFD" , this proposal involves only minor procedural enhancements to the widely deployed BFD itself. Thus, we believe that this proposal is inherently simpler in the protocol itself and deployment. As an example, it does not require the exchange of BFD discriminators over an out-of-band channel before BFD session bring-up. When BGP Add-Path is deployed at an IXP using a Route Server, multiple BGP paths (when they exist) can be made available to the clients of the Route Server as described in . Unsolicited BFD can be used by BGP route selection's Route Resolvability Condition to exclude routes where the NEXT_HOP is not reachable using the procedures specified in this document.

With "unsolicited BFD", one side takes the "Active role" and the other side takes only the "Passive role" as described in , section 6.1. Passive unsolicited BFD support MUST be disabled by default, and MUST require explicit configuration to be enabled. On the passive side, the following BFD parameters, from section 6.8.1 SHOULD be configurable: bfd.DesiredMinTxInterval bfd.RequiredMinRxInterval bfd.DetectMult The passive side MAY also choose to use the values of the parameters above that the active side uses in its BFD Control packets. However, the bfd.LocalDiscr value MUST be selected by the passive side to allow multiple unsolicited BFD sessions. The active side starts sending the BFD Control packets as specified in . The passive side does not send BFD Control packets initially, it sends BFD Control packets only after it has received BFD Control packets from the active side. When the passive side receives a BFD Control packet from the active side with 0 as "Your Discriminator" and does not find an existing BFD session, the passive side SHOULD create a matching BFD session toward the active side, unless not permitted by local configuration or policy. When the passive side receives an incoming BFD Control packet on a numbered interface, the source address of that packet MUST belong to the subnet of the interface on which the BFD packet is received, else the BFD control packet MUST NOT be processed. The passive side MUST then start sending BFD Control packets and perform the necessary procedure for bringing up, maintaining and tearing down the BFD session. If the BFD session fails to get established within a certain amount of time (which is implementation specific but has to be at least equal to the local failure detection time), or if an established BFD session goes down, the passive side MUST stop sending BFD Control packets and SHOULD delete the BFD session created until BFD Control packets are initiated by the active side again. When an Unsolicited BFD session goes down, an implementation may retain the session state for a period of time. Retaining this state can be useful for operational purposes.

This document defines a new state variable called Role. bfd.Role The role of the local system during BFD session initialization, as per , section 6.1. Possible values are Active or Passive.

This section extends the YANG data model for BFD to cover unsolicited BFD. The new module imports since the "bfd" container in is under "control-plane-protocol". The YANG module in this document conforms to the Network Management Datastore Architecture (NMDA) .

Configuration for unsolicited BFD parameters for IP single-hop sessions can be done at 2 levels: Globally, i.e. for all interfaces. For specific interfaces. This requires support for the "unsolicited-params-per-interface" feature. If configuration exists at both levels, per-interface configuration takes precedence over global configuration. For operational data, a new "unsolicited" container has been added for BFD IP single-hop sessions. The tree diagram below uses the graphical representation of data models, as defined in .

file "ietf-bfd-unsolicited@2023-04-22.yang" module ietf-bfd-unsolicited { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-unsolicited"; prefix "bfd-unsol"; // RFC Ed.: replace occurences of YYYY with actual RFC numbers // and remove this note import ietf-bfd-types { prefix "bfd-types"; reference "RFC 9314: YANG Data Model for Bidirectional Forwarding Detection (BFD)"; } import ietf-bfd { prefix "bfd"; reference "RFC 9314: YANG Data Model for Bidirectional Forwarding Detection (BFD)"; } import ietf-bfd-ip-sh { prefix "bfd-ip-sh"; reference "RFC 9314: YANG Data Model for Bidirectional Forwarding Detection (BFD)"; } import ietf-routing { prefix "rt"; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA version)"; } organization "IETF BFD Working Group"; contact "WG Web: WG List: Editors: Enke Chen (enchen@paloaltonetworks.com), Naiming Shen (naiming@zededa.com), Robert Raszuk (robert@raszuk.net), Reshad Rahman (reshad@yahoo.com)"; description "This module contains the YANG definition for BFD unsolicited as per RFC YYYY. Copyright (c) 2023 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC YYYY; see the RFC itself for full legal notices."; reference "RFC YYYY"; revision 2023-04-22 { description "Initial revision."; reference "RFC YYYY: Unsolicited BFD for Sessionless Applications."; } /* * Feature definitions */ feature unsolicited-params-per-interface { description "This feature indicates that the server supports per-interface parameters for unsolicited sessions."; reference "RFC YYYY: Unsolicited BFD for Sessionless Applications."; } /* * Type Definitions */ identity role { description "Base identity from which all roles are derived. Role of local system during BFD session initialization."; } identity active { base "bfd-unsol:role"; description "Active role"; reference "RFC5880: Bidirectional Forwarding Detection (BFD), Section 6.1"; } identity passive { base "bfd-unsol:role"; description "Passive role"; reference "RFC5880: Bidirectional Forwarding Detection (BFD), Section 6.1"; } /* * Augments */ augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/bfd:bfd/bfd-ip-sh:ip-sh" { description "Augmentation for BFD unsolicited parameters"; container unsolicited { description "BFD IP single-hop unsolicited top level container"; uses bfd-types:base-cfg-parms; } } augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/bfd:bfd/bfd-ip-sh:ip-sh/" + "bfd-ip-sh:interfaces" { description "Augmentation for BFD unsolicited on IP single-hop interface"; container unsolicited { description "BFD IP single-hop interface unsolicited top level container"; leaf enabled { type boolean; default false; description "BFD unsolicited enabled on this interface."; } /* * The following is the same as bfd-types:base-cfg-parms, but * without default values (for inheritance) */ leaf local-multiplier { if-feature bfd-unsol:unsolicited-params-per-interface; type bfd-types:multiplier; description "Multiplier transmitted by the local system. Defaults to ../../unsolicited/local-multiplier. A multiplier configured under an interface takes precedence over the mulitiplier configured at the global level."; } choice interval-config-type { if-feature bfd-unsol:unsolicited-params-per-interface; description "Two interval values or one value used for both transmit and receive. Defaults to ../../unsolicited/interval-config-type. An interval configured under an interface takes precedence over any interval configured at the global level."; case tx-rx-intervals { leaf desired-min-tx-interval { type uint32; units "microseconds"; description "Desired minimum transmit interval of control packets."; } leaf required-min-rx-interval { type uint32; units "microseconds"; description "Required minimum receive interval of control packets."; } } case single-interval { if-feature "bfd-types:single-minimum-interval"; leaf min-interval { type uint32; units "microseconds"; description "Desired minimum transmit interval and required minimum receive interval of control packets."; } } } } } augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/bfd:bfd/bfd-ip-sh:ip-sh/" + "bfd-ip-sh:sessions/bfd-ip-sh:session" { description "Augmentation for BFD unsolicited on IP single-hop session"; leaf role { type identityref { base "bfd-unsol:role"; } config false; description "Role."; } } }

]]>


  
  This section shows an example on how to configure the passive end of unsolicited BFD:
       
       We have global BFD IP single-hop unsolicited configuration with a local-multiplier of 2 and min-interval at 50ms
       BFD IP single-hop unsolicited is enabled on interface eth0, with a local-multiplier of 3 and min-interval at 250 ms
       BFD IP single-hop unsolicited is enabled on interface eth1. Since there is no parameter configuration for eth1, it inherits from the global configuration.
       
  
          
	  

          


  
    eth0
    ianaift:ethernetCsmacd
  
  
    eth1
    ianaift:ethernetCsmacd
  


  
    
      bfd-types:bfdv1
      name:BFD
      
        
          
            2
            50000
          
          
              eth0
              
                true
                3
                250000
              
          
          
              eth1
              
                true
              
          
        
      
    
  

       
        ]]>



	
	    
            This document registers the following namespace URI in the "IETF XML Registry" :
            
            URI:  urn:ietf:params:xml:ns:yang:ietf-bfd-unsolicited
            Registrant Contact:  The IESG.
            XML:  N/A; the requested URI is an XML namespace.
            
            This document registers the following YANG module in the "YANG Module Names" registry :
            
            Name:  ietf-bfd-unsolicited
            Namespace:  urn:ietf:params:xml:ns:yang:ietf-bfd-unsolicited
            Prefix:  bfd-unsol
            Reference:  RFC YYYY
	


	 

	Authors would like to thank Acee Lindem, Alvaro Retana, Dan Romascanu, Derek Atkins, Greg Mirsky, Gyan Mishra, Henning Rogge, Jeffrey Haas,
      John Scudder, Lars Eggert, Magnus Westerlund, Mahesh Jethanandani, Murray Kucherawy, Raj Chetan, Robert Wilton, Roman Danyliw, Tom Petch,
      and Zaheduzzaman Sarker for their review and valuable input.

	 

	
	   
	    
	    The same security considerations and protection measures as those described 
      in  and  apply 
      to this document. 

	    In addition, with "unsolicited BFD" there is potential risk for excessive resource usage 
      by BFD from "unexpected" remote systems. To mitigate such risks, implementations of unsolicited BFD MUST:
	    

	   
     
	   
     Limit the feature to specific interfaces, and to single-hop BFD sessions using the procedures from
     .  See  for the details of these procedures.
     
     
     Apply policy to process BFD packets only from certain subnets or hosts.
      
	    
     Deploy the feature only in an environment that does not 
     offer anonymous participation. Examples include an IXP, 
     where the IXP operator will have a business relationship with 
     all IXP participants, or between a provider and its customers. 
	   
	   
	    
     
     
     
     Implementations of unsolicited BFD are RECOMMENDED to
     use BFD authentication; see .
     If BFD authentication is used, the strongest BFD authentication mechanism that is supported MUST be used.
     
     
     In some environments, such as an Internet Exchange Points (IXPs), BFD authentication cannot be used because of the lack of coordination for the operation of the two endpoints of the BFD session.
     
     
     In other environments, such as when BFD is used to track the next hop of static routes, it is possible to use BFD authentication. This comes with the extra cost of configuring matching keychains between the two endpoints.
     
	   
	   
      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  or RESTCONF .
      The lowest NETCONF layer is the secure transport layer, and the
      mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the
      mandatory-to-implement secure transport is TLS .

      The NETCONF access control model  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.

      There are a number of data nodes defined in this YANG module that are
      writable/creatable/deletable (i.e., config true, which is the default).
      These data nodes may be considered sensitive or vulnerable in some
      network environments. Write operations (e.g., edit-config) to these data
      nodes without proper protection can have a negative effect on network
      operations. These are the subtrees and data nodes and their
      sensitivity/vulnerability:

      /routing/control-plane-protocols/control-plane-protocol/bfd/ip-sh
         /unsolicited:
      
      data node "enabled" enables creation of unsolicited BFD IP single-hop sessions globally, i.e. on all interfaces.
         See .
      data nodes local-multiplier, desired-min-tx-interval,
      required-min-rx-interval and min-interval all impact the parameters of the unsolicited
      BFD IP single-hop sessions. Write operations to these nodes change the
      rates of BFD packet generation and detection time of the failures of a
      BFD session.
      
      

      /routing/control-plane-protocols/control-plane-protocol/bfd/ip-sh
         /interfaces/interface/unsolicited:
      
      data node "enabled" enables creation of unsolicited BFD IP single-hop sessions on a specific interface.
         See .
      data nodes local-multiplier, desired-min-tx-interval,
      required-min-rx-interval and min-interval all impact the parameters of the unsolicited
      BFD IP single-hop sessions on the interface.
      
      

      Some of the readable data nodes in this 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. These are the subtrees and data nodes
      and their sensitivity/vulnerability:

      /routing/control-plane-protocols/control-plane-protocol/bfd/ip-sh
         /sessions/session/role:
      access to this information discloses the role of the local system in the creation of the unsolicited BFD session.