Advertising Segment Routing Policies Attributes in BGP
draft-peng-idr-segment-routing-te-policy-attr-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-06-05
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
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)
|
Network P. Shaofu
Internet-Draft L. Yao
Intended status: Standards Track ZTE Corporation
Expires: December 7, 2020 June 5, 2020
Advertising Segment Routing Policies Attributes in BGP
draft-peng-idr-segment-routing-te-policy-attr-00
Abstract
This document defines necessary attributes advertised with a
candidate path of a Segment Routing (SR) Policy when BGP is used to
distribute SR Policy. New sub-TLVs for the SR Policy attributes are
defined for signaling information about each segment to meet more
requirements.
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 December 7, 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.
Shaofu & Yao Expires December 7, 2020 [Page 1]
Internet-Draft BGP SR Policy Attr June 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. New Segment Types for SR-MPLS Policy . . . . . . . . . . . . 3
2.1. Type L: SID only, in the form of Algorithm related MPLS
Label . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Type M: IPv4 Address + Local Interface ID with optional
Algorithm related SID . . . . . . . . . . . . . . . . . . 4
2.3. Type N: IPv4 Local and Remote addresses with optional
Algorithm related SID . . . . . . . . . . . . . . . . . . 5
2.4. Type O: IPv6 Address + Interface ID for local and remote
pair with optional Algorithm related SID for SR MPLS . . 5
2.5. Type P: IPv6 Local and Remote addresses with optional
Algorithm related SID for SR MPLS . . . . . . . . . . . . 6
3. New Segment Types for SRv6 Policy . . . . . . . . . . . . . . 7
3.1. Type Q: SID only, in the form of Algorithm related IPv6
address . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2. Type R: IPv6 Node Address with optional Algorithm related
SRv6 SID . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3. Type S: IPv6 Address + Interface ID for local and remote
pair for SRv6 with optional Algorithm related SID . . . . 10
3.4. Type T: IPv6 Local and Remote addresses for SRv6 with
optional Algorithm related SID . . . . . . . . . . . . . 11
4. Operatoins . . . . . . . . . . . . . . . . . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
8. Normative References . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
Segment Routing (SR) [RFC8402] allows a headend node to steer a
packet flow along any path. Intermediate per-flow states are
eliminated thanks to source routing.
[I-D.ietf-spring-segment-routing-policy] details the concepts of SR
Policy and steering into an SR Policy. These apply equally to the
MPLS and IPv6 (known as SRv6) data plane instantiations of Segment
Routing with their respective representations of segments as SR-MPLS
SID and SRv6 SID as described in [RFC8402].
[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. It defines a new BGP address family
Show full document text