Re: [sfc] 答复: questions of "load balancing considerations" in the draft-quinn-sfc-arch-05

"Andrew G. Malis" <agmalis@gmail.com> Thu, 29 May 2014 20:06 UTC

Return-Path: <agmalis@gmail.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A84E1A0644 for <sfc@ietfa.amsl.com>; Thu, 29 May 2014 13:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7LMFepI7JGLq for <sfc@ietfa.amsl.com>; Thu, 29 May 2014 13:06:28 -0700 (PDT)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36F921A04B1 for <sfc@ietf.org>; Thu, 29 May 2014 13:06:28 -0700 (PDT)
Received: by mail-qg0-f45.google.com with SMTP id z60so2575358qgd.32 for <sfc@ietf.org>; Thu, 29 May 2014 13:06:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5rjkp7LBnW88M1rTLuXzWHQAxV/UAcyET40p3LzPvMU=; b=Hs6ObnPsNx9z/QeAWy1Vk/s+Xnw+NsjBEK6j05nPTdxqzIHjauUoPWbJiSzQqziOjn bZi8igdqnFbYO8veg77soq+3XXHZ5MN38inCQ5OGVuRQI2M7pQCseDyT4JfvmDPM3nDF ABIghdCReteeC0FN26VXD3URLAFt3TUWSdfoW4QXopTA30IQUWQEoN6zZL0i0tXatFQ6 Lf3Ha07UV07dO1cmbpF/jQMJQMufgFUD8uE8hW9AmnyYVmNYTv2kLF2ACt4i0zKPvxdF nPmLFRB4F4zWWdaIKHZfKs/XwxpYw0w2QejGs7i+qhvBTUPcfIS+jJXQT9SeT+89jwpf Anxg==
X-Received: by 10.140.20.144 with SMTP id 16mr13100225qgj.114.1401393983858; Thu, 29 May 2014 13:06:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.86.148 with HTTP; Thu, 29 May 2014 13:06:03 -0700 (PDT)
In-Reply-To: <53879137.7010900@joelhalpern.com>
References: <CFABB759.2DEF3%kegray@cisco.com> <4A95BA014132FF49AE685FAB4B9F17F645D2762A@dfweml701-chm.china.huawei.com> <16984558-2B4C-4873-AFC7-DCD2698CA745@cisco.com> <B8F9A780D330094D99AF023C5877DABA84546203@nkgeml501-mbs.china.huawei.com> <53873333.80807@joelhalpern.com> <2691CE0099834E4A9C5044EEC662BB9D45389906@dfweml701-chm.china.huawei.com> <CDF2F015F4429F458815ED2A6C2B6B0B1A836043@MBX021-W3-CA-2.exch021.domain.local> <2691CE0099834E4A9C5044EEC662BB9D453899C2@dfweml701-chm.china.huawei.com> <CDF2F015F4429F458815ED2A6C2B6B0B1A836249@MBX021-W3-CA-2.exch021.domain.local> <4A95BA014132FF49AE685FAB4B9F17F645D28EAF@dfweml701-chm.china.huawei.com> <53879137.7010900@joelhalpern.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 29 May 2014 16:06:03 -0400
Message-ID: <CAA=duU1uHvkdg4rmTmPv9tMKNrxb_EuJ-jgi58=NAN4tVAJGfQ@mail.gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary="001a11c12632992ba504fa8f766b"
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/TC6Q6S09sezMwoWfTxwg54OTmzY
Cc: "Ken Gray (kegray)" <kegray@cisco.com>, "sfc@ietf.org" <sfc@ietf.org>, Lucy yong <lucy.yong@huawei.com>, Linda Dunbar <linda.dunbar@huawei.com>, "Paul Quinn (paulq)" <paulq@cisco.com>, Ron Parker <Ron_Parker@affirmednetworks.com>, Qin Wu <bill.wu@huawei.com>
Subject: Re: [sfc] 答复: questions of "load balancing considerations" in the draft-quinn-sfc-arch-05
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 May 2014 20:06:29 -0000

Joel,

I disagree, I really don't see it as confusing at all. We're all in
agreement that there will be cases where a service function is split among
multiple hardware and/or software entities that can work in parallel, or
else there wouldn't be a section on load sharing. How else would one
describe these entities if not as "Service Function Instances"?

Cheers,
Andy

On Thu, May 29, 2014 at 3:57 PM, Joel M. Halpern <jmh@joelhalpern.com>wrote:

> the problem I have with the definition you propose for Service Function
> Instance is that what is an instance will depend upon where you look.
> What management, and particularly what virtual machine monitoring and
> management, sees as an instance has to be a single image running on a
> single VM.
> But what Service Chaining sees as an instance may be one such thing, or
> may be a cluster of such things organized in such a way as to present a
> single view to the service chaining infrastructure.
>
> Thus, trying to define Service Function Instance, and then talk explicitly
> about such instances in service chaining, gets very difficult.  We are
> likely to end up with a definition that says that a service function
> instance may be made up of multiple software instances.  Such a definition
> seems likely to cause more confusion than it solves.
>
> If we can come up with a definition that allows for the range of
> deployments, and does not itself further confuse the readers, then I am
> happy to add such a term definition and usage in the document.
>
> Yours,
> Joel
>
>
> On 5/29/14, 2:25 PM, Linda Dunbar wrote:
>
>> It would be so much easier to formally introduce the concept of
>> "Service Function Instance" in SFC. For example:
>>
>> "Service Function Instance: One instantiation of a service function.
>> One service function could have multiple identical instances.
>>
>> For a service function with different functional instantiations, e.g.
>> one instantiation applies policy-set-A (NAT44-A) and other applies
>> policy-set-B (NAT44-B), they are considered as two different service
>> functions."
>>
>> Some Service Function Instances are visible to Service Chain Path.
>> Sometimes a collection of service function instances can appear as
>> one single entity to the Service Chain Path."
>>
>>
>> Linda
>>
>>