[MEXT] FW: New Version Notification for draft-cui-mext-route-optimization-cn-proxy-01.txt

Xiangsong Cui <Xiangsong.Cui@huawei.com> Mon, 18 July 2011 02:34 UTC

Return-Path: <Xiangsong.Cui@huawei.com>
X-Original-To: mext@ietfa.amsl.com
Delivered-To: mext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF06121F8A7B for <mext@ietfa.amsl.com>; Sun, 17 Jul 2011 19:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e2pFnadoWD8g for <mext@ietfa.amsl.com>; Sun, 17 Jul 2011 19:34:13 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 216E221F8A71 for <mext@ietf.org>; Sun, 17 Jul 2011 19:34:13 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOI00LNTCGIC1@szxga03-in.huawei.com> for mext@ietf.org; Mon, 18 Jul 2011 10:33:54 +0800 (CST)
Received: from c00111037 ([10.111.132.96]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LOI00DW5CGHPI@szxga03-in.huawei.com> for mext@ietf.org; Mon, 18 Jul 2011 10:33:54 +0800 (CST)
Date: Mon, 18 Jul 2011 10:33:53 +0800
From: Xiangsong Cui <Xiangsong.Cui@huawei.com>
To: 'mext' <mext@ietf.org>
Message-id: <021601cc44f3$231c7130$69555390$%cui@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=UTF-8
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: Acw/eBPveEEBIOj+RL2qA+41pmYmSwFeqqlQ
Subject: [MEXT] FW: New Version Notification for draft-cui-mext-route-optimization-cn-proxy-01.txt
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 02:34:14 -0000

Hi folks,

We have submitted a new draft, http://tools.ietf.org/id/draft-cui-mext-route-optimization-cn-proxy-01.txt.
Please review and comment.

Best regards,
Xiangsong


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, July 11, 2011 11:10 AM
To: Xiangsong.Cui@huawei.com
Cc: antti.makela@aalto.fi; Peter.McCann@huawei.com; Xiangsong.Cui@huawei.com
Subject: New Version Notification for draft-cui-mext-route-optimization-cn-proxy-01.txt

A new version of I-D, draft-cui-mext-route-optimization-cn-proxy-01.txt has been successfully submitted by Xiangsong Cui and posted to the IETF repository.

Filename:	 draft-cui-mext-route-optimization-cn-proxy
Revision:	 01
Title:		 Proxy Correspondent Node Operation for Mobile IPv6 Route Optimization
Creation date:	 2011-07-11
WG ID:		 Individual Submission
Number of pages: 21

Abstract:
   Route Optimization is a useful aspect of Mobile IPv6.  In Route
   Optimization mode a Mobile Node (MN) can communicate with a
   Correspondent Node (CN) without the involvement of the MN&#39;s home
   agent.  However, there are some limitations to this feature,
   including that the Mobile Node and the Correspondent Node must both
   be capable of Route Optimization.  This document introduces a Route
   Optimization Proxy function that can be used to enable Route
   Optimization between an MN and an arbitrary other IP CN - the Route
   Optimization functions are delegated to the Proxy.  The Route
   Optimization Proxy function may be implemented in the access router
   attached to the CN or any other node present on both the path from
   the MN to the CN and from the HA to the CN, and the Route
   Optimization Proxy can conduct RO-related signaling and accomplish
   the Route Optimization procedure on behalf of the Correspondent Node.

                                                                                  


The IETF Secretariat