[Nfvrg] "Verification of NFV Services : Problem Statement and Challenges" draft
<Ramki_Krishnan@Dell.com> Wed, 09 September 2015 14:58 UTC
Return-Path: <Ramki_Krishnan@dell.com>
X-Original-To: nfvrg@ietfa.amsl.com
Delivered-To: nfvrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A55611B2F82 for <nfvrg@ietfa.amsl.com>; Wed, 9 Sep 2015 07:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level:
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 eN0Npd2ui1CB for <nfvrg@ietfa.amsl.com>; Wed, 9 Sep 2015 07:58:14 -0700 (PDT)
Received: from ausxippc101.us.dell.com (ausxippc101.us.dell.com [143.166.85.207]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5941D1B2F93 for <nfvrg@irtf.org>; Wed, 9 Sep 2015 07:58:14 -0700 (PDT)
DomainKey-Signature: s=smtpout; d=dell.com; c=nofws; q=dns; h=X-LoopCount0:X-IronPort-AV:From:To:CC:Date:Subject: Thread-Topic:Thread-Index:Message-ID:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: acceptlanguage:Content-Type:MIME-Version; b=daB1Cg1dI9FqnRzaYVlq9FcYo9X2GEmTjP9J42ZVO4hQymZKU5qtEcfE Zu0rF0QtsPxQjUEBGZJGOq169yz7Wvaw7x9moMrvVUwR7bdk7Rjgc4hPM A8+5GIF3jzip2Q9J8byjymIqqT05lMOC0TnnLje3K0B7sgYGujkuZQD67 c=;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1441810694; x=1473346694; h=from:to:cc:date:subject:message-id:mime-version: content-transfer-encoding; bh=gQcVGSzwqxmQ+HjIi3NcRcf5XIRTGYqkIHwytCbz9wc=; b=0Li8EL9ih2dFjXKKDutULP6k2gMftIHxj/RzMo/CRwwdL/b2k5RslMra pSFqt163eQ9XC8DQDOG3s3Yot+RBcQOix6bUPcCg8i5U92FZVL4bGLkpq YVMM8icrWiUHAzpDdYRycua1qQG3u0Fa5I2R9p+61kCdojm8eQUxWFPyZ g=;
X-LoopCount0: from 10.175.216.251
X-IronPort-AV: E=Sophos;i="5.17,496,1437454800"; d="scan'208,217";a="704405655"
From: Ramki_Krishnan@Dell.com
To: draft-shin-nfvrg-service-verification@ietf.org
Date: Wed, 09 Sep 2015 09:54:16 -0500
Thread-Topic: "Verification of NFV Services : Problem Statement and Challenges" draft
Thread-Index: AdDrDzqvXAHllJYuS2uLO2qNgnwVxA==
Message-ID: <DF91EBC32A031943A8B78D81D40122BC040238F9BD@AUSX7MCPC103.AMER.DELL.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_DF91EBC32A031943A8B78D81D40122BC040238F9BDAUSX7MCPC103A_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/nfvrg/1gg6GZKz7jc2_EZ3BC_uO1ymEvE>
Cc: nfvrg@irtf.org
Subject: [Nfvrg] "Verification of NFV Services : Problem Statement and Challenges" draft
X-BeenThere: nfvrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Network Function Virtualization Research Group \(NFVRG\) discussion list" <nfvrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nfvrg>, <mailto:nfvrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfvrg/>
List-Post: <mailto:nfvrg@irtf.org>
List-Help: <mailto:nfvrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nfvrg>, <mailto:nfvrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2015 14:58:16 -0000
* Dear All, Below are our thoughts on the "Verification of NFV Services : Problem Statement and Challenges" draft. * This draft lacks detailed implementation example(s) - our request to authors is to provide concrete infrastructure policy example(s) pertinent to service verification. Our suggestion is to use the examples in the draft https://datatracker.ietf.org/doc/draft-krishnan-nfvrg-policy-based-rm-nfviaas/, which map to an implementation, as a guideline. * This would entail the following o Mapping to an implementation whose results can be shared; the implementation (specifically source code) could be open or closed o Identify gaps in the implementation and suggest ways to fill those gaps Link to draft: https://datatracker.ietf.org/doc/draft-shin-nfvrg-service-verification/ Note: We see the community (and thus personal) benefit being maximized through an open source implementation. Relevant open source projects include but are not limited to OPNFV, OpenStack, OpenDaylight etc. Thanks, Ramki & Diego