Re: [vnfpool] Overlap with SFC?

Zongning <zongning@huawei.com> Wed, 22 January 2014 01:35 UTC

Return-Path: <zongning@huawei.com>
X-Original-To: vnfpool@ietfa.amsl.com
Delivered-To: vnfpool@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B60041A03E8 for <vnfpool@ietfa.amsl.com>; Tue, 21 Jan 2014 17:35:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.736
X-Spam-Level:
X-Spam-Status: No, score=-104.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 YWNDtRYTxgd2 for <vnfpool@ietfa.amsl.com>; Tue, 21 Jan 2014 17:35:33 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 98DFF1A027D for <vnfpool@ietf.org>; Tue, 21 Jan 2014 17:35:32 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAG01565; Wed, 22 Jan 2014 01:35:31 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan 2014 01:34:30 +0000
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan 2014 01:35:30 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.56]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Wed, 22 Jan 2014 09:35:23 +0800
From: Zongning <zongning@huawei.com>
To: Susan Hares <shares@ndzh.com>, "'King, Daniel'" <d.king@lancaster.ac.uk>, 'Melinda Shore' <melinda.shore@nomountain.net>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Thread-Topic: [vnfpool] Overlap with SFC?
Thread-Index: Ac8W0iZRlSKtK4GNSoKpOSf5YsDYg///ha+AgAAMmQD//yC/UIABQTuA//90UMA=
Date: Wed, 22 Jan 2014 01:35:23 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC666779258686E5@nkgeml501-mbs.china.huawei.com>
References: <0b3501cf16d2$2a3c1e80$7eb45b80$@olddog.co.uk> <52DEBEC3.7030605@nomountain.net> <65174429B5AF4C45BD0798810EC48E0A0D9A9C@EX-0-MB2.lancs.local> <B0D29E0424F2DE47A0B36779EC6667792586867F@nkgeml501-mbs.china.huawei.com> <00d701cf170f$56bf4e40$043deac0$@ndzh.com>
In-Reply-To: <00d701cf170f$56bf4e40$043deac0$@ndzh.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.28]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "vnfpool@ietf.org" <vnfpool@ietf.org>
Subject: Re: [vnfpool] Overlap with SFC?
X-BeenThere: vnfpool@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for virtual network function resource pooling." <vnfpool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vnfpool>, <mailto:vnfpool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vnfpool/>
List-Post: <mailto:vnfpool@ietf.org>
List-Help: <mailto:vnfpool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vnfpool>, <mailto:vnfpool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 01:35:35 -0000

You are more than welcome, Sue. :-)

-Ning

