Analysis of Failure Cases in IPv6 Roaming Scenarios (RFC7445)
Original Publication Date: 2015-Mar-01
Included in the Prior Art Database: 2015-Mar-12
Internet Society Requests For Comment (RFCs)
G. Chen: AUTHOR [+5]
Many mobile operators have deployed IPv6, or are about to, in their operational networks. A customer in such a network can be provided IPv6 connectivity if their User Equipment (UE) is IPv6 compliant. Operators may adopt various approaches to deploy IPv6 in mobile networks, such as the solutions described in [TR23.975]. Depending on network conditions, either dual-stack or IPv6-only deployment schemes can be enabled.
Internet Engineering Task Force (IETF) G. Chen Request for Comments: 7445 H. Deng Category: Informational China Mobile ISSN: 2070-1721 D. Michaud Rogers Communications J. Korhonen Broadcom Corporation M. Boucadair France Telecom March 2015
Analysis of Failure Cases in IPv6 Roaming Scenarios
This document identifies a set of failure cases that may be encountered by IPv6-enabled mobile customers in roaming scenarios. The analysis reveals that the failure causes include improper configurations, incomplete functionality support in equipment, and inconsistent IPv6 deployment strategies between the home and the visited networks.
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/rfc7445.
Chen, et al. Informational [Page 1]
RFC 7445 IPv6 Roaming Analysis March 2015
Copyright (c) 2015 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 ...