[sami] 答复: Trying to figure out where we are

"Yingjie Gu(yingjie)" <guyingjie@huawei.com> Tue, 30 August 2011 01:29 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 9D64B21F8513 for <sami@ietfa.amsl.com>; Mon, 29 Aug 2011 18:29:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.715
X-Spam-Level:
X-Spam-Status: No, score=-100.715 tagged_above=-999 required=5 tests=[AWL=-1.750, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345, 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 giwdS-193zsI for <sami@ietfa.amsl.com>; Mon, 29 Aug 2011 18:29:38 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id E8ACB21F8512 for <sami@ietf.org>; Mon, 29 Aug 2011 18:29:37 -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 <0LQP001B9W690O@szxga05-in.huawei.com> for sami@ietf.org; Tue, 30 Aug 2011 09:30:10 +0800 (CST)
Received: from szxrg02-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 <0LQP00FRNW690C@szxga05-in.huawei.com> for sami@ietf.org; Tue, 30 Aug 2011 09:30:09 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml208-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ADM09190; Tue, 30 Aug 2011 09:30:08 +0800 (CST)
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 30 Aug 2011 09:30:05 +0800
Received: from g00107907 (10.138.41.134) by szxeml402-hub.china.huawei.com (10.82.67.32) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 30 Aug 2011 09:30:06 +0800
Date: Tue, 30 Aug 2011 09:30:58 +0800
From: "Yingjie Gu(yingjie)" <guyingjie@huawei.com>
In-reply-to: <201108251311.p7PDB8e1019968@cichlid.raleigh.ibm.com>
X-Originating-IP: [10.138.41.134]
To: 'Thomas Narten' <narten@us.ibm.com>
Message-id: <001901cc66b4$789ad060$69d07120$@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: AcxjKKZ9/K94vpAmSF675tdIpJXszQDi6mZA
X-CFilter-Loop: Reflected
References: <CA77E180.13DD5%bschlies@cisco.com> <4E541EE7.1080605@gmail.com> <000c01cc6220$3b18fa70$b14aef50$@com> <201108241403546051654@chinamobile.com> <201108241223.p7OCN51m005937@cichlid.raleigh.ibm.com> <005e01cc6325$c3bceca0$4b36c5e0$@com> <201108251311.p7PDB8e1019968@cichlid.raleigh.ibm.com>
Cc: 'Melinda Shore' <melinda.shore@gmail.com>, sami@ietf.org, 'zhangyunfei' <zhangyunfei@chinamobile.com>
Subject: [sami] 答复: Trying to figure out where we are
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: Tue, 30 Aug 2011 01:29:38 -0000

Hi Thomas and all,

We are making effort on a use case draft now, and will present it at early
Sep.




Best Regards
Gu Yingjie

-----邮件原件-----
发件人: Thomas Narten [mailto:narten@us.ibm.com] 
发送时间: 2011年8月25日 乐乐21:11
收件人: Yingjie Gu(yingjie)
抄送: 'zhangyunfei'; 'Melinda Shore'; sami@ietf.org
主题: Re: [sami] Trying to figure out where we are

"Yingjie Gu(yingjie)" <guyingjie@huawei.com> writes:

> In previous mail discussion, there are questions on why should VM be
> migrated.

I think we should take it as a given that VMs move around. People do
that today, we all see the value.

> And also, in the side meeting at Quebec, people want to learn the use case
> from real scenario.

Yes. looking at specific scenarios allows us to ask the question of
whether the scenario is realistic and corresponds to what operators
actual do today (or want to do), or whether it is just a theoretical
problem (in which case it's very questionable whether the IETF should
do work.)

> I guess Yunfei's use case could be an answer to that.

See my previous posting, I don't understand what use case this is yet.

> Here are some of the states that I can see on the devices that need to be
> migrated.

> 1. States on switches:
> 1.1  DHCP snooping table on ports;

How often does DHCP snooping take place in data centers? In other
words, is this a real problem, or a theoretical one?

> 1.2  IGMP snooping table on ports;

I think we need to outline some specific scenarios that describe what
the problem actually is here. Who is doing snooping, why, and why a VM
move leaves something not working.

> 1.3  Dynamic ACL which is created by traffic or authentication;

A specific scenario  would be helpful here. Both so I can understand
the details of the problem,  and so we can discuss whether the
scenario is a real problem in existing datacenters today, or just a
theoretical problem.

> 2. States on FW
> 2.1  TCP Connect States
> 2.2  Dynamic ACL

Same as above.


> 3. States on LB
> 3.1  Connect States.
> 3.2  Session States.

Same as above.

> 4. States on IPS/IDS.
> 4.1 Cumulative data

Same as above.

> We can think about two scenarios:
> 1. VM migrate within the subnet under the same FW/LB/IPS. In this case,
> states also migrate under the same FW/LB/IPS etc.
> States need to be migrated include 1.1, 1.2, 1.3.

Before we spend a lot of time on this, we need to establish that there
are actual real scenarios that correspond to real problems happening
in data centers today. If a problem is just theoretical, it becomes
very unclear whether the IETF should do any work (at this time).

I am not interested in discussing solutions, or even the problem in
much detail, if there is no compelling scenario motivating the
problems for which solutions are being considred.

Thomas