%% You should probably cite rfc8330 instead of this I-D.
@techreport{ietf-ccamp-ospf-availability-extension-07,
    number =    {draft-ietf-ccamp-ospf-availability-extension-07},
    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/07/},
    author =    {Hao Long and Min Ye and Greg Mirsky and Alessandro D'Alessandro and Himanshu C. Shah},
    title =     {{OSPF-TE Link Availability Extension for Links with Variable Discrete Bandwidth}},
    pagetotal = 8,
    year =      2016,
    month =     oct,
    day =       8,
    abstract =  {A network may contain links with variable discrete bandwidth, e.g., copper, radio, etc. The bandwidth of such links may change discretely in reaction to changing external environment. Availability is typically used for describing such links during network planning. This document introduces an optional ISCD Availability sub-TLV to extend the Generalized Multi-Protocol Label Switching (GMPLS) Open Shortest Path First (OSPF) routing protocol. This extension can be used for route computation in a network that contains links with variable discrete bandwidth. Note, 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.},
}