Subject: [nemo] RFC 4888 on Network Mobility Route Optimization Problem Statement

From: [email-masked]
Date: Wed, 18 Jul 2007 17:13:14 -0700 (PDT)

A new Request for Comments is now available in online RFC libraries.

        RFC 4888

        Title:      Network Mobility Route Optimization Problem 

                    Statement 

        Author:     C. NgUC Davis, P. Thubert,

                    M. Watari, F. Zhao

        Status:     Informational

        Date:       July 2007

        Mailbox:    [email-masked], 

                    [email-masked], 

                    [email-masked],  [email-masked]

        Pages:      26

        Characters: 56756

        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nemo-ro-problem-statement-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4888.txt

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.

This document is a product of the Network Mobility

Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community. 

It does not specify an Internet standard of any kind. Distribution

of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.

Requests to be added to or deleted from the IETF distribution list

should be sent to [email-masked].  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to [email-masked].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to [email-masked] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email-masked]

        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the

author of the RFC in question, or to [email-masked].  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.

Submissions for Requests for Comments should be sent to

[email-masked].  Please consult RFC 2223, Instructions to RFC

Authors, for further information.

The RFC Editor Team

USC/Information Sciences Institute

...