[GROW] [IANA #1292473] [Errata Verified] RFC7854 (7703)

Amanda Baber via RT <iana-matrix@iana.org> Thu, 14 December 2023 00:19 UTC

RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-matrix@iana.org>
Reply-To: iana-matrix@iana.org
In-Reply-To: <20231211165018.3F2BCE7067@rfcpa.amsl.com>
References: <RT-Ticket-1292473@icann.org> <20231211165018.3F2BCE7067@rfcpa.amsl.com>
Message-ID: <rt-5.0.3-965085-1702513185-81.1292473-37-0@icann.org>
To: rfc-editor@rfc-editor.org
CC: warren@kumari.net, sstuart@google.com, rex@cisco.com, jgs@juniper.net, grow@ietf.org, dhpatki@cisco.com
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk
Date: Thu, 14 Dec 2023 00:19:45 +0000
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/EFSf4KHx1Hf8njvJugFMX1HuWn8>
Subject: [GROW] [IANA #1292473] [Errata Verified] RFC7854 (7703)

Hi all,

Should this errata report be listed as an additional reference for the "L Flag" registration in the "BMP Peer Flags for Peer Types 0 through 2" registry? See

https://www.iana.org/assignments/bmp-parameters

thanks,

Amanda Baber
IANA Operations Manager

On Mon Dec 11 16:51:10 2023, rfc-editor@rfc-editor.org wrote:
> 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

[GROW] [Errata Verified] RFC7854 (7703) RFC Errata System
[GROW] [IANA #1292473] [Errata Verified] RFC7854 … Amanda Baber via RT
Re: [GROW] [IANA #1292473] [Errata Verified] RFC7… Dhananjay Patki (dhpatki)
[GROW] [IANA #1292473] [Errata Verified] RFC7854 … Amanda Baber via RT
Re: [GROW] [IANA #1292473] [Errata Verified] RFC7… Dhananjay Patki (dhpatki)