IGP Extensions for Segment Routing Service Segment
draft-lz-lsr-igp-sr-service-segments-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-02-24
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
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)
|
LSR Working Group Yao. Liu
Internet-Draft Zheng. Zhang
Intended status: Standards Track ZTE Corporation
Expires: August 27, 2020 February 24, 2020
IGP Extensions for Segment Routing Service Segment
draft-lz-lsr-igp-sr-service-segments-01
Abstract
This document defines extensions to the link-state routing protocols
(IS-IS and OSPF) in order to carry service segment information via
IGP.
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 August 27, 2020.
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.
Liu & Zhang Expires August 27, 2020 [Page 1]
Internet-Draft IGP for Service Segment February 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IGP Extensions for Service Segments . . . . . . . . . . . . . 3
2.1. IS-IS Extensions . . . . . . . . . . . . . . . . . . . . 3
2.2. OSPF Extensions . . . . . . . . . . . . . . . . . . . . . 5
3. Security Considerations . . . . . . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Normative References . . . . . . . . . . . . . . . . . . 7
5.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
Segments are introduced in the SR architecture [RFC8402]. Segment
Routing (SR) allows for a flexible definition of end-to-end paths by
encoding paths as sequences of topological sub-paths, called
"segments".
Service Function Chaining (SFC) [RFC7665] provides support for the
creation of composite services that consist of an ordered set of
Service Functions (SF) that are to be applied to packets and/or
frames selected as a result of classification.
[I-D.ietf-spring-sr-service-programming] describes how a service can
be associated with a SID and how to achieve service funtion chaining
in SR-enabled MPLS and IPv6 networks. It also defines SR-aware and
SR-unaware services. For a SR-unaware service ,there has to be a SR
proxy handling the SR processing on behalf of the service .
[I-D.dawra-idr-bgp-ls-sr-service-segments] propose extensions to BGP-
LS for Service Chaining to distribute the service segment information
to SR Controller.
The network topology is shown in figure 1.
SR-C
|
|
A----1----2----3----4----5----B
| |
| |
S1 S2 proxy----S2
Figure 1: Figure 1:Network with Services
Liu & Zhang Expires August 27, 2020 [Page 2]
Internet-Draft IGP for Service Segment February 2020
Node 1-5 are nodes capital of segment routing. A and B are two end
hosts. S1 is an SR-aware Service. S2 is an SR-unaware Service.
SR Controller (SR-C) is connected to node 1, but may be attached to
any node 1-5 in the network.
SR-C is capable of receiving BGP-LS updates to discover topology, and
calculating constrained paths between 1 and 5.
If node 1 gets the service segment information, it can use the BGP-LS
extensions [I-D.ietf-spring-sr-service-programming] to advertise it
to the SR-C, but how can node 1 get it is a question.but node 1 must
get the service segment information from other nodes at first.
Show full document text