Extending an IPv6 /64 Prefix from a Third Generation Partnership Project (3GPP) Mobile Interface to a LAN Link
RFC 7278
Document | Type | RFC - Informational (June 2014; No errata) | |
---|---|---|---|
Authors | Cameron Byrne , Dan Drown , Vizdal Ales | ||
Last updated | 2015-10-14 | ||
Replaces | draft-byrne-v6ops-64share | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Fred Baker | ||
Shepherd write-up | Show (last changed 2014-02-06) | ||
IESG | IESG state | RFC 7278 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Joel Jaeggli | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) C. Byrne Request for Comments: 7278 T-Mobile USA Category: Informational D. Drown ISSN: 2070-1721 A. Vizdal Deutsche Telekom AG June 2014 Extending an IPv6 /64 Prefix from a Third Generation Partnership Project (3GPP) Mobile Interface to a LAN Link Abstract 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. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7278. Byrne, et al. Informational [Page 1] RFC 7278 Extending an IPv6 /64 Prefix June 2014 Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ....................................................3 2. The Challenge of Providing IPv6 Addresses to a LAN Link via a 3GPP UE .........................................................4 3. Requirements for Extending the 3GPP Interface /64 IPv6 Prefix to a LAN Link ............................................4 4. Example Methods for Extending the 3GPP Interface /64 IPv6 Prefix to a LAN Link .......................................5 4.1. General Behavior for All Example Scenarios .................5 4.2. Example Scenario 1: Global Address Only Assigned to LAN Link ...................................................5 4.3. Example Scenario 2: A Single Global Address Assigned to a 3GPP Radio and LAN Link ....................................7 5. Security Considerations .........................................8 6. Acknowledgments .................................................8 7. Informative References ..........................................8 Byrne, et al. Informational [Page 2] RFC 7278 Extending an IPv6 /64 Prefix June 2014 1. Introduction 3GPP mobile cellular networks such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), and Long Term Evolution (LTE) have architectural support for IPv6 [RFC6459], but only 3GPP Release-10 and onwards of the 3GPP specification [TS.23401] supports DHCPv6 Prefix Delegation [RFC3633] for delegating IPv6 prefixes to a single LAN link. To facilitate the use of IPv6 in a LAN prior to the deployment of DHCPv6 Prefix Delegation in 3GPP networks and in User Equipment (UE), this document describes requirements and provides examples on how the 3GPP UE radio interface assigned global /64 prefix may be extended from the 3GPP radio interface to a LAN link. There are two scenarios where this might be done. The first is where the 3GPP node sets up and manages its own LAN (e.g., an IEEE 802.11 Service Set Identifier (SSID)) and provides single-homed service to hosts that connect to this LAN. A second scenario is where the 3GPP node connects to an existing LAN and acts as a router in order to provide redundant or multi-homed IPv6 service. This document is intended to address the first scenario; it is not applicable to the second scenario, because the operational complexities of the second scenario are not addressed. This can be achieved by receiving the Router Advertisement (RA)Show full document text