%% You should probably cite draft-ietf-mpls-sr-epe-oam instead of this I-D.
@techreport{hegde-mpls-spring-epe-oam-04,
    number =    {draft-hegde-mpls-spring-epe-oam-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-hegde-mpls-spring-epe-oam/04/},
    author =    {Shraddha Hegde and Kapil Arora and Mukul Srivastava and Samson Ninan and Xiaohu Xu},
    title =     {{Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer engineering Segment Identifiers (SIDs) with MPLS Data Planes}},
    pagetotal = 10,
    year =      2020,
    month =     feb,
    day =       3,
    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.},
}