BGP-LS extensions for Segment Routing BGP Egress Peer Engineering
draft-ietf-idr-bgpls-segment-routing-epe-19
| Document | Type | Active Internet-Draft (idr WG) | ||
|---|---|---|---|---|
| Authors | Stefano Previdi , Ketan Talaulikar , Clarence Filsfils , Keyur Patel , Saikat Ray , Jie Dong | |||
| Last updated | 2019-05-23 (latest revision 2019-05-16) | |||
| Replaces | draft-previdi-idr-bgpls-segment-routing-epe | |||
| Stream | IETF | |||
| Intended RFC status | Proposed Standard | |||
| Formats | plain text pdf htmlized (tools) htmlized bibtex | |||
| Reviews | ||||
| Stream | WG state | Submitted to IESG for Publication | ||
| Document shepherd | Susan Hares | |||
| Shepherd write-up | Show (last changed 2018-11-04) | |||
| IESG | IESG state | RFC Ed Queue | ||
| Action Holders |
(None)
|
|||
| Consensus Boilerplate | Yes | |||
| Telechat date | ||||
| Responsible AD | Alvaro Retana | |||
| Send notices to | "Susan Hares" <shares@ndzh.com>, aretana.ietf@gmail.com | |||
| IANA | IANA review state | IANA OK - Actions Needed | ||
| IANA action state | RFC-Ed-Ack | |||
| RFC Editor | RFC Editor state | MISSREF | ||
| Details | ||||
Inter-Domain Routing S. Previdi
Internet-Draft Individual
Intended status: Standards Track K. Talaulikar, Ed.
Expires: November 17, 2019 C. Filsfils
Cisco Systems, Inc.
K. Patel
Arrcus, Inc.
S. Ray
Individual Contributor
J. Dong
Huawei Technologies
May 16, 2019
BGP-LS extensions for Segment Routing BGP Egress Peer Engineering
draft-ietf-idr-bgpls-segment-routing-epe-19
Abstract
Segment Routing (SR) leverages source routing. A node steers a
packet through a controlled set of instructions, called segments, by
prepending the packet with an SR header. A segment can represent any
instruction, topological or service-based. SR segments allow
steering a flow through any topological path and service chain while
maintaining per-flow state only at the ingress node of the SR domain.
This document describes an extension to BGP Link-State (BGP-LS) for
advertisement of BGP Peering Segments along with their BGP peering
node information so that efficient BGP Egress Peer Engineering (EPE)
policies and strategies can be computed based on Segment Routing.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [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/.
Previdi, et al. Expires November 17, 2019 [Page 1]
Internet-Draft Segment Routing EPE BGP-LS Extensions May 2019
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 November 17, 2019.
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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. BGP Peering Segments . . . . . . . . . . . . . . . . . . . . 4
3. BGP-LS NLRI Advertisement for BGP Protocol . . . . . . . . . 5
3.1. BGP Router-ID and Member AS Number . . . . . . . . . . . 6
3.2. Mandatory BGP Node Descriptors . . . . . . . . . . . . . 6
3.3. Optional BGP Node Descriptors . . . . . . . . . . . . . . 7
4. BGP-LS Attributes for BGP Peering Segments . . . . . . . . . 7
4.1. Advertisement of the PeerNode SID . . . . . . . . . . . . 10
4.2. Advertisement of the PeerAdj SID . . . . . . . . . . . . 11
4.3. Advertisement of the PeerSet SID . . . . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
5.1. New BGP-LS Protocol-ID . . . . . . . . . . . . . . . . . 13
5.2. Node Descriptors and Link Attribute TLVs . . . . . . . . 13
6. Manageability Considerations . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 15
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
10.1. Normative References . . . . . . . . . . . . . . . . . . 16
Show full document text