IETF Logo Mail Archive

Re: [sami] A new draft on state migration use cases is submitted.

"Yingjie Gu(yingjie)" <guyingjie@huawei.com> Mon, 10 October 2011 14:01 UTC

Return-Path: <guyingjie@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 DEB6621F8B11 for <sami@ietfa.amsl.com>; Mon, 10 Oct 2011 07:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.48
X-Spam-Level:
X-Spam-Status: No, score=-104.48 tagged_above=-999 required=5 tests=[AWL=-0.669, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 ZC5aiv-HC7g9 for <sami@ietfa.amsl.com>; Mon, 10 Oct 2011 07:01:45 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB7721F8AD1 for <sami@ietf.org>; Mon, 10 Oct 2011 07:01:44 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSU00AFSS91OS@szxga05-in.huawei.com> for sami@ietf.org; Mon, 10 Oct 2011 22:00:37 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSU00IJTS8ZOR@szxga05-in.huawei.com> for sami@ietf.org; Mon, 10 Oct 2011 22:00:37 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEI72767; Mon, 10 Oct 2011 22:00:19 +0800
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 10 Oct 2011 22:00:17 +0800
Received: from g00107907 (10.138.41.134) by szxeml401-hub.china.huawei.com (10.82.67.31) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 10 Oct 2011 22:00:09 +0800
Date: Mon, 10 Oct 2011 22:02:56 +0800
From: "Yingjie Gu(yingjie)" <guyingjie@huawei.com>
In-reply-to: <4E925C03.6040107@gmail.com>
X-Originating-IP: [10.138.41.134]
To: 'Melinda Shore' <melinda.shore@gmail.com>, sami@ietf.org
Message-id: <004a01cc8755$502936f0$f07ba4d0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset="gb2312"
Content-language: zh-cn
Content-transfer-encoding: quoted-printable
Thread-index: AcyG9tpVlsAhgxeyTIu0fCgzkYP7CQABqfCQ
X-CFilter-Loop: Reflected
References: <CAHYyOzweXppJvn=ruCVZJLRkT-JsFBb0JMBVhLdKCNFTHLM4dA@mail.gmail.com> <4E925C03.6040107@gmail.com>
Subject: Re: [sami] A new draft on state migration use cases is submitted.
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: Mon, 10 Oct 2011 14:01:46 -0000

I think the state we are talking about is the flow-coupled network state
located on such devices as physical switches and firewalls. We don't try to
migrate the states on Hypervisor. The figures in the use case draft give
some examples on the states on physical switches and firewalls. 




Best Regards
Gu Yingjie


-----邮件原件-----
发件人: sami-bounces@ietf.org [mailto:sami-bounces@ietf.org] 代表 Melinda
Shore
发送时间: 2011年10月10日 乐乐10:44
收件人: sami@ietf.org
主题: Re: [sami] A new draft on state migration use cases is submitted.

On 10/9/11 6:31 PM, chen li wrote:
> During the research we have talked with related providers and network
> equipment vendors. We consider this problem to be an question needed
> to be handled when providing virtualization based DC services.

That really doesn't address the question raised by Juergen: why is the
*switch* involved in migrating ACLs located on hypervisors?  I've read
these documents a few times and I still don't have a very clear picture of
where you think network state and "flow"-coupled state are located.

Melinda
_______________________________________________
sami mailing list
sami@ietf.org
https://www.ietf.org/mailman/listinfo/sami

v2.23.0 | Report a Bug | By Email