Browse Prior Art Database

Network Renumbering Overview: Why would I want it and what is it anyway? (RFC2071)

IP.com Disclosure Number: IPCOM000002623D
Original Publication Date: 1997-Jan-01
Included in the Prior Art Database: 2019-Feb-16
Document File: 14 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

P. Ferguson: AUTHOR [+1]

Related Documents

10.17487/RFC2071: DOI

Abstract

This document attempts to clearly define the concept of network renumbering and discuss some of the more pertinent reasons why an organization would have a need to do so. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 11% of the total text.

Network Working Group P. Ferguson Request for Comments: 2071 cisco Systems, Inc. Category: Informational H. Berkowitz PSC International January 1997

Network Renumbering Overview: Why would I want it and what is it anyway?

Status of this Memo

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.

Abstract

The PIER [Procedures for Internet/Enterprise Renumbering] working group is compiling a series of documents to assist and instruct organizations in their efforts to renumber. However, it is becoming apparent that, with the increasing number of new Internet Service Providers (ISP’s) and organizations getting connected to the Internet for the first time, the concept of network renumbering needs to be further defined. This document attempts to clearly define the concept of network renumbering and discuss some of the more pertinent reasons why an organization would have a need to do so.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. Network Renumbering Defined. . . . . . . . . . . . . . . . . 3 4. Reasons for Renumbering. . . . . . . . . . . . . . . . . . . 3 5. Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . 12 7. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. Authors’ Addresses . . . . . . . . . . . . . . . . . . . . . 14

Ferguson & Berkowitz Informational [Page 1]

RFC 2071 Network Renumbering Overview January 1997

1. Introduction

The popularity of connecting to the global Internet over the course of the past several years has spawned new problems; what most people casually refer to as "growing pains" can be attributed to more basic problems in understanding the requirements for Internet connectivity. However, the reasons why organizations may need to renumber their networks can greatly vary. We’ll discuss these issues in some amount of detail below. It is not within the intended scope of this document to discuss renumbering methodologies, techniques, or tools.

2. Background

The ability for any network or interconnected devices, such as desktop PCs or workstations, to obtain connectivity to any potential destination in the global Internet is reliant upon the possession of unique IP host addresses [1]. A duplicate host address that is being used elsewhere in the Internet could best be described as problematic, since the presence of duplicate addresses would cause one of the destinations to be unreachable from some origins in the Internet. It should be noted, however, that globally unique IP addresses are not always necessary, and is dependent on the connectivity requirements [2].

However, the recent popularity in obtaining Internet connectivity has made these types of connecti...

Processing...
Loading...