@techreport{dubrovsky-ospf-non-compatible-02,
    number =    {draft-dubrovsky-ospf-non-compatible-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-dubrovsky-ospf-non-compatible/02/},
    author =    {Mike Dubrovsky and Rashmi Shrivastava and Dean Cheng},
    title =     {{Extensions to OSPF facilitating the deployment of non-backward- compatible changes.}},
    pagetotal = 10,
    year =      2014,
    month =     oct,
    day =       19,
    abstract =  {This document specifies a generic mechanism that facilitates the deployment of non-backward-compatible changes in OSPF protocol. This mechanism allows the OSPF routers to advertise the capability of non- backward-compatible functionality and to make the functionality operational only when supported by all participating routers. Depending on the functionality scope, capability advertisements must be propagated across a link, area or autonomous system (AS). For link and area scope functionality, Router Information Link State Advertisement (LSA) is utilized to propagate the capability information. For the cases when compatibility must be maintained across the whole OSPF autonomous system, new Area Information (AI) LSA is introduced. The AI LSA is a TLV-based analog of Indication- LSA that is used for demand circuit functionality and described in RFC1793.},
}