IETF Logo Mail Archive

Re: [DMM] draft-yegin-ip-mobility-orchestrator-00.txt

Weixinpeng <weixinpeng@huawei.com> Mon, 07 July 2014 03:58 UTC

Return-Path: <weixinpeng@huawei.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB2A21A0AE4 for <dmm@ietfa.amsl.com>; Sun, 6 Jul 2014 20:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HcHm2xfbgoWM for <dmm@ietfa.amsl.com>; Sun, 6 Jul 2014 20:58:46 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB8CE1A0AE0 for <dmm@ietf.org>; Sun, 6 Jul 2014 20:58:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJR69755; Mon, 07 Jul 2014 03:58:44 +0000 (GMT)
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 7 Jul 2014 04:57:29 +0100
Received: from NKGEML507-MBX.china.huawei.com ([169.254.5.117]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Mon, 7 Jul 2014 11:57:26 +0800
From: Weixinpeng <weixinpeng@huawei.com>
To: Alper Yegin <alper.yegin@yegin.org>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] draft-yegin-ip-mobility-orchestrator-00.txt
Thread-Index: AQHPl1ckYzeVrwOOg0GtiUKJolKs6ZuT9b2A
Date: Mon, 07 Jul 2014 03:57:25 +0000
Message-ID: <C5C3BB522B1DDF478AA09545169155B46D81B10D@nkgeml507-mbx.china.huawei.com>
References: <20140704070253.4172.77879.idtracker@ietfa.amsl.com> <C65DC9B8-C8EA-4E7B-94D4-9C1D50B17E9C@yegin.org>
In-Reply-To: <C65DC9B8-C8EA-4E7B-94D4-9C1D50B17E9C@yegin.org>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.76.176]
Content-Type: multipart/alternative; boundary="_000_C5C3BB522B1DDF478AA09545169155B46D81B10Dnkgeml507mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/EzmvN9rGPqngomjLCmyC3evglZU
Subject: Re: [DMM] draft-yegin-ip-mobility-orchestrator-00.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jul 2014 03:58:49 -0000

Hi Alper,
I agree with you that there should be some kind of coordination between different mobility mechanisms.
Thanks for providing this document, and here are some of my questions:
(1) It's possible for orchestrator to discovery mobility capabilities such as MIPv6, PMIPv6, GTP, MPTCP, but I think it's not convenient to find out whether L7 application is mobility capable.
(2) If there is no communication between MN and CN, then which mobility management scheme will be used when MN moving in network?
(3) what's the criteria for Mobility Protocol Selection in section 4.4? I think that may depends on the characteristic of application traffic.
(4) In Fig. 2, step 5b, you mean the DNS system is used to discovery CN's mobility capability? Could be explain how it works?

Thanks!
Best Regards,
Xinpeng

From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Alper Yegin
Sent: Friday, July 04, 2014 3:11 PM
To: dmm@ietf.org
Subject: [DMM] draft-yegin-ip-mobility-orchestrator-00.txt

Hello DMMers,

We have a new I-D for your reading and discussion.

 Title           : IP Mobility Orchestrator
 Authors     : Alper Yegin
                      Jungshin Park
                      Kisuk Kweon
                      Jinsung Lee
Filename   : draft-yegin-ip-mobility-orchestrator-00.txt
Pages         : 13
Date            : 2014-07-03

Abstract:
  Host stacks can support mobility at multiple layers.  Mobility
  protocols operating at different layers constitute alternate
  solutions with various pros and cons, and they can also have adverse
  affects on each other when used simultaneously.  Optimal results in
  terms of seamless handover and data-path optimization can be achieved
  when execution of these protocols are coordinated.

We'll also be submitting an IPR statement to IETF.

https://datatracker.ietf.org/doc/draft-yegin-ip-mobility-orchestrator/

Please review this I-D and share your comments.

Thanks,

Alper

v2.23.0 | Report a Bug | By Email