NSDManagement.yaml

        504:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/504"

  ###############################################################################
  # Individual Subscription                                                     #
  ###############################################################################
  /subscriptions/{subscriptionId}:
    #ETSI GS NFV-SOL 005 V2.4.1 location: 5.4.9    
    parameters:
      - $ref: '#/components/parameters/SubscriptionId'
      - $ref: ../components/SOL005_params.yaml#/components/parameters/Authorization
      - $ref: ../components/SOL005_params.yaml#/components/parameters/Version

    get:
      description: |
        The GET method retrieves information about a subscription by reading an individual subscription resource.
        See clause 5.4.9.3.2.
      parameters:
        - $ref: ../components/SOL005_params.yaml#/components/parameters/Accept
      responses:
        200:
          $ref: '#/components/responses/IndividualSubscription.Get.200'
        400:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/400"
        401:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/401"
        403:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/403"
        404:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/404"
        405:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/405"
        406:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/406"
        500:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/500"
        503:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/503"
        504:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/504"

    delete:
      description: |
        The DELETE method terminates an individual subscription. See clause 5.4.9.3.5.
      responses:
        204:
          $ref: '#/components/responses/IndividualSubscription.Delete.204'
        400:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/400"
        401:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/401"
        403:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/403"
        404:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/404"
        405:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/405"
        406:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/406"
        500:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/500"
        503:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/503"
        504:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/504"

