Subject: RFC 4889 on Network Mobility Route Optimization Solution Space Analysis

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

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

        RFC 4889

        Title:      Network Mobility Route Optimization Solution 

                    Space Analysis 

        Author:     C. Ng, F. Zhao,

                    M. Watari, P. Thubert

        Status:     Informational

        Date:       July 2007

        Mailbox:    [email-masked], 

                    [email-masked], 

                    [email-masked],  [email-masked]

        Pages:      38

        Characters: 95880

        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nemo-ro-space-analysis-03.txt

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

With current Network Mobility (NEMO) Basic Support, all

communications to and from Mobile Network Nodes must go through the

Mobile Router and Home Agent (MRHA) tunnel when the mobile network is

away.  This results in increased length of packet route and increased

packet delay in most cases.  To overcome these limitations, one might

have to turn to Route Optimization (RO) for NEMO.  This memo

documents various types of Route Optimization in NEMO and explores

the benefits and tradeoffs in different aspects of NEMO Route

Optimization.  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

...

_______________________________________________
IETF-Announce mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ietf-announce