%% You should probably cite draft-ietf-ospf-link-overload instead of this I-D.
@techreport{hegde-ospf-link-overload-01,
    number =    {draft-hegde-ospf-link-overload-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-hegde-ospf-link-overload/01/},
    author =    {Shraddha Hegde and Hannes Gredler and Mohan Nanduri and Luay Jalil},
    title =     {{OSPF Link Overload}},
    pagetotal = 8,
    year =      2015,
    month =     jul,
    day =       19,
    abstract =  {Many OSPFv2 or OSPFv3 deployments run on overlay networks provisioned by means of pseudo-wires or L2-circuits. when the devices in the underlying network go for maintenance, it is useful to divert the traffic away from the node before the maintenance is actually scheduled. Since the nodes in the underlying network are not visible to OSPF, existing stub router mechanism described in {[}RFC3137{]} cannot be used. It is useful for routers in OSPFv2 or OSPFv3 routing domain to be able to advertise a link being in overload state to indicate impending maintenance activity in the underlying network devices. This document describes the protocol extensions to disseminate link overload information in OSPFv2 and OSPFv3 protocol.},
}