RFC Errata
Found 3 records.
Status: Verified (2)
RFC 6428, "Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile", November 2011
Note: This RFC has been updated by RFC 7214
Source of RFC: mpls (rtg)
Errata ID: 3629
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alan Davey
Date Reported: 2013-05-20
Verifier Name: Adrian Farrel
Date Verified: 2013-05-21
Section 3.5.3 says:
The length is the length of the following data: the Global_ID, Node Identifier, and Attachment Circuit ID (AC_ID) are as per [9].
It should say:
The length is the length in octets of the data following the length field. The Global_ID, Node Identifier, and Attachment Circuit ID (AC_ID) are as per [9].
Notes:
Original text gave the impression that the length related to only three fields, but it actually applies to all data following the Length field. It should also be noted that the length is counted in octets.
Errata ID: 4415
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Greg Mirsky
Date Reported: 2015-07-14
Verifier Name: Deborah Brungard
Date Verified: 2015-07-20
Section text says:
bfd.MinRxInterval
It should say:
bfd.RequiredMinRxInterval
Notes:
Throughout the text document refers to bfd.MinRxInterval even though RFC 5880 refers to this state variable as bfd.RequiredMinRxInterval.
Status: Rejected (1)
RFC 6428, "Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile", November 2011
Note: This RFC has been updated by RFC 7214
Source of RFC: mpls (rtg)
Errata ID: 6296
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Sudipta Das
Date Reported: 2020-09-29
Rejected by: Deborah Brungard
Date Rejected: 2021-02-26
Section 3.7 says:
In coordinated mode, an implementation SHOULD NOT reset bfd.RemoteDiscr until it is exiting the DOWN state.
It should say:
In coordinated mode, an implementation SHOULD reset bfd.RemoteDiscr upon transitioning to the DOWN state, due to period of a Detection Time passing without the receipt of a valid, authenticated BFD packet from the remote system.
Notes:
This section seems to imply that when a BFD session, running in coordinated mode, experiences Control Detection Timer expiry, then it SHOULD retain the remote discriminator value *and* SHOULD also transmit the same value in Down packets.
However, in the case when the remote system, configured in Passive role, has its discriminator gets changed (say, after a system reboot which had caused the Detection Timer expiry), it may reject these packets as the received Your Discriminator value is no longer valid for the current session.
So the BFD session would never come back to Up state.
In a second scenario (unrelated to above one), if the local system is configured in Passive role and experiences Control Detection Timer expiry, it may continue transmitting Down packets since the bfd.RemoteDiscr is not reset to zero.
--VERIFIER NOTES--
This should be addressed by the working group (e.g., updating or revising the RFC).