[Technical Errata Reported] RFC5880 (7082)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 12 August 2022 14:11 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C6BDC14F73E for <rtg-bfd@ietfa.amsl.com>; Fri, 12 Aug 2022 07:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kzvWaqN-cqK0 for <rtg-bfd@ietfa.amsl.com>; Fri, 12 Aug 2022 07:11:51 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43659C14F732 for <rtg-bfd@ietf.org>; Fri, 12 Aug 2022 07:11:51 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 29F126AAE9; Fri, 12 Aug 2022 07:11:51 -0700 (PDT)
To: dkatz@juniper.net, dward@juniper.net, aretana.ietf@gmail.com, jgs@juniper.net, andrew-ietf@liquid.tech, jhaas@pfrc.org, reshad@yahoo.com
Subject: [Technical Errata Reported] RFC5880 (7082)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: glebs@mikrotik.com, rtg-bfd@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220812141151.29F126AAE9@rfcpa.amsl.com>
Date: Fri, 12 Aug 2022 07:11:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/Jk4AzhGptj4gz0bvU2ZBl4Mg5-0>
X-Mailman-Approved-At: Fri, 12 Aug 2022 07:41:00 -0700
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2022 14:11:55 -0000
The following errata report has been submitted for RFC5880, "Bidirectional Forwarding Detection (BFD)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7082 -------------------------------------- Type: Technical Reported by: Glebs Ivanovskis <glebs@mikrotik.com> Section: 6.7.3 Original Text ------------- Otherwise (bfd.AuthSeqKnown is 0), bfd.AuthSeqKnown MUST be set to 1, and bfd.RcvAuthSeq MUST be set to the value of the received Sequence Number field. Replace the contents of the Auth Key/Digest field with the authentication key selected by the received Auth Key ID field. If the MD5 digest of the entire BFD Control packet is equal to the received value of the Auth Key/Digest field, the received packet MUST be accepted. Otherwise (the digest does not match the Auth Key/Digest field), the received packet MUST be discarded. Corrected Text -------------- Replace the contents of the Auth Key/Digest field with the authentication key selected by the received Auth Key ID field. If the MD5 digest of the entire BFD Control packet is not equal to the received value of the Auth Key/Digest 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/Digest 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/ 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
- [Technical Errata Reported] RFC5880 (7082) RFC Errata System
- Re: [Technical Errata Reported] RFC5880 (7082) John Scudder
- Re: [Technical Errata Reported] RFC5880 (7082) Dave Katz