draft-ietf-grow-bmp-local-rib-08.txt   draft-ietf-grow-bmp-local-rib-09.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: 20 May 2021 P. Lucente Expires: 18 July 2021 P. Lucente
NTT Communications NTT Communications
16 November 2020 14 January 2021
Support for Local RIB in BGP Monitoring Protocol (BMP) Support for Local RIB in BGP Monitoring Protocol (BMP)
draft-ietf-grow-bmp-local-rib-08 draft-ietf-grow-bmp-local-rib-09
Abstract Abstract
The BGP Monitoring Protocol (BMP) defines access to various Routing The BGP Monitoring Protocol (BMP) defines access to various Routing
Information Bases (RIBs). This document updates BMP (RFC 7854) by Information Bases (RIBs). This document updates BMP (RFC 7854) by
adding access to the Local Routing Information Base (Loc-RIB), as adding access to the Local Routing Information Base (Loc-RIB), as
defined in RFC 4271. The Loc-RIB contains the routes that have been defined in RFC 4271. The Loc-RIB contains the routes that have been
selected by the local BGP speaker's Decision Process. selected by the local BGP speaker's Decision Process.
Status of This Memo Status of This Memo
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 20 May 2021. This Internet-Draft will expire on 18 July 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2021 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Simplified BSD License.
skipping to change at page 11, line 14 skipping to change at page 11, line 14
Multiple TLVs of the same type can be repeated as part of the same Multiple TLVs of the same type can be repeated as part of the same
message, for example to convey a filtered view of a VRF. A BMP message, for example to convey a filtered view of a VRF. A BMP
receiver should append multiple TLVs of the same type to a set in receiver should append multiple TLVs of the same type to a set in
order to support alternate or additional names for the same peer. If order to support alternate or additional names for the same peer. If
multiple strings are included, their ordering MUST be preserved when multiple strings are included, their ordering MUST be preserved when
they are reported. they are reported.
5.3. Peer Down Notification 5.3. Peer Down Notification
Peer down notification MUST use reason code TBD3. Following the Peer down notification MUST use reason code 6. Following the reason
reason is data in TLV format. The following peer Down information is data in TLV format. The following peer Down information TLV type
TLV type is defined: is defined:
* Type = 3: VRF/Table Name. The Information field contains a UTF-8 * Type = 3: VRF/Table Name. The Information field contains a UTF-8
string whose value MUST be equal to the value of the VRF or table string whose value MUST be equal to the value of the VRF or table
name (e.g. RD instance name) being conveyed. The string size name (e.g. RD instance name) being conveyed. The string size
MUST be within the range of 1 to 255 bytes. The VRF/Table Name MUST be within the range of 1 to 255 bytes. The VRF/Table Name
informational TLV MUST be included if it was in the Peer UP. informational TLV MUST be included if it was in the Peer UP.
5.4. Route Monitoring 5.4. Route Monitoring
Route Monitoring messages are used for initial synchronization of the Route Monitoring messages are used for initial synchronization of the
skipping to change at page 14, line 20 skipping to change at page 14, line 20
* Type = 3: VRF/Table Name. The Information field contains a UTF-8 * Type = 3: VRF/Table Name. The Information field contains a UTF-8
string whose value MUST be equal to the value of the VRF or table string whose value MUST be equal to the value of the VRF or table
name (e.g. RD instance name) being conveyed. The string size name (e.g. RD instance name) being conveyed. The string size
MUST be within the range of 1 to 255 bytes. MUST be within the range of 1 to 255 bytes.
8.4. Peer Down Reason code 8.4. Peer Down Reason code
This document defines the following new BMP Peer Down reason code This document defines the following new BMP Peer Down reason code
(Section 5.3): (Section 5.3):
* Type = TBD3: Local system closed, TLV data follows. * Type = 6: Local system closed, TLV data follows.
9. Normative References 9. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271, Border Gateway Protocol 4 (BGP-4)", RFC 4271,
 End of changes. 7 change blocks. 
9 lines changed or deleted 9 lines changed or added

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