Add PNF Descriptor Capability requirements

[vnfrqts/requirements.git] / docs / Chapter5 / Tosca.rst

diff --git a/docs/Chapter5/Tosca.rst b/docs/Chapter5/Tosca.rst
index 9e2c953..dfb9b5d 100644 (file)
--- a/docs/Chapter5/Tosca.rst
+++ b/docs/Chapter5/Tosca.rst
@@ -201,11 +201,23 @@ VNF Package Contents
 
       - onap_others
 
-VNF Package Authenticity
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+VNF or PNF Package Authenticity
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+VNF or PNF package shall support a method for authenticity and integrity
+assurance. Note, Option 2 specified in SOL004 is supported in Dublin release.
 
-Will be added in future releases.
+.. req::
+    :id: R-444945
+    :target: VNF or PNF
+    :keyword: MUST
+    :introduced: dublin
 
+    The complete CSAR file **MUST** be digitally signed with the VNF or PNF
+    provider private key. The VNF or PNF provider delivers one zip file
+    consisting of the CSAR file, a signature file and a certificate file that
+    includes the VNF or PNF provider public key. The certificate may also be
+    included in the signaturecontainer, if the signature format allows that.
 
 VNF Package ONAP Extensions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -467,18 +479,76 @@ TOSCA PNF Descriptor
 General
 ~~~~~~~~~~
 
+.. req::
+    :id: R-24632
+    :target: PNF
+    :keyword: MUST
+    :introduced: dublin
+
+    The PNF Descriptor (PNFD) provided by PNF vendor **MUST** comply with
+    TOSCA/YAML based Service template for PNF descriptor specified in ETSI
+    NFV-SOL001.
+
+
+.. req::
+    :id: R-998862
+    :target: PNF
+    :keyword: MUST
+    :introduced: dublin
+
+    The PNFD provided by a PNF vendor **MUST** comply with the following TOSCA
+    Types as specified in ETSI NFV-SOL001 standard:
+
+      - tosca.nodes.nfv.PNF
+
+      - tosca.nodes.nfv.PnfExtCp
+
 
 Data Types
 ~~~~~~~~~~~~~~
 
+.. req::
+    :id: R-484843
+    :target: PNF
+    :keyword: MUST
+    :introduced: dublin
+
+    The PNFD provided by a PNF vendor **MUST** comply with the following Data
+    Types as specified in ETSI NFV-SOL001 standard:
+
+      - tosca.datatypes.nfv.CpProtocolData
+
+      - tosca.datatypes.nfv.AddressData
+
+      - tosca.datatypes.nfv.L2AddressData
+
+      - tosca.datatypes.nfv.L3AddressData
+
+      - tosca.datatypes.nfv.LocationInfo
+
+      - tosca.datatypes.nfv.CivicAddressElement
+
 
 Artifact Types
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
+No artifact type is currently supported in ONAP.
+
 
 Capability Types
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
+.. req::
+    :id: R-177937
+    :target: PNF
+    :keyword: MUST
+    :introduced: dublin
+
+    The PNFD provided by a PNF vendor **MUST** comply with the following
+    Capabilities Types as specified in ETSI NFV-SOL001 standard:
+
+      - tosca.datatypes.nfv.VirtualLinkable
+
 
 Requirements Types
 ~~~~~~~~~~~~~~~~~~~~~~~~
@@ -487,10 +557,14 @@ Requirements Types
 Relationship Types
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
+No requirements type is currently supported in ONAP.
+
 
 Interface Types
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
+No interface type is currently supported in ONAP.
+
 
 Node Types
 ~~~~~~~~~~~~~~
@@ -499,6 +573,8 @@ Node Types
 Group Types
 ~~~~~~~~~~~~~~
 
+No group type is currently supported in ONAP.
+
 
 Policy Types
 ~~~~~~~~~~~~~~