[NFVCON] NFVCon BoF request

"Songhaibin (A)" <haibin.song@huawei.com> Wed, 11 June 2014 01:07 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 E67A31A010F for <nfvcon@ietfa.amsl.com>; Tue, 10 Jun 2014 18:07:46 -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 NgNmIbd0wdad for <nfvcon@ietfa.amsl.com>; Tue, 10 Jun 2014 18:07:44 -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 61CD31A021B for <nfvcon@ietf.org>; Tue, 10 Jun 2014 18:07:44 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BFH07820; Wed, 11 Jun 2014 01:07:42 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 11 Jun 2014 02:07:42 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Wed, 11 Jun 2014 09:07:36 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "nfvcon@ietf.org" <nfvcon@ietf.org>
Thread-Topic: NFVCon BoF request
Thread-Index: Ac+FEYdFQykgC3xITGyMLeg5Ah19jw==
Date: Wed, 11 Jun 2014 01:07:35 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F650ED2E5@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/sZF8kLv2K1pMz0i8i6NWU11tU_g
Subject: [NFVCON] NFVCon BoF request
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: Wed, 11 Jun 2014 01:07:47 -0000

Dear folks,

We sent a non-wg-forming BoF request to OPS AD for meeting at Toronto. The goal of the BoF is NOT to form a working group, but mainly with discussing the NFV use cases, to identify the potential protocol extensions or interactions with existing WGs (such like Netconf , SFC). 

Now the information is on the bof wiki page.

http://tools.ietf.org/bof

Best Regards!
-Haibin