[NFVCON] virtualization of network functions makes the management different

"Songhaibin (A)" <haibin.song@huawei.com> Fri, 23 May 2014 03:02 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 616901A0307 for <nfvcon@ietfa.amsl.com>; Thu, 22 May 2014 20:02:29 -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 5kAIkKKmvfhl for <nfvcon@ietfa.amsl.com>; Thu, 22 May 2014 20:02:28 -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 0D4321A005B for <nfvcon@ietf.org>; Thu, 22 May 2014 20:02:27 -0700 (PDT)
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 BEL24182; Fri, 23 May 2014 03:02:24 +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; Fri, 23 May 2014 04:02:08 +0100
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 23 May 2014 04:02:21 +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 11:02:16 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "nfvcon@ietf.org" <nfvcon@ietf.org>
Thread-Topic: virtualization of network functions makes the management different
Thread-Index: Ac92M2ZTQwJ5rnZ6SmyQB+VHbtBcFg==
Date: Fri, 23 May 2014 03:02:15 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F650E4BD7@nkgeml501-mbs.china.huawei.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.49]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/nfvcon/0pSt043kx2-JpUR0xn9l_t964vA
Subject: [NFVCON] virtualization of network functions makes the management different
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 03:02:29 -0000

Hi guys,

I'm thinking the virtualization of network functions makes the management different from the conventional network appliances, for example, when compared with hard appliances, virtual network functions are easy to install/update/delete, or migrate from one place to another (for something like virtual residential gateway). And virtual network functions can also be open to the network function consumers. What are other differences in your opinion?

Best Regards!
-Haibin