%% You should probably cite draft-ietf-lsr-ospf-transport-instance-06 instead of this revision.
@techreport{ietf-lsr-ospf-transport-instance-03,
    number =    {draft-ietf-lsr-ospf-transport-instance-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-lsr-ospf-transport-instance/03/},
    author =    {Acee Lindem and Yingzhen Qu and Abhay Roy and Sina Mirtorabi},
    title =     {{OSPF-GT (Generalized Transport)}},
    pagetotal = 15,
    year =      2022,
    month =     jul,
    day =       9,
    abstract =  {OSPFv2 and OSPFv3 include a reliable flooding mechanism to disseminate routing topology and Traffic Engineering (TE) information within a routing domain. Given the effectiveness of these mechanisms, it is advantageous to use the same mechanism for dissemination of other types of information within the domain. However, burdening OSPF with this additional information will impact intra-domain routing convergence and possibly jeopardize the stability of the OSPF routing domain. This document presents mechanisms to advertise this non-routing information in separate OSPF Generalized Transport (OSPF-GT) instances. OSPF-GT is not constrained to the semantics as traditional OSPF. OSPF-GT neighbors are not required to be directly attached since they are never used to compute hop-by-hop routing. Consequently, independent sparse topologies can be defined to dissemenate non- routing information only to those OSPF-GT routers requiring it.},
}