%% You should probably cite rfc7347 instead of this I-D.
@techreport{zulr-mpls-tp-linear-protection-switching-11,
    number =    {draft-zulr-mpls-tp-linear-protection-switching-11},
    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/11/},
    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 = 31,
    year =      2014,
    month =     feb,
    day =       13,
    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. {[}Editor's note{]} The followings are to be included in "Status of Memo": This document is not an Internet Standards Track specification; it is published for informational purposes. This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc- editor.org/info/rfcxxxx.},
}