[Technical Errata Reported] RFC5884 (5085)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 11 August 2017 05:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B800613247C for <rtg-bfd@ietfa.amsl.com>; Thu, 10 Aug 2017 22:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id LTtLZoL80JGQ for <rtg-bfd@ietfa.amsl.com>; Thu, 10 Aug 2017 22:36:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E60B6132473 for <rtg-bfd@ietf.org>; Thu, 10 Aug 2017 22:36:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 27303B81263; Thu, 10 Aug 2017 22:35:50 -0700 (PDT)
To: rahul@juniper.net, kireeti@juniper.net, tom.nadeau@bt.com, swallow@cisco.com, akatlas@gmail.com, db3546@att.com, aretana@cisco.com, jhaas@pfrc.org, rrahman@cisco.com
Subject: [Technical Errata Reported] RFC5884 (5085)
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: balajir@juniper.net, rtg-bfd@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20170811053550.27303B81263@rfc-editor.org>
Date: Thu, 10 Aug 2017 22:35:50 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/GBtq31HDPv-c5-LWGK2rBV4MCwo>
X-Mailman-Approved-At: Fri, 11 Aug 2017 10:23:59 -0700
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
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, 11 Aug 2017 05:36:07 -0000

The following errata report has been submitted for RFC5884,
"Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)".

You may review the report below and at:

Type: Technical
Reported by: Balaji Rajagopalan <balajir@juniper.net>;

Section: 6

Original Text
The egress LSR MAY respond with an LSP Ping Echo
reply message that carries the local discriminator assigned by it for
the BFD session.

Corrected Text
The egress LSR MUST respond with an LSP Ping Echo reply message that
MAY carry the local discriminator assigned by it for the BFD session.

It is not clear from the original text which of the following is optional:
  -  The egress MUST send a reply, but the discriminator in the reply is optional
  -  The reply itself is optional
Technically, the reply cannot be optional, because the egress needs to report LSP-Ping verification status to the ingress.

The proposed text recommends to include BFD discriminator in the reply. This was the intent of the original text.

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. 

RFC5884 (draft-ietf-bfd-mpls-07)
Title               : Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)
Publication Date    : June 2010
Author(s)           : R. Aggarwal, K. Kompella, T. Nadeau, G. Swallow
Category            : PROPOSED STANDARD
Source              : Bidirectional Forwarding Detection
Area                : Routing
Stream              : IETF
Verifying Party     : IESG