Authors, We briefly discussed this during the bar BoF for BMP last IETF. My apologies for not presenting text before this point.
While there are use cases where an end-user may want per-peer rib-out state, some applications may not quite that level of granularity of information. In many cases, it is sufficient to know what route will be sent to the peers that belong to the BGP's peer-group/update-group. (I'll be using peer-group for the remainder of this e-mail.) In such cases, the adj-rib-out in its current form can be quite noisy. It effectively can turn the BMP feed into trying to squeeze the entire firehose of BGP traffic through the straw of a single session. I'd offer the following proposal for per-group BMP rib-out: The Per-Peer BMP header (RFC 7854, section 4.2) gets a new "peer-type" of "Rib-Out Group" (value TBD). For this new value, the Peer Distinguisher is set to a system-wide group-ID. The Peer-Address, Peer AS and Peer BGP ID is zero-filled. The group-ID is sufficient to determine the contents of the BGP data sent to the peer-group. A new message is allocated, called "BGP Rib-Out Groups". Its contents are: Flags (1 byte), a Delete flag is specified. Group-Id (8 bytes) Group-Name Length (1 byte) Group-Name A UTF-8 string of up to 255 bytes representing the group name. Number of Peers (2 bytes) Peer-List Section: (for each peer) Peer Type (1 byte) Peer Flags (1 byte) Peer Distinguisher (8 bytes) Peer Address (16 bytes) Peer AS (4 bytes) Peer BGP ID (4 bytes) The peer-list section is filled as per RFC 7854, section 4.2. The BGP Rib-Out Groups message should be sent prior to sending Route Monitoring or Route Mirroring messages. However, the application should be prepared to receive such messages without the group mapping. A group mapping by ID may be updated by sending a replacement with the same Group Id. A group mapping may be deleted by sending a truncated message containing only the flags with the delete bit set and the Group-Id. --- The contents above are missing some finer points, such as V and A flags and the O flag from the base bmp-adj-rib-out spec. However, this should serve as a coarse proposal. -- Jeff On Wed, Jun 21, 2017 at 12:08:17PM -0700, internet-dra...@ietf.org wrote: > Abstract: > The BGP Monitoring Protocol (BMP) defines access to only the Adj-RIB- > In Routing Information Bases (RIBs). This document updates the BGP > Monitoring Protocol (BMP) RFC 7854 by adding access to the Adj-RIB- > Out RIBs. It adds a new flag to the peer header to distinguish Adj- > RIB-In and Adj-RIB-Out. _______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