components:
  parameters:
    AcceptTextOrZip:
      name: Accept
      description: >
        The request shall contain the appropriate entries in the "Accept" HTTP header.
      in: header
      required: true
      schema:
        type: string
        enum:
          - text/plain
          - application/zip
    AcceptText:
      name: Accept
      description: >
        The request shall contain the appropriate entries in the "Accept" HTTP header.
      in: header
      required: true
      schema:
        type: string
        enum:
          - text/plain
    ContentTypeZip:
      name: Content-Type
      description: |
        The payload body contains a ZIP file that represents the NSD archive, as specified above.
            The request shall set the "Content-Type" HTTP header to "application/zip".
      in: header
      required: true
      schema:
        type: string
        enum:
          - application/zip

    NsdInfoId:
      name: nsdInfoId
      in: path
      description: |
        Identifier of the individual NS descriptor resource.
      required: true
      style: simple
      explode: false
      schema:
        type: string
    
    PnfdInfoId:
      name: pnfdInfoId
      in: path
      description: |
          Identifier of the individual PNF descriptor resource.
      required: true
      style: simple
      explode: false
      schema:
        type: string

    ArtifactPathInNSD:
      name: artifactPath
      in: path
      description: |
        For an artifact contained as a file in the NSD archive, this variable shall 
        contain a sequence of one or path segments representing the path of the 
        artifact within the NSD archive, relative to the root of the package.

        EXAMPLE: foo/bar/m%40ster.sh
        
        For an external artifact represented as a URI in the NSD archive manifest, 
        this variable shall contain the URI as provided in the NS archive.

        This identifier can be retrieved from the "artifactPath" attribute of the 
        applicable "artifacts" entry in the body of the response to a GET request 
        querying the "Individual NSD" resource.
        
        Since multiple path segments are allowed to be contained in this variable, 
        the "/" character that separates these segments is not percent-encoded. 
        Each individual segment is percent-encoded if necessary as defined in 
        clause 4.1 of ETSI GS NFV-SOL 013.
      required: true
      style: simple
      explode: false
      schema:
        type: string

    ArtifactPathInPNFD:
      name: artifactPath
      in: path
      description: |
        For an artifact contained as a file in the PNFD archive, this variable shall contain 
        a sequence of one or path segments representing the path of the artifact within the 
        PNFD archive, relative to the root of the package.

        EXAMPLE: foo/bar/m%40ster.sh

        For an external artifact represented as a URI in the PNFD archive manifest, this variable 
        shall contain the URI as provided in the NS archive.

        This identifier can be retrieved from the "artifactPath" attribute of the applicable 
        "artifacts" entry in the body of the response to a GET request querying the "Individual PNFD" 
        resource. 
        
        Since multiple path segments are allowed to be contained in this variable, the "/" character 
        that separates these segments is not percent-encoded. Each individual segment is percent-encoded 
        if necessary as defined in clause 4.1 of ETSI GS NFV-SOL 013.
      required: true
      style: simple
      explode: false
      schema:
        type: string

    SubscriptionId:
      name: subscriptionId
      in: path
      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 subscription resource. It can also be retrieved
          from the "id" attribute in the payload body of that response.
      required: true
      style: simple
      explode: false
      schema:
        type: string
  
  requestBodies:
    CreateNsdInfoRequest:
      description: |
        Parameters of creating an NS descriptor resource, as defined in clause 5.5.2.3.
      content:
        application/json:
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/CreateNsdInfoRequest"
      required: true

    NsdInfoModifications:
      description: |
        Parameters for the modification of an individual NS descriptor resource, as defined in clause 5.5.2.1.
        The Content-Type header shall be set to "application/merge-patch+json" according to IETF RFC 7396.
      content:
        application/json:
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfoModifications"
      required: true

    CreatePnfdInfoRequest:
      description: |
        Parameters of creating a PNF descriptor resource.
      content:
        application/json:
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/CreatePnfdInfoRequest"
      required: true

    PnfdInfoModifications:
      description: |
        Parameters for the modification of an individual
        PNF descriptor resource, as defined in clause 5.5.2.4.
        The Content-Type header shall be set to "application/merge-patch+json"
        according to IETF RFC 7396.
      content:
        application/json:
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/PnfdInfoModifications"
      required: true

    NsdmSubscriptionRequest:
      description: |
        Details of the subscription to be created, as defined in clause 5.5.2.7.
      content:
        application/json:
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdmSubscriptionRequest"
      required: true

  responses:
    NSDescriptors.Post.201:
      description: |
        201 CREATED

        Shall be returned when a new "Individual NS descriptor" resource
        and the associated NS descriptor identifier has been created successfully.
        The response body shall contain a representation of the created NS descriptor
        resource, as defined in clause 5.5.2.2.
        The HTTP response shall include a "Location" HTTP header that contains the
        resource URI of the created NS descriptor resource.
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo"

    NSDescriptors.Get.200:
      description: |
        200 OK

        Shall be returned when information about zero or
        more NS descriptors has been queried successfully.
        The response body shall contain in an array the
        representations of zero or more NS descriptors, as
        defined in clause 5.5.2.2.
        If the NFVO supports alternative 2 (paging) according
        to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for
        this resource, inclusion of the Link HTTP header in
        this response shall follow the provisions in clause
        5.4.2.3 of ETSI GS NFV-SOL 013.
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string
        Link:
          description: |
            Reference to other resources. Used for paging in the present document, see clause 4.7.2.1.
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            type: array
            items:
              $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo"

    IndividualNSDescriptor.Get.200:
      description: |
        200 OK

        Shall be returned when information about the individual
        NS descriptor has been read successfully.
        The response body shall contain a representation of
        the individual NS descriptor, as defined in
        clause 5.5.2.2.
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo"

    IndividualNSDescriptor.Patch.200:
      description: |
        200 OK

        Shall be returned when the operation has been accepted and completed successfully.
        The response body shall contain attribute modifications for an 'Individual NS descriptor'
        resource (see clause 5.5.2.6).
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfoModifications"

    IndividualNSDescriptor.Delete.204:
      description: |
        204 NO CONTENT

        Shall be returned when the operation has completed successfully.
        The response body shall be empty.
      headers:
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    NsdArchiveContent.Get.200:
      description: |
        200 OK

        Shall be returned when the content of the NSD has been read successfully.
        The payload body shall contain a copy of the ZIP file that contains the NSD file structure.
        The "Content-Type" HTTP header shall be set to "application/zip".
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    NsdArchiveContent.Put.202:
      description: |
        202 ACCEPTED

        Shall be returned when the NSD archive has been accepted for uploading,
        but the processing has not been completed. It is expected to take some
        time for processing (asynchronous mode).
        The response body shall be empty.
        The API consumer can track the uploading progress by receiving the
        "NsdOnBoardingNotification" and "NsdOnBoardingFailureNotification"
        from the NFVO or by reading the status of the individual NS descriptor
        resource using the GET method.
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    NsdArchiveContent.Put.204:
      description: |
        204 NO CONTENT

        The NSD content successfully uploaded and
        validated (synchronous mode).
        The response body shall be empty.
      headers:
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    NSD.Get.200:
      description: |
        200 OK

        Shall be returned when the content of the NSD has been read successfully.
        The payload body shall contain a copy of the file representing the NSD or
        a ZIP file that contains the file or multiple files representing the NSD,
        as specified above.
        The "Content-Type" HTTP header shall be set according to the format of
        the returned file. It shall be set to "text/plain" for a YAML file.
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    NsdArchiveManifest.Get.200:
      description: |
        200 OK

        Shall be returned when the content of the manifest file has been 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
        NSD 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:
        -	a copy of the manifest file of the NSD archive;
        -	a copy of the related individual certificate file.
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    IndividualNsdArchiveArtifact.Get.200:
      description: |
        200 OK

        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 
        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:
        - 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).
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    IndividualNsdArchiveArtifact.Get.206:
      description: |
        206 PARTIAL CONTENT

        If the NFVO supports range requests and the "include_signatures" request URI parameter was
        not present in the related request, this response shall be returned when a single consecutive 
        byte range from the content of the artifact file has been read successfully according to the 
        request.

        The response body shall contain the requested part of the artifact file from the NSD archive, 
        as defined by ETSI GS NFV-SOL 007. 
        
        The "Content-Type" HTTP header shall be set according to the content type of the artifact file. 
        If the content type cannot be determined, the header shall be set to the value 
        "application/octet-stream".

        The "Content-Range" HTTP header shall be provided according to IETF RFC 7233.
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    PNFDescriptors.Post.201:
      description: |
        201 CREATED

        Shall be returned when a new "Individual PNF descriptor"
        resource and the associated PNF descriptor identifier
        has been created successfully.
        The response body shall contain a representation of the
        created PNF descriptor resource, as defined in clause 5.5.2.5.
        The HTTP response shall include a "Location" HTTP header that
        contains the resource URI of the created PNF descriptor resource.
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/PnfdInfo"

    PNFDescriptors.Get.200:
      description: |
        200 OK

        Shall be returned when information about zero or more PNF descriptors has
        been queried successfully.
        The response body shall contain in an array the representations of zero or
        more PNF descriptors, as defined in clause 5.5.2.5.
        If the NFVO supports alternative 2 (paging) according to clause 5.4.2.1 of
        ETSI GS NFV-SOL 013 for this resource, inclusion of the Link HTTP header in
        this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string
        Link:
          description: |
            Reference to other resources. Used for paging in the present document, see clause 4.7.2.1.
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            description: |
              Information about zero or more PNF descriptors.
              The response body shall contain a representation in an array the representations
              of zero or more PNF descriptors, as defined in clause  5.5.2.2.
              If the NFVO supports alternative 2 (paging) according to clause 4.7.2.1 for this resource,
              inclusion of the Link HTTP header in this response shall follow the provisions in clause 4.7.2.3.
            type: array
            items:
              $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/PnfdInfo"

    IndividualPnfDescriptor.Get.200:
      description: |
        200 OK

        Shall be returned when information about the individual PNFD
        descriptor has been read successfully.
        The response body shall contain a representation of the
        individual PNF descriptor, as defined in clause 5.5.2.5.
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/PnfdInfo"

    IndividualPnfDescriptor.Patch.200:
      description: |
        200 OK

        Shall be returned when the operation has been accepted
        and completed successfully.
        The response body shall contain attribute modifications
        for an 'Individual PNF Descriptor' resource (see clause 5.5.2.4).
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/PnfdInfoModifications"

    IndividualPnfDescriptor.Delete.200:
      description: |
        204 NO CONTENT

        Shall be returned when the operation
        has completed successfully.
        The response body shall be empty.
      headers:
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    PnfdArchiveContent.Get.200:
      description: |
        200 OK

        Shall be returned when the content of the PNFD archive has
        been read successfully.
        The payload body shall contain a copy of the PNFD archive
        The "Content-Type" HTTP header shall be set to "application/zip".
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    PnfdArchiveContent.Get.206:
      description: |
        206 PARTIAL CONTENT

        If the NFVO supports range requests, this response shall be returned
        when a single consecutive byte range from the content of the PNFD archive
        has been read successfully according to the request.
        The response body shall contain the requested part of the PNFD archive.
        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:
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
        Content-Range:
          description: The Content-Range response HTTP header indicates where in a full body message a partial message belongs.
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    PnfdArchiveContent.Put.200:
      description: |
        202 ACCEPTED

        Shall be returned when the PNFD archive has been accepted for uploading,
        but the processing has not been completed. It is expected to take some
        time for processing (asynchronous mode).
        The response body shall be empty.
        The API consumer can track the uploading progress by receiving the
        "PnfdOnBoardingNotification" and "PnfdOnBoardingFailureNotification"
        from the NFVO or by reading the status of the individual PNF descriptor
        resource using the GET method.
      headers:
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    PnfdArchiveContent.Put.204:
      description: |
        204 NO CONTENT

        Shall be returned when the PNFD archive content has been
        uploaded and validated successfully.
        The response body shall be empty.
      headers:
        WWW-Authenticate:
          description: |
            Challenge if the corresponding HTTP request has not provided authorization, or error details if the
            corresponding HTTP request has provided an invalid authorization token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          style: simple
          explode: false
          schema:
            type: string

    PNFD.Get.200:
      description: |
        200 OK

        Shall be returned when the content of the PNFD has been read successfully.
        The payload body shall contain a copy of the file representing the PNFD
        or a ZIP file that contains the file or multiple files representing the
        PNFD, as specified above.
        The "Content-Type" HTTP header shall be set according to the format of
        the returned file. It shall be set to "text/plain" for a YAML file.
      headers:
        Content-Type: