BGP Extensions for Routing Policy Distribution (RPD)
draft-ietf-idr-rpd-07
Network Working Group Z. Li
Internet-Draft Huawei
Intended status: Standards Track L. Ou
Expires: February 4, 2021 Y. Luo
China Telcom Co., Ltd.
S. Lu
Tencent
G. Mishra
Verizon Inc.
H. Chen
Futurewei
S. Zhuang
H. Wang
Huawei
August 3, 2020
BGP Extensions for Routing Policy Distribution (RPD)
draft-ietf-idr-rpd-07
Abstract
It is hard to adjust traffic and optimize traffic paths in a
traditional IP network from time to time through manual
configurations. It is desirable to have a mechanism for setting up
routing policies, which adjusts traffic and optimizes traffic paths
automatically. This document describes BGP Extensions for Routing
Policy Distribution (BGP RPD) to support this.
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 [RFC2119] [RFC8174]
when, and only when, they appear in all capitals, as shown here.
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
Li, et al. Expires February 4, 2021 [Page 1]
Internet-Draft BGP RPD August 2020
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 February 4, 2021.
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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Inbound Traffic Control . . . . . . . . . . . . . . . . . 4
3.2. Outbound Traffic Control . . . . . . . . . . . . . . . . 4
4. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 5
4.1. Using a New AFI and SAFI . . . . . . . . . . . . . . . . 5
4.2. BGP Wide Community and Atoms . . . . . . . . . . . . . . 6
4.2.1. RouteAttr TLV/sub-TLV . . . . . . . . . . . . . . . . 7
4.2.2. Sub-TLVs of the Parameters TLV . . . . . . . . . . . 10
4.3. Capability Negotiation . . . . . . . . . . . . . . . . . 12
5. Routing Policy Considerations . . . . . . . . . . . . . . . . 13
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9.1. Existing Assignments . . . . . . . . . . . . . . . . . . 14
9.2. Routing Policy Type Registry . . . . . . . . . . . . . . 14
9.3. RouteAttr Atom Type . . . . . . . . . . . . . . . . . . . 15
9.4. Route Attributes Sub-TLV Registry . . . . . . . . . . . . 15
9.5. Attribute Change Sub-TLV Registry . . . . . . . . . . . . 16
Show full document text