addresses for private nets

Fri Mar 18 13:02:18 UTC 1994

fyi

******  The following is a COPY  *****************************
Received: from IETF.nri.reston.VA.US by watson.ibm.com (IBM VM SMTP V2R3)
   with TCP; Thu, 17 Mar 94 20:00:31 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11828;
          17 Mar 94 16:07 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa11800;
          17 Mar 94 16:06 EST
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa22233;
          17 Mar 94 16:06 EST
Received: from zephyr.isi.edu by zephyr.isi.edu (5.65c/5.61+local-16)
    id <AA20030>; Thu, 17 Mar 1994 13:06:58 -0800
Message-Id: <199403172106.AA20030 at zephyr.isi.edu>
To: IETF-Announce: ;
Subject: RFC1597 on Address Allocation for Private Internets
Cc: jkrey at isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Thu, 17 Mar 94 13:06:58 PST
Sender:ietf-announce-request at IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey at isi.edu>

--NextPart

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

        RFC 1597:

        Title:      Address Allocation for Private Internets
        Author:     Y. Rekhter, B. Moskowitz, D. Karrenberg
                    & G. de Groot
        Mailbox:    yakov at watson.ibm.com, 3858921 at mcimail.com,
                    Daniel.Karrenberg at ripe.net,
                    GeertJan.deGroot at ripe.net
        Pages:      8
        Characters: 17,430
        Update/Obsoletes:  none

This RFC describes methods to preserve IP address space by not
allocating globally unique IP addresses to hosts private to an
enterprise while still permitting full network layer connectivity
between all hosts inside an enterprise as well as between all public
hosts of different enterprises.  The authors hope, that using these
methods, significant savings can be made on allocating IP address
space.  For the purposes of this memo, an enterprise is an entity
autonomously operating a network using TCP/IP and in particular
determining the addressing plan and address assignments within that
network.

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 at CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST at NIC.DDN.MIL.

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

        To: rfc-info at 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 at 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 at 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 at ds.internic.net"

Content-Type: text/plain
Content-ID: <940317130307.RFC at ISI.EDU>

SEND /rfc/rfc1597.txt

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

Content-Type: text/plain
Content-ID: <940317130307.RFC at ISI.EDU>

--OtherAccess--
--NextPart--