Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering Segment Identifiers (SIDs) with MPLS Data Plane
draft-ietf-mpls-sr-epe-oam-19

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mpls-sr-epe-oam@ietf.org, james.n.guichard@futurewei.com, mpls-chairs@ietf.org, mpls@ietf.org, rfc-editor@rfc-editor.org, tsaad.net@gmail.com
Subject: Protocol Action: 'Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering Segment Identifiers (SIDs) with MPLS Data Plane' to Proposed Standard (draft-ietf-mpls-sr-epe-oam-19.txt)

The IESG has approved the following document:
- 'Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR)
   Egress Peer Engineering Segment Identifiers (SIDs) with MPLS Data
   Plane'
  (draft-ietf-mpls-sr-epe-oam-19.txt) as Proposed Standard

This document is the product of the Multiprotocol Label Switching Working
Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and John
Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mpls-sr-epe-oam/

Ballot Text

Technical Summary

   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.

Working Group Summary

   Working group reached broad consensus.

Document Quality

   Section 8 of the document provides details on existing implementations.


Personnel

   The Document Shepherd for this document is Tarek Saad. The Responsible
   Area Director is Jim Guichard.

RFC Editor Note