--NextPart


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

  
        RFC 1380:

        Title:      IESG Deliberations on Routing and Addressing
        Author:     P. Gross & P. Almquist
        Mailbox:    pgross@ans.net, Almquist@JESSICA.STANFORD.EDU
        Pages:      22
        Characters: 49,415 
        Updates/Obsoletes:  none


This memo summarizes issues surrounding the routing and addressing
scaling problems in the IP architecture, and it provides a brief
background of the ROAD (ROuting and ADdressing) group and related
activities in the Internet Engineering Task Force (IETF).

It also provides a preliminary report of the Internet Engineering
Steering Group (IESG) deliberations on how these routing and
addressing issues should be pursued in the Internet Architecture Board
(IAB)/IETF.

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 rfc1380.txt

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

Content-Type: text/plain


--OtherAccess--
--NextPart--