Color Operation with BGP Label Unicast
draft-chan-idr-bgp-lu2-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-04-16
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized (tools)
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)
|
IDR Working Group Louis Chan
INTERNET-DRAFT
Intended status: Experimental Juniper Networks
Expires: Oct 15, 2020 Apr 16, 2020
Color Operation with BGP Label Unicast
draft-chan-idr-bgp-lu2-01.txt
Abstract
This document specifies how to carry colored path advertisement via an enhancement
to the existing protocol BGP Label Unicast. It would allow backward compatibility
with RFC8277.
The targeted solution is to use stack of labels advertised via BGP Label Unicast
2.0 for end to end traffic steering across multiple IGP domains. The operation is
similar to Segment Routing.
This proposed protocol will convey the necessary reachability information to the
ingress PE node to construct an end to end path
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
http://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 Oct 15, 2020.
Copyright Notice
Copyright (c) 2017 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 (http://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
Chan Expires Oct 15, 2020 [Page 1]
Internet-Draft draft-chan-idr-bgp-lu2-01.txt April 2020
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. Conventions used in this document..............................3
3. Carrying Label Mapping Information with Color and Label Stack..4
3.1. Color extended community for BGP Labeled Unicast..........4
3.2. Color extended community for service prefixes.............5
4. Uniqueness of path entries.....................................5
5. AIGP consideration.............................................5
6. Explicit Withdraw of a <color, prefix>.........................6
7. Error Handling Procedure.......................................6
8. Controller Compatibility.......................................6
9. Security Considerations........................................6
10. IANA Considerations...........................................6
11. References....................................................7
11.1. Normative References.....................................7
11.2. Informative References...................................7
12. Acknowledgments...............................................8
1. Introduction
The proposed protocol is aimed to solve interdomain traffic steering, with
different transport services in mind. One application is low latency service across
multiple IGP domains, which could scale up to 100k routers network.
BGP is a flexible protocol. With additional of color attribute to BGP Label
Unicast, a path with specific color would be given a meaning in application - a low
latency path, a fully protected path, or a path for diversity.
The stack of labels would mean an end to end path across domains through each ABR
or ASBR. Each ABR or ASBR will take one label from the stack, and hence pick the
forwarding path to next ABR, ASBR, or the final destination.
And the label in the stack may be derived from any of the below
- Prefix SID
- Binding SID for RSVP LSP
Show full document text