%% You should probably cite rfc8185 instead of this I-D.
@techreport{ietf-pals-mpls-tp-dual-homing-coordination-01,
    number =    {draft-ietf-pals-mpls-tp-dual-homing-coordination-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-pals-mpls-tp-dual-homing-coordination/01/},
    author =    {Weiqiang Cheng and Lei Wang and Han Li and Kai Liu and Shahram Davari and Jie Dong and Alessandro D'Alessandro},
    title =     {{Dual-Homing Coordination for MPLS Transport Profile (MPLS-TP) Pseudowires Protection}},
    pagetotal = 13,
    year =      2015,
    month =     oct,
    day =       19,
    abstract =  {In some scenarios, the MPLS Transport Profile (MPLS-TP) Pseudowires (PWs) are provisioned through either static configuration or management plane, where a dynamic control plane is not available. A fast protection mechanism for MPLS-TP PWs is needed to protect against the failure of Attachment Circuit (AC), the failure of Provider Edge (PE) and also the failure in the Packet Switched Network (PSN). The framework and scenarios for dual-homing pseudowire (PW) local protection are described in {[}draft-ietf-pals- mpls-tp-dual-homing-protection{]}. This document proposes a dual- homing coordination mechanism for MPLS-TP PWs, which is used for state exchange and coordination between the dual-homing PEs for dual- homing PW local protection.},
}