API Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 4888
[ACTIVE]

Network Mobility Route Optimization Problem Statement

Metadata

Publisher
IETF
Doc Type
Informational
Pages
26
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.
Publication Date
2007-07-01
Status Note
Informational
DOI
10.17487/RFC4888
Link
https://doi.org/10.17487/RFC4888
Author(s)
Chan-Wah Ng
Pascal Thubert
Masafumi Watari
Fan Zhao
Keyword(s)
NEMO
Latest version of IETF RFC 4888

Document Versions — IETF RFC 4888

  • ▶ IETF RFC 4888 (2007-07-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

  • Deering, S. and B. Zill, "Redundant Address Deletion when Encapsulating IPv6 in IPv6", Work in Progress, November 2001. EXTERNAL
  • Petrescu, A., Olivereau, A., Janneteau, C., and H-Y. Lach, "Threats for Basic Network Mobility Support (NEMO threats)", Work in Progress, January 2004. EXTERNAL
  • Jung, S., Zhao, F., Wu, S., Kim, H-G., and S-W. Sohn, "Threat Analysis on NEMO Basic Operations", Work in Progress, July 2004. EXTERNAL
  • IETF RFC 1889 [Superseded*]
  • IETF RFC 3484 [Superseded*]
  • IETF RFC 3753 [Active*]
  • IETF RFC 3775 [Superseded*]
  • IETF RFC 3963 [Active*]
  • IETF RFC 4885 [Active*]
  • IETF RFC 4886 [Active*]
  • IETF RFC 4887 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4888.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 4888, Network Mobility Route Optimization Problem Statement. Available at https://doi.org/10.17487/RFC4888
Snippet:
IETF RFC 4888, Network Mobility Route Optimization Problem Statement. Available at https://doi.org/10.17487/RFC4888

HTML (ISO 690 compliant)

Preview:
IETF RFC 4888, Network Mobility Route Optimization Problem Statement. Available at https://doi.org/10.17487/RFC4888
Snippet:
<span class="citation"><cite>IETF RFC 4888</cite>, Network Mobility Route Optimization Problem Statement. Available at <a href="https://doi.org/10.17487/RFC4888" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4888</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 4888, Network Mobility Route Optimization Problem Statement
doi: 10.17487/RFC4888
url: https://doi.org/10.17487/RFC4888
Snippet:
<li>
<cite id="bib-rfc4888">IETF RFC 4888</cite>, Network Mobility Route Optimization Problem Statement
<span class="doi">10.17487/RFC4888</span>
</li>

Referenced By