NSDManagement.yaml

          Reference: IETF RFC 7235
        in: header
        required: false
        type: string
      - name: Version
        description: >
          Version of the API requested to use when responding to this request.
        in: header
        required: true
        type: string

    get:
      description: >
        The GET method reads the content of the PNFD within a PNFD archive.
        The PNFD can be implemented as a single file or as a collection of
        multiple files. If the PNFD is implemented in the form of multiple
        files, a ZIP file embedding these files shall be returned. If the
        PNFD is implemented as a single file, either that file or a ZIP file
        embedding that file shall be returned.
        The selection of the format is controlled by the "Accept" HTTP header
        passed in the GET request:
        •	If the "Accept" header contains only "text/plain" and the PNFD is
            implemented as a single file, the file shall be returned; otherwise,
            an error message shall be returned.
        •	If the "Accept" header contains only "application/zip", the single
            file or the multiple files that make up the PNFD shall be returned
            embedded in a ZIP file.
        •	If the "Accept" header contains both "text/plain" and "application/zip",
            it is up to the NFVO to choose the format to return for a single-file PNFD;
            for a multi-file PNFD, a ZIP file shall be returned.
        The default format of the ZIP file shall be the one specified in ETSI GS
        NFV-SOL 004 where only the YAML files representing the PNFD, and information
        necessary to navigate the ZIP file and to identify the file that is the entry
        point for parsing the PNFD and (if requested) further security information
        are included. This means that the content of the ZIP archive shall contain
        the following files from the PNFD archive:
        •	TOSCA.meta (if available in the PNFD archive);
        •	the main service template (either as referenced from TOSCA.meta or
            available as a file with the extension ".yml" or ".yaml" from the
            root of the archive);
        •	every component of the PNFD referenced (recursively) from the main
            service template;
        •	the related security information, if the "include_signatures" URI
            parameter is provided, as follows:
            -	the manifest file;
            -	the singleton certificate file in the root of the PNFD archive
                (if available in the PNFD archive);
            -	the signing certificates of the individual files included in the
                ZIP archive (if available in the PNFD archive);
            -	the signatures of the individual files (if available in the PNFD archive).
        This method shall follow the provisions specified in the Tables 5.4.7a.3.2-1 and
        5.4.7a.3.2-2 for URI query parameters, request and response data structures, and response codes.
      parameters:
        - name: Accept
          description: >
            Content-Types that are acceptable for the response.
          in: header
          required: true
          type: string
          enum:
            - text/plain
        - name: Range
          description: >
            The request may contain a "Range" HTTP header to obtain
            single range of bytes from the PNFD archive. This can be
            used to continue an aborted transmission.
            If the NFVO does not support range requests, the NFVO
            shall ignore the "Range" header, process the GET request,
            and return the whole PNFD archive with a 200 OK response
            (rather than returning a 4xx error status code).
          in: header
          required: false
          type: string
        - name: include_signatures
          description: >
            If this parameter is provided, the NFVO shall include in the
            ZIP file the security information as specified above.
            This URI query parameter is a flag, i.e. it shall have no value.
            The NFVO shall support this parameter.
          in: query
          required: false
          type: string
      responses:
        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:
              type: string
              description: >
                The MIME type of the body of the response.This header
                field shall be present if the response has a non-empty message
                body.
            WWW-Authenticate:
              type: string
              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.
              maximum: 1
              minimum: 0
            Version:
              description: >
                Version of the API used in the response.
              type: string
              maximum: 1
              minimum: 1
        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"
        409:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/409"
        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"

  ###############################################################################
  # PNFD Archive Manifest                                                       #
  ###############################################################################
  '/pnf_descriptors/{pnfdInfoId}/manifest':
    #ETSI GS NFV-SOL 005 V2.4.1 location: 5.4.7b
    parameters:
      - name: pnfdInfoId
        description: >
          Identifier of the individual PNF descriptor.
          This identifier can be retrieved from the resource referenced
          by the "Location" HTTP header in the response to a POST request
          creating a new PNF descriptor resource. It can also be retrieved
          from the "id" attribute in the payload body of that response.
        in: path
        required: true
        type: string
      - name: Authorization
        description: >
          The authorization token for the request.
          Reference: IETF RFC 7235
        in: header
        required: false
        type: string
      - name: Version
        description: >
          Version of the API requested to use when responding to this request.
        in: header
        required: true
        type: string

    get:
      description: >
        The GET method reads the content of the manifest file within a PNFD archive.
        This method shall follow the provisions specified in the Tables 5.4.7b.3.2-1
        and 5.4.7b.3.2-2 for URI query parameters, request and response data structures,
        and response codes.
      parameters:
        - name: Accept
          description: >
            Content-Types that are acceptable for the response.
          in: header
          required: true
          type: string
          enum:
            - text/plain
            - application/zip
        - name: include_signatures
          description: >
            If this parameter is provided, the NFVO shall return the manifest
            and related security information (signature and certificate) either
            in a single text file if the signature and certificate are included
            in the manifest file, or in a zip file containing the manifest and
            the certificate file, if this is provided as a separate file in the
            PNFD archive.
            If this parameter is not given, the NFVO shall provide only a copy
            of the manifest file, as onboarded. If the security information is
            included in the onboarded manifest, it shall also be included in
            the returned copy.
            This URI query parameter is a flag, i.e. it shall have no value.
            The NFVO shall support this parameter.
          in: query
          required: false
          type: string
      responses:
        200:
          description: >
            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 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:
            -	a copy of the manifest file of the PNFD archive;
            -	a copy of the related individual certificate file.
          headers:
            Content-Type:
              type: string
              description: >
                The MIME type of the body of the response.This header
                field shall be present if the response has a non-empty message
                body.
              enum:
                - text/plain
                - application/zip
            WWW-Authenticate:
              type: string
              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.
              maximum: 1
              minimum: 0
            Version:
              description: >
                Version of the API used in the response.
              type: string
              maximum: 1
              minimum: 1
        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"
        409:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/409"
        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"

  ###############################################################################
  # Individual PNFD Archive Artifact                                            #
  ###############################################################################
  '/pnf_descriptors/{pnfdInfoId}/artifacts/{artifactPath}':
    #ETSI GS NFV-SOL 005 V3.3.1 location: 5.4.7c
    parameters:
      - name: pnfdInfoId
        description: >
          Identifier of the individual PNF descriptor.
          This identifier can be retrieved from the resource referenced
          by the "Location" HTTP header in the response to a POST request
          creating a new PNF descriptor resource. It can also be retrieved
          from the "id" attribute in the payload body of that response.
        in: path
        required: true
        type: string
      - name: artifactPath
        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.
        in: path
        required: true
        type: string
      - name: Authorization
        description: >
          The authorization token for the request.
          Reference: IETF RFC 7235.
        in: header
        required: false
        type: string
      - name: Version
        description: >
          Version of the API requested to use when responding to this request.
        in: header
        required: true
        type: string
    get:
      description: >
        The GET method fetches the content of an individual artifact within a PNFD archive.

        This method shall follow the provisions specified in the Tables 5.4.7c.3.2-1 and 
        5.4.7c.3.2-2 for URI query parameters, request and response data structures, and 
        response codes.
      parameters:
        - name : Range
          description: >
            The request may contain a "Range" HTTP header to obtain single
            range of bytes from an artifact file. This can be used to continue
            an aborted transmission.

            If the Range header is present in the request and the NFVO does
            not support responding to range requests with a 206 response, it
            shall return a 200 OK response instead.
          in: header
          required: false
          type: string
        - name : include_signatures
          description: >
            If this parameter is provided, the NFVO shall return the artifact 
            and related security information (such as signature and optional 
            certificate) in a ZIP archive.
            
            If this parameter is not given, the NFVO shall provide only a copy 
            of the artifact file. This URI query parameter is a flag, i.e. 
            it shall have no value.
            
            The NFVO shall support this parameter.
          in: query
          required: false
          type: string
      responses:
        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 PNFD archive, as defined 
            by ETSI GS NFV-SOL 004, 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/octetstream". 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 004
            - 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 response.
              type: string
              maximum: 1
              minimum: 1
            WWW-Authenticate:
              type: string
              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.
              maximum: 1
              minimum: 0
            Version:
              description: >
                Version of the API used in the response.
              type: string
              maximum: 1
              minimum: 1
        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 PNFD archive, 
            as defined by ETSI GS NFV-SOL 004. 
            
            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 response.
              type: string
              maximum: 1
              minimum: 1
            WWW-Authenticate:
              type: string
              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.
              maximum: 1
              minimum: 0
            Version:
              description: >
                Version of the API used in the response.
              type: string
              maximum: 1
              minimum: 1
        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"
        406:
          # description: >
          #   If the related request contained an "Accept" header not compatible with the Content type
          #   "application/zip" but the "include_signatures" flag was provided, the NFVO shall respond 
          #   with this response code.

          #   The "ProblemDetails" structure may be included with the "detail" attribute providing more 
          #   information about the error.
          $ref: "../responses/SOL005_resp.yaml#/components/responses/405"
        405:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/406"
        409:
          # description: >
          #   Shall be returned upon the following error: The operation cannot be executed currently, 
          #   due to a conflict with the state of the resource. 

          #   Typically, this is due to the fact that "pnfdOnboardingState" has a value different from
          #   "ONBOARDED".

          #   The response body shall contain a ProblemDetails structure, in which the "detail" attribute 
          #   shall convey more information about the error.
          $ref: "../responses/SOL005_resp.yaml#/components/responses/409"
        416:
          # description: >
          #   The byte range passed in the "Range" header did not match any available byte range in the 
          #   artifact file (e.g. "access after end of file").

          #   The response body may contain a ProblemDetails structure.
          $ref: "../responses/SOL005_resp.yaml#/components/responses/416"
        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"
    

  ###############################################################################
  # Subscriptions                                                               #
  ###############################################################################
  '/subscriptions':
    #ETSI GS NFV-SOL 005 V2.4.1 location: 5.4.8
    parameters:
      - name: Authorization
        description: >
          The authorization token for the request.
          Reference: IETF RFC 7235.
        in: header
        required: false
        type: string
      - name: Version
        description: >
          Version of the API requested to use when responding to this request.
        in: header
        required: true
        type: string

    post:
      summary: Subscribe to NSD and PNFD change notifications.
      description: >
        The POST method creates a new subscription.
        This method shall support the URI query parameters, request and
        response data structures, and response codes, as specified in
        the Tables 5.4.8.3.1-1 and 5.4.8.3.1-2.
        Creation of two subscription resources with the same callback URI
        and the same filter can result in performance degradation and will
        provide duplicates of notifications to the OSS, and might make
        sense only in very rare use cases. Consequently, the NFVO may
        either allow creating a subscription resource if another subscription
        resource with the same filter and callback URI already exists (in which
        case it shall return the "201 Created" response code), or may decide to
        not create a duplicate subscription resource (in which case it shall
        return a "303 See Other" response code referencing the existing
        subscription resource with the same filter and callbackUricallback URI).
      parameters:
        - name: Accept
          description: >
            Content-Types that are acceptable for the response.
            Reference: IETF RFC 7231.
          in: header
          required: true
          type: string
        - name: Content-Type
          description: >
            The MIME type of the body of the request.
            Reference: IETF RFC 7231.
          in: header
          required: true
          type: string
        - name: NsdmSubscriptionRequest
          in: body
          required: true
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdmSubscriptionRequest"
            description: >
              Details of the subscription to be created, as defined in clause 5.5.2.7.
      responses:
        201:
          description: >
            201 CREATED

            Shall be returned when the subscription has been created successfully.
            A representation of the created "Individual subscription" resource shall
            be returned in the response body, as defined in clause 5.5.2.8.
            The HTTP response shall include a "Location:" HTTP header that points
            to the created "Individual subscription" resource.
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdmSubscription"
          headers:
            Content-Type:
              type: string
              description: >
                The MIME type of the body of the response.This header
                field shall be present if the response has a non-empty message
                body.
            WWW-Authenticate:
              type: string
              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.
              maximum: 1
              minimum: 0
            Version:
              description: >
                Version of the API used in the response.
              type: string
              maximum: 1
              minimum: 1
        303:
          #  description: >
          #    303 SEE OTHER

          #    Shall be returned when a subscription with the
          #    same callbackURI and the same filter already
          #    exits and the policy of the NFVO is to not create
          #    redundant subscriptions.
          #    The HTTP response shall include a "Location"
          #    HTTP header that contains the resource URI of
          #    the existing subscription resource.
          #    The response body shall be empty.
          $ref: "../responses/SOL005_resp.yaml#/components/responses/303"
        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"
        422:
          $ref: "../responses/SOL005_resp.yaml#/components/responses/422"
        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"

    get:
      summary: Query multiple subscriptions.
      description: >
        TThe GET method queries the list of active subscriptions of the
        functional block that invokes the method. It can be used e.g.
        for resynchronization after error situations.
        This method shall support the URI query parameters, request and
        response data structures, and response codes, as specified in
        the Tables 5.4.8.3.2-1 and 5.4.8.3.2-2.
      parameters:
        - name: filter
          in: query
          required: false
          type: string
          description: >
            AAttribute filtering expression according to clause 5.2 of ETSI GS NFV SOL 013.
            The NFVO shall support receiving this parameter as part of the URI query string.
            the OSS/BSS may supply this parameter.
            All attribute names that appear in the NsdmSubscription and in data types referenced
            from it shall be supported by the NFVO in the filter expression.
        - name: nextpage_opaque_marker
          in: query
          required: false
          type: string
          description: >
            Marker to obtain the next page of a paged response. Shall be supported by
            the NFVO if the NFVO supports alternative 2 (paging) according to clause
            5.4.2.1 of ETSI GS NFV-SOL 013 for this resource.
        - name: Accept
          description: >
            Content-Types that are acceptable for the response.
            Reference: IETF RFC 7231.
          in: header
          required: true
          type: string
      responses:
        200:
          description: >
            200 OK

            Shall be returned when the list of subscriptions has been queried successfully.
            The response body shall contain in an array the representations of all active
            subscriptions of the functional block that invokes the method, i.e. zero or more
            representations of NSD management subscriptions as defined in clause 5.5.2.8.
            If the "filter" URI parameter was supplied in the request, the data in the
            response body shall have been transformed according to the rules specified in
            clause 5.2.2 of ETSI GS NFV-SOL 013.
            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 response.
              type: string
              maximum: 1
              minimum: 1
            WWW-Authenticate:
              type: string
              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.
              maximum: 1
              minimum: 0
            Version:
              description: >
                Version of the API used in the response.
              type: string
              maximum: 1
              minimum: 1
            Link:
              description: >
                Reference to other resources. Used for paging in the present document, see clause 4.7.2.1.
              type: string
              maximum: 1
              minimum: 0
          schema:
            description: >
              The list of subscriptions was queried successfully.
              The response body shall contain in an array the representations of all active subscriptions
              of the functional block that invokes the method, i.e., zero or more representations of NSD management
              subscriptions as defined in clause 5.5.2.8.
              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/NsdmSubscription"
        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"

  ###############################################################################
  # Individual Subscription                                                     #
  ###############################################################################
  '/subscriptions/{subscriptionId}':
    #ETSI GS NFV-SOL 005 V2.4.1 location: 5.4.9    
    parameters:
      - name: subscriptionId
        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.
        in: path
        required: true
        type: string
      - name: Authorization
        in: header
        required: false
        type: string
        description: >
          The authorization token for the request. Details are specified
          in clause 4.5.3 of GS NFV-SOL 005.
      - name: Version
        description: >
          Version of the API requested to use when responding to this request.
        in: header
        required: true
        type: string

    get:
      summary: Read an individual subscription resource.
      description: >
        This resource represents an individual subscription. 
        It can be used by the client to read and to terminate a subscription to
        notifications related to NSD management.

        The GET method retrieves information about a subscription by reading
        an individual subscription resource. 
        This resource represents an individual subscription. 
        It can be used by the client to read and to terminate a subscription to
        notifications related to NSD management.
      parameters:
        - name: Accept
          in: header
          required: true
          type: string
          description: >
            Content-Types that are acceptable for the response. This header
            field shall be present if the response is expected to have a non-empty
            message body.
      responses:
        200:
          description: >
            200 OK

            Shall be returned when information about an individual subscription has been read successfully.
            The response body shall contain a representation of the subscription resource.
          schema:
            $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdmSubscription"
          headers:
            Content-Type:
              type: string
              description: >
                The MIME type of the body of the response. This header
                field shall be present if the response has a non-empty message body.
            WWW-Authenticate:
              type: string
              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.
              maximum: 1
              minimum: 0
            Version:
              description: >
                Version of the API used in the response.
              type: string
              maximum: 1
              minimum: 1
        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:
      summary: Terminate Subscription
      description: >
        This resource represents an individual subscription. 
        It can be used by the client to read and to terminate a subscription to
        notifications related to NSD management.

        The DELETE method terminates an individual subscription.
        This method shall support the URI query parameters, request and 
        response data structures, and response codes, as
        specified in the Table 5.4.9.3.3-2.      
      parameters:
        - name: Authorization
          in: header
          required: false
          type: string
          description: >
            The authorization token for the request.
            Details are specified in clause 4.5.3 of GS NFV-SOL 005.
        - name: Version
          description: >
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          type: string
      responses:
        204:
          description: >
            204 NO CONTENT

            Shall be returned when the "Individual subscription" resource
            has been deleted successfully.
            The response body shall be empty.
          headers:
            WWW-Authenticate:
              type: string
              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.
              maximum: 1
              minimum: 0
            Version:
              description: >
                Version of the API used in the response.
              type: string
              maximum: 1
              minimum: 1
        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"