RFC 3316: Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular Hosts
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7066.
Current version: RFC 7066 — IPv6 for Third Generation Partnership Project (3GPP) Cellular Hosts
In plain English — editorial summary, not part of the RFC
As the deployment of second and third generation cellular networks progresses, a large number of cellular hosts are being connected to the Internet. Standardization organizations are making IPv6 mandatory in their specifications. However, the concept of IPv6 covers many aspects and numerous specifications. In addition, the characteristics of cellular links in terms of bandwidth, cost and delay put special requirements on how IPv6 is used. This document considers IPv6 for cellular hosts that attach to the General Packet Radio Service (GPRS), or Universal Mobile Telecommunications System (UMTS) networks. The document lists basic components of IPv6 functionality and discusses some issues relating to the use of these components when operating in these networks.
Document record
- Document ID
- RFC3316
- Published
- May 2003
- Authors
- J. Arkko; G. Kuijpers; H. Soliman; J. Loughney; J. Wiljakka
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 22
- Also known as
- —
- Obsoleted by:
- RFC 7066
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2760Ongoing TCP Research Related to SatellitesCurrent
February 2000
- RFC 2507IP Header CompressionCurrent
February 1999
- RFC 1962The PPP Compression Control Protocol (CCP)Updated
June 1996
- RFC 7969Customizing DHCP Configuration on the Basis of Network TopologyCurrent
October 2016
- RFC 3373Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point AdjacenciesObsoleted
September 2002
- RFC 3449TCP Performance Implications of Network Path AsymmetryCurrent
December 2002
- RFC 5136Defining Network CapacityCurrent
February 2008
- RFC 7728RTP Stream Pause and ResumeCurrent
February 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?