A new Request for Comments is now available from SRI's Network
Information Systems Center in the online library at FTP.NISC.SRI.COM.

Note: This is a PostScript RFC, a secondary version is available in
ASCII.  The secondary ASCII version may lack figures and the
information encoded in typographic variation (italics, boldface,
etc.).  Since this information often provides essential context, the
ASCII version is at best incomplete and at worst misleading.  Anyone
expecting to understand this document is strongly encouraged to obtain
the PostScript version.


	RFC 1247:

        Title:      OSPF Version 2
       	Author:     J. Moy
	Mailbox:    jmoy@proteon.com
        PS-Pages:  129          ASCII-Pages:  189
        PS-Characters:  989,724 ASCII-Characters:  433,332
	Obsoletes:  RFC 1131

		pathname: rfc/rfc1247.ps


This memo documents version 2 of the OSPF protocol.  OSPF is a link-
state based 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.

OSPF recalculates routes quickly in the face of topological changes,
utilizing a minimum of routing protocol traffic.  OSPF provides
support for equal-cost multipath.  Separate routes can be calculated
for each IP type of service.  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.

Version 1 of the OSPF protocol was documented in RFC 1131.  The
differences between the two versions are explained in Appendix F.

This RFC specifies a Draft Standard Protocol for the Internet
community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "IAB Official Protocol
Standards" for the standardization state and status of this protocol.
Distribution of this memo is unlimited.

RFCs can be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET, or
NISC.JVNC.NET.

This RFC can be obtained via FTP from FTP.NISC.SRI.COM, with the pathname
rfc/rfcnnnn.ps.  Login with FTP username "anonymous" and password
"guest".

SRI also provides an automatic mail service for those sites which
cannot use FTP.  Address the request to MAIL-SERVER@NISC.SRI.COM and
in the body of the message indicate the RFC to be sent: "send
rfcnnnn.ps" where nnnn is the RFC number.  Multiple requests may be
included in the same message by listing the "send" commands on
separate lines.  To obtain a PostScript RFC or FYI, specifically
indicate the ".ps" extension: "send rfc1131.ps".

To obtain RFCs from NIS.NSF.NET via FTP, login with username
"anonymous" and password "guest"; then connect to the RFC directory
("cd RFC").  The file name is of the form RFCnnnn.PS-1 (where "nnnn"
refers to the number of the RFC).

The NIS also provides an automatic mail service for those sites which
cannot use FTP.  Address the request to NIS-INFO@NIS.NSF.NET and leave
the subject field of the message blank.  The first line of the text of
the message must be "SEND RFCnnnn.PS-1", where nnnn is replaced by
the RFC number.

RFCs can also be obtained via FTP from NISC.JVNC.NET, with the
pathname rfc/RFCnnnn.PS.v (where "nnnn" refers to the number of the RFC
and "v" refers to the version number of the RFC).  Login with FTP,
username "anonymous" and your e-mail address as your password.

JvNCnet also provides a mail service for those sites which cannot use
FTP.  Address the request to SENDRFC@JVNC.NET and in the subject field
of the message indicate the RFC number, as in "Subject: RFCnnnn.PS" where
nnnn is the RFC number.  Please note that RFCs whose number are less
than 1000 need not place a "0". (For example, RFC932 is fine.)  No
text in the body of the message is needed.

To obtain the ASCII version, substitute "TXT" for "PS" in the
preceeding instructions.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
POSTEL@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.

Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.


Joyce K. Reynolds
USC/Information Sciences Institute