draft-ietf-grow-bmp-local-rib-12.txt   draft-ietf-grow-bmp-local-rib-13.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: 16 December 2021 P. Lucente Expires: 4 March 2022 P. Lucente
NTT Communications NTT Communications
14 June 2021 31 August 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-12 draft-ietf-grow-bmp-local-rib-13
Abstract Abstract
The BGP Monitoring Protocol (BMP) defines access to local Routing The BGP Monitoring Protocol (BMP) defines access to local 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 16 December 2021. This Internet-Draft will expire on 4 March 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 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
skipping to change at page 2, line 44 skipping to change at page 2, line 44
6.1. Loc-RIB Implementation . . . . . . . . . . . . . . . . . 11 6.1. Loc-RIB Implementation . . . . . . . . . . . . . . . . . 11
6.1.1. Multiple Loc-RIB Peers . . . . . . . . . . . . . . . 11 6.1.1. Multiple Loc-RIB Peers . . . . . . . . . . . . . . . 11
6.1.2. Filtering Loc-RIB to BMP Receivers . . . . . . . . . 12 6.1.2. Filtering Loc-RIB to BMP Receivers . . . . . . . . . 12
6.1.3. Changes to existing BMP sessions . . . . . . . . . . 12 6.1.3. Changes to existing BMP sessions . . . . . . . . . . 12
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8.1. BMP Peer Type . . . . . . . . . . . . . . . . . . . . . . 12 8.1. BMP Peer Type . . . . . . . . . . . . . . . . . . . . . . 12
8.2. BMP Loc-RIB Instance Peer Flags . . . . . . . . . . . . . 12 8.2. BMP Loc-RIB Instance Peer Flags . . . . . . . . . . . . . 12
8.3. Peer Up Information TLV . . . . . . . . . . . . . . . . . 13 8.3. Peer Up Information TLV . . . . . . . . . . . . . . . . . 13
8.4. Peer Down Reason code . . . . . . . . . . . . . . . . . . 13 8.4. Peer Down Reason code . . . . . . . . . . . . . . . . . . 13
8.5. Deprecated entries . . . . . . . . . . . . . . . . . . . 13
9. Normative References . . . . . . . . . . . . . . . . . . . . 13 9. Normative References . . . . . . . . . . . . . . . . . . . . 13
10. Informative References . . . . . . . . . . . . . . . . . . . 14 10. Informative References . . . . . . . . . . . . . . . . . . . 14
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 14 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
This document defines a mechanism to monitor the BGP Loc-RIB state of This document defines a mechanism to monitor the BGP Loc-RIB state of
remote BGP instances without the need to establish BGP peering remote BGP instances without the need to establish BGP peering
sessions. BMP [RFC7854] does not define a method to send the BGP sessions. BMP [RFC7854] does not define a method to send the BGP
skipping to change at page 12, line 48 skipping to change at page 12, line 48
8.1. BMP Peer Type 8.1. BMP Peer Type
This document defines a new peer type (Section 4.1): This document defines a new peer type (Section 4.1):
* Peer Type = 3: Loc-RIB Instance Peer * Peer Type = 3: Loc-RIB Instance Peer
8.2. BMP Loc-RIB Instance Peer Flags 8.2. BMP Loc-RIB Instance Peer Flags
This document requests IANA to rename "BMP Peer Flags" to "BMP Peer 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 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 "BMP Peer Flags for Loc-RIB Instance Peer Type 3." This document
defines that peer flags are specific to the Loc-RIB instance peer defines that peer flags are specific to the Loc-RIB instance peer
type. As defined in (Section 4.2): type. As defined in (Section 4.2):
* Flag 0: 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 indicates that the Loc-RIB does not represent the complete routing
table. table.
Flags 0 through 3 and 5 through 7 are unassigned. The registration Flags 0 through 3 and 5 through 7 are unassigned. The registration
procedure for the registry is "Standards Action". procedure for the registry is "Standards Action".
skipping to change at page 13, line 32 skipping to change at page 13, line 32
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 = 6: Local system closed, TLV data follows. * Type = 6: Local system closed, TLV data follows.
8.5. Deprecated entries
This document also requests that IANA marks as "deprecated" the F
Flag entry in the "BMP Peer Flags for Peer Types 0 through 2"
registry.
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,
DOI 10.17487/RFC4271, January 2006, DOI 10.17487/RFC4271, January 2006,
 End of changes. 7 change blocks. 
5 lines changed or deleted 12 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/