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

Note: These are PostScript RFCs, secondary versions are available in
ASCII.  The secondary ASCII versions may lack figures and the
information encoded in typographic variation (italics, boldface,
etc.).  Since this information often provides essential context, the
ASCII versions are at best incomplete and at worst misleading.  Anyone
expecting to understand these documents is strongly encouraged to
obtain the PostScript versions.


	RFC 1246:

        Title:      Experience with the OSPF Protocol    
       	Author:     J. Moy, Editor
	Mailbox:    jmoy@proteon.com
        PS-Pages:  38           ASCII-Pages:  31
        PS-Characters:  141,924 ASCII-Characters:  70,441
	Obsoletes/Updates:  none

		pathname: rfc/rfc1246.ps


This is the second of two reports on the OSPF protocol.  These reports
are required by the IAB/IESG in order for an Internet routing protocol
to advance to Draft Standard Status.  OSPF is a TCP/IP routing protocol,
designed to be used internal to an Autonomous System (in other words,
OSPF is an Interior Gateway Protocol).

OSPF is currently designated as a Proposed Standard.  Version 1 of the
OSPF protocol was published in RFC 1131.  Since then OSPF version 2 has
been developed.  Version 2 has been documented in RFC 1247.  The changes
between version 1 and version 2 of the OSPF protocol are explained in
Appendix F of RFC 1247.  It is OSPF Version 2 that is the subject of this
report.

This report documents experience with OSPF V2.  This includes reports
on interoperability testing, field experience, simulations and the
current state of OSPF implementations.  It also presents a summary of
the OSPF Management Information Base (MIB), and a summary of OSPF
authentication mechanism.

This memo provides information for the Internet community.  It does not
specify any Internet standard.  Distribution of this memo is
unlimited.

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

These RFCs 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, 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