RE: Implementation/Conformance Poll for rfc5880 (draft-ietf-bfd-rfc5880bis) - Cisco Details

["Rajaguru Veluchamy (rvelucha)" <[e-mail]>]

HI Team,

Organization: Cisco Systems, Inc

Implementation Name:
IOS XR Version 4.0
IOS XE Version 12.0(31)S2
IOS NX Version 5.0(2)

Description: Details about Cisco Implementation of RFC 5880.

Maturity: Widely used in general terms.

Coverage:

  For each section, indicate if implemented or not.

  6.3: unique discriminator per session - Implemented

  6.4: Echo Function - Implemented

  6.5: Poll Sequence - Implemented

  6.6: Demand Mode   - Implemented

  6.7.2: Simple Password Authentication                                           - Not Implemented

  6.7.3: Keyed MD5 and Meticulous Keyed MD5 Authentication - Implemented

  6.7.4: Keyed SHA1 and Meticulous Keyed SHA1 Authentication - Implemented

  6.8.1: State Variables (indicate individual conformance)
    bfd.SessionState                   - Implemented
    bfd.RemoteSessionState  - Implemented
    bfd.LocalDiscr                         - Implemented
    bfd.RemoteDiscr                   - Implemented
    bfd.LocalDiag                          - Implemented
    bfd.DesiredMinTxInterval  - Implemented
    bfd.RequiredMinRxInterval              - Implemented
    bfd.RemoteMinRxInterval - Implemented
    bfd.DemandMode                 - Implemented
    bfd.RemoteDemandMode               - Implemented
    bfd.DetectMult                       - Implemented
    bfd.AuthType                           - Implemented
    bfd.RcvAuthSeq                     - Implemented
    bfd.XmitAuthSeq                   - Implemented
    bfd.AuthSeqKnown                             - Implemented

  6.8.2: Timer Negotiation      - Implemented

  6.8.3: Timer Manipulation   - Implemented

  6.8.4: Detection Time Calculation                               - Implemented

  6.8.5: Echo Function Failure Detection         - Implemented

  6.8.6: Reception of BFD Control Packets             - Implemented

  6.8.7: Transmitting BFD Control Packets             - Implemented

  6.8.8: Reception of BFD Echo Packets                            - Implemented

  6.8.9: Transmission of BFD Echo Packets             - Implemented

  6.8.10: Min Rx Interval Change                         - Implemented

  6.8.11: Min Tx Interval Change                          - Implemented

  6.8.12: Detect Multiplier Change                   - Implemented

  6.8.13: Enabling or Disabling The Echo Function - Implemented

  6.8.14: Enabling or Disabling Demand Mode             - Not Implemented

  6.8.15: Forwarding Plane Reset                     - Implemented

  6.8.16: Administrative Control                        - Implemented

  6.8.17: Concatenated Paths                                           - Implemented

  6.8.18: Session Hold Down                                             - Implemented

  9: Generalized TTL Security Mechanism                    - Implemented

Licensing: Proprietary

Implementation experience:

      -  As to Section 6.7.18 BFD session might be put on hold from being established
               with PEER, due to local system unable to run the session due to resource issues
               such as system cannot transmit BFD packets at rate which is requested. The session
               would be kept in ADMINDOWN state without packet being transmitted out.

      -  As to Section 6.6 Demand mode from received packet is processed and transmit is blocked if
                Demand mode is set. Device does not set Demand mode on BFD packets transmitted from local.

      -  As to Section 6.8.17 concatenated paths are supported only for MPLS pseudowire (VCCV endpoint).

Comments (optional):

Contact Information: Rajaguru Veluchamy - [e-mail]<mailto:[e-mail]>

Date: July 02, 2026

Regards
V.Rajaguru
XR/BFD/PI

From: Vengada Prasad Govindan (venggovi) <[e-mail]>
Sent: 24 June 2026 10:44 AM
To: Rajaguru Veluchamy (rvelucha) <[e-mail]>
Subject: FW: Implementation/Conformance Poll for rfc5880 (draft-ietf-bfd-rfc5880bis)



From: Alvaro Retana <[e-mail]<mailto:[e-mail]>>
Sent: Saturday, June 20, 2026 01:34 AM
To: [e-mail]<mailto:[e-mail]>
Subject: Implementation/Conformance Poll for rfc5880 (draft-ietf-bfd-rfc5880bis)

Hi!

This email starts an implementation/conformance poll for rfc5880.

Please consider the information requested below and reply to this poll with data about your implementation. You can do it in one of the following ways:

(1) Reply to this message.

(2) Fill out this form: https://forms.gle/M5ss7weaYebwjhRy5

(3) Submit a PR in GitHub; here's a template: https://github.com/bfd-wg/draft-ietf-bfd-rfc5880-bis/blob/main/rfc5880_Conformance.xml

Thanks!

Alvaro.


# Required Information

Organization:

Implementation Name:

Description:

Maturity:

Coverage:

  For each section, indicate if implemented or not.

  6.3: unique discriminator per session

  6.4: Echo Function

  6.5: Poll Sequence

  6.6: Demand Mode

  6.7.2: Simple Password Authentication

  6.7.3: Keyed MD5 and Meticulous Keyed MD5 Authentication

  6.7.4: Keyed SHA1 and Meticulous Keyed SHA1 Authentication

  6.8.1: State Variables (indicate individual conformance)
    bfd.SessionState
    bfd.RemoteSessionState
    bfd.LocalDiscr
    bfd.RemoteDiscr
    bfd.LocalDiag
    bfd.DesiredMinTxInterval
    bfd.RequiredMinRxInterval
    bfd.RemoteMinRxInterval
    bfd.DemandMode
    bfd.RemoteDemandMode
    bfd.DetectMult
    bfd.AuthType
    bfd.RcvAuthSeq
    bfd.XmitAuthSeq
    bfd.AuthSeqKnown

  6.8.2: Timer Negotiation

  6.8.3: Timer Manipulation

  6.8.4: Detection Time Calculation

  6.8.5: Echo Function Failure Detection

  6.8.6: Reception of BFD Control Packets

  6.8.7: Transmitting BFD Control Packets

  6.8.8: Reception of BFD Echo Packets

  6.8.9: Transmission of BFD Echo Packets

  6.8.10: Min Rx Interval Change

  6.8.11: Min Tx Interval Change

  6.8.12: Detect Multiplier Change

  6.8.13: Enabling or Disabling The Echo Function

  6.8.14: Enabling or Disabling Demand Mode

  6.8.15: Forwarding Plane Reset

  6.8.16: Administrative Control

  6.8.17: Concatenated Paths

  6.8.18: Session Hold Down

  9: Generalized TTL Security Mechanism

Licensing:

Implementation Experience:

Comments (optional):

Contact Information:

Date: