From 7cf815e5a3218740157bd33ce5f487afd0af473b Mon Sep 17 00:00:00 2001 From: "Bozawglanian, Hagop (hb755d)" Date: Fri, 25 May 2018 18:24:11 +0000 Subject: VNFRQTS - Update Chapter 2 Scope Changing VNF/PNF to reference xNF. Change-Id: I7825140659598307f64b1e84d16c55b5741cc860 Issue-ID: VNFRQTS-218 Signed-off-by: Bozawglanian, Hagop (hb755d) --- docs/Chapter2.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/Chapter2.rst b/docs/Chapter2.rst index fcc4f45..ceee9ed 100644 --- a/docs/Chapter2.rst +++ b/docs/Chapter2.rst @@ -5,18 +5,18 @@ **Scope** ============ -- The audience for this document are VNF/PNF providers, NCSPs and other +- The audience for this document are xNF providers, NCSPs and other interested 3rd parties who need to know the design, build and lifecycle - management requirements for VNFs/PNFs to be compliant with ONAP. -- These requirements are strictly from a standpoint of what the VNF/PNF + management requirements for xNFs to be compliant with ONAP. +- These requirements are strictly from a standpoint of what the xNF developer needs to know to operate and be compliant with ONAP. -- Requirements that are not applicable to VNF/PNF providers such as those +- Requirements that are not applicable to xNF providers such as those that applicable to service providers are not included in this document. - These requirements are applicable to the current release of ONAP. - Scope of the ONAP versions/release and future functionality - The VNF Requirements should include support for the functionality of the ONAP E-E use cases. -- These requirements apply to VNFs at both ONAP Design-Time and ONAP Run-Time. +- These requirements apply to xNFs at both ONAP Design-Time and ONAP Run-Time. - Network Service Descriptions are beyond the scope of these requirements. References -- cgit 1.2.3-korg