From 895783604439557c400b580dab8ec2420c575687 Mon Sep 17 00:00:00 2001 From: fzhang Date: Fri, 15 Mar 2019 01:26:16 -0700 Subject: Add requirement R-444945 Add requirement R-444945 to support VNF/VNF authenticity. Change-Id: I46b7703bd3b010a16bea62b41612c90a24f5d9d3 Issue-ID: VNFRQTS-497 Signed-off-by: fzhang --- docs/Chapter5/Tosca.rst | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) (limited to 'docs/Chapter5') diff --git a/docs/Chapter5/Tosca.rst b/docs/Chapter5/Tosca.rst index 9e2c953..13fcd32 100644 --- 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- cgit 1.2.3-korg