RFC1367 on Schedule for IP Address Space Guidelines

" Joyce K. Reynolds " <jkrey@isi.edu> Fri, 23 October 1992 00:53 UTC

Message-Id: <199210230053.AA16047@zephyr.isi.edu>
To: IETF-Announce:;, rfc-dist@nic.ddn.mil
Subject: RFC1367 on Schedule for IP Address Space Guidelines
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 22 Oct 1992 17:53:35 -0700
Sender: List Manager <Postmaster@NRI.Reston.VA.US>
From: " Joyce K. Reynolds " <jkrey@isi.edu>

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

        RFC 1367:

        Title:      Schedule for IP Address Space Management
                    Guidelines
        Author:     C. Topolcic
        Mailbox:    topolcic@NRI.Reston.VA.US
        Pages:      3
        Characters: 4,780
        Updates/Obsoletes:  none

This memo suggests a schedule for the implementation of the IP network
number allocation plan described in RFC 1366.  This schedule is meant
to support the implementation and deployment of an address aggregation
mechanism for the Internet by proposing an achievable target for which
we can all aim.  The timely deployment of that aggregation mechanism
and the IP addressing plan will help the the size of the Internet
router forwarding tables and management of the IP address space.  By
doing so, it will help the current Internet addressing and routing
technology operate during the interim period until the next generation
technology is deployed. This interim solution in no way constrains the
selection of the next generation addressing and routing technology.

This draft schedule was put together by the FNC Engineering and
Planning Group (FEPG) based on the IP addressing plan BOF of the July
1992 IETF meeting, as well as discussions with a number (though, of
course, not all) of knowledgeable and interested parties,
including the IANA and IR.  This draft schedule assumes that the
address
aggregation mechanism will be available in the Internet by mid-1993.
The activities described in this schedule are the precursors to that
deployment, and will promote the efficient operation of that
mechanism.  We feel that our assumptions are realistic and that this
schedule can be met.  We encourage its open discussion as we move
toward community consensus.

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@NRI.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@NIC.DDN.MIL.  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 retreive the ASCII version
of the RFCs.

ftp://nic.ddn.mil/rfc/rfc1367.txt"><ftp://nic.ddn.mil/rfc/rfc1367.txt>

RFC1367 on Schedule for IP Address Space Guidelin… Joyce K. Reynolds