%% You should probably cite rfc8379 instead of this I-D.
@techreport{ietf-ospf-link-overload-03,
    number =    {draft-ietf-ospf-link-overload-03},
    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-ospf-link-overload/03/},
    author =    {Shraddha Hegde and Pushpasis Sarkar and Hannes Gredler and Mohan Nanduri and Luay Jalil},
    title =     {{OSPF Link Overload}},
    pagetotal = 11,
    year =      2017,
    month =     feb,
    day =       13,
    abstract =  {When a link is being prepared to be taken out of service, the traffic needs to be diverted from both ends of the link. Increasing the metric to the highest metric on one side of the link is not sufficient to divert the traffic flowing in the other direction. It is useful for routers in an OSPFv2 or OSPFv3 routing domain to be able to advertise a link being in an overload state to indicate impending maintenance activity on the link. This information can be used by the network devices to re-route the traffic effectively. This document describes the protocol extensions to disseminate link overload information in OSPFv2 and OSPFv3.},
}