--- 1/draft-ietf-grow-bmp-adj-rib-out-01.txt 2018-09-17 13:13:16.719657052 -0700 +++ 2/draft-ietf-grow-bmp-adj-rib-out-02.txt 2018-09-17 13:13:16.743657634 -0700 @@ -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: September 3, 2018 NTT Communications +Expires: March 21, 2019 NTT Communications P. Mi Tencent S. Zhuang Huawei - March 2, 2018 + September 17, 2018 Support for Adj-RIB-Out in BGP Monitoring Protocol (BMP) - draft-ietf-grow-bmp-adj-rib-out-01 + draft-ietf-grow-bmp-adj-rib-out-02 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 September 3, 2018. + This Internet-Draft will expire on March 21, 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 @@ -207,52 +207,52 @@ 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 = TBD: (64-bit Gauge) Number of routes in Adj-RIBs-Out + o Stat Type = TBD1: (64-bit Gauge) Number of routes in Adj-RIBs-Out Pre-Policy. - o Stat Type = TBD: (64-bit Gauge) Number of routes in Adj-RIBs-Out + o Stat Type = TBD2: (64-bit Gauge) Number of routes in Adj-RIBs-Out Post-Policy. - o Stat Type = TBD: Number of routes in per-AFI/SAFI Adj-RIB-Out Pre- - Policy. The value is structured as: 2-byte Address Family + 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 Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. - o Stat Type = TBD: Number of routes in per-AFI/SAFI Adj-RIB-Out + 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 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 = TBD: Admin Label. The Information field contains a free- + o Type = TBD5: 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,42 +307,42 @@ (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 = TBD: (64-bit Gauge) Number of routes in Adj-RIBs-Out + o Stat Type = TBD1: (64-bit Gauge) Number of routes in Adj-RIBs-Out Pre-Policy. - o Stat Type = TBD: (64-bit Gauge) Number of routes in Adj-RIBs-Out + o Stat Type = TBD2: (64-bit Gauge) Number of routes in Adj-RIBs-Out Post-Policy. - o Stat Type = TBD: Number of routes in per-AFI/SAFI Adj-RIB-Out Pre- - Policy. The value is structured as: 2-byte Address Family + 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 Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. - o Stat Type = TBD: Number of routes in per-AFI/SAFI Adj-RIB-Out + 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 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 = TBD: Admin Label. The Information field contains a free- + o Type = TBD5: 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