RFC Errata
RFC 7880, "Seamless Bidirectional Forwarding Detection (S-BFD)", July 2016
Source of RFC: bfd (rtg)
Errata ID: 5211
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Greg Mirsky
Date Reported: 2017-12-16
Rejected by: Alvaro Retana
Date Rejected: 2018-03-14
Section 6.1 says:
o bfd.SessionType: This is a new state variable that describes
the type of a particular session. Allowable values for S-BFD
sessions are:
* SBFDInitiator - an S-BFD session on a network node that
performs a continuity test to a target entity by sending S-BFD
packets.
* SBFDReflector - an S-BFD session on a network node that listens
for incoming S-BFD Control packets to local entities and
generates response S-BFD Control packets.
The bfd.SessionType variable MUST be initialized to the appropriate
type when an S-BFD session is created.
It should say:
o bfd.SessionType: This is a new state variable that describes
the type of a particular session. Allowable values for S-BFD
sessions are:
* SBFDNone - indicates that the BFD session is not of S-BFD type.
* SBFDInitiator - an S-BFD session on a network node that
performs a continuity test to a target entity by sending S-BFD
packets.
* SBFDReflector - an S-BFD session on a network node that listens
for incoming S-BFD Control packets to local entities and
generates response S-BFD Control packets.
The bfd.SessionType variable MUST be set to SBFDNone when a BFD
session other than S-BFD. The bfd.SessionType variable MUST be
initialized to the appropriate type when an S-BFD session is created.
Notes:
The original text leaves value of the new variable bfd.SessionType unspecified if the type of BFD session is other than S-BFD.
--VERIFIER NOTES--
This report goes beyond pointing out an error in the document. If the changes are to me made (or discussed beyond the thread related to this report), it should be done through the normal WG channels.
https://mailarchive.ietf.org/arch/msg/rtg-bfd/dI5Y2YXBG3kACEjX5vIZgSJHVw4