<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ospf-rfc4970bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-ospf-rfc4970bis-00">
   <front>
      <title>Extensions to OSPF for Advertising Optional Router Capabilities</title>
      <author initials="A." surname="Lindem" fullname="Acee Lindem">
         </author>
      <author initials="N." surname="Shen" fullname="Naiming Shen">
         </author>
      <author initials="J." surname="Vasseur" fullname="JP Vasseur">
         </author>
      <author initials="R." surname="Aggarwal" fullname="Rahul Aggarwal">
         </author>
      <author initials="S." surname="Shaffer" fullname="Scott Shaffer">
         </author>
      <date month="January" day="23" year="2015" />
      <abstract>
	 <t>   It is useful for routers in an OSPFv2 or OSPFv3 routing domain to
   know the capabilities of their neighbors and other routers in the
   routing domain.  This document proposes extensions to OSPFv2 and
   OSPFv3 for advertising optional router capabilities.  A new Router
   Information (RI) Link State Advertisement (LSA) is proposed for this
   purpose.  In OSPFv2, the RI LSA will be implemented with a new opaque
   LSA type ID.  In OSPFv3, the RI LSA will be implemented with a new
   LSA type function code.  In both protocols, the RI LSA can be
   advertised at any of the defined flooding scopes (link, area, or
   autonomous system (AS)).  This document obsoletes RFC 4970 by
   providing a revised specification including support for advertisement
   of multiple instances of the RI LSA and a TLV for functional
   capabilities.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ospf-rfc4970bis-00" />
   
</reference>
