IETF Logo Mail Archive

Re: [NFVCON] NFV Store

"Songhaibin (A)" <haibin.song@huawei.com> Fri, 23 May 2014 09:37 UTC

Return-Path: <haibin.song@huawei.com>
X-Original-To: nfvcon@ietfa.amsl.com
Delivered-To: nfvcon@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E360A1A0164 for <nfvcon@ietfa.amsl.com>; Fri, 23 May 2014 02:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 RdCGQ5Yd2Z9U for <nfvcon@ietfa.amsl.com>; Fri, 23 May 2014 02:37:54 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0502D1A0150 for <nfvcon@ietf.org>; Fri, 23 May 2014 02:37:53 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BHD27520; Fri, 23 May 2014 09:37:51 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 23 May 2014 10:37:26 +0100
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 23 May 2014 10:37:42 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Fri, 23 May 2014 17:37:35 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "Diego R. Lopez" <diego@tid.es>
Thread-Topic: [NFVCON] NFV Store
Thread-Index: Ac92X80YpTiVlJ7xRieSNj6GW3wz4///7qIA///ZjoA=
Date: Fri, 23 May 2014 09:37:34 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F650E5541@nkgeml501-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F650E54DA@nkgeml501-mbs.china.huawei.com> <D85A656C-1122-49C1-90BB-86BD7F96D191@tid.es>
In-Reply-To: <D85A656C-1122-49C1-90BB-86BD7F96D191@tid.es>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.49]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/nfvcon/1nzmcoL3sVloNmDWPJrZD4FCYfY
Cc: "nfvcon@ietf.org" <nfvcon@ietf.org>
Subject: Re: [NFVCON] NFV Store
X-BeenThere: nfvcon@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "NFV \(Network Function Virtualization\) Configuration and Modeling" <nfvcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfvcon>, <mailto:nfvcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfvcon/>
List-Post: <mailto:nfvcon@ietf.org>
List-Help: <mailto:nfvcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfvcon>, <mailto:nfvcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 May 2014 09:37:56 -0000

Dear Diego,

I fully agree with you. VNF description is very important, for both VNF provider and the VNF consumer IMO.

Best Regards!
-Haibin


> -----Original Message-----
> From: Diego R. Lopez [mailto:diego@tid.es]
> Sent: Friday, May 23, 2014 5:18 PM
> To: Songhaibin (A)
> Cc: nfvcon@ietf.org
> Subject: Re: [NFVCON] NFV Store
> 
> In general, I think the store issue has to deal more with how you describe the
> VNF metadata (its manifest) than with the access protocol itself, that should be
> shaped by the metadata information model...
> 
> Be goode,
> 
> On 23 May 2014, at 10:20 , Songhaibin (A) <haibin.song@huawei.com> wrote:
> 
> > Hi guys,
> >
> > One very interesting concept in the area of NFV is NFV store. It can be seen in
> many places, such like in this European FP7 project called T-NOVA:
> >
> https://www.google.com.hk/url?q=http://cordis.europa.eu/fp7/ict/future-net
> works/documents/call11projects/t-nova.pdf&sa=U&ei=Ov5-U4n3EMWn8AXgy
> 4Jo&ved=0CCoQFjAC&usg=AFQjCNGcdpGz-DzpN5kNet1colSp4iWXgQ
> >
> > Or in the following presentation slides by RAD:
> >
> https://www.google.com.hk/url?q=http://www.celtic-initiative.org/Events/Eve
> nt2014-Monaco/presentations/PDF-23/09-NFV--CELTIC%2520Event%252022.0
> 4.14.pdf&sa=U&ei=Ov5-U4n3EMWn8AXgy4Jo&ved=0CB0QFjAA&usg=AFQjCN
> HGlnHvypahbwxeooh_ZE93m_329A
> >
> > NFV store brings the need of the standards for virtual network function
> vendors to access the NFV store, and for the virtual network function
> consumers to access the NFV store. Any thoughts?
> >
> >
> > Best Regards!
> > -Haibin
> >
> >
> > _______________________________________________
> > NFVCON mailing list
> > NFVCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/nfvcon
> 
> 
> --
> "Esta vez no fallaremos, Doctor Infierno"
> 
> Dr Diego R. Lopez
> Telefonica I+D
> http://people.tid.es/diego.lopez/
> 
> e-mail: diego@tid.es
> Tel:    +34 913 129 041
> Mobile: +34 682 051 091
> -----------------------------------------
> 
> 
> ________________________________
> 
> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
> nuestra política de envío y recepción de correo electrónico en el enlace
> situado más abajo.
> This message is intended exclusively for its addressee. We only send and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx

v2.23.0 | Report a Bug | By Email