Network Mobility Route Optimization Problem Statement
RFC 4888, “Network Mobility Route Optimization Problem Statement”, is an Informational document published in July 2007 by C. Ng, P. Thubert, M. Watari, F. Zhao. The canonical text is published by the RFC Editor.
Abstract
With current Network Mobility (NEMO) Basic Support, all communications to and from Mobile Network Nodes must go through the bi-directional tunnel established between the Mobile Router and Home Agent when the mobile network is away. This sub-optimal routing results in various inefficiencies associated with packet delivery, such as increased delay and bottleneck links leading to traffic congestion, which can ultimately disrupt all communications to and from the Mobile Network Nodes. Additionally, with nesting of Mobile Networks, these inefficiencies get compounded, and stalemate conditions may occur in specific dispositions. This document investigates such problems and provides the motivation behind Route Optimization (RO) for NEMO. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 4888 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4887 Network Mobility Home Network Models
- RFC 4889 Network Mobility Route Optimization Solution Space Analysis
- RFC 4886 Network Mobility Support Goals and Requirements
- RFC 4890 Recommendations for Filtering ICMPv6 Messages in Firewalls
- RFC 4885 Network Mobility Support Terminology
- RFC 4891 Using IPsec to Secure IPv6-in-IPv4 Tunnels
- RFC 4884 Extended ICMP to Support Multi-Part Messages
- RFC 4892 Requirements for a Mechanism Identifying a Name Server Instance