RFC 1674 (rfc1674) - Page 3 of 3

A Cellular Industry View of IPng

RFC 1674            A Cellular Industry View of IPng         August 1994


Route Selection

   In the voice communications arena, "equal access" and choice of an
   "interexchange carrier (IXC)" are issues that must be addressed.
   Similar requirements for data may also exist.

   Source- and policy-based routing for inter-domain traffic can address
   this requirement.  IPng must allow the selection of at least the
   first transient network service provider based on the source host.

Data Efficiency

   The bandwidth of wide area wireless networks is a precious resource,
   the use of which must be optimized.  IPng must allow optimal use of
   the underlying Layer 2 medium.  Layer 3 Protocol Control Information
   (PCI) should be as condensed as possible.  The protocol should be
   optimized for data efficiency.

   Packet prioritization must also be supported by IPng in order to
   optimize the use of low speed networks.  This requirement includes
   both class and grade of service definitions for flexibility.

Transition

   The final requirement for IPng is that it must interoperate with IP
   for the foreseeable future.  Bridging mechanisms must be supported
   and a strategy for the transition from IPv4 to IPng must be defined.
   Use of options fields, etc., are one mechanism to support the
   requirement for IPng protocols to support IP addresses and headers.

Security Considerations

   See section on Security.

Author's Address

   Mark S. Taylor
   Director of System Development
   McCaw Cellular Communications, Inc.
   Wireless Data Division
   10230 NE Points Drive
   Kirkland, WA 98033-7869 USA

   EMail: mark.s.taylor@airdata.com







Taylor