%% You should probably cite rfc7347 instead of this I-D.
@techreport{zulr-mpls-tp-linear-protection-switching-09,
    number =    {draft-zulr-mpls-tp-linear-protection-switching-09},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-zulr-mpls-tp-linear-protection-switching/09/},
    author =    {Huub van Helvoort and Jeong-dong Ryoo and Zhang Haiyan and Feng Huang and Han Li and Alessandro D'Alessandro},
    title =     {{Pre-standard Linear Protection Switching in MPLS-TP}},
    pagetotal = 27,
    year =      2014,
    month =     jan,
    day =       25,
    abstract =  {The IETF Standards Track solution for MPLS Transport Profile (MPLS- TP) Linear Protection is provided in RFC 6378, draft-ietf-mpls-psc- updates and draft-ietf- mpls-tp-psc-itu. This document describes the pre-standard implementation of MPLS-TP Linear Protection that has been deployed by several network operators using equipment from multiple vendors. At the time of publication these pre-standard implementations were still in operation carrying live traffic." The specified mechanism supports 1+1 unidirectional/bidirectional protection switching and 1:1 bidirectional protection switching. It is purely supported by MPLS-TP data plane, and can work without any control plane. This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunications Union Telecommunications Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and PWE3 architectures to support the capabilities and functionalities of a packet transport network as defined by the ITU-T. {[}Editor's note{]} To be included in "Status of Memo": This document is not an Internet Standards Track specification; it is published for informational purposes.},
}