%% You should probably cite rfc8330 instead of this I-D.
@techreport{ietf-ccamp-ospf-availability-extension-13,
    number =    {draft-ietf-ccamp-ospf-availability-extension-13},
    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-ccamp-ospf-availability-extension/13/},
    author =    {Hao Long and Min Ye and Greg Mirsky and Alessandro D'Alessandro and Himanshu C. Shah},
    title =     {{OSPF Traffic Engineering (OSPF-TE) Link Availability Extension for Links with Variable Discrete Bandwidth}},
    pagetotal = 10,
    year =      2017,
    month =     dec,
    day =       5,
    abstract =  {A network may contain links with variable discrete bandwidth, e.g., microwave and copper. The bandwidth of such links may change discretely in response to a changing external environment. The word "availability" is typically used to describe such links during network planning. This document defines a new type of Generalized Switching Capability-Specific Information (SCSI) TLV to extend the Generalized Multiprotocol Label Switching (GMPLS) Open Shortest Path First (OSPF) routing protocol. The extension can be used for route computation in a network that contains links with variable discrete bandwidth. Note that this document only covers the mechanisms by which the availability information is distributed. The mechanisms by which availability information of a link is determined and the use of the distributed information for route computation are outside the scope of this document. It is intended that technology-specific documents will reference this document to describe specific uses.},
}