> -----Original Message-----
> From: Susan Hares [mailto:shares@ndzh.com]
> Sent: Wednesday, January 22, 2014 9:15 AM
> To: Zongning; 'King, Daniel'; 'Melinda Shore'; adrian@olddog.co.uk
> Cc: vnfpool@ietf.org
> Subject: RE: [vnfpool] Overlap with SFC?
> 
> Ning:
> 
> Therefore, some of the mechanisms may be in parallel or serial.  Shall I add
> comments in my use cases to indicate when VNF functions are parallel or
> serial?
> 
> Sue
> 
> -----Original Message-----
> From: vnfpool [mailto:vnfpool-bounces@ietf.org] On Behalf Of Zongning
> Sent: Tuesday, January 21, 2014 7:57 PM
> To: King, Daniel; Melinda Shore; adrian@olddog.co.uk
> Cc: vnfpool@ietf.org
> Subject: Re: [vnfpool] Overlap with SFC?
> 
> Hi, Dan and Melinda,
> 
> Thanks for your reply.
> 
> Both of you are right in that our proposal here is narrowly focused on
> redundancy mechanism for VNF. This goal is basically complementary to SFC
> charter. Another point I want to add is that vnfpool is not only used in
> "chained service nodes", but applicable to other cases where service nodes
> are not necessarily sequentially connected.
> 
> -Ning
> 
> > -----Original Message-----
> > From: vnfpool [mailto:vnfpool-bounces@ietf.org] On Behalf Of King,
> > Daniel
> > Sent: Wednesday, January 22, 2014 3:24 AM
> > To: Melinda Shore; adrian@olddog.co.uk
> > Cc: vnfpool@ietf.org
> > Subject: Re: [vnfpool] Overlap with SFC?
> >
> > Hi Again,
> >
> > Thanks Melinda, you are far more succinct than I have been. However,
> > seeing as we may have some additional interest in the vnfpool work, it
> > may be worth summarizing our problem space and some of our discussion
> > thus far for anyone peeking at the list for the first time:
> >
> > A Virtualized Network Function (VNF) (e.g. vBRAS vFirewall,
> > vLoadbalancer) provides the equivalent function as a dedicated
> > hardware platform. These VNF instances are typically instantiated in
> > clusters running on general purpose servers via a variety of
> > virtualization platforms. As per discussions within the SFC Working
> > Group (WG), a user/network service is typically realized by a chain of
> > VNFs (also known as a VNF Forwarding Graph -VNFG)  to deliver function
> > in a deterministic sequence. Whereas SFC WG is tasked with
> > investigating and documenting SFC architecture, and  SFC protocol
> > mechanisms (new or extensions to existing solutions) in order to
> > encapsulate and steer traffic, and convey SFC and Service Function Path
> (SFP) information to function nodes, both virtual and physical.
> >
> > The vnfpool list was initiated to investigate the resilience
> > requirements and solutions  for virtual network functions, running as
> > single, or pools (sets) of VNFs. So clearly some of the vnfpool work
> > may be complimentary to the SFC WG, but I think the majority of work
> > will be in parallel to the SFC WG. Initially this list has scoped the
> > vnfpool work into a problem statement, use cases, architecture and
> > signalling to deploy and manage VNF pool resilience (reliability,
> redundancy, availability, failover), these discussions have included:
> >
> > - Signalling between VNF pools for transition (e.g. state change,
> > scaling, moving) management, notification, backup, performance
> > monitoring and announcements;
> >
> > - Service state management (e.g. synchronizing method, state data
> > format, location and mechanism to access state data);
> >
> > - Obtaining underlying network information (e.g., this is where we
> > expect cooperation with existing working groups - ALTO, I2RS);
> >
> > - Mechanisms for instance deployment reflecting resilience requirements
> (e.g.
> > distribution of instances across different VMs or hypervisors);
> >
> > - Explore and document requirements for reliable transport of traffic
> > and security mechanisms between VNF pools, and reliable and secure
> > control of VNF pools.
> >
> > We have established that for some use cases (Virtualisation of Mobile
> > Core Network and IMS (vEPC & vIMS), Virtualisation of the Home
> > Environment (vHome), Virtualisation of Content Distribution Network
> > (vCDN)) there will also be specific resilience requirements, when
> > relevant to the SFC WG, i.e., traffic steering between (virtual)
> > network function nodes, these application specific requirements may
> > require co-operation (via requirements or problem statement I-Ds between
> vnfpool and SFC WG).
> >
> > Br, Dan.
> >
> > -----Original Message-----
> > From: vnfpool [mailto:vnfpool-bounces@ietf.org] On Behalf Of Melinda
> > Shore
> > Sent: 21 January 2014 18:39
> > To: adrian@olddog.co.uk
> > Cc: vnfpool@ietf.org
> > Subject: Re: [vnfpool] Overlap with SFC?
> >
> > Hi, Adrian:
> >
> > The vnfpool proposal is quite narrowly focused on redundancy
> > mechanisms for virtualized network functions.
> >
> > Melinda
> >
> >
> > --
> > Melinda Shore
> > No Mountain Software
> > melinda.shore@nomountain.net
> >
> > "Software longa, hardware brevis."
> > _______________________________________________
> > vnfpool mailing list
> > vnfpool@ietf.org
> > https://www.ietf.org/mailman/listinfo/vnfpool
> > _______________________________________________
> > vnfpool mailing list
> > vnfpool@ietf.org
> > https://www.ietf.org/mailman/listinfo/vnfpool
> _______________________________________________
> vnfpool mailing list
> vnfpool@ietf.org
> https://www.ietf.org/mailman/listinfo/vnfpool