--- 1/draft-ietf-grow-bmp-adj-rib-out-02.txt 2018-12-19 09:13:14.000693737 -0800 +++ 2/draft-ietf-grow-bmp-adj-rib-out-03.txt 2018-12-19 09:13:14.024694312 -0800 @@ -1,24 +1,24 @@ Global Routing Operations T. Evens Internet-Draft S. Bayraktar Updates: 7854 (if approved) Cisco Systems Intended status: Standards Track P. Lucente -Expires: March 21, 2019 NTT Communications +Expires: June 22, 2019 NTT Communications P. Mi Tencent S. Zhuang Huawei - September 17, 2018 + December 19, 2018 Support for Adj-RIB-Out in BGP Monitoring Protocol (BMP) - draft-ietf-grow-bmp-adj-rib-out-02 + draft-ietf-grow-bmp-adj-rib-out-03 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. Status of This Memo @@ -29,21 +29,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on March 21, 2019. + This Internet-Draft will expire on June 22, 2019. Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -58,34 +58,34 @@ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Per-Peer Header . . . . . . . . . . . . . . . . . . . . . . . 4 5. Adj-RIB-Out . . . . . . . . . . . . . . . . . . . . . . . . . 4 5.1. Post-Policy . . . . . . . . . . . . . . . . . . . . . . . 4 5.2. Pre-Policy . . . . . . . . . . . . . . . . . . . . . . . 4 6. BMP Messages . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1. Route Monitoring and Route Mirroring . . . . . . . . . . 5 6.2. Statistics Report . . . . . . . . . . . . . . . . . . . . 5 - 6.3. Peer Down and Up Notifications . . . . . . . . . . . . . 5 + 6.3. Peer Down and Up Notifications . . . . . . . . . . . . . 6 6.3.1. Peer Up Information . . . . . . . . . . . . . . . . . 6 7. Other Considerations . . . . . . . . . . . . . . . . . . . . 6 7.1. Peer and Update Groups . . . . . . . . . . . . . . . . . 6 8. Security Considerations . . . . . . . . . . . . . . . . . . . 7 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 9.1. BMP Peer Flags . . . . . . . . . . . . . . . . . . . . . 7 9.2. BMP Statistics Types . . . . . . . . . . . . . . . . . . 7 9.3. Peer UP Information TLV . . . . . . . . . . . . . . . . . 8 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 10.1. Normative References . . . . . . . . . . . . . . . . . . 8 10.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 8 - Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 8 + Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 9 + Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 1. Introduction BGP Monitoring Protocol (BMP) defines monitoring of the received (e.g. Adj-RIB-In) Routing Information Bases (RIBs) per peer. The Adj-RIB-In pre-policy conveys to a BMP receiver all RIB data before any policy has been applied. The Adj-RIB-In post-policy conveys to a BMP receiver all RIB data after policy filters and/or modifications have been applied. An example of pre-policy verses post-policy is @@ -147,21 +147,31 @@ 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ |V|L|A|O| Resv | +-+-+-+-+-+-+-+-+ o The O flag indicates Adj-RIB-In if set to 0 and Adj-RIB-Out if set to 1. The existing flags are defined in section 4.2 [RFC7854] and the remaining bits are reserved for future use. They SHOULD be - transmitted as 0 and their values MUST be ignored on receipt. + transmitted as 0 and their values MUST be ignored on receipt. The + following fields in Per-Peer Header are redefined: + + o Peer Address: The remote IP address associated with the TCP + session over which the encapsulated PDU was sent. + + o Peer AS: The Autonomous System number of the peer from which the + encapsulated PDU was sent. + + o Peer BGP ID: The BGP Identifier of the peer from which the + encapsulated PDU was sent. 5. Adj-RIB-Out 5.1. Post-Policy The primary use-case in monitoring Adj-RIB-Out is to monitor the updates transmitted to the BGP peer after outbound policy has been applied. These updates reflect the result after modifications and filters have been applied (e.g. Adj-RIB-Out Post-Policy). Some attributes are set when the BGP message is transmitted, such as next- @@ -172,25 +182,25 @@ The L flag MUST be set to 1 to indicate post-policy. 5.2. Pre-Policy As with Adj-RIB-In policy validation, there are use-cases that pre- policy Adj-RIB-Out is used to validate and audit outbound policies. For example, a comparison between pre-policy and post-policy can be used to validate the outbound policy. Depending on BGP peering session type (IBGP, IBGP route reflector - client, EBGP) the candidate routes that make up the Pre-Policy Adj- - RIB-Out do not contain all local-rib routes. Pre-Policy Adj-RIB-Out - conveys only routes that are available based on the peering type. - Post-Policy represents the filtered/changed routes from the available - routes. + client, EBGP, BGP confederations, Route Server Client) the candidate + routes that make up the Pre-Policy Adj-RIB-Out do not contain all + local-rib routes. Pre-Policy Adj-RIB-Out conveys only routes that + are available based on the peering type. Post-Policy represents the + filtered/changed routes from the available routes. Some attributes are set only during transmission of the BGP message, e.g. Post-Policy. It is common that next-hop may be null, loopback, or similar during this phase. All mandatory attributes, such as next-hop, MUST be either ZERO or have an empty length if they are unknown at the Pre-Policy phase. The BMP receiver will treat zero or empty mandatory attributes as self originated. The L flag MUST be set to 0 to indicate pre-policy. @@ -207,53 +217,53 @@ 6.2. Statistics Report Statistics report message has Stat Type field to indicate the statistic carried in the Stat Data field. Statistics report messages are not specific to Adj-RIB-In or Adj-RIB-Out and MUST have the O flag set to zero. The O flag SHOULD be ignored by the BMP receiver. The following new statistic types are added: - o Stat Type = TBD1: (64-bit Gauge) Number of routes in Adj-RIBs-Out + o Stat Type = 14: (64-bit Gauge) Number of routes in Adj-RIBs-Out Pre-Policy. - o Stat Type = TBD2: (64-bit Gauge) Number of routes in Adj-RIBs-Out + o Stat Type = 15: (64-bit Gauge) Number of routes in Adj-RIBs-Out Post-Policy. - o Stat Type = TBD3: Number of routes in per-AFI/SAFI Adj-RIB-Out - Pre- Policy. The value is structured as: 2-byte Address Family + o Stat Type = 16: Number of routes in per-AFI/SAFI Adj-RIB-Out Pre- + Policy. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. - o Stat Type = TBD4: Number of routes in per-AFI/SAFI Adj-RIB-Out - Post-Policy. The value is structured as: 2-byte Address Family + o Stat Type = 17: Number of routes in per-AFI/SAFI Adj-RIB-Out Post- + Policy. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. 6.3. Peer Down and Up Notifications PEER UP and DOWN notifications convey BGP peering session state to BMP receivers. The state is independent of whether or not route monitoring or route mirroring messages will be sent for Adj-RIB-In, Adj-RIB-Out, or both. BMP receiver implementations SHOULD ignore the O flag in PEER UP and DOWN notifications. BMP receiver implementations MUST use the per-peer header O flag in route monitoring and mirroring messages in order to identify if the message is for Adj-RIB-In or Adj-RIB-Out. 6.3.1. Peer Up Information The following peer UP information TLV types are added: - o Type = TBD5: Admin Label. The Information field contains a free- - form UTF-8 string whose length is given by the Information Length + o Type = 4: Admin Label. The Information field contains a free-form + UTF-8 string whose length is given by the Information Length field. The value is administratively assigned. There is no requirement to terminate the string with null or any other character. Multiple admin labels can be included in the Peer UP. When multiple admin labels are included the BMP receiver MUST preserve the order. The TLV is optional. @@ -307,43 +317,43 @@ (Section 4): o Flag 3 as O flag: The O flag indicates Adj-RIB-In if set to 0 and Adj-RIB-Out if set to 1. 9.2. BMP Statistics Types This document defines four new statistic types for statistics reporting (Section 6.2): - o Stat Type = TBD1: (64-bit Gauge) Number of routes in Adj-RIBs-Out + o Stat Type = 14: (64-bit Gauge) Number of routes in Adj-RIBs-Out Pre-Policy. - o Stat Type = TBD2: (64-bit Gauge) Number of routes in Adj-RIBs-Out + o Stat Type = 15: (64-bit Gauge) Number of routes in Adj-RIBs-Out Post-Policy. - o Stat Type = TBD3: Number of routes in per-AFI/SAFI Adj-RIB-Out - Pre- Policy. The value is structured as: 2-byte Address Family + o Stat Type = 16: Number of routes in per-AFI/SAFI Adj-RIB-Out Pre- + Policy. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. - o Stat Type = TBD4: Number of routes in per-AFI/SAFI Adj-RIB-Out - Post-Policy. The value is structured as: 2-byte Address Family + o Stat Type = 17: Number of routes in per-AFI/SAFI Adj-RIB-Out Post- + Policy. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. 9.3. Peer UP Information TLV This document defines the following new BMP PEER UP informational message TLV types (Section 6.3.1): - o Type = TBD5: Admin Label. The Information field contains a free- - form UTF-8 string whose length is given by the Information Length + o Type = 4: Admin Label. The Information field contains a free-form + UTF-8 string whose length is given by the Information Length field. The value is administratively given by the Information Length field. The value is administratively assigned. There is no requirement to terminate the string with null or any other character. 10. References 10.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate