RFC 7854, "BGP Monitoring Protocol (BMP)", June 2016

Note: This RFC has been updated by RFC 8671, RFC 9069, RFC 9515

Errata ID: 4830
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Suhas Anand
Date Reported: 2016-10-12
Held for Document Update by: Joel Jaeggli
Date Held: 2017-03-29

Section 4.9 says:

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)               |
     ~                                                               ~
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

It should say:

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

Report New Errata