draft-ietf-grow-bmp-05.txt   draft-ietf-grow-bmp-06.txt 
Network Working Group J. Scudder Network Working Group J. Scudder
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track R. Fernando Intended status: Standards Track R. Fernando
Expires: June 18, 2011 Cisco Systems Expires: June 2, 2012 Cisco Systems
S. Stuart S. Stuart
Google Google
December 15, 2010 November 30, 2011
BGP Monitoring Protocol BGP Monitoring Protocol
draft-ietf-grow-bmp-05 draft-ietf-grow-bmp-06
Abstract Abstract
This document proposes a simple protocol, BMP, which can be used to This document proposes a simple protocol, BMP, which can be used to
monitor BGP sessions. BMP is intended to provide a more convenient monitor BGP sessions. BMP is intended to provide a more convenient
interface for obtaining route views for research purpose than the interface for obtaining route views for research purpose than the
screen-scraping approach in common use today. The design goals are screen-scraping approach in common use today. The design goals are
to keep BMP simple, useful, easily implemented, and minimally to keep BMP simple, useful, easily implemented, and minimally
service-affecting. BMP is not suitable for use as a routing service-affecting. BMP is not suitable for use as a routing
protocol. protocol.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 18, 2011. This Internet-Draft will expire on June 2, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 9 skipping to change at page 3, line 9
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 5 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 5
2. BMP Message Format . . . . . . . . . . . . . . . . . . . . . . 5 2. Lifecycle of a BMP Session . . . . . . . . . . . . . . . . . . 5
2.1. Common Header . . . . . . . . . . . . . . . . . . . . . . 5 3. BMP Message Format . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Per-Peer Header . . . . . . . . . . . . . . . . . . . . . 5 3.1. Common Header . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Initiation Message . . . . . . . . . . . . . . . . . . . . 7 3.2. Per-Peer Header . . . . . . . . . . . . . . . . . . . . . 6
2.4. Route Monitoring . . . . . . . . . . . . . . . . . . . . . 8 3.3. Initiation Message . . . . . . . . . . . . . . . . . . . . 8
2.5. Stats Reports . . . . . . . . . . . . . . . . . . . . . . 8 3.4. Route Monitoring . . . . . . . . . . . . . . . . . . . . . 9
2.6. Peer Down Notification . . . . . . . . . . . . . . . . . . 9 3.5. Stats Reports . . . . . . . . . . . . . . . . . . . . . . 9
2.7. Peer Up Notification . . . . . . . . . . . . . . . . . . . 10 3.6. Peer Down Notification . . . . . . . . . . . . . . . . . . 10
3. Route Monitoring . . . . . . . . . . . . . . . . . . . . . . . 11 3.7. Peer Up Notification . . . . . . . . . . . . . . . . . . . 11
4. Stat Reports . . . . . . . . . . . . . . . . . . . . . . . . . 12 4. Route Monitoring . . . . . . . . . . . . . . . . . . . . . . . 12
5. Other Considerations . . . . . . . . . . . . . . . . . . . . . 12 5. Stat Reports . . . . . . . . . . . . . . . . . . . . . . . . . 13
6. Using BMP . . . . . . . . . . . . . . . . . . . . . . . . . . 13 6. Other Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 7. Using BMP . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 9. Security Considerations . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . . 14 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . . 15 11.1. Normative References . . . . . . . . . . . . . . . . . . . 15
Appendix A. Changes Between BMP Versions 1 and 2 . . . . . . . . 15 11.2. Informative References . . . . . . . . . . . . . . . . . . 16
Appendix B. Changes Between BMP Versions 2 and 3 . . . . . . . . 15 Appendix A. Changes Between BMP Versions 1 and 2 . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Appendix B. Changes Between BMP Versions 2 and 3 . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
Many researchers wish to have access to the contents of routers' BGP Many researchers wish to have access to the contents of routers' BGP
RIBs as well as a view of protocol updates that the router is RIBs as well as a view of protocol updates that the router is
receiving. This monitoring task cannot be realized by standard receiving. This monitoring task cannot be realized by standard
protocol mechanisms. At present, this data can only be obtained protocol mechanisms. At present, this data can only be obtained
through screen-scraping. through screen-scraping.
The BMP protocol provides access to the Adj-RIB-In of a peer on an The BMP protocol provides access to the Adj-RIB-In of a peer on an
skipping to change at page 5, line 15 skipping to change at page 5, line 15
If the monitoring station intends to restart BMP processing, it If the monitoring station intends to restart BMP processing, it
simply drops the connection. The router then re-establishes the simply drops the connection. The router then re-establishes the
connection and resends the messages. connection and resends the messages.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. BMP Message Format 2. Lifecycle of a BMP Session
2.1. Common Header A BMP session begins when a router running BMP successfully opens a
TCP session (the "BMP session") to the monitoring station it is
configured to talk to. It MAY first send an Initiation message. It
subsequently sends a Peer Up message over the BMP session for each of
its BGP peers which are in Established state. It follows by sending
the contents of its Adj-RIBs-In (or Loc-RIB, see Section 4)
encapsulated in Route Monitoring messages. Once it has sent all the
routes for a given peer, it sends an End-of-RIB message for that
peer; when End-of-RIB has been sent for each peer, the initial table
dump has completed. (A monitoring station that wishes only to gather
a table dump could close the connection once it has gathered an End-
of-RIB or Peer Down message corresponding to each Peer Up message.)
Following the initial table dump, the router sends incremental
updates encapsulated in Route Monitoring messages. It MAY
periodically send Stats Reports or even new Initiation messages,
according to configuration. If any new BGP peers become Established,
corresponding Peer Up messages are sent. If any BGP peers for which
Peer Up messages were sent transition out of the Established state,
corresponding Peer Down messages are sent.
A BMP session ends when the TCP session that carries it is closed for
any reason.
3. BMP Message Format
3.1. Common Header
The following common header appears in all BMP messages. The rest of The following common header appears in all BMP messages. The rest of
the data in a BMP message is dependent on the "Message Type" field in the data in a BMP message is dependent on the "Message Type" field in
the common header. the common header.
0 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+
| Version |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Length | Msg. Type | | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg. Type |
+---------------+
o Version (1 byte): Indicates the BMP version. This is set to '3' o Version (1 byte): Indicates the BMP version. This is set to '3'
for all messages defined in this specification. for all messages defined in this specification. Version 0 is
reserved and MUST NOT be sent.
o Message Length (2 bytes): Length of the message in bytes o Message Length (4 bytes): Length of the message in bytes
(including headers, data and encapsulated messages, if any). (including headers, data and encapsulated messages, if any).
o Message Type (1 byte): This identifies the type of the BMP o Message Type (1 byte): This identifies the type of the BMP
message. A BMP implementation MUST ignore unrecognized message message. A BMP implementation MUST ignore unrecognized message
types upon receipt. types upon receipt.
* Type = 0: Route Monitoring * Type = 0: Route Monitoring
* Type = 1: Statistics Report * Type = 1: Statistics Report
* Type = 2: Peer Down Notification * Type = 2: Peer Down Notification
* Type = 3: Peer Up Notification * Type = 3: Peer Up Notification
* Type = 4: Initiation Message * Type = 4: Initiation Message
2.2. Per-Peer Header 3.2. Per-Peer Header
The per-peer header follows the common header for most BMP messages. The per-peer header follows the common header for most BMP messages.
The rest of the data in a BMP message is dependent on the "Message The rest of the data in a BMP message is dependent on the "Message
Type" field in the common header. Type" field in the common header.
0 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Type | Peer Flags | | Peer Type | Peer Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Distinguisher (present based on peer type) | | Peer Distinguisher (present based on peer type) |
skipping to change at page 6, line 43 skipping to change at page 7, line 43
0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|V|L| Reserved | |V|L| Reserved |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
* The V flag indicates the the Peer address is an IPv6 address. * The V flag indicates the the Peer address is an IPv6 address.
For IPv4 peers this is set to 0. For IPv4 peers this is set to 0.
* The L flag, if set to 1, indicates that the message reflects * The L flag, if set to 1, indicates that the message reflects
the Loc-RIB (i.e., it reflects the application of inbound the Loc-RIB (i.e., it reflects the application of inbound
policy). It is set to 0 if the message reflects the policy). It is set to 0 if the message reflects the
Adj-RIB-In. See Section 3 for further detail. Adj-RIB-In. See Section 4 for further detail.
* The remaining bits are reserved for future use. * The remaining bits are reserved for future use.
o Peer Distinguisher (8 bytes): Routers today can have multiple o Peer Distinguisher (8 bytes): Routers today can have multiple
instances (example L3VPNs). This field is present to distinguish instances (example L3VPNs). This field is present to distinguish
peers that belong to one address domain from the other. peers that belong to one address domain from the other.
If the peer is a "Global Instance Peer", this field is zero If the peer is a "Global Instance Peer", this field is zero
filled. If the peer is a "L3VPN Instance Peer", it is set to the filled. If the peer is a "L3VPN Instance Peer", it is set to the
route distinguisher of the particular L3VPN instance that the peer route distinguisher of the particular L3VPN instance that the peer
belongs to. belongs to.
skipping to change at page 7, line 29 skipping to change at page 8, line 29
o Peer BGP ID: The BGP Identifier of the peer from which the o Peer BGP ID: The BGP Identifier of the peer from which the
encapsulated PDU was received. encapsulated PDU was received.
o Timestamp: The time when the encapsulated routes were received o Timestamp: The time when the encapsulated routes were received
(one may also think of this as the time when they were installed (one may also think of this as the time when they were installed
in the Adj-RIB-In), expressed in seconds and microseconds since in the Adj-RIB-In), expressed in seconds and microseconds since
midnight (zero hour), January 1, 1970 (UTC). If zero, the time is midnight (zero hour), January 1, 1970 (UTC). If zero, the time is
unavailable. Precision of the timestamp is implementation- unavailable. Precision of the timestamp is implementation-
dependent. dependent.
2.3. Initiation Message 3.3. Initiation Message
The initiation message provides a means for the monitored router to The initiation message provides a means for the monitored router to
inform the monitoring station of its vendor, software version, and so inform the monitoring station of its vendor, software version, and so
on. The initiation message is OPTIONAL. When used, an initiation on. The initiation message is OPTIONAL. When used, an initiation
message MUST be sent as the first message after the TCP session comes message MUST be sent as the first message after the TCP session comes
up. An initiation message MAY be sent at any point thereafter, if up. An initiation message MAY be sent at any point thereafter, if
warranted by a change on the monitored router. warranted by a change on the monitored router.
The initiation message consists of the common BMP header followed by The initiation message consists of the common BMP header followed by
one or more TLVs containing information about the monitored router, one or more TLVs containing information about the monitored router,
skipping to change at page 8, line 9 skipping to change at page 9, line 9
| Information Type | Information Length | | Information Type | Information Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Information (variable) | | Information (variable) |
~ ~ ~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Information Type (2 bytes): Type of information provided. Defined o Information Type (2 bytes): Type of information provided. Defined
types are: types are:
* Type = 0: String. The Information field contains a free-form * Type = 0: String. The Information field contains a free-form
ASCII string whose length is given by the "Information Length" UTF-8 string whose length is given by the "Information Length"
field. field.
o Information Length (2 bytes): The length of the following o Information Length (2 bytes): The length of the following
Information field, in bytes. Information field, in bytes.
o Information (variable): Information about the monitored router, o Information (variable): Information about the monitored router,
according to the type. according to the type.
2.4. Route Monitoring 3.4. Route Monitoring
Route Monitoring messages are used for initial synchronization of Route Monitoring messages are used for initial synchronization of
ADJ-RIB-In. They are also used for ongoing monitoring of received ADJ-RIB-In. They are also used for ongoing monitoring of received
advertisements and withdraws. This is discussed in more detail in advertisements and withdraws. This is discussed in more detail in
subsequent sections. subsequent sections.
Following the common BMP header and per-peer header is a BGP PDU. Following the common BMP header and per-peer header is a BGP PDU.
2.5. Stats Reports 3.5. Stats Reports
These messages contain information that could be used by the These messages contain information that could be used by the
monitoring station to observe interesting events that occur on the monitoring station to observe interesting events that occur on the
router. 'Stats Report' messages have a message type of '3'. router. 'Stats Report' messages have a message type of '3'.
The transmission of the SR messages could be timer triggered or event The transmission of the SR messages could be timer triggered or event
driven (for example, when a significant event occurs or a threshold driven (for example, when a significant event occurs or a threshold
is reached). This specification does not impose any timing is reached). This specification does not impose any timing
restrictions on when and on what event these reports have to be restrictions on when and on what event these reports have to be
transmitted. It is left to the implementation to determine transmitted. It is left to the implementation to determine
skipping to change at page 9, line 45 skipping to change at page 10, line 45
o Stat Type = 6: Number of updates invalidated due to AS_CONFED o Stat Type = 6: Number of updates invalidated due to AS_CONFED
loop. loop.
Note that the current specification only specifies 4-byte counters as Note that the current specification only specifies 4-byte counters as
"Stat Data". This does not preclude future versions from "Stat Data". This does not preclude future versions from
incorporating more complex TLV-type "Stat Data" (for example, one incorporating more complex TLV-type "Stat Data" (for example, one
which can carry prefix specific data). SR messages are optional. which can carry prefix specific data). SR messages are optional.
However if an SR message is transmitted, this specification requires However if an SR message is transmitted, this specification requires
at least one statistic to be carried in it. at least one statistic to be carried in it.
2.6. Peer Down Notification 3.6. Peer Down Notification
This message is used to indicate that a peering session was This message is used to indicate that a peering session was
terminated. The type of this message is 4. terminated. The type of this message is 4.
0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Reason | 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 | Reason | 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data (present if Reason = 1, 2 or 3) | | Data (present if Reason = 1, 2 or 3) |
~ ~ ~ ~
skipping to change at page 10, line 32 skipping to change at page 11, line 32
the system to close the session (see Section 8.1 of [RFC4271]). the system to close the session (see Section 8.1 of [RFC4271]).
Zero is used to indicate that no relevant Event code is defined. Zero is used to indicate that no relevant Event code is defined.
o Reason 3: The remote system closed the session with a notification o Reason 3: The remote system closed the session with a notification
message. Following the Reason is a BGP PDU containing the BGP message. Following the Reason is a BGP PDU containing the BGP
NOTIFICATION message as received from the peer. NOTIFICATION message as received from the peer.
o Reason 4: The remote system closed the session without a o Reason 4: The remote system closed the session without a
notification message. notification message.
2.7. Peer Up Notification 3.7. Peer Up Notification
The Peer Up message is used to indicate that a peering session has The Peer Up message is used to indicate that a peering session has
come up (i.e., has transitioned into ESTABLISHED state). Following come up (i.e., has transitioned into ESTABLISHED state). Following
the common BMP header and per-peer header is the following: the common BMP header and per-peer header is the following:
0 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Address (16 bytes) | | Local Address (16 bytes) |
~ ~ ~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 11, line 24 skipping to change at page 12, line 24
o Remote Port: The remote port number associated with the peering o Remote Port: The remote port number associated with the peering
TCP session. (Note that the remote address can be found in the TCP session. (Note that the remote address can be found in the
Peer Address field of the fixed header.) Peer Address field of the fixed header.)
o Sent OPEN Message: The full OPEN message transmitted by the o Sent OPEN Message: The full OPEN message transmitted by the
monitored router to its peer. monitored router to its peer.
o Received OPEN Message: The full OPEN message received by the o Received OPEN Message: The full OPEN message received by the
monitored router from its peer. monitored router from its peer.
3. Route Monitoring 4. Route Monitoring
After the BMP session is up, Route Monitoring messages are used to After the BMP session is up, Route Monitoring messages are used to
provide a snapshot of the Adj-RIB-In of a particular peer. This is provide a snapshot of the Adj-RIB-In of a particular peer. This is
done by sending all routes stored in the Adj-RIB-In of that peer done by sending all routes stored in the Adj-RIB-In of that peer
using standard BGP Update messages. There is no requirement on the using standard BGP Update messages. There is no requirement on the
ordering of messages in the peer dump. When the initial peer dump is ordering of messages in the peer dump. When the initial peer dump is
completed, this MUST be indicated by sending an End-of-RIB marker (as completed, this MUST be indicated by sending an End-of-RIB marker (as
specified in Section 2 of [RFC4724], plus the BMP encapsulation specified in Section 2 of [RFC4724], plus the BMP encapsulation
header). header).
Depending on the implementation or configuration, it may only be Depending on the implementation or configuration, it may only be
possible to send the Loc-RIB (post-policy routes) instead of the Adj- possible to send the Loc-RIB (post-policy routes) instead of the Adj-
RIB-In. This is because it is possible that a BGP implementation may RIB-In. This is because it is possible that a BGP implementation may
not store, for example, routes which have been filtered out by not store, for example, routes which have been filtered out by
policy. If this is the case, the implementation may send the Loc-RIB policy. If this is the case, the implementation may send the Loc-RIB
path that pertains to a particular peer in the route monitor message. path that pertains to a particular peer in the route monitor message.
Such paths MUST have the L flag set in the BMP header (see Such paths MUST have the L flag set in the BMP header (see
Section 2). Section 3).
If the implementation is able to provide information about when If the implementation is able to provide information about when
routes were received, it MAY provide such information in the BMP routes were received, it MAY provide such information in the BMP
timestamp field. Otherwise, the BMP timestamp field MUST be set to timestamp field. Otherwise, the BMP timestamp field MUST be set to
zero, indicating that time is not available. zero, indicating that time is not available.
AS Numbers in the BMP UPDATE message MUST be sent as 4-octet AS Numbers in the BMP UPDATE message MUST be sent as 4-octet
quantities, as described in [RFC4893]. This affects the AS_PATH and quantities, as described in [RFC4893]. This affects the AS_PATH and
AGGREGATOR path attributes. AS4_PATH or AS4_AGGREGATOR path AGGREGATOR path attributes. AS4_PATH or AS4_AGGREGATOR path
attributes MUST NOT be sent in a BMP UPDATE message, as it makes no attributes MUST NOT be sent in a BMP UPDATE message, as it makes no
skipping to change at page 12, line 28 skipping to change at page 13, line 28
generate updates as soon as they are received there is a finite time generate updates as soon as they are received there is a finite time
that could elapse between reception of an update and the generation that could elapse between reception of an update and the generation
an RM message and its transmission to the monitoring station. If an RM message and its transmission to the monitoring station. If
there are state changes in the interim for that prefix, it is there are state changes in the interim for that prefix, it is
acceptable that the router generate the final state of that prefix to acceptable that the router generate the final state of that prefix to
the monitoring station. The actual PDU generated and transmitted to the monitoring station. The actual PDU generated and transmitted to
the station might also differ from the exact PDU received from the the station might also differ from the exact PDU received from the
peer, for example due to differences between how different peer, for example due to differences between how different
implementations format path attributes. implementations format path attributes.
4. Stat Reports 5. Stat Reports
As outlined above, SR messages are used to monitor specific events As outlined above, SR messages are used to monitor specific events
and counters on the monitored router. One type of monitoring could and counters on the monitored router. One type of monitoring could
be to find out if there are an undue number of route advertisements be to find out if there are an undue number of route advertisements
and withdraws happening (churn) on the monitored router. Another and withdraws happening (churn) on the monitored router. Another
metric is to evaluate the number of looped AS-Paths on the router. metric is to evaluate the number of looped AS-Paths on the router.
While this document proposes a small set of counters to begin with, While this document proposes a small set of counters to begin with,
the authors envision this list may grow in the future with new the authors envision this list may grow in the future with new
applications that require BMP style monitoring. applications that require BMP style monitoring.
5. Other Considerations 6. Other Considerations
Some routers may support multiple instances of the BGP protocol, for Some routers may support multiple instances of the BGP protocol, for
example as "logical routers" or through some other facility. The BMP example as "logical routers" or through some other facility. The BMP
protocol relates to a single instance of BGP; thus, if a router protocol relates to a single instance of BGP; thus, if a router
supports multiple BGP instances it should also support multiple BMP supports multiple BGP instances it should also support multiple BMP
instances (one per BMP instance). instances (one per BMP instance).
6. Using BMP 7. Using BMP
Once the BMP session is established route monitoring starts dumping Once the BMP session is established route monitoring starts dumping
the current snapshot as well as incremental changes simultaneously. the current snapshot as well as incremental changes simultaneously.
It is fine to have these operations occur concurrently. If the It is fine to have these operations occur concurrently. If the
initial dump visits a route and subsequently a withdraw is received, initial dump visits a route and subsequently a withdraw is received,
this will be forwarded to the monitoring station which would have to this will be forwarded to the monitoring station which would have to
correlate and reflect the deletion of that route in its internal correlate and reflect the deletion of that route in its internal
state. This is an operation a monitoring station would need to state. This is an operation a monitoring station would need to
support regardless. support regardless.
If the router receives a withdraw for a prefix even before the peer If the router receives a withdraw for a prefix even before the peer
dump procedure visits that prefix, then the router would clean up dump procedure visits that prefix, then the router would clean up
that route from its internal state and will not forward it to the that route from its internal state and will not forward it to the
monitoring station. In this case, the monitoring station may receive monitoring station. In this case, the monitoring station may receive
a bogus withdraw which it can safely ignore. a bogus withdraw which it can safely ignore.
7. IANA Considerations 8. IANA Considerations
This document defines five message types for transferring BGP This document defines five message types for transferring BGP
messages between cooperating systems (Section 2): messages between cooperating systems (Section 3):
o Type 0: Route Monitor o Type 0: Route Monitor
o Type 1: Statistics Report o Type 1: Statistics Report
o Type 2: Peer Down Notification o Type 2: Peer Down Notification
o Type 3: Peer Up Notification o Type 3: Peer Up Notification
o Type 4: Initiation o Type 4: Initiation
Type values 5 through 128 MUST be assigned using the "Standards Type values 5 through 128 MUST be assigned using the "Standards
Action" policy, and values 129 through 255 using the "Specification Action" policy, and values 129 through 255 using the "Specification
Required" policy defined in [RFC5226]. Required" policy defined in [RFC5226].
This document defines five statistics types for statistics reporting This document defines five statistics types for statistics reporting
(Section 2.5): (Section 3.5):
o Stat Type = 0: Number of prefixes rejected by inbound policy. o Stat Type = 0: Number of prefixes rejected by inbound policy.
o Stat Type = 1: Number of (known) duplicate prefix advertisements. o Stat Type = 1: Number of (known) duplicate prefix advertisements.
o Stat Type = 2: Number of (known) duplicate withdraws. o Stat Type = 2: Number of (known) duplicate withdraws.
o Stat Type = 3: Number of updates invalidated due to CLUSTER_LIST o Stat Type = 3: Number of updates invalidated due to CLUSTER_LIST
loop. loop.
o Stat Type = 4: Number of updates invalidated due to AS_PATH loop. o Stat Type = 4: Number of updates invalidated due to AS_PATH loop.
o Stat Type = 5: Number of updates invalidated due to ORIGINATOR_ID. o Stat Type = 5: Number of updates invalidated due to ORIGINATOR_ID.
o Stat Type = 6: Number of updates invalidated due to AS_CONFED o Stat Type = 6: Number of updates invalidated due to AS_CONFED
loop. loop.
Stat Type values 7 through 32767 MUST be assigned using the Stat Type values 7 through 32767 MUST be assigned using the
"Standards Action" policy, and values 32768 through 65535 using the "Standards Action" policy, and values 32768 through 65535 using the
"Specification Required" policy, defined in [RFC5226]. "Specification Required" policy, defined in [RFC5226].
This document defines one type for information carried in the This document defines one type for information carried in the
Initiation message (Section 2.3): Initiation message (Section 3.3):
o Type = 0: String. o Type = 0: String.
Information type values 1 through 32767 MUST be assigned using the Information type values 1 through 32767 MUST be assigned using the
"Standards Action" policy, and values 32768 through 65535 using the "Standards Action" policy, and values 32768 through 65535 using the
"Specification Required" policy, defined in [RFC5226]. "Specification Required" policy, defined in [RFC5226].
8. Security Considerations 9. Security Considerations
This document defines a mechanism to obtain a full dump or provide This document defines a mechanism to obtain a full dump or provide
continuous monitoring of a BGP speaker's local BGP table, including continuous monitoring of a BGP speaker's local BGP table, including
received BGP messages. This capability could allow an outside party received BGP messages. This capability could allow an outside party
to obtain information not otherwise obtainable. to obtain information not otherwise obtainable.
Implementations of this protocol MUST require manual configuration of Implementations of this protocol MUST require manual configuration of
the monitored and monitoring devices. the monitored and monitoring devices.
Users of this protocol MAY use some type of secure transmission Users of this protocol MAY use some type of secure transmission
mechanism, such as IPSec [RFC4303], to transmit this data. mechanism, such as IPSec [RFC4303], to transmit this data.
9. Acknowledgements 10. Acknowledgements
Thanks to John ji Ioannidis, Mack McBride, Danny McPherson, Dimitri Thanks to John ji Ioannidis, Mack McBride, Danny McPherson, Dimitri
Papadimitriou, Erik Romijn, and the members of the GROW working group Papadimitriou, Erik Romijn, and the members of the GROW working group
for their comments. for their comments.
10. References 11. References
10.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4724] Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y. [RFC4724] Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y.
Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724, Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724,
January 2007. January 2007.
[RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS [RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS
Number Space", RFC 4893, May 2007. Number Space", RFC 4893, May 2007.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
10.2. Informative References 11.2. Informative References
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, December 2005. RFC 4303, December 2005.
Appendix A. Changes Between BMP Versions 1 and 2 Appendix A. Changes Between BMP Versions 1 and 2
o Added Peer Up Message o Added Peer Up Message
o Added L flag o Added L flag
o Editorial changes o Editorial changes
 End of changes. 35 change blocks. 
53 lines changed or deleted 85 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/