%% You should probably cite draft-zhang-ccamp-mpls-tp-rsvpte-ext-tunnel-num-05 instead of this revision.
@techreport{zhang-ccamp-mpls-tp-rsvpte-ext-tunnel-num-04,
    number =    {draft-zhang-ccamp-mpls-tp-rsvpte-ext-tunnel-num-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-zhang-ccamp-mpls-tp-rsvpte-ext-tunnel-num/04/},
    author =    {Fei Zhang and Venkatesan Mahalingam and Yunbin Xu and Rakesh Gandhi},
    title =     {{RSVP-TE Extensions to Exchange MPLS-TP LSP Tunnel Numbers}},
    pagetotal = 7,
    year =      2012,
    month =     aug,
    day =       16,
    abstract =  {The MPLS Transport Profile (MPLS-TP) identifiers document {[}RFC6370{]} specifies an initial set of identifiers, including the local assigned Z9-Tunnel\_Num, which can be used to form Maintenance Entity Point Identifier (MEP\_ID). As to some Operation, Administration and Maintenance (OAM) functions, such as Connectivity Verification (CV) {[}RFC6428{]}, source MEP\_ID must be inserted in the OAM packets, so that the peer endpoint can compare the received and expected MEP\_IDs to judge whether there is a mis-connectivity defect {[}RFC6371{]}, which means that the two MEP nodes need to pre-store each other's MEP\_IDs. This document defines the signaling extensions to communicate the local assigned Z9-Tunnel\_Num to the ingress LSR (Label Switching Router) of a co-routed bidirectional LSP.},
}