IETF Logo Mail Archive

[GROW] [Errata Verified] RFC7854 (7703)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 11 December 2023 16:50 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EB63C14CF1A; Mon, 11 Dec 2023 08:50:22 -0800 (PST)
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.249, 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 kpaHA_iBSfIz; Mon, 11 Dec 2023 08:50:18 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 AC543C14F747; Mon, 11 Dec 2023 08:50:18 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 3F2BCE7067; Mon, 11 Dec 2023 08:50:18 -0800 (PST)
To: dhpatki@cisco.com, jgs@juniper.net, rex@cisco.com, sstuart@google.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: warren@kumari.net, iesg@ietf.org, grow@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231211165018.3F2BCE7067@rfcpa.amsl.com>
Date: Mon, 11 Dec 2023 08:50:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/m84064dpV0bj50KUTGhYMcuqwMQ>
Subject: [GROW] [Errata Verified] RFC7854 (7703)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Dec 2023 16:50:22 -0000

The following errata report has been verified for RFC7854,
"BGP Monitoring Protocol (BMP)". 

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

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

Reported by: Dhananjay S. Patki <dhpatki@cisco.com>
Date Reported: 2023-11-16
Verified by: Warren Kumari (Ops AD) (IESG)

Section: 4.2

Original Text
-------------
      *  The L flag, if set to 1, indicates that the message reflects
         the post-policy Adj-RIB-In (i.e., its path attributes reflect
         the application of inbound policy).  It is set to 0 if the
         message reflects the pre-policy Adj-RIB-In.  Locally sourced
         routes also carry an L flag of 1.  See Section 5 for further
         detail.  This flag has no significance when used with route
         mirroring messages (Section 4.7).

Corrected Text
--------------
      *  The L flag, if set to 1, indicates that the message reflects
         the post-policy Adj-RIB-In (i.e., its path attributes reflect
         the application of inbound policy).  It is set to 0 if the
         message reflects the pre-policy Adj-RIB-In.  Locally sourced
         routes also carry an L flag of 1.  See Section 5 for further
         detail.  This flag has significance only when used with Route
         Monitoring messages.

Notes
-----
The L flag is used to indicate whether the route monitoring update reflects Adj-RIB-In pre-policy or post-policy (RFC 7854), or Adj-RIB-Out pre-policy or post-policy (RFC 8671). It does not apply to any message other than the Route Monitoring message.


--------------------------------------
RFC7854 (draft-ietf-grow-bmp-17)
--------------------------------------
Title               : BGP Monitoring Protocol (BMP)
Publication Date    : June 2016
Author(s)           : J. Scudder, Ed., R. Fernando, S. Stuart
Category            : PROPOSED STANDARD
Source              : Global Routing Operations
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email