Issues with IP Address Sharing
draft-ford-shared-addressing-issues-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Mat Ford , Mohamed Boucadair , Alain Durand , Pierre Levis , Phil Roberts | ||
Last updated | 2010-07-07 (Latest revision 2010-03-08) | ||
Replaced by | draft-ietf-intarea-shared-addressing-issues | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-intarea-shared-addressing-issues | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The completion of IPv4 address allocations from IANA and the RIRs is causing service providers around the world to question how they will continue providing IPv4 connectivity service to their subscribers when there are no longer sufficient IPv4 addresses to allocate them one per subscriber. Several possible solutions to this problem are now emerging based around the idea of shared IPv4 addressing. These solutions give rise to a number of issues and this memo identifies those common to all such address sharing approaches. Solution- specific discussions are out of scope.
Authors
Mat Ford
Mohamed Boucadair
Alain Durand
Pierre Levis
Phil Roberts
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)