SR Policies Extensions for Path Segment and Bidirectional Path in BGP-LS
draft-li-idr-bgp-ls-sr-policy-path-segment-03
|
| Document |
Type |
|
Active Internet-Draft (idr WG)
|
|
Last updated |
|
2019-08-15
(latest revision 2019-08-08)
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
WG state
|
|
Candidate for WG Adoption
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Interdomain Routing Working Group C. Li
Internet-Draft Huawei Technologies
Intended status: Standards Track H. Chen
Expires: February 9, 2020 China Telecom
M. Chen
J. Dong
Z. Li
Huawei Technologies
August 8, 2019
SR Policies Extensions for Path Segment and Bidirectional Path in BGP-LS
draft-li-idr-bgp-ls-sr-policy-path-segment-03
Abstract
This document specifies the way of collecting configuration and
states of SR policies carrying Path Segment and bidirectional path
information by using BPG-LS. Such information can be used by
external conponents for many use cases such as performance
measurement, path re-optimization and end-to-end protection.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
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 February 9, 2020.
Li, et al. Expires February 9, 2020 [Page 1]
Internet-Draft Path ID and Bi-directional Path in BGP-LS August 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Carrying SR Path Sub-TLVs in BGP-LS . . . . . . . . . . . . . 3
3.1. SR Path Segment Sub-TLV . . . . . . . . . . . . . . . . . 5
3.2. Sub-TLVs for Bidirectional Path . . . . . . . . . . . . . 6
3.2.1. SR Bidirectional Path Sub-TLV . . . . . . . . . . . . 6
3.2.2. SR Reverse Path Segment List Sub-TLV . . . . . . . . 7
4. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
5.1. BGP-LS TLVs . . . . . . . . . . . . . . . . . . . . . . . 7
5.2. BGP-LS SR Segment Descriptors . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
Segment routing (SR) [RFC8402] is a source routing paradigm that
allows the ingress node steers packets into a specific path according
to the Segment Routing Policy
[I-D.ietf-spring-segment-routing-policy].
However, the SR Policies defined in
[I-D.ietf-spring-segment-routing-policy] only supports unidirectional
SR paths and there is no path ID in a Segment List to identify an SR
path. For identifying an SR path and supporting bidirectional path
[I-D.ietf-spring-mpls-path-segment], new policies carrying Path
Segment and bidirectional path information are defined in
Li, et al. Expires February 9, 2020 [Page 2]
Internet-Draft Path ID and Bi-directional Path in BGP-LS August 2019
[I-D.li-idr-sr-policy-path-segment-distribution], as well as the
Show full document text