RFC1627 on Network 10 Considered Harmful (fwd)
NIC
From jk...@ISI.EDU Fri Jul 1 16:30:43 1994
Message-Id: <1994070120...@zephyr.isi.edu>
To: rfc-...@nic.ddn.mil
Subject: RFC1627 on Network 10 Considered Harmful
Cc: jk...@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 01 Jul 94 13:35:20 PDT
From: "Joyce K. Reynolds" <jk...@ISI.EDU>
--NextPart
A new Request for Comments is now available in online RFC libraries.
RFC 1627:
Title: Network 10 Considered Harmful (Some Practices
Shouldn't be Codified)
Author: E. Lear, E. Fair, D. Crocker & T. Kessler
Mailbox: le...@sgi.com, fa...@apple.com, dcro...@sgi.com,
kes...@eng.sun.com
Pages: 8
Characters: 18,823
Updates/Obsoletes: none
Re-use of Internet addresses for private IP networks is the topic of
the recent RFC 1597. It reserves a set of IP network numbers, for
(re-)use by any number of organizations, so long as those networks are
not routed outside any single, private IP network. RFC 1597 departs
from the basic architectural rule that IP addresses must be globally
unique, and it does so without having had the benefit of the usual,
public review and approval by the IETF or IAB. This document restates
the arguments for maintaining a unique address space. Concerns for
Internet architecture and operations, as well as IETF procedure, are
explored.
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-R...@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-R...@NIC.DDN.MIL.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-...@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-...@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 ad...@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-E...@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="mail...@ds.internic.net"
Content-Type: text/plain
Content-ID: <94070113...@ISI.EDU>
SEND /rfc/rfc1627.txt
--OtherAccess
Content-Type: Message/External-body;
name="rfc1627.txt";
site="ds.internic.net";
access-type="anon-ftp";
directory="rfc"
Content-Type: text/plain
Content-ID: <94070113...@ISI.EDU>
--OtherAccess--
--NextPart--