[NFVCON] related work progress in IETF

"Songhaibin (A)" <haibin.song@huawei.com> Mon, 20 January 2014 08:34 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 0763B1A00A4 for <nfvcon@ietfa.amsl.com>; Mon, 20 Jan 2014 00:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.036
X-Spam-Status: No, score=-2.036 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id X_FUQ0XIhGEM for <nfvcon@ietfa.amsl.com>; Mon, 20 Jan 2014 00:34:31 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) by ietfa.amsl.com (Postfix) with ESMTP id C32481A009F for <nfvcon@ietf.org>; Mon, 20 Jan 2014 00:34:30 -0800 (PST)
Received: from (EHLO lhreml203-edg.china.huawei.com) ([]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCR08937; Mon, 20 Jan 2014 08:34:29 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com ( by lhreml203-edg.huawei.com ( with Microsoft SMTP Server (TLS) id; Mon, 20 Jan 2014 08:33:18 +0000
Received: from NKGEML408-HUB.china.huawei.com ( by lhreml401-hub.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Mon, 20 Jan 2014 08:34:25 +0000
Received: from NKGEML501-MBS.china.huawei.com ([]) by nkgeml408-hub.china.huawei.com ([]) with mapi id 14.03.0158.001; Mon, 20 Jan 2014 16:34:18 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "nfvcon@ietf.org" <nfvcon@ietf.org>
Thread-Topic: related work progress in IETF
Thread-Index: Ac8Vumh5w6PZ4oHzST+GpLqxi8P/tA==
Date: Mon, 20 Jan 2014 08:34:18 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F24827A37@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [NFVCON] related work progress in IETF
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: Mon, 20 Jan 2014 08:34:33 -0000

Recently we noticed that SFC working group was formed. While SFC is focusing on the chaining logic for a virtual network function list and the encapsulation format for packets to enforce the chaining. I think there is still a lot of blank space to do. we can focus on the configuration of VNF itself, e.g. the VNF components selection, the resource requirement model (including automatic scale-out/in), the administration of VNF migration, and etc.

I think we can have another bar BoF at next IETF meeting to discuss these things. And we noticed that ETSI had some gap analysis work done. We can also discuss it.

Best Regards!