RFC1466 is out at last
- Date: Wed, 26 May 1993 23:29:26 +0200
------- Forwarded Message
Date: Wed, 26 May 93 11:44:55 PDT
From: "Joyce K. Reynolds" jkrey@localhost
Sender: ietf-announce-request@localhost
To: IETF-Announce:group list ;
cc: jkrey@localhost
Subject: RFC1466 on Guidelines for Management of IP Address Space
- --NextPart
A new Request for Comments is now available in online RFC libraries.
RFC 1466:
Title: Guidelines for Management of IP Address Space
Author: E. Gerich
Mailbox: epg@localhost
Pages: 10
Characters: 22,262
Obsoletes: RFC 1366
This document has been reviewed by the Federal Engineering Planning
Group (FEPG) on behalf of the Federal Networking Council (FNC), the
co-chairs of the Intercontinental Engineering Planning Group (IEPG),
and the Reseaux IP Europeens (RIPE). There was general consensus by
those groups to support the recommendations proposed in this document
for management of the IP address space.
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@localhost. Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@localhost.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@localhost" with the message body
"help: ways_to_get_rfcs". For example:
To: rfc-info@localhost
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@localhost. 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@localhost. 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 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-server@localhost"
Content-Type: text/plain
SEND rfc1466.txt
- --OtherAccess
Content-Type: Message/External-body;
name="rfc1466.txt";
site="nic.ddn.mil";
access-type="anon-ftp";
directory="rfc"
Content-Type: text/plain
- --OtherAccess--
- --NextPart--
------- End of Forwarded Message
