As per Relevance of the word experience, we have this rfc below:
Network Working Group H.
Request for Comments: 1916 PSC
Category: Informational P.
cisco Systems, Inc
W.
P.
Nesser & Nesser
February 1996
Enterprise Renumbering: Experience and Information
Status of this
This memo provides information for the Internet community. This
does not specify an Internet standard of any kind. Distribution
this memo is unlimited
Because of the urgent need for, and substantial difficulty in
renumbering IP networks, the PIER working group is compiling a
of documents to assist sites in their renumbering efforts.
intent of these documents is to provide both educational
practical information to the Internet community. To this end
working group is soliciting information from organizations
already have gone through, or are in the process of going through
renumbering efforts. Case studies, tools, and lists of
that require special attention are sought
Table of
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Renumbering Experience . . . . . . . . . . . . . . . . . . . 4
3. Information on Tools . . . . . . . . . . . . . . . . . . . . 5
4. Application Information . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . 6
6. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 7
A. Formatting Rules (from RFC 1543) . . . . . . . . . . . . . . 8
Berkowitz, et al Informational [Page 1]
RFC 1916 Enterprise Renumbering Solicitation February 1996
1.
There are immediate and increasingly severe requirements to
both small and large-scale networks. The Procedures
Internet/Enterprise Renumbering (PIER) working group in the
urgently requests specific input for producing concrete guidance
the renumbering task as quickly as possible. As part of
such information, the PIER working group therefore is
input from people and organizations with experience in changing
IP addresses of enterprise networks or in making major changes in
subnetting of existing networks. We are especially interested
actual case studies -- that is, accounts describing what was
done to renumber one or more networks. Information is also
on specific tools used in the process, and on areas in which
were needed but not available. Because applications that use
addresses directly in their configuration or security mechanisms
specific difficulties and coordination issues for renumbering,
catalogue of such applications is being compiled
All interested parties are invited to submit material in any of
areas
A) Accounts of the experience of renumbering networks
-- Retrospective reports on renumbering efforts
-- Journals or running accounts of a renumbering effort,
while the task is underway
B) Information on tools to help renumbering
-- Descriptions of tools used, whether commercial, freeware, or
hoc (such as perl scripts).
-- Descriptions of specific needs where a tool could clearly
helped, but none was found
C) Information on applications using embedded IP addresses
-- Software applications that use embedded IP addresses for
keys, authentication, or any other "inappropriate" purposes
-- Hardware devices whose IP addresses are hardcoded into
hardware design (and so may require extensive time lags
retool).
-- Both software and hardware whose vendors are no longer in
and that may require replacement or specialized solutions
The focus of this solicitation is on experience with renumbering
has been done or is now underway in IPv4 networks, and not on
changes to protocols or environments that may eventually be useful
We are especially concerned with the most common situation
today: single-homed networks that are not transit providers. However
experience with renumbering more complex environments is
Berkowitz, et al Informational [Page 2]
RFC 1916 Enterprise Renumbering Solicitation February 1996
welcome
The information provided will be used as an information base
which at least three documents will be composed: a
summarizing the processes to follow when renumbering, a
describing the available tools, and a document containing a list
known applications requiring special attention when renumbering.
information will also be available on the PIER home page
http://www.isi.edu/div7/pier. More specific reports on
particular environments may also be produced in those cases
enough information is received from the community
Although our emphasis is on technical issues and responses,
based advice on smoothing the human problems is also appreciated
Political and cultural sensitivities, and handling them, are
issues in the real world
There is no requirement that a formal document be submitted,
with the permission of the submitter, selected accounts of
in renumbering will be published by PIER as part of their
series of case studies. If you wish to have your account released
a PIER case study, please follow the standard RFC format described
RFC 1543, "Instructions to RFC Authors". (For convenience,
formatting rules are given in Appendix A below.)
The people and organization(s) involved and the network(s)
need not be identified in any document made public by PIER:
explicitly indicate if a submission should have its
protected
The deadline for the submission of your information is May 15, 1996,
though early submission is encouraged. Any information,
informally written, that can be submitted earlier, would be
appreciated and will help shape the further work of the PIER group
In particular, if you expect to submit a detailed write-up by May 15,
1996, please let us know as soon as possible
Please send submissions, questions, or suggestions to the
discussion list, pier@isi.edu
To subscribe to the PIER discussion list, please send your request
pier-request@isi.edu. Further information on PIER is available on
PIER home page, http://www.isi.edu/div7/pier
Mail may also be sent directly to the editors, without its
on the PIER list, by sending to pier-solicit@bellcore.com
Berkowitz, et al Informational [Page 3]
RFC 1916 Enterprise Renumbering Solicitation February 1996
2. Renumbering
An account of a renumbering effort should provide enough
information, based on actual experience, so that the reader
understand exactly what was done. Broadly speaking, we anticipate
styles of account
i) Retrospective
Based on one or more renumbering efforts, recapitulate what
done and what was learned in the effort. Such a report
describe
-- The environment being renumbered
-- The planning undertaken
-- What was done
-- What worked
-- What didn't (unanticipated issues, problems with
approaches).
In addition, the report would be even more useful if it
addressed
-- The reasons for taking the approach chosen
-- Any alternative approaches that were rejected, and why
-- What could have been done in advance to make the task easier
-- Lessons learned: how would you do it next time
It is hoped that individuals and organizations that have
been through a renumbering effort could quickly look back
their experiences, and capture their knowledge
ii) Running
Many people are in the midst of a renumbering effort, or are
to embark on one in the next few months. If, in the midst of
hectic task, one could write down a brief account or "diary"
what actually happens, as it happens, such a report is likely
capture the glitches and fixes of even the best-planned
more accurately than any retrospective
Of course, these are only rough categories: any record of
experience of renumbering or of information gained by such
can be a valuable contribution to PIER. When submitting accounts
renumbering efforts, please attempt to be as articulate and
as possible
Berkowitz, et al Informational [Page 4]
RFC 1916 Enterprise Renumbering Solicitation February 1996
3. Information on
Information on the tools that were used in renumbering is valuable
whether provided as a separate note or as part of an account of
renumbering effort. We welcome comments, however detailed or brief
on any tools that helped with renumbering, whether or not you
to produce an account of the entire renumbering effort
Some areas in which tools may be used in renumbering include
-- Identifying what needs to be changed in your network, such
configuration files, hosts and servers with embedded or cached
addresses, DNS, access control lists (ACLs), firewalls, routers
license servers, and other applications
-- Identifying external factors (such as remote servers, routers,
Internet registries) that need to be updated to accommodate
new numbers
-- Identifying dependencies between the different places where
numbers must be updated
-- Notifying external agents
-- Generating the new information (such as routing, configuration
and ACLs) required in order to carry out the updates
-- Coordinating updates
-- Making the updates
-- Verifying the updates
-- Trouble-shooting and debugging
-- Maintaining network functionality
-- Informing your users and other affected human beings (such as
staff) of the changes
The most useful tools are those that are, or can be, available
other renumbering efforts. For a given tool, it would be helpful
describe
-- How to obtain it (if not a well-known tool).
-- What you used it for
-- How you used it
-- What its strengths and limitations are for these specific uses
If a tool was created as part of the renumbering effort,
description of exactly what it does should be included. (For example
a script to check for IP addresses in configuration files on
machines should be described in terms of just what it did to
the list of machines, what files it looked for, and how it
them.)
Although the primary goal of this solicitation is to learn what
exist and are useful, we also value specific, experience-
descriptions of ways in which tools could have helped even
nothing was available during the renumbering to perform
Berkowitz, et al Informational [Page 5]
RFC 1916 Enterprise Renumbering Solicitation February 1996
functions. Advisories on tools that appear to be useful but
practice created further problems may also be considered,
appropriate
4. Application
Information on applications that require special attention
renumbering are of particular interest, since
applications are among the most difficult aspects of renumbering.
typically requires special intervention with the vendor to
new security keys, new license addresses, new versions
applications, or perhaps even new hardware or proms to change
hardcoded IP addresses
A list of any such applications that required "extra" efforts
the renumbering process is valuable. Please include as much
information as possible, including but not limited to:
name, version, platform, vendor, operating system, operating
version, the steps taken to overcome the problem, and lead
needed
In particular, any applications that are no longer supported,
whose vendor has ceased to do business, are extremely important
these applications will likely be some of the more difficult issues
renumbering effort will encounter. Any solutions to these types
problems, including replacement applications and
solutions, are also sought
5. Security
This RFC raises no security issues, although accounts of
are encouraged to describe any security issues encountered, any
that helped identify or resolve the issues, and the actions taken
address them. Submissions should give serious consideration to
content and context of issues regarding security
Berkowitz, et al Informational [Page 6]
RFC 1916 Enterprise Renumbering Solicitation February 1996
6. Authors'
Howard C.
PSC
8260 Greensboro Drive, Suite 330
McLean, VA 22102
Phone: (703) 998-5819
Fax: (703) 998-5058
EMail: hcb@clark.
Paul
cisco Systems, Inc
1835 Alexander Bell
Suite 100
Reston, VA 22091
Phone: (703) 716-9538
Fax: (703) 716-9538
EMail: pferguso@cisco.
Will E.
Room 1A-228
445 South
Morristown, NJ 07960-6438
Phone: (201) 829-4376
Fax: (201) 829-2504
EMail: wel@bellcore.
Philip J. Nesser
Nesser & Nesser
16015 84th Ave.
Bothell, WA 98011
Phone: (206) 488-6268
EMail: pjnesser@rocket.
Berkowitz, et al Informational [Page 7]
RFC 1916 Enterprise Renumbering Solicitation February 1996
Appendix A - Formatting Rules (from RFC 1543)
Note: there are a set of NROFF formatting macros for the
format. Please contact pier-solicit@bellcore.com if you would
to get a copy
3a. ASCII Format
The character codes are ASCII
Each page must be limited to 58 lines followed by a form feed on
line by itself
Each line must be limited to 72 characters followed by
return and line feed
No overstriking (or underlining) is allowed
These "height" and "width" constraints include any headers, footers
page numbers, or left side indenting
Do not fill the text with extra spaces to provide a straight
margin
Do not do hyphenation of words at the right margin
Do not use footnotes. If such notes are necessary, put them at
end of a section, or at the end of the document
Use single spaced text within a paragraph, and one blank line
paragraphs
Note that the number of pages in a document and the page numbers
which various sections fall will likely change with reformatting
Thus cross references in the text by section number usually
easier to keep consistent than cross references by page number
Berkowitz, et al Informational [Page 8]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
