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

Thomas Narten <narten@us.ibm.com> Thu, 01 March 2012 13:31 UTC

Return-Path: <narten@us.ibm.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 9619521E81F7 for <sami@ietfa.amsl.com>; Thu, 1 Mar 2012 05:31:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.415
X-Spam-Level:
X-Spam-Status: No, score=-109.415 tagged_above=-999 required=5 tests=[AWL=1.184, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 XIfxNLHlW+5i for <sami@ietfa.amsl.com>; Thu, 1 Mar 2012 05:31:06 -0800 (PST)
Received: from e5.ny.us.ibm.com (e5.ny.us.ibm.com [32.97.182.145]) by ietfa.amsl.com (Postfix) with ESMTP id 8D40821E8221 for <sami@ietf.org>; Thu, 1 Mar 2012 05:30:44 -0800 (PST)
Received: from /spool/local by e5.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <sami@ietf.org> from <narten@us.ibm.com>; Thu, 1 Mar 2012 08:30:42 -0500
Received: from d01dlp02.pok.ibm.com (9.56.224.85) by e5.ny.us.ibm.com (192.168.1.105) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Thu, 1 Mar 2012 08:30:39 -0500
Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id E40D06E805E for <sami@ietf.org>; Thu, 1 Mar 2012 08:30:38 -0500 (EST)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q21DUcjs285056 for <sami@ietf.org>; Thu, 1 Mar 2012 08:30:38 -0500
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q21DUcLL012160 for <sami@ietf.org>; Thu, 1 Mar 2012 10:30:38 -0300
Received: from cichlid.raleigh.ibm.com (sig-9-65-232-28.mts.ibm.com [9.65.232.28]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q21DUMKF010678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Mar 2012 10:30:28 -0300
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q21DTbkD023885; Thu, 1 Mar 2012 08:29:37 -0500
Message-Id: <201203011329.q21DTbkD023885@cichlid.raleigh.ibm.com>
To: "Yingjie Gu(yingjie)" <guyingjie@huawei.com>
In-reply-to: <A27496C192613C44A82D819E1B98DB5721DAE9A6@SZXEML511-MBS.china.huawei.com>
References: <A27496C192613C44A82D819E1B98DB5721DAE9A6@SZXEML511-MBS.china.huawei.com>
Comments: In-reply-to "Yingjie Gu(yingjie)" <guyingjie@huawei.com> message dated "Thu, 01 Mar 2012 01:16:09 +0000."
Date: Thu, 01 Mar 2012 08:29:36 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12030113-5930-0000-0000-000005B2F7CA
Cc: "sami@ietf.org" <sami@ietf.org>
Subject: Re: [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: Thu, 01 Mar 2012 13:31:06 -0000

Hi.

> According to previous discussion, one of the arguement is that we
>  don't need State Migration if there is no VM Migration, we can, for
>  example running active-active VMs mechanism to replace VM
>  Migration.

I think this is a bit of a strawman.

I would expect pretty much everyone on this list would agree that VM
migration takes place, under a wide range of conditions. So let's just
take it as a given that VM migration exists.

Personally, I can see the theoretical benefit of state migration
(e.g., of a firewall). But for me, the biggest reason I have been
skeptical of this effort so far is that I don't see real operators
stepping forwarding saying they need "state migration" in a real
concrete sense.

The IETF does much better when it has a real operational problem
driving a solution. We need such a problem in order to privide a
verification that should we attempt to develop a solution, the
solution actually solves a real world problem.

Thomas