<?xml version='1.0'?>

<reference anchor='RFC2178'>

<front>
<title>OSPF Version 2</title>
<author initials='J.' surname='Moy' fullname='John Moy'>
<organization>Cascade Communications Corp.</organization>
<address>
<postal>
<street>5 Carlisle Road</street>
<city>Westford</city>
<region>MA</region>
<code>01886</code>
<country>US</country></postal>
<phone>+1 508 952 1367</phone>
<facsimile>+1 508 692 9214</facsimile>
<email>jmoy@casc.com</email></address></author>
<date month='July' year='1997' />
<abstract>
<t>This memo documents version 2 of the OSPF protocol. OSPF is a link-state routing protocol.  It is designed to be run internal to a single Autonomous System.  Each OSPF router maintains an identical database describing the Autonomous System's topology.  From this database, a routing table is calculated by constructing a shortest-path tree.</t>
<t>OSPF recalculates routes quickly in the face of topological changes, utilizing a minimum of routing protocol traffic.  OSPF provides support for equal-cost multipath.  An area routing capability is provided, enabling an additional level of routing protection and a reduction in routing protocol traffic.  In addition, all OSPF routing protocol exchanges are authenticated.</t>
<t>The differences between this memo and RFC 1583 are explained in Appendix G. All differences are backward-compatible in nature. Implementations of this memo and of RFC 1583 will interoperate.</t>
<t>Please send comments to ospf@gated.cornell.edu.</t></abstract></front>

<seriesInfo name='RFC' value='2178' />
</reference>
