As per Relevance of the word organization, we have this rfc below:
Network Working Group B.
Request for Comments: 1900 Y.
Category: Informational
February 1996
Renumbering Needs
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
Renumbering, i.e., changes in the IP addressing information
various network components, is likely to become more and
widespread and common. The Internet Architecture Board (IAB)
like to stress the need to develop and deploy solutions that
facilitate such changes
Table of
1. Motivation................................................... 1
2. DNS versus IP Addresses...................................... 2
3. Recommendations.............................................. 3
4. Security Considerations...................................... 4
Acknowledgements................................................ 4
Authors' Addresses.............................................. 4
1.
Hosts in an IP network are identified by IP addresses, and the
address prefixes of subnets are advertised by routing protocols.
change in such IP addressing information associated with a host
subnet is known as "renumbering".
Renumbering may occur for a variety of reasons. For example,
an IP host from one subnet to another requires changing the host's
address. Physically splitting a subnet due to traffic overload
also require renumbering. A third example where renumbering
happen is when an organization changes its addressing plan.
changes imply changing not only hosts' addresses, but subnet
as well. These are just three examples that illustrate
scenarios where renumbering could occur
Carpenter & Rekhter Informational [Page 1]
RFC 1900 Renumbering Needs Work February 1996
Increasingly, renumbering will be needed for organizations
require Internet-wide IP connectivity, but do not themselves
a sufficient degree of address information aggregation. Unless
until viable alternatives are developed, extended deployment
Classless Inter-Domain Routing (CIDR) is vital to keep the
routing system alive and to maintain continuous uninterrupted
of the Internet. With current IP technology, this requires
organizations to use addresses belonging to a single large block
address space, allocated to their current service provider which
as an aggregator for these addresses. To contain the growth
routing information, whenever such an organization changes to a
service provider, the organization's addresses will have to change
Occasionally, service providers themselves may have to change to
new and larger block of address space. In either of these cases,
contain the growth of routing information, the
concerned would need to renumber their subnet(s) and host(s). If
organization does not renumber, then some of the
consequences may include (a) limited (less than Internet-wide)
connectivity, or (b) extra cost to offset the overhead
with the organization's routing information that Internet
Providers have to maintain, or both
Currently, renumbering is usually a costly, tedious and error-
process. It normally requires the services of experts in the
and considerable advance planning. Tools to facilitate
are few, not widely available, and not widely deployed. While
variety of ad hoc approaches to renumbering have been developed
used, the overall situation is far from satisfactory. There
little or no documentation that describes renumbering procedures
While renumbering occurs in various parts of the Internet, there
little or no documented experience sharing
2. DNS versus IP
Within the Internet architecture an individual host can be
by the IP address(es) assigned to the network interface(s) on
host. The Domain Name System (DNS) provides a convenient way
associate legible names with IP addresses. The DNS name space
independent of the IP address space. DNS names are usually
to the ownership and function of the hosts, not to the mechanisms
addressing and routing. A change in DNS name may be a sign of a
change in function or ownership, whereas a change in IP address is
purely technical event
Expressing information in terms of Domain Names allows one to
binding between a particular network entity and its IP address
run time. Domain Names for enterprises, and Fully Qualified
Names (FQDNs, see RFC 1594) for servers and many user systems,
Carpenter & Rekhter Informational [Page 2]
RFC 1900 Renumbering Needs Work February 1996
expected to be fairly long-lived, and more stable than IP addresses
Deferring the binding avoids the risk of changed mapping between
addresses and specific network entities (due to changing
information). Moreover, reliance on FQDNs (rather than IP addresses
also localizes to the DNS the changes needed to deal with
addressing information due to renumbering
In some cases, both the addresses and FQDNs of desk top or
systems are allocated dynamically. It is only a highly
dynamic DNS update mechanism that can cope with this
3.
To make renumbering more feasible, the IAB strongly recommends
all designs and implementations should minimise the cases in which
addresses are stored in non-volatile storage maintained by humans
such as configuration files. Configuration information used
TCP/IP protocols should be expressed, whenever possible, in terms
Fully Qualified Domain Names, rather than IP addresses. Hardcoding
addresses into applications should be deprecated. Files
lists of name to address mappings, other than that used as part
DNS configuration, should be deprecated, and avoided
possible
There are times when legacy applications which require
files with IP addresses rather than Domain Names cannot be
to meet these recommendations. In those cases, it is recommended
the configuration files be generated automatically from another
which uses Domain Names, with the substitution of addresses
done by lookup in the DNS
Use of licensing technology that is based upon the IP address of
host system makes renumbering quite difficult. Therefore, the use
such technology should be strongly discouraged
The development and deployment of a toolkit to facilitate
automate host renumbering is essential. The Dynamic
Configuration Protocol (DHCP) is clearly an essential part of such
toolkit. The IAB strongly encourages implementation and wide-
deployment of DHCP. Dynamic router discovery (RFC 1256) and
location (work in progress in the IETF) also belong in this toolkit
Support for dynamic update capabilities to the Domain Name
(DNS) that could be done with sufficient authentication would
facilitate host renumbering. The IAB strongly encourages
of work in this area towards standardization within the IETF,
the goal of integrating DHCP and dynamic update capabilities
provide truly autoconfigurable TCP/IP hosts
Carpenter & Rekhter Informational [Page 3]
RFC 1900 Renumbering Needs Work February 1996
The IAB strongly encourages sharing of experience with
and documenting this sharing within the Internet community. The
suggests that the IETF (and specifically its Operational
Area) may be the most appropriate place to develop
documentation. The IAB welcomes the creation of the PIER (
for Internet and Enterprise Renumbering) working group
4. Security
Renumbering is believed to be compatible with the Internet
architecture, as long as addresses do not change during the
of a security association
This document is a collective product of the Internet
Board
Useful comments were received from several people, especially
Patton, Steve Bellovin, Jeff Schiller, and Bill Simpson
Authors'
Brian E.
Group Leader, Communications
Computing and Networks
European Laboratory for Particle
1211 Geneva 23,
Phone: +41 22 767-4967
Fax: +41 22 767-7155
Telex: 419000 cer
EMail: brian@dxcoms.cern.
Yakov
cisco
170 West Tasman
San Jose, CA 95134
Phone: (914) 528-0090
EMail: yakov@cisco.
Carpenter & Rekhter Informational [Page 4]
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
