IETF Logo Mail Archive

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

chen li <lichen.cmcc@gmail.com> Mon, 10 October 2011 03:14 UTC

Return-Path: <lichen.cmcc@gmail.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 2699021F877F for <sami@ietfa.amsl.com>; Sun, 9 Oct 2011 20:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.204
X-Spam-Level:
X-Spam-Status: No, score=-3.204 tagged_above=-999 required=5 tests=[AWL=0.395, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 iaPvrlzpQvD2 for <sami@ietfa.amsl.com>; Sun, 9 Oct 2011 20:14:36 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id A704B21F8726 for <sami@ietf.org>; Sun, 9 Oct 2011 20:14:36 -0700 (PDT)
Received: by ggnk3 with SMTP id k3so5119582ggn.31 for <sami@ietf.org>; Sun, 09 Oct 2011 20:14:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=pcxYAnR7TWDxJwRlxEy3fj+bKJpDB7D9dNu2g9qmZ0g=; b=YIqbj6uFiJUflD37fFQKiq4dwR0PAUGCx8gWZoG7X3jJAtnnEJ/Rg3M3elp5cVvp9d OkHGRLT9jD934Wg+sQnn4RQNljaI0AVdtSYexUgKh/v7JB9+liM7Dtq+vw4rNx7oXRGD MqUlzGMVTYXGuMfYrB9kPe97gJQeVaS2hNoug=
MIME-Version: 1.0
Received: by 10.68.17.4 with SMTP id k4mr33735883pbd.8.1318216476082; Sun, 09 Oct 2011 20:14:36 -0700 (PDT)
Received: by 10.143.91.6 with HTTP; Sun, 9 Oct 2011 20:14:36 -0700 (PDT)
Date: Mon, 10 Oct 2011 11:14:36 +0800
Message-ID: <CAHYyOzzU4OaGAB837rEbutRqsOwaSTOmO_48sX_csRCDqd4Wfg@mail.gmail.com>
From: chen li <lichen.cmcc@gmail.com>
To: melinda.shore@gmail.com, sami@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
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 03:14:37 -0000

On 10/9/11 6:31 PM,  Melinda wrote:

>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.




for Juergen's question, i mean that it's necessroy to deploy vlan ACL
on hypervisor.

and aslo, the hypervisor supports limited functions. such as DHCP
Snooping that we need cannot be support yet.

Li Chen



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

v2.23.0 | Report a Bug | By Email