%% You should probably cite draft-ietf-mpls-tp-bfd-cc-cv instead of this I-D.
@techreport{asm-mpls-tp-bfd-cc-cv-04,
    number =    {draft-asm-mpls-tp-bfd-cc-cv-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-asm-mpls-tp-bfd-cc-cv/04/},
    author =    {David Allan and John Drake and George Swallow and Sami Boutros and Siva Sivabalan and David Ward},
    title =     {{Proactive Connection Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile}},
    pagetotal = 12,
    year =      2010,
    month =     may,
    day =       11,
    abstract =  {Continuity Check (CC), Proactive Connectivity Verification (CV) and Remote Defect Indication (RDI) functionalities required for are MPLS- TP OAM. Continuity Check monitors the integrity of the continuity of the path for any loss of continuity defect. Connectivity verification monitors the integrity of the routing of the path between sink and source for any connectivity issues. RDI enables an End Point to report, to its associated End Point, a fault or defect condition that it detects on a PW, LSP or Section. This document specifies methods for proactive CV, CC, and RDI for MPLS-TP Label Switched Path (LSP), PWs and Sections using Bidirectional Forwarding Detection (BFD). Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119 {[}1{]}.},
}