I don’t understand the point of the change (which is also grammatically incorrect.)
—Dave > On Jan 15, 2022, at 7:01 AM, RFC Errata System <[email protected]> > wrote: > > [External Email. Be cautious of content] > > > The following errata report has been submitted for RFC5880, > "Bidirectional Forwarding Detection (BFD)". > > -------------------------------------- > You may review the report below and at: > https://urldefense.com/v3/__https://www.rfc-editor.org/errata/eid6818__;!!NEt6yMaO-gk!Ra5HUkg5sPHd17WHgnWnUr4pI3dlhgQPO6rUvJ3rHV3CvdecLxi_nliiBbmKOx8$ > > -------------------------------------- > Type: Technical > Reported by: Nikolai Malykh <[email protected]> > > Section: 6.7.2 > > Original Text > ------------- > If the Auth Len field is not equal to the length of the password > selected by the key ID, plus three, the packet MUST be discarded. > > > Corrected Text > -------------- > If the Auth Len field is not match to the length of the password > selected by the key ID, plus three, the packet MUST be discarded. > > > Notes > ----- > The value of the Auth Len field is the length of the password plus 3. > > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > 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
