draft-ietf-grow-bmp-local-rib-05.txt   draft-ietf-grow-bmp-local-rib-06.txt 
Global Routing Operations T. Evens Global Routing Operations T. Evens
Internet-Draft S. Bayraktar Internet-Draft S. Bayraktar
Updates: 7854 (if approved) M. Bhardwaj Updates: 7854 (if approved) M. Bhardwaj
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: February 6, 2020 P. Lucente Expires: May 6, 2020 P. Lucente
NTT Communications NTT Communications
August 5, 2019 November 3, 2019
Support for Local RIB in BGP Monitoring Protocol (BMP) Support for Local RIB in BGP Monitoring Protocol (BMP)
draft-ietf-grow-bmp-local-rib-05 draft-ietf-grow-bmp-local-rib-06
Abstract Abstract
The BGP Monitoring Protocol (BMP) defines access to the Adj-RIB-In The BGP Monitoring Protocol (BMP) defines access to the Adj-RIB-In
and locally originated routes (e.g. routes distributed into BGP from and locally originated routes (e.g. routes distributed into BGP from
protocols such as static) but not access to the BGP instance Loc-RIB. protocols such as static) but not access to the BGP instance Loc-RIB.
This document updates the BGP Monitoring Protocol (BMP) RFC 7854 by This document updates the BGP Monitoring Protocol (BMP) RFC 7854 by
adding access to the BGP instance Local-RIB, as defined in RFC 4271 adding access to the BGP instance Local-RIB, as defined in RFC 4271
the routes that have been selected by the local BGP speaker's the routes that have been selected by the local BGP speaker's
Decision Process. These are the routes over all peers, locally Decision Process. These are the routes over all peers, locally
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 February 6, 2020. This Internet-Draft will expire on May 6, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 9, line 44 skipping to change at page 9, line 44
All peer messages that include a per-peer header MUST use the All peer messages that include a per-peer header MUST use the
following values: following values:
o Peer Type: Set to 3 to indicate Loc-RIB Instance Peer. o Peer Type: Set to 3 to indicate Loc-RIB Instance Peer.
o Peer Distinguisher: Zero filled if the Loc-RIB represents the o Peer Distinguisher: Zero filled if the Loc-RIB represents the
global instance. Otherwise set to the route distinguisher or global instance. Otherwise set to the route distinguisher or
unique locally defined value of the particular instance the Loc- unique locally defined value of the particular instance the Loc-
RIB belongs to. RIB belongs to.
o Peer Address: The remote IP address associated with the TCP o Peer Address: Zero-filled. Remote peer address is not applicable.
session over which the encapsulated PDU was received. If zero- The V flag is not applicable with Local-RIB Instance peer type
filled, the information is not available and setting the V flag is considering addresses are zero-filed.
not applicable.
o Peer AS: Set to the BGP instance global or default ASN value. o Peer AS: Set to the BGP instance global or default ASN value.
o Peer BGP ID: Set to the BGP instance global or RD (e.g. VRF) o Peer BGP ID: Set to the BGP instance global or RD (e.g. VRF)
specific router-id section 1.1 of [RFC7854]. specific router-id section 1.1 of [RFC7854].
o Timestamp: The time when the encapsulated routes were installed in o Timestamp: The time when the encapsulated routes were installed in
The Loc-RIB, expressed in seconds and microseconds since midnight The Loc-RIB, expressed in seconds and microseconds since midnight
(zero hour), January 1, 1970 (UTC). If zero, the time is (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-
 End of changes. 5 change blocks. 
8 lines changed or deleted 7 lines changed or added

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