BGP Extensions for Routing Policy Distribution (RPD)
draft-ietf-idr-rpd-00
|
| Document |
Type |
|
Active Internet-Draft (idr WG)
|
|
Last updated |
|
2019-11-01
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group Z. Li
Internet-Draft Huawei
Intended status: Standards Track L. Ou
Expires: May 4, 2020 Y. Luo
China Telcom Co., Ltd.
S. Lu
Tencent
H. Chen
Futurewei
S. Zhuang
H. Wang
Huawei
November 1, 2019
BGP Extensions for Routing Policy Distribution (RPD)
draft-ietf-idr-rpd-00
Abstract
It is hard to adjust traffic and optimize traffic paths on a
traditional IP network from time to time through manual
configurations. It is desirable to have an automatic mechanism for
setting up routing policies, which adjust traffic and optimize
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 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."
Li, et al. Expires May 4, 2020 [Page 1]
Internet-Draft BGP RPD November 2019
This Internet-Draft will expire on May 4, 2020.
Copyright Notice
Copyright (c) 2019 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
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Problem Statements . . . . . . . . . . . . . . . . . . . . . 3
3.1. Inbound Traffic Control . . . . . . . . . . . . . . . . . 3
3.2. Outbound Traffic Control . . . . . . . . . . . . . . . . 4
4. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 5
4.1. Using a New AFI and SAFI . . . . . . . . . . . . . . . . 5
4.2. BGP Wide Community . . . . . . . . . . . . . . . . . . . 6
4.2.1. New Wide Community Atoms . . . . . . . . . . . . . . 6
4.3. Capability Negotiation . . . . . . . . . . . . . . . . . 12
5. Consideration . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. Route-Policy . . . . . . . . . . . . . . . . . . . . . . 12
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
It is difficult to optimize traffic paths on a traditional IP network
because of:
o Heavy configuration and error prone. Traffic can only be adjusted
Show full document text