home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_j_p
/
draft-ietf-pier-solicitation-00.txt
< prev
next >
Wrap
Text File
|
1996-02-29
|
2KB
|
64 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1916:
Title: Enterprise Renumbering: Experience and Information
Solicitation
Author: H. Berkowitz, P. Ferguson, W. Leland, & P. Nesser
Date: February 1996
Mailbox: hcb@clark.net, pferguso@cisco.com,
wel@bellcore.com, pjnesser@rocket.com
Pages: 8
Characters: 16,117
Updates/Obsoletes: none
URL: ftp://ds.internic.net/rfc/rfc1916.txt
Because of the urgent need for, and substantial difficulty in,
renumbering IP networks, the PIER working group is compiling a series
of documents to assist sites in their renumbering efforts. The intent
of these documents is to provide both educational and practical
information to the Internet community. To this end the working group
is soliciting information from organizations that already have gone
through, or are in the process of going through, renumbering efforts.
Case studies, tools, and lists of applications that require special
attention are sought. This RFC is the product of the Procedures for
Internet/Enterprise Renumbering Working Group of the IETF.
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@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.
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 admin@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@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds
USC/Information Sciences Institute