Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering Segment Identifiers (SIDs) with MPLS Data Planes
draft-ietf-mpls-sr-epe-oam-00
Routing area S. Hegde
Internet-Draft K. Arora
Intended status: Standards Track M. Srivastava
Expires: December 18, 2020 Juniper Networks Inc.
S. Ninan
Individual Contributor
X. Xu
Alibaba Inc.
June 16, 2020
Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR)
Egress Peer Engineering Segment Identifiers (SIDs) with MPLS Data Planes
draft-ietf-mpls-sr-epe-oam-00
Abstract
Egress Peer Engineering (EPE) is an application of Segment Routing to
Solve the problem of egress peer selection. The Segment Routing
based BGP-EPE solution allows a centralized controller, e.g. a
Software Defined Network (SDN) controller to program any egress peer.
The EPE solution requires a node to program the PeerNode Segment
Identifier(SID) describing a session between two nodes, the PeerAdj
SID describing the link (one or more) that is used by sessions
between peer nodes, and the PeerSet SID describing an arbitrary set
of sessions or links between a local node and its peers. This
document provides new sub-TLVs for EPE Segment Identifiers (SID) that
would be used in the MPLS Target stack TLV (Type 1), in MPLS Ping and
Traceroute procedures.
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 18, 2020.
Hegde, et al. Expires December 18, 2020 [Page 1]
Internet-Draft EPE-OAM June 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Theory of Operation . . . . . . . . . . . . . . . . . . . . . 3
3. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
4. FEC Definitions . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. PeerAdj SID Sub-TLV . . . . . . . . . . . . . . . . . . . 4
4.2. PeerNode SID Sub-TLV . . . . . . . . . . . . . . . . . . 6
4.3. PeerSet SID Sub-TLV . . . . . . . . . . . . . . . . . . . 9
5. EPE-SID FEC validation . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 15
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction
Egress Peer Engineering (EPE) as defined in
[I-D.ietf-spring-segment-routing-central-epe] is an effective
mechanism to select the egress peer link based on different criteria.
The EPE-SIDs provide means to represent egress peer links. Many
network deployments have built their networks consisting of multiple
Autonomous Systems either for ease of operations or as a result of
network mergers and acquisitons. The inter-AS links connecting the
two Autonomous Systems could be traffic engineered using EPE-SIDs in
this case as well.It is important to be able to validate the control
plane to forwarding plane synchronization for these SIDs so that any
Show full document text