RFC 3314: Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards
In plain English — editorial summary, not part of the RFC
This document contains recommendations from the Internet Engineering Task Force (IETF) IPv6 Working Group to the Third Generation Partnership Project (3GPP) community regarding the use of IPv6 in the 3GPP standards. Specifically, this document recommends that the 3GPP: 1. Specify that multiple prefixes may be assigned to each primary PDP context, 2. Require that a given prefix must not be assigned to more than one primary PDP context, and 3. Allow 3GPP nodes to use multiple identifiers within those prefixes, including randomly generated identifiers. The IPv6 Working Group supports the use of IPv6 within 3GPP and offers these recommendations in a spirit of open cooperation between the IPv6 Working Group and the 3GPP community. Since the original publication of this document as an Internet-Draft, the 3GPP has adopted the primary recommendations of this document.
Document record
- Document ID
- RFC3314
- Published
- September 2002
- Authors
- M. Wasserman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3315Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
July 2003
- RFC 3306Unicast-Prefix-based IPv6 Multicast AddressesUpdated
September 2002
- RFC 3122Extensions to IPv6 Neighbor Discovery for Inverse Discovery SpecificationCurrent
June 2001
- RFC 3115Mobile IP Vendor/Organization-Specific ExtensionsCurrent
April 2001
- RFC 3111Service Location Protocol Modifications for IPv6Current
May 2001
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 3531A Flexible Method for Managing the Assignment of Bits of an IPv6 Address BlockCurrent
April 2003
- RFC 3543Registration Revocation in Mobile IPv4Current
August 2003
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?