Subject: Re: [GROW] [Technical Errata Reported] RFC7854 (4830)

From: John Scudder <[email-masked]>
Date: Fri, 24 Feb 2017 10:21:31 -0500

This looks right to me. Suggest moving it to "Verified".

Thanks,

--John

> On Oct 12, 2016, at 3:27 AM, RFC Errata System <[email-masked]> wrote:
> 
> The following errata report has been submitted for RFC7854,
> "BGP Monitoring Protocol (BMP)".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=7854&eid=4830
> 
> --------------------------------------
> Type: Technical
> Reported by: Suhas Anand <[email-masked]>
> 
> Section: 4.9
> 
> Original Text
> -------------
> Peer Down Notification
> 
>   This message is used to indicate that a peering session was
>   terminated.
> 
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>     +-+-+-+-+-+-+-+-+
>     |    Reason     |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |            Data (present if Reason = 1, 2 or 3)               |
>     ~                                                               ~
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> Corrected Text
> --------------
> Peer Down Notification
> 
>   This message is used to indicate that a peering session was
>   terminated. Following the common BMP header and per-peer header is 
>   the following:
> 
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>     +-+-+-+-+-+-+-+-+
>     |    Reason     |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |            Data (present if Reason = 1, 2 or 3)               |
>     ~                                                               ~
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> Notes
> -----
> What: 
> 
> For Peer Down Notification: To the programmer implementing the RFC, it is not clear if the Peer Down message consists of per peer header
> 
> 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 (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> 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
>