Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer engineering Segment Identifiers (SIDs) with MPLS Data Planes
draft-hegde-mpls-spring-epe-oam-02

Document Type Active Internet-Draft (individual)
Last updated 2019-07-03
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)
Routing area                                                    S. Hegde
Internet-Draft                                                  K. Arora
Intended status: Standards Track                           M. Srivastava
Expires: January 4, 2020                           Juniper Networks Inc.
                                                            July 3, 2019

   Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR)
Egress Peer engineering Segment Identifiers (SIDs) with MPLS Data Planes
                   draft-hegde-mpls-spring-epe-oam-02

Abstract

   Egress Peer Engineering is an application of Segment Routing to solve
   the problem of egress peer selection.  The SR-based BGP-EPE solution
   allows a centralized (Software Defined Network, SDN)controller to
   program any egress peer.  The EPE solution requires a node to program
   PeerNodeSID, PeerAdjSID, PeerSetSID as described in
   [I-D.ietf-spring-segment-routing-central-epe].  This document
   provides new sub-TLVs for EPE SIDs that would be used in Target stack
   TLV (Type 1) as defined in [RFC8029] for the EPE SIDs.

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 January 4, 2020.

Hegde, et al.            Expires January 4, 2020                [Page 1]
Internet-Draft                   EPE-OAM                       July 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.  FEC Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  PeerAdjSID Sub-TLV  . . . . . . . . . . . . . . . . . . .   3
     2.2.  PeerNodeSID Sub-TLV . . . . . . . . . . . . . . . . . . .   4
     2.3.  PeerSetSID Sub-TLV  . . . . . . . . . . . . . . . . . . .   6
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

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 anomaly can be detected easily by the operator.

   This document provides Target FEC stack TLV definitions for EPE SIDs.
   Other procedures for mpls ping and traceroute as defined in [RFC8287]
   are applicable for EPE-SIDs as well.

Hegde, et al.            Expires January 4, 2020                [Page 2]
Internet-Draft                   EPE-OAM                       July 2019

2.  FEC Definitions

   As described in [RFC8287] sec 5, 3 new type of sub-TLVs for the
Show full document text