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


        RFC 1620:

        Title:      Internet Architecture Extensions for Shared Media
        Author:     B. Braden, J. Postel & Y. Rekhter
        Mailbox:    Braden@ISI.EDU, Postel@ISI.EDU,
                    Yakov@WATSON.IBM.COM 
        Pages:      19
        Characters: 44,999
        Updates/Obsoletes:  none


The original Internet architecture assumed that each network is
labeled with a single IP network number.  This assumption may be
violated for shared media, including "large public data networks"
(LPDNs).  The architecture still works if this assumption is violated,
but it does not have a means to prevent multiple host-router and
router-router hops through the shared medium.  This memo discusses
alternative approaches to extending the Internet architecture to
eliminate some or all unnecessary hops.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  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@CNRI.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 admin@DS.INTERNIC.NET.  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 1543, 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 retrieve the ASCII version
of the RFCs.

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

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="mailserv@ds.internic.net"

Content-Type: text/plain
Content-ID: <940519173237.RFC@ISI.EDU>

SEND /rfc/rfc1620.txt

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc1620.txt";
        site="ds.internic.net";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain
Content-ID: <940519173237.RFC@ISI.EDU>

--OtherAccess--
--NextPart--