Found 3 records.

Status: Verified (2)

RFC 7331, "Bidirectional Forwarding Detection (BFD) Management Information Base", August 2014

Errata ID: 8327
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Goutham Jain
Date Reported: 2025-03-01
Verifier Name: John Scudder
Date Verified: 2025-03-18

Section 5 says:

bfdSessUp NOTIFICATION-TYPE
     OBJECTS {
         bfdSessDiag, -- low range value
         bfdSessDiag  -- high range value
     }
     STATUS     current
     DESCRIPTION
         "This notification is generated when the
          bfdSessState object for one or more contiguous
          entries in bfdSessTable are about to enter the up(4)
          state from some other state.  The included values of
          bfdSessDiag MUST both be set equal to this
          new state (i.e., up(4)).  The two instances of
          bfdSessDiag in this notification indicate the range
          of indexes that are affected.  Note that all the indexes
          of the two ends of the range can be derived from the
          instance identifiers of these two objects.  For the
          cases where a contiguous range of sessions
          have transitioned into the up(4) state at roughly
          the same time, the device SHOULD issue a single
          notification for each range of contiguous indexes in
          an effort to minimize the emission of a large number
          of notifications.  If a notification has to be
          issued for just a single bfdSessEntry, then
          the instance identifier (and values) of the two
          bfdSessDiag objects MUST be identical."
     ::= { bfdNotifications 1 }

 bfdSessDown NOTIFICATION-TYPE
     OBJECTS {
         bfdSessDiag, -- low range value
         bfdSessDiag  -- high range value
     }
     STATUS     current
     DESCRIPTION
         "This notification is generated when the
          bfdSessState object for one or more contiguous
          entries in bfdSessTable are about to enter the down(2)
          or adminDown(1) states from some other state.  The included
          values of bfdSessDiag MUST both be set equal to this new
          state (i.e., down(2) or adminDown(1)).  The two instances
          of bfdSessDiag in this notification indicate the range
          of indexes that are affected.  Note that all the indexes
          of the two ends of the range can be derived from the
          instance identifiers of these two objects.  For
          cases where a contiguous range of sessions
          have transitioned into the down(2) or adminDown(1) states
          at roughly the same time, the device SHOULD issue a single
          notification for each range of contiguous indexes in
          an effort to minimize the emission of a large number
          of notifications.  If a notification has to be
          issued for just a single bfdSessEntry, then
          the instance identifier (and values) of the two
          bfdSessDiag objects MUST be identical."

It should say:

bfdSessUp NOTIFICATION-TYPE
     OBJECTS {
         bfdSessDiag, -- low range value
         bfdSessDiag  -- high range value
     }
     STATUS     current
     DESCRIPTION
         "This notification is generated when the
          bfdSessState object for one or more contiguous
          entries in bfdSessTable are about to enter the up(4)
          state from some other state.  The current values of
          bfdSessDiag MUST be included. The two instances of
          bfdSessDiag in this notification indicate the range
          of indexes that are affected.  Note that all the indexes
          of the two ends of the range can be derived from the
          instance identifiers of these two objects.  For the
          state from some other state.  The current values of
          bfdSessDiag MUST be included. The two instances of
          the same time, the device SHOULD issue a single
          notification for each range of contiguous indexes in
          an effort to minimize the emission of a large number
          of notifications.  If a notification has to be
          issued for just a single bfdSessEntry, then
          the instance identifier (and values) of the two
          bfdSessDiag objects MUST be identical."
     ::= { bfdNotifications 1 }

 bfdSessDown NOTIFICATION-TYPE
     OBJECTS {
         bfdSessDiag, -- low range value
         bfdSessDiag  -- high range value
     }
     STATUS     current
     DESCRIPTION
         "This notification is generated when the
          bfdSessState object for one or more contiguous
          entries in bfdSessTable are about to enter the down(2)
          or adminDown(1) states from some other state.  The current
          values of bfdSessDiag MUST be included.  The two instances
          of bfdSessDiag in this notification indicate the range
          of indexes that are affected.  Note that all the indexes
          of the two ends of the range can be derived from the
          instance identifiers of these two objects.  For
          cases where a contiguous range of sessions
          have transitioned into the down(2) or adminDown(1) states
          at roughly the same time, the device SHOULD issue a single
          notification for each range of contiguous indexes in
          an effort to minimize the emission of a large number
          of notifications.  If a notification has to be
          issued for just a single bfdSessEntry, then
          the instance identifier (and values) of the two
          bfdSessDiag objects MUST be identical."

Notes:

See discussion at https://mailarchive.ietf.org/arch/msg/rtg-bfd/TGQZeib-j2NAZL2PFPrTykfSLoE/

The changes are

OLD:
state from some other state. The included values of
bfdSessDiag MUST both be set equal to this
new state (i.e., up(4)). The two instances of

NEW:
state from some other state. The current values of
bfdSessDiag MUST be included. The two instances of

and

OLD:
or adminDown(1) states from some other state. The included
values of bfdSessDiag MUST both be set equal to this new
state (i.e., down(2) or adminDown(1)). The two instances

NEW:
or adminDown(1) states from some other state. The current
values of bfdSessDiag MUST be included. The two instances

(The up(4), down(2), and adminDown(1) states are not defined for bfdSessDiag.)

Errata ID: 4214
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Jeffrey Haas
Date Reported: 2014-12-30
Verifier Name: Adrian Farrel
Date Verified: 2015-01-03

Section Various says:

bfdSessionTable, bfdSessionPerfTable 

It should say:

bfdSessTable, bfdSessPerfTable

Notes:

Throughout the document, bfdSessionTable and bfdSessionPerfTable are used in various text. The underlying MIB OBJECT-TYPEs are bfdSessTable and bfdSessPerfTable. While these discrepancies occur within the MIB module itself, they do not do so in any component that impacts compilation of the MIB module.

Status: Held for Document Update (1)

RFC 7331, "Bidirectional Forwarding Detection (BFD) Management Information Base", August 2014

Errata ID: 4441
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Rui Lin
Date Reported: 2015-08-09
Held for Document Update by: Alvaro Retana
Date Held: 2015-08-11

Section 4.5 says:

Given bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr,
bfdSessDstAddrType, and bfdSessSrcAddrType, the BFD Session IP
Mapping Table maps to an associated BFD session found in the
bfdSessionTable.

It should say:

Given bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr,
bfdSessDstAddrType, and bfdSessDstAddr, the BFD Session IP
Mapping Table maps to an associated BFD session found in the
bfdSessionTable.

Notes:

Duplicate bfdSessSrcAddrType but missing bfdSessDstAddr

(Alvaro Retana): the MIB Module itself has the correct description.

Report New Errata