SOL005_110 to SOL005_114, SOL005_116 to SOL005_119

        shall be returned when a single consecutive byte range from the content of the NSD file has been read

        successfully according to the request.

        The response body shall contain the requested part of the NSD archive.

        The "Content-Range" HTTP header shall be provided according to IETF RFC 9110.

        The "Content-Range" HTTP header shall be provided according to IETF RFC 7233.

        The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response.

      headers:

        Content-Type:

        Shall be returned when the content of the artifact file has been read successfully.

        If the "include_signatures" request URI parameter was not provided in the related request, 

        the payload body shall contain a copy of the artifact file from the NSD archive, as defined 

        the message content shall contain a copy of the artifact file from the NSD archive, as defined 

        by ETSI GS NFV-SOL 007, and the "Content-Type" HTTP header shall be set according to the 

        content type of the artifact file. If the artifact is encrypted, the header shall be set to

        the value "application/cms" (IETF RFC 7193). 

        If the content type cannot be determined, the header shall be set to the value 

        "application/octet-stream". If the "include_signatures" request URI parameter was provided 

        in the related request, the "Content-Type" HTTP header shall be set to "application/zip"

        and the payload body shall contain a ZIP archive which includes:

        and the message content shall contain a ZIP archive which includes:

        - a copy of the artifact file from the VNF package, as defined by ETSI GS NFVSOL 007

        - the related security information (individual signature file and optional related individual 

        certificate file).

        read successfully.

        If the "include_signatures" URI query parameter was absent in the

        request, or if the manifest file has all security-related information

        embedded (i.e. there is no separate certificate file), the payload

        body shall contain a copy of the manifest file of the PNFD archive,

        embedded (i.e. there is no separate certificate file), the message

        content shall contain a copy of the manifest file of the PNFD archive,

        and the "Content-Type" HTTP header shall be set to "text/plain".

        If the "include_signatures" URI query parameter was present in the

        related request and the manifest file does not have all the

        security-related information embedded (i.e. there is a separate certificate file),

        the "Content-Type" HTTP header shall be set to "application/zip" and

        the payload body shall contain a ZIP archive which includes:

        the message content shall contain a ZIP archive which includes:

        - a copy of the manifest file of the PNFD archive;

        - a copy of the related individual certificate file.

      headers:

    NsLcmOpOccCancelRequest:

      description: |

        The POST request to this resource shall include a CancelMode structure in the payload body to choose between

        The POST request to this resource shall include a CancelMode structure in the message content to choose between

        "graceful" and "forceful" cancellation.

      content:

        application/json:

      as it may describe the version dependencies of the descriptor referenced in the

      profile or of other descriptors with the same external invariant identifier.

      NOTE 3:  The "overridingVersionDependency" attribute may only be present if

      the "overrridingNsdId" attribute is present.

      the "overridingNsdId" attribute is present.

    type: object

    required:

      - nsProfileId

  InstantiateVnfData:

    description: >

      This type represents the information related to a SAP of a NS. The InstantiateVnfData data type specifies the

      parameters that are needed for VNF instantiation. This information element is used for the bottom-up NS creation when

      the OSS/BSS explicitly requests VNF instantiation for a given NS. When the NFVO invokes the Instantiate VNF

      update operation, a set of these parameters are then passed by the NFVO to the VNFM.

      The InstantiateVnfData data type specifies the parameters that are needed for VNF instantiation. This 

      information element is used for the bottom-up NS creation when the OSS/BSS explicitly requests VNF 

      instantiation for a given NS. When the NFVO invokes the Instantiate VNF update operation, a set of 

      these parameters are then passed by the NFVO to the VNFM.

      NOTE 1: It is possible to have several ExtManagedVirtualLinkData for the same VNF internal

              VL in case of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkData

#          Identifier of the subscription.

#          This identifier can be retrieved from the resource referenced by the "Location" HTTP header in the response

#          to a POST request creating a new subscription resource. It can also be retrieved from the "id" attribute in the

#          payload body of that response.

#          message content of that response.

#        in: path

#        type: string

#        required: true

      description: |

        Identifier of this subscription. This identifier can be retrieved from the resource referenced by the "Location"

        HTTP header in the response to a POST request creating a new "Individual subscription" resource. It can also be retrieved

        from the "id" attribute in the payload body of that response.

        from the "id" attribute in the message content of that response.

      required: true

      style: simple

      explode: false