BGP Extensions for Unified SID in TE Policy
draft-liu-idr-segment-routing-te-policy-complement-03
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-05-11
|
|
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 Yao. Liu
Internet-Draft Shaofu. Peng
Intended status: Standards Track ZTE Corporation
Expires: November 12, 2020 May 11, 2020
BGP Extensions for Unified SID in TE Policy
draft-liu-idr-segment-routing-te-policy-complement-03
Abstract
This document defines extensions to BGP in order to advertise Unified
SIDs in SR-TE policies.
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 November 12, 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 & Peng Expires November 12, 2020 [Page 1]
Internet-Draft BGP for Unified SID May 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. SR policy with Unified SID . . . . . . . . . . . . . . . . . 2
3. SR policy with U-SID Information Encoding . . . . . . . . . . 4
3.1. Option 1: Advertising SID Attribute within existing
Segment List sub-TLV . . . . . . . . . . . . . . . . . . 4
3.1.1. Indicating the UET Flavor of the First SID . . . . . 5
3.1.2. Indicating the UET Flavor of the Other SIDs . . . . . 6
3.1.3. Indicating the SID Structure and Truncated
Information . . . . . . . . . . . . . . . . . . . . . 7
3.2. Option 2: Introducing a new U-Segment List sub-TLV . . . 8
4. Controller Processing . . . . . . . . . . . . . . . . . . . . 9
5. Head-end Processing . . . . . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
Segment Routing [RFC8402] leverages the source routing paradigm. An
ingress node steers a packet through an ordered list of instructions,
called segments.
[I-D.ietf-spring-segment-routing-policy] details the concepts of SR
Policy and steering flow into an SR Policy.
[I-D.ietf-idr-segment-routing-te-policy] specifies the way to use BGP
to distribute one or more of the candidate paths of an SR Policy to
the headend of that policy.
With increasing requirements for a shorter identifier in a segment
routing network with the IPv6 data plane,
[I-D.mirsky-6man-unified-id-sr] proposed an extension of SRH that
enables the use of a shorter segment identifier, such as 32-bits
Label format SID or 32-bits IP address format SID.
This document defines extensions to BGP in order to advertise Unified
SIDs in SR-TE policies.
2. SR policy with Unified SID
As discussed in [I-D.ietf-spring-srv6-network-programming], the node
with the SRv6 capability will maintain its local SID table. A Local
Liu & Peng Expires November 12, 2020 [Page 2]
Internet-Draft BGP for Unified SID May 2020
SID is generally composed of two parts, that is, LOC:FUNCT, or may
carry arguments at the same time, that is, LOC:FUNCT:ARGS.
FUNCT indicates the local function of the packet on the node that
generates the LOC. ARGS may contain information related to traffic
and services, or any other information required for executing the
function. LOC indicates locator. In most cases, other nodes in the
Show full document text