The following errata report has been verified for RFC5880,
"Bidirectional Forwarding Detection (BFD)". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7083

--------------------------------------
Status: Verified
Type: Technical

Reported by: Glebs Ivanovskis <gl...@mikrotik.com>
Date Reported: 2022-08-12
Verified by: John Scudder (IESG)

Section: 6.7.4

Original Text
-------------
Otherwise (bfd.AuthSeqKnown is 0), bfd.AuthSeqKnown MUST be set to
1, bfd.RcvAuthSeq MUST be set to the value of the received
Sequence Number field, and the received packet MUST be accepted.

Replace the contents of the Auth Key/Hash field with the
authentication key selected by the received Auth Key ID field.  If
the SHA1 hash of the entire BFD Control packet is equal to the
received value of the Auth Key/Hash field, the received packet
MUST be accepted.  Otherwise (the hash does not match the Auth
Key/Hash field), the received packet MUST be discarded.

Corrected Text
--------------
Replace the contents of the Auth Key/Hash field with the
authentication key selected by the received Auth Key ID field.  If
the SHA1 hash of the entire BFD Control packet is not equal to the
received value of the Auth Key/Hash field, the received packet
MUST be discarded.

Otherwise, the packet MUST be accepted, bfd.AuthSeqKnown MUST be set to
1, and bfd.RcvAuthSeq MUST be set to the value of the received
Sequence Number field.

Notes
-----
1. Don't manipulate bfd.AuthSeqKnown and bfd.RcvAuthSeq before Auth Key/Hash 
check.
2. Explicitly mention what bfd.AuthSeqKnown and bfd.RcvAuthSeq must be set to 
in both cases (bfd.AuthSeqKnown is 0 and bfd.AuthSeqKnown is 1).

Based on email exchange: 
https://mailarchive.ietf.org/arch/msg/rtg-bfd/lDxFfNpqo4kwuNEUY0AbjMBb8JU/

(See also 
https://mailarchive.ietf.org/arch/msg/rtg-bfd/Ngf3Chmpy_EqNPlmuMZOslayy2E/)

--------------------------------------
RFC5880 (draft-ietf-bfd-base-11)
--------------------------------------
Title               : Bidirectional Forwarding Detection (BFD)
Publication Date    : June 2010
Author(s)           : D. Katz, D. Ward
Category            : PROPOSED STANDARD
Source              : Bidirectional Forwarding Detection
Area                : Routing
Stream              : IETF
Verifying Party     : IESG

Reply via email to