BGP-LS Advertisement of Segment Routing Service Segments
draft-dawra-idr-bgp-ls-sr-service-segments-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-07-08
|
|
Replaces |
|
draft-dawra-idr-bgp-sr-service-chaining
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
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)
|
Inter-Domain Routing G. Dawra, Ed.
Internet-Draft LinkedIn
Intended status: Standards Track C. Filsfils
Expires: January 9, 2020 Cisco Systems
D. Bernier
Bell Canada
J. Uttaro
AT&T
B. Decraene
Orange
H. Elmalky
Ericsson
X. Xu
Alibaba
F. Clad
K. Talaulikar
Cisco Systems
July 8, 2019
BGP-LS Advertisement of Segment Routing Service Segments
draft-dawra-idr-bgp-ls-sr-service-segments-02
Abstract
BGP Link-State (BGP-LS) enables distribution of topology information
from the network to a Path Computation Engine (PCE) or any
controller/application in general so it can learn the network
topology. Service functions are deployed as virtualized elements
along with network elements or on servers in data centers. The
advertisement of such attached service capabilities along with the
network nodes that they are attached to or associated with enable
their discovery and for programming of service paths that use these
service functions. Segment Routing (SR) bring in the concept of
segments which can be topological or service instructions. SR
Policies enable setup of paths which are a mix of topological and
service segments.
This document specifies the extensions to BGP-LS for discovery and
advertisement of service segments so as to enable setup of service
programming paths using 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
Dawra, et al. Expires January 9, 2020 [Page 1]
Internet-Draft BGP-LS Extensions for SR Service Segments July 2019
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/.
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 January 9, 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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. BGP-LS Extensions for Service Chaining . . . . . . . . . . . 4
3. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 7
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
4.1. Service Type Table . . . . . . . . . . . . . . . . . . . 7
4.2. Segment routing function Identifier(SFI) . . . . . . . . 8
5. Manageability Considerations . . . . . . . . . . . . . . . . 8
6. Operational Considerations . . . . . . . . . . . . . . . . . 8
6.1. Operations . . . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
Show full document text