--- 1/draft-ietf-grow-bmp-local-rib-11.txt 2021-06-14 16:13:17.349921383 -0700 +++ 2/draft-ietf-grow-bmp-local-rib-12.txt 2021-06-14 16:13:17.381922192 -0700 @@ -1,21 +1,21 @@ Global Routing Operations T. Evens Internet-Draft S. Bayraktar Updates: 7854 (if approved) M. Bhardwaj Intended status: Standards Track Cisco Systems -Expires: 1 November 2021 P. Lucente +Expires: 16 December 2021 P. Lucente NTT Communications - 30 April 2021 + 14 June 2021 Support for Local RIB in BGP Monitoring Protocol (BMP) - draft-ietf-grow-bmp-local-rib-11 + draft-ietf-grow-bmp-local-rib-12 Abstract The BGP Monitoring Protocol (BMP) defines access to local Routing Information Bases (RIBs). This document updates BMP (RFC 7854) by adding access to the Local Routing Information Base (Loc-RIB), as defined in RFC 4271. The Loc-RIB contains the routes that have been selected by the local BGP speaker's Decision Process. Status of This Memo @@ -26,21 +26,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 1 November 2021. + This Internet-Draft will expire on 16 December 2021. Copyright Notice Copyright (c) 2021 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 carefully, as they describe your rights @@ -310,21 +310,21 @@ 4.2. Peer Flags If locally sourced routes are communicated using BMP, they MUST be conveyed using the Loc-RIB instance peer type. The per-peer header flags for Loc-RIB Instance Peer type are defined as follows: 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ - | | | | |F| | | | + |F| | | | | | | | +-+-+-+-+-+-+-+-+ * The F flag indicates that the Loc-RIB is filtered. This MUST be set when a filter is applied to Loc-RIB routes sent to the BMP collector. The unused bits are reserved for future use. They MUST be transmitted as 0 and their values MUST be ignored on receipt. 5. Loc-RIB Monitoring @@ -544,21 +544,21 @@ * Peer Type = 3: Loc-RIB Instance Peer 8.2. BMP Loc-RIB Instance Peer Flags This document requests IANA to rename "BMP Peer Flags" to "BMP Peer Flags for Peer Types 0 through 2" and create a new registry named "BMP Peer Flags for Loc-RIB Instance Peer Type 3" This document defines that peer flags are specific to the Loc-RIB instance peer type. As defined in (Section 4.2): - * Flag 4: The F flag indicates that the Loc-RIB is filtered. This + * Flag 0: The F flag indicates that the Loc-RIB is filtered. This indicates that the Loc-RIB does not represent the complete routing table. Flags 0 through 3 and 5 through 7 are unassigned. The registration procedure for the registry is "Standards Action". 8.3. Peer Up Information TLV This document requests that IANA rename "BMP Initiation Message TLVs" registry to "BMP Initiation and Peer Up Information TLVs." section