2 files changed, 64 insertions, 2 deletions
diff --git a/docs/files/VNFSDK-LFN-CVC.rst b/docs/files/VNFSDK-LFN-CVC.rst
index bfb6f0c..814701f 100644
--- a/docs/files/VNFSDK-LFN-CVC.rst
+++ b/docs/files/VNFSDK-LFN-CVC.rst
@@ -31,7 +31,7 @@ We propose expanding the program in 2018 to include VNF Compliance
 
 VNF Test Platform (VTP)
 =======================
-Deploy VNF test cases once and trigger it safely from anywhere
+Deploy VNF/PNF test cases once and trigger it safely from anywhere
 
 Objectives
 ----------
@@ -162,7 +162,7 @@ CVC Structures
    :width: 600px
 
 
-Casablanca Implemented requriements
+Casablanca Implemented requirements
 ===================================
 
 .. list-table::
@@ -192,3 +192,65 @@ Casablanca Implemented requriements
 
    * - R-77786
      - The VNF Package MUST include all relevant cookbooks to be loaded on the ONAP Chef Server.
+
+
+Dublin Implemented requirements
+===================================
+
+.. list-table::
+   :header-rows: 1
+
+
+   * - **Requirement No.**
+     - **Requirement Description**
+
+   * - R-10087
+     - The VNF/PNF package MUST contain all standard artifacts as specified in ETSI GS NFV-SOL004 including Manifest file, VNFD/PNFD (or Main TOSCA/YAML based Service Template) and other optional artifacts. CSAR Manifest file as per SOL004 - for example ROOT\ MainServiceTemplate.mf
+
+   * - R-17852
+     - The VNFD/PNFD MAY include TOSCA/YAML definitions that are not part of NFV Profile. If provided, these definitions MUST comply with TOSCA Simple Profile in YAML v.1.2.
+
+   * - R-35854
+     - The VNF/PNF Descriptor (VNFD/PNFD) provided by VNF/PNF vendor MUST comply with TOSCA/YAML based Service template for VNF/PNF descriptor specified in ETSI NFV-SOL001.
+
+   * - R-57019
+     - The PNF TOSCA CSAR package Manifest file MUST start with the PNF package metadata in the form of a name-value pairs. Each pair shall appear on a different line. The name is specified as following: pnfd_provider, pnfd_name, pnfd_release_date_time, pnfd_archive_version
+
+   * - R-87234
+     - The VNF/PNF package provided by a VNF/PNF vendor MAY be either with TOSCA-Metadata directory (CSAR Option 1) or without TOSCA-Metadata directory (CSAR Option 2) as specified in ETSI GS NFV-SOL004. On-boarding entity (ONAP SDC) must support both options.
+
+   * - R-146092
+     - The VNF/PNF package Manifest file MUST contain: non-mano artifact set with following ONAP public tag: onap_ves_events, onap_pm_dictionary, onap_yang_module, onap_others
+  
+   * - R-293901
+     - For a VNF/PNF package CSAR MUST contains a TOSCA-Metadata directory with the TOSCA.meta metadata file. The TOSCA.meta metadata file MUST includes block_0 with the Entry-Definitions keyword pointing to a TOSCA definitions YAML file. Additional keyname extension must be included as following: ETSI-Entry-Manifest, ETSI-Entry-Change-Log
+
+   * - R-787965
+     - If the VNF or PNF CSAR Package utilizes Option 2 for package security, then 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 signature container, if the signature format allows that. The VNF or PNF provider creates a zip file consisting of the CSAR file with .csar extension, signature and certificate files. The signature and certificate files must be siblings of the CSAR file with extensions .cms and .cert respectively.
+
+OCLIP additional parameters in Dublin
+=====================================
+
+To run validation of PNF csar additional --pnf parameter must be used.
+
+  oclip --product onap-vtp csar-validate --pnf --csar <path to pnf.csar or package.zip>
+
+Package zip structure 
+=====================
+|image3|
+
+.. |image3| image:: zip_package.png
+   :height: 250px
+   :width: 260px
+
+Generate certificates
+---------------------
+  openssl req -nodes -x509 -sha256 -newkey rsa:4096 -keyout "pnf.key" -out "pnf.cert" -days 365 -subj "/C=NL/ST=Zuid Holland/L=Rotterdam/O=Sparkling Network/OU=IT Dept/CN=$(whoami)s Sign Key"
+
+Sign csar file with private key
+-------------------------------
+  openssl dgst -sha256 -sign "pnf.key" -out pnf.sha256.cms pnf.csar
+
+Verify signature
+----------------
+  openssl dgst -sha256 -verify  <(openssl x509 -in "pnf.cert"  -pubkey -noout) -signature pnf.sha256.cms pnf.csar
+\ No newline at end of file
diff --git a/docs/files/zip_package.png b/docs/files/zip_package.png
new file mode 100644
index 0000000..8bafb01
--- /dev/null
+++ b/docs/files/zip_package.png