RFC1467 on Status of CIDR Deployment in the Internet

"Joyce K. Reynolds" <jkrey@isi.edu> Fri, 06 August 1993 22:26 UTC

Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa15727; 6 Aug 93 18:26 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa12852; 6 Aug 93 18:26 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15717; 6 Aug 93 18:26 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa15656; 6 Aug 93 18:24 EDT
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa12797; 6 Aug 93 18:24 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-13) id <AA18538>; Fri, 6 Aug 1993 15:25:33 -0700
Message-Id: <199308062225.AA18538@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1467 on Status of CIDR Deployment in the Internet
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 06 Aug 1993 15:25:27 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

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


        RFC 1467:

        Title:      Status of CIDR Deployment in the Internet
        Author:     C. Topolcic
        Mailbox:    topolcic@CNRI.Reston.VA.US
        Pages:      9
        Characters: 20,720
        Obsoletes:  1367


This document describes the current status of the development and
deployment of CIDR technology into the Internet. This document
replaces RFC 1367, which was a schedule for the deployment of IP
address space management procedures to support route aggregation.
Since all the milestones proposed in RFC 1367 except for the delivery
and installation of CIDR software were met, it does not seem
appropriate to issue an updated schedule. Rather, this document is
intended to provide information about how this effort is proceeding,
which may be of interest to the community.

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@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 NIC.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 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.
ftp://ds.internic.net/rfc/rfc1467.txt"><ftp://ds.internic.net/rfc/rfc1467.txt>