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

["Dhananjay Patki (dhpatki)" <[e-mail]>]

Thanks Amanda!
--
Regards,
Dhananjay

From: Amanda Baber via RT <[e-mail]>
Date: Thursday, 21 December 2023 at 7:34 AM
To: [e-mail] <[e-mail]>
Cc: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, Rex Fernando (rex) <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, Dhananjay Patki (dhpatki) <[e-mail]>
Subject: [IANA #1292473] [Errata Verified] RFC7854 (7703)
Hi Dhananjay,

Sorry about the delay. I've added a link to the errata report:

1       L flag  [RFC7854][RFC Errata 7703]

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

thanks,
Amanda

On Thu Dec 14 06:00:50 2023, [e-mail] wrote:
> Hi Amanda,
>
> Yes, it would indeed be useful.
> --
> Regards,
> Dhananjay
>
> From: Amanda Baber via RT <[e-mail]>
> Date: Thursday, 14 December 2023 at 5:49 AM
> To: [e-mail] <[e-mail]>
> Cc: [e-mail] <[e-mail]>, [e-mail]
> <[e-mail]>, Rex Fernando (rex) <[e-mail]>,
> [e-mail] <[e-mail]>, [e-mail] <[e-mail]>,
> Dhananjay Patki (dhpatki) <[e-mail]>
> Subject: [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, [e-mail] 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 <[e-mail]>
> > 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