%% You should probably cite rfc8770 instead of this I-D.
@techreport{ietf-ospf-ospfv2-hbit-07,
    number =    {draft-ietf-ospf-ospfv2-hbit-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-ospf-ospfv2-hbit/07/},
    author =    {Keyur Patel and Padma Pillay-Esnault and Manish Bhardwaj and Serpil Bayraktar},
    title =     {{Host Router Support for OSPFv2}},
    pagetotal = 9,
    year =      2019,
    month =     may,
    day =       19,
    abstract =  {The OSPFv2 specifies an SPF algorithm that identifies transit vertices based on their adjacencies. Therefore, OSPFv2 does not have a mechanism to prevent traffic transiting a participating node if it is a transit vertex in the only existing or shortest path to the destination. The use of metrics to make the node undesirable can only help to repel traffic if an alternative better route exists. This document defines the Host-bit functionality to prevent other OSPFv2 routers from using the router for transit traffic in OSPFv2 routing domains. This document updates the {[}RFC2328{]} by assigning a new bit (Host-bit) in the OSPF Router-LSA bit registry. If the Host- bit is set, the calculation of the shortest-path tree for an area, as described in {[}RFC2328{]}, is modified by including a new check to verify that transit vertices have the Host-bit clear.},
}