A new Request for Comments is now available in online RFC libraries.

  
        RFC 1370:

        Title:      Applicability Statement for OSPF
        Author:     Internet Architecture Board
        Mailbox:    Lyman@BBN.COM
        Pages:      2
        Characters: 4,303
        Updates/Obsoletes:  none


Users and vendors have expressed a strong need for IP routers from
different vendors that can interoperate using a common Interior
Gateway Protocol (IGP).  There is therefore an urgent requirement for
a high-functionality non-proprietary 'open' IGP that will be
ubiquitously available from all IP router vendors.

The Open Shortest Path First (OSPF) routing protocol was developed by
the IETF to fill this need.  This Applicability Statement specifies
the circumstances under which OSPF must be implemented by router
vendors.  The history of OSPF development and the reasoning behind
this Applicability Statement will be found in RFC 1371.

This Applicability Statement places a requirement on vendors claiming
conformance to this standard, in order to assure that users will have
the option of deploying OSPF when they need a multivendor,
interoperable IGP in their environment.  Users are of course free to
use whatever routing protocol best meets their requirements.

This is now a Proposed Standard Protocol.

This memo is an IAB standards track Applicability Statement 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 specification.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@NRI.RESTON.VA.US.  Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body 
"help: ways_to_get_rfcs".  For example:

	To: rfc-info@ISI.EDU
	Subject: getting rfcs

	help: ways_to_get_rfcs

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
RFC-EDITOR@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retreive the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="mail-server@nisc.sri.com"

Content-Type: text/plain

SEND rfc1370.txt

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc1370.txt";
        site="nic.ddn.mil";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain


--OtherAccess--
--NextPart--