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

  
        RFC 1371:

        Title:      Choosing a "Common IGP" for the IP Internet
                    (The IESG's Recommendation to the IAB)
        Author:     P. Gross, Editor
        Mailbox:    pgross@ans.net
        Pages:      9
        Characters: 18,168
        Updates/Obsoletes:  none


This memo presents motivation, rationale and other surrounding
background information leading to the IESG's (Internet Engineering
Steering Group) recommendation to the IAB for a single "common IGP"
for the IP portions of the Internet.

This document was originally prepared as an IESG recommendation to the
Internet Architecture Board (IAB) in mid-summer 1991, reaching the
current version by the date shown above.  Although the document is now
somewhat dated (e.g., CIDR and RIP II are not mentioned), the IESG
felt it was important to publish this along with the recent OSPF
Applicability Statement (RFC 1370) to help establish context and
motivation.

This memo provides information for the Internet community.  It does
not specify an Internet standard.  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 rfc1371.txt

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

Content-Type: text/plain


--OtherAccess--
--NextPart--