[sami] 答复: First SAMI email in the new year, can we go further? Look forward to your opinions.

"Dacheng Zhang(Dacheng)" <zhangdacheng@huawei.com> Fri, 02 March 2012 02:41 UTC

Return-Path: <zhangdacheng@huawei.com>
X-Original-To: sami@ietfa.amsl.com
Delivered-To: sami@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABC2221F8A04 for <sami@ietfa.amsl.com>; Thu, 1 Mar 2012 18:41:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.554
X-Spam-Level:
X-Spam-Status: No, score=-0.554 tagged_above=-999 required=5 tests=[AWL=-1.250, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68H7Ri-htxPf for <sami@ietfa.amsl.com>; Thu, 1 Mar 2012 18:41:42 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2D921F8A03 for <sami@ietf.org>; Thu, 1 Mar 2012 18:41:42 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M08001NSKP3NC@szxga04-in.huawei.com> for sami@ietf.org; Fri, 02 Mar 2012 10:39:03 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0800436KOYPJ@szxga04-in.huawei.com> for sami@ietf.org; Fri, 02 Mar 2012 10:39:03 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AHN69201; Fri, 02 Mar 2012 10:39:03 +0800
Received: from SZXEML428-HUB.china.huawei.com (10.72.61.36) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 02 Mar 2012 10:38:51 +0800
Received: from SZXEML528-MBX.china.huawei.com ([169.254.4.52]) by szxeml428-hub.china.huawei.com ([10.72.61.36]) with mapi id 14.01.0323.003; Fri, 02 Mar 2012 10:38:58 +0800
Date: Fri, 02 Mar 2012 02:38:58 +0000
From: "Dacheng Zhang(Dacheng)" <zhangdacheng@huawei.com>
In-reply-to: <C4183517-50F0-4D50-A5A5-6D6904209C5F@cisco.com>
X-Originating-IP: [10.108.4.58]
To: Benson Schliesser <bschlies@cisco.com>, "sami@ietf.org" <sami@ietf.org>
Message-id: <C72CBD9FE3CA604887B1B3F1D145D05E120626DD@szxeml528-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="gb2312"
Content-language: zh-CN
Content-transfer-encoding: 7bit
Accept-Language: zh-CN, en-US
Thread-topic: [sami] First SAMI email in the new year, can we go further? Look forward to your opinions.
Thread-index: AQHM+ByBW9BnaudsDU6Syq1ZqtckXZZWSUKQ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: <A27496C192613C44A82D819E1B98DB5721DAE9A6@SZXEML511-MBS.china.huawei.com> <201203011329.q21DTbkD023885@cichlid.raleigh.ibm.com> <4F4F9DA3.5030901@gmail.com> <201203011613.q21GDAob025552@cichlid.raleigh.ibm.com> <4F4FA2CA.9060205@gmail.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AEC8CCDE@MX14A.corp.emc.com> <C4183517-50F0-4D50-A5A5-6D6904209C5F@cisco.com>
Subject: [sami] 答复: First SAMI email in the new year, can we go further? Look forward to your opinions.
X-BeenThere: sami@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: State Migration <sami.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sami>, <mailto:sami-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sami>
List-Post: <mailto:sami@ietf.org>
List-Help: <mailto:sami-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sami>, <mailto:sami-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 02:41:42 -0000

>> Right. Minor packet loss is possible, but the VM migration is designed so that
>> e.g. established TCP connections don't fail.
>> 
[Dacheng Zhang] I just checked with somebody working in this area, you are correct. So, +1

>> 
>> Further, are there any non-VM mobility use-cases for state migration? I can
>> imagine a few, but again I want to make sure they're being driven by
>> operational needs rather than mere possibility.
[Dacheng Zhang] 
In addition, even after we have found some useful use case, we still need to find out whether there are some other ways instead of state migration that we can go . 
>> 
>> Cheers,
>> -Benson
>> 
>> 
>> _______________________________________________
>> sami mailing list
>> sami@ietf.org
>> https://www.ietf.org/mailman/listinfo/sami