RFC 7445: Analysis of Failure Cases in IPv6 Roaming Scenarios
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7445
- Published
- March 2015
- Authors
- G. Chen; H. Deng; D. Michaud; J. Korhonen; M. Boucadair
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7755SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center EnvironmentsCurrent
February 2016
- RFC 7756Stateless IP/ICMP Translation for IPv6 Internet Data Center Environments (SIIT-DC): Dual Translation ModeCurrent
February 2016
- RFC 7757Explicit Address Mappings for Stateless IP/ICMP TranslationCurrent
February 2016
- RFC 9313Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)Current
October 2022
- RFC 9386IPv6 Deployment StatusCurrent
April 2023
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 5889IP Addressing Model in Ad Hoc NetworksCurrent
September 2010
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?