BGP Route Policy and Attribute Trace Using BMP
draft-xu-grow-bmp-route-policy-attr-trace-04
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-01-05
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group F. Xu
Internet-Draft Tencent
Intended status: Standards Track T. Graf
Expires: July 9, 2020 Swisscom
Y. Gu
S. Zhuang
Z. Li
Huawei
January 6, 2020
BGP Route Policy and Attribute Trace Using BMP
draft-xu-grow-bmp-route-policy-attr-trace-04
Abstract
The generation of BGP adj-rib-in, local-rib or adj-rib-out comes from
BGP route exchange and route policy processing. BGP Monitoring
Protocol (BMP) provides the monitoring of BGP adj-rib-in [RFC7854],
BGP local-rib [I-D.ietf-grow-bmp-local-rib] and BGP adj-rib-out
[I-D.ietf-grow-bmp-adj-rib-out]. By monitoring these BGP RIB's the
full state of the network is visible, but how route-policies affect
the route propagation or changes BGP attributes is still not. This
document describes a method of using BMP to record the trace data on
how BGP routes are (not) changed under the process of route policies.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
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 July 9, 2020.
Xu, et al. Expires July 9, 2020 [Page 1]
Internet-Draft Route Policy-Attribute Trace January 2020
Copyright Notice
Copyright (c) 2020 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 and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. BGP Route Policy and Attribute Trace Overview . . . . . . 3
1.2. Use cases . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Extension of BMP for Route Policy and Attribute Trace . . . . 4
2.1. Common Header . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Per Peer Header . . . . . . . . . . . . . . . . . . . . . 4
2.3. Route Policy and Attribute Trace Message . . . . . . . . 4
2.3.1. VRF/Table TLV . . . . . . . . . . . . . . . . . . . . 7
2.3.2. Policy TLV . . . . . . . . . . . . . . . . . . . . . 8
2.3.3. Pre Policy Attribute TLV . . . . . . . . . . . . . . 11
2.3.4. Post Policy Attribute TLV . . . . . . . . . . . . . . 11
2.3.5. String TLV . . . . . . . . . . . . . . . . . . . . . 12
3. Implementation Considerations . . . . . . . . . . . . . . . . 13
4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. Normative References . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
The typical processing procedure after receiving a BGP Update Message
at a routing device is as follows: 1. Adding the pre-policy routes
into the pre-policy adj-rib-in (if any); 2. Filtering the pre-policy
routes through inbound route policies; 3. Selecting the BGP best
routes from the post-policy routes; 4. Adding the selected routes
into the BGP local-rib; 5-a. Adding the BGP best routes from local-
Show full document text