RFC 7278: Extending an IPv6 /64 Prefix from a Third Generation Partnership Project (3GPP) Mobile Interface to a LAN Link
In plain English — editorial summary, not part of the RFC
This document describes requirements for extending an IPv6 /64 prefix from a User Equipment Third Generation Partnership Project (3GPP) radio interface to a LAN link and describes two implementation examples.
Document record
- Document ID
- RFC7278
- Published
- June 2014
- Authors
- C. Byrne; D. Drown; A. Vizdal
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7277A YANG Data Model for IP ManagementObsoleted
June 2014
- RFC 7276An Overview of Operations, Administration, and Maintenance (OAM) ToolsCurrent
June 2014
- RFC 7285Application-Layer Traffic Optimization (ALTO) ProtocolUpdated
September 2014
- RFC 7286Application-Layer Traffic Optimization (ALTO) Server DiscoveryCurrent
November 2014
- RFC 7269NAT64 Deployment Options and ExperienceCurrent
June 2014
- RFC 7289Carrier-Grade NAT (CGN) Deployment with BGP/MPLS IP VPNsCurrent
June 2014
- RFC 7290Test Plan and Results for Advancing RFC 2680 on the Standards TrackCurrent
July 2014
- RFC 7312Advanced Stream and Sampling Framework for IP Performance Metrics (IPPM)Current
August 2014
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?