A Cellular Industry View of IPng (RFC1674)
Original Publication Date: 1994-Aug-01
Included in the Prior Art Database: 2019-Feb-12
Internet Society Requests For Comment (RFCs)
This is a draft of the requirements for IPng as envisioned by representatives of the Cellular Digital Packet Data (CDPD) consortium of service providers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Network Working Group M. Taylor Request for Comments: 1674 CDPD Consortium Category: Informational August 1994
A Cellular Industry View of IPng
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.
This memo is a response to RFC 1550, "IP: Next Generation (IPng) White Paper Solicitation". The statements in this paper are intended as input to the technical discussions within IETF, and do not represent any endorsement or commitment on the part of the cellular industry, the Cellular Digital Packet Data (CDPD) consortium of service providers or any of its constituent companies.
This is a draft of the requirements for IPng as envisioned by representatives of the Cellular Digital Packet Data (CDPD) consortium of service providers. As the leading service providers for this nascent technology, which will provide the capability for mobility of native mainstream connectionless network layer-based applications it is our intention to support whatever form IPng takes. However, there are several requirements which we feel IPng must meet.
Since we will offer mobile services, our primary requirement is that IPng not inhibit our support of mobility. IPng must not impede devices from being able to operate anywhere anytime. Applications on these mobile devices must look and feel the same to the user regardless of location. NPDUs should be self-contained and not disallow the redirection inherent to our mobility solution, i.e., IPng must be connectionless.
Further, since IPng provides an opportunity for design enhancements above and beyond IPv4, we propose that native support for mobility be regarded as an explicit IPng requirement. Local area and wide area wireless technology creates new opportunities for both TCP/IP and the Internet. Although the capability for mobility is orthogonal to the wired or wireless nature of the data link in use, the rapid
Taylor [Page 1]
RFC 1674 A Cellular Industry View of IPng August 1994
deployment wireless technology amplifies the requirement for topological flexibility.
As a by-product of mobility, the significance of "occasionally- connected hosts" increases. The ability to accommodate occasionally-connected hosts in IPng is a requirement.
In terms of scale, we envision some 20 to 40 million users by the year 2007. In this context a "user" can be anything from a vending machine to a "road warrior". These numbers are for North America alone. Worldwide, we anticipate that IPng should be able to support billions of "users". Of course, the sparseness of network address assignments which is necessary for subnetting, etc., dictates that IPng should support at least tens or hundreds of billions of addresses.
In terms of addressing, we would expect addresses to be hierarchical. In addition, a node with multiple links should require only a single address although mo...