The following errata report has been verified for RFC7331, "Bidirectional Forwarding Detection (BFD) Management Information Base".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8327 -------------------------------------- Status: Verified Type: Technical Reported by: Goutham Jain <[email protected]> Date Reported: 2025-03-1 Verified by: John Scudder (IESG) Section: 5 Original Text ------------- 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." Corrected Text -------------- 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.) -------------------------------------- RFC7331 (draft-ietf-bfd-mib-22) -------------------------------------- Title : Bidirectional Forwarding Detection (BFD) Management Information Base Publication Date : August 2014 Author(s) : T. Nadeau, Z. Ali, N. Akiya Category : PROPOSED STANDARD Source : Bidirectional Forwarding Detection Stream : IETF Verifying Party : IESG
