openapi: 3.0.2
info:
  title: SOL002 - VNF Lifecycle Management Notification interface
  description: |
    SOL002 - VNF Lifecycle Management Notification interface

    IMPORTANT: Please note that this file might be not aligned to the current
    version of the ETSI Group Specification it refers to. In case of
    discrepancies the published ETSI Group Specification takes precedence.

    Please report bugs to https://forge.etsi.org/rep/nfv/SOL002-SOL003/issues
  contact:
    name: NFV-SOL WG
  license:
    name: ETSI Forge copyright notice
    url: 'https://forge.etsi.org/etsi-forge-copyright-notice.txt'
  version: '2.14.0-impl:etsi.org:ETSI_NFV_OpenAPI:1'
externalDocs:
  description: ETSI GS NFV-SOL 002 V5.2.1
  url: >-
    https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/05.02.01_60/gs_NFV-SOL002v050201p.pdf
servers:
  - url: 'http://127.0.0.1/callback/v2'
  - url: 'https://127.0.0.1/callback/v2'
paths:
  /URI_is_provided_by_the_client_when_creating_the_subscription-VnfLcmOperationOccurrenceNotification:
    parameters:
      - name: Version
        description: |
          Version of the API requested to use when responding to this request.
        in: header
        required: true
        schema:
          type: string
      - name: Authorization
        description: |
          The authorization token for the request. Reference: IETF RFC 7235.
        in: header
        required: false
        schema:
          type: string
    get:
      description: >
        The GET method allows the server to test the notification endpoint that
        is provided by the API consumer,

        e.g. during subscription. See clause 5.4.20.3.2.
      responses:
        '204':
          $ref: '#/components/responses/VNFLCMNotification.Get.204'
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the message
            content contains a syntactically incorrect data structure), the API
            producer shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
    post:
      description: >
        The POST method delivers a notification from the API producer to an API
        consumer. The API consumer shall have

        previously created an "Individual subscription" resource with a matching
        filter. See clause 5.4.20.3.1.
      parameters:
        - name: Content-Type
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          in: header
          required: true
          schema:
            type: string
      requestBody:
        $ref: '#/components/requestBodies/VnfLcmOperationOccurrenceNotification'
      responses:
        '204':
          $ref: '#/components/responses/VNFLCMNotification.Post.204'
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the message
            content contains a syntactically incorrect data structure), the API
            producer shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
  /URI_is_provided_by_the_client_when_creating_the_subscription-VnfIdentifierCreationNotification:
    parameters:
      - name: Version
        description: |
          Version of the API requested to use when responding to this request.
        in: header
        required: true
        schema:
          type: string
      - name: Authorization
        description: |
          The authorization token for the request. Reference: IETF RFC 7235.
        in: header
        required: false
        schema:
          type: string
    get:
      description: >
        The GET method allows the server to test the notification endpoint that
        is provided by the API consumer,

        e.g. during subscription. See clause 5.4.20.3.2.
      responses:
        '204':
          $ref: '#/components/responses/VNFLCMNotification.Get.204'
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the message
            content contains a syntactically incorrect data structure), the API
            producer shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
    post:
      description: >
        The POST method delivers a notification from the API producer to an API
        consumer. The API consumer shall have

        previously created an "Individual subscription" resource with a matching
        filter. See clause 5.4.20.3.1.
      parameters:
        - name: Content-Type
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          in: header
          required: true
          schema:
            type: string
      requestBody:
        $ref: '#/components/requestBodies/VnfIdentifierCreationNotification'
      responses:
        '204':
          $ref: '#/components/responses/VNFLCMNotification.Post.204'
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the message
            content contains a syntactically incorrect data structure), the API
            producer shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
  /URI_is_provided_by_the_client_when_creating_the_subscription-VnfIdentifierDeletionNotification:
    parameters:
      - name: Version
        description: |
          Version of the API requested to use when responding to this request.
        in: header
        required: true
        schema:
          type: string
      - name: Authorization
        description: |
          The authorization token for the request. Reference: IETF RFC 7235.
        in: header
        required: false
        schema:
          type: string
    get:
      description: >
        The GET method allows the server to test the notification endpoint that
        is provided by the API consumer,

        e.g. during subscription. See clause 5.4.20.3.2.
      responses:
        '204':
          $ref: '#/components/responses/VNFLCMNotification.Get.204'
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the message
            content contains a syntactically incorrect data structure), the API
            producer shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
    post:
      description: >
        The POST method delivers a notification from the API producer to an API
        consumer. The API consumer shall have

        previously created an "Individual subscription" resource with a matching
        filter. See clause 5.4.20.3.1.
      parameters:
        - name: Content-Type
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          in: header
          required: true
          schema:
            type: string
      requestBody:
        $ref: '#/components/requestBodies/VnfIdentifierDeletionNotification'
      responses:
        '204':
          $ref: '#/components/responses/VNFLCMNotification.Post.204'
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the message
            content contains a syntactically incorrect data structure), the API
            producer shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            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.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
components:
  requestBodies:
    VnfLcmOperationOccurrenceNotification:
      description: >
        A notification about lifecycle changes triggered by a VNF LCM operation
        occurrence.
      content:
        application/json:
          schema:
            description: "This type represents a VNF lifecycle management operation occurrence notification, which informs the receiver of changes in the VNF lifecycle caused by a VNF LCM operation occurrence. The support of the notification is mandatory. This notification shall be triggered by the VNFM when there is a change in the VNF lifecycle caused by a VNF LCM operation occurrence, including: * Instantiation of the VNF * Scaling of the VNF instance (including auto-scaling) * Healing of the VNF instance (including auto-healing) * Change of the state of the VNF instance (i.e. Operate VNF) * Change of the deployment flavour of the VNF instance * Change of the external connectivity of the VNF instance * Selection of deployable modules of the VNF instance * Termination of the VNF instance * Modification of VNF instance information and/or VNF configurable\n  properties through the \"PATCH\" method on the \"Individual VNF instance\"\n  resource.\nIf this is the initial notification about the start of a VNF LCM operation occurrence, it is assumed that the notification is sent by the VNFM before any action (including sending the grant request) is taken as part of the LCM operation. Due to possible race conditions, the \"start\" notification, the grant request and the LCM operation acknowledgment can arrive in any order at the NFVO, and the NFVO shall be able to handle such a situation. If this is a notification about a final or intermediate result state of a VNF LCM operation occurrence, the notification shall be sent after all related actions of the LCM operation that led to this state have been executed.  The new state shall be set in the \"Individual VNF LCM operation occurrence\"  resource before the notification about the state change is sent. * NOTE 1:\tShall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set\n          to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise.\n          This attribute contains information about the cumulative changes to virtualised resources that\n          were performed so far by the VNF LCM operation occurrence and by any of the error handling\n          procedures for that operation occurrence.\n  NOTE 2:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" entries as needed\n          for signalling the different types of changes, i.e. one per virtual link and change type.\n          For instance, in the case of signaling affected VL instances involving the addition of a particular\n          VL instance with links ports, one \"AffectedVirtualLink\" entry signals the addition of the VL by using\n          the \"changeType\" attribute of \"AffectedVirtualLink\" structure equal to \"ADDED\", and another\n          \"AffectedVirtualLink\" entry signals the addition of VNF link ports of the VL by using the\n          \"changeType\" equal to \"LINK_PORT_ADDED\".\n  NOTE 3: Not more than one of changedInfo and modificationsTriggeredByVnfPkgChange shall be present.\n"
            type: object
            required:
              - id
              - notificationType
              - subscriptionId
              - timeStamp
              - notificationStatus
              - operationState
              - vnfInstanceId
              - operation
              - isAutomaticInvocation
              - vnfLcmOpOccId
              - _links
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              notificationType:
                description: >
                  Discriminator for the different notification types. Shall be
                  set to "VnfLcmOperationOccurrenceNotification" for this
                  notification type.
                type: string
                enum:
                  - VnfLcmOperationOccurrenceNotification
              subscriptionId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              timeStamp:
                description: >
                  Date-time stamp. Representation: String formatted according to
                  IETF RFC 3339.
                type: string
                format: date-time
              notificationStatus:
                description: >
                  Indicates whether this notification reports about the start of
                  a lifecycle operation or the result of a lifecycle operation.
                  Permitted values: * START: Informs about the start of the VNF
                  LCM operation
                    occurrence.
                  * RESULT: Informs about the final or intermediate result of
                  the VNF
                    LCM operation occurrence.
                type: string
                enum:
                  - START
                  - RESULT
              operationState:
                description: >
                  STARTING: The LCM operation is starting. PROCESSING: The LCM
                  operation is currently in execution. COMPLETED: The LCM
                  operation has been completed successfully. FAILED_TEMP: The
                  LCM operation has failed and execution has stopped, but the
                  execution of the operation is not considered to be closed.
                  FAILED: The LCM operation has failed and it cannot be retried
                  or rolled back, as it is determined that such action won't
                  succeed. ROLLING_BACK: The LCM operation is currently being
                  rolled back. ROLLED_BACK: The LCM operation has been
                  successfully rolled back, i.e. The state of the VNF prior to
                  the original operation invocation has been restored as closely
                  as possible.
                type: string
                enum:
                  - STARTING
                  - PROCESSING
                  - COMPLETED
                  - FAILED_TEMP
                  - FAILED
                  - ROLLING_BACK
                  - ROLLED_BACK
              vnfInstanceId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              operation:
                description: >
                  The enumeration LcmOpType defines the permitted values to
                  represent  VNF lifecycle operation types in VNF lifecycle
                  management operation  occurrence resources and VNF lifecycle
                  management operation occurrence  notifications.

                  Value | Description ------|------------ INSTANTIATE |
                  Represents the "Instantiate VNF" LCM operation.    SCALE |
                  Represents the "Scale VNF" LCM operation. SCALE_TO_LEVEL |
                  Represents the "Scale VNF to Level" LCM operation.
                  CHANGE_FLAVOUR | Represents the "Change VNF Flavour" LCM
                  operation. TERMINATE | Represents the "Terminate VNF" LCM
                  operation. HEAL | Represents the "Heal VNF" LCM operation.
                  OPERATE | Represents the "Operate VNF" LCM operation.
                  CHANGE_EXT_CONN | Represents the "Change external VNF
                  connectivity" LCM operation. MODIFY_INFO | Represents the
                  "Modify VNF Information" LCM operation. CREATE_SNAPSHOT |
                  Represents the "Create VNF Snapshot" LCM operation.
                  REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot"
                  LCM operation. CHANGE_VNFPKG | Represents the "Change current
                  VNF package" LCM operation. SELECT_DEPL_MODS  | Represents the
                  "Select VNF deployable modules" LCM operation 
                type: string
                enum:
                  - INSTANTIATE
                  - SCALE
                  - SCALE_TO_LEVEL
                  - CHANGE_FLAVOUR
                  - TERMINATE
                  - HEAL
                  - OPERATE
                  - CHANGE_EXT_CONN
                  - MODIFY_INFO
                  - CREATE_SNAPSHOT
                  - REVERT_TO_SNAPSHOT
                  - CHANGE_VNFPKG
                  - SELECT_DEPL_MODS
              isAutomaticInvocation:
                description: >
                  Set to true if this VNF LCM operation occurrence has been
                  triggered by an automated procedure inside the VNFM (i.e.
                  ScaleVnf / ScaleVnfToLevel triggered by auto-scale, or HealVnf
                  triggered by auto-heal). Set to false otherwise.
                type: boolean
              verbosity:
                description: >
                  The enumeration LcmOpOccNotificationVerbosityType provides
                  values to control the verbosity of LCM operation occurrence
                  notifications. * FULL: This signals a full notification which
                  contains all change details. * SHORT:  This signals a short
                  notification which omits large-volume change details to reduce
                  the size of data to
                            be sent via the notification mechanism.
                type: string
                enum:
                  - FULL
                  - SHORT
              vnfLcmOpOccId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              affectedVnfcs:
                description: >
                  Information about VNFC instances that were affected during the
                  lifecycle operation. See note 1.
                type: array
                items:
                  description: >
                    This type provides information about added, deleted,
                    modified and temporary VNFCs.
                  type: object
                  required:
                    - id
                    - vduId
                    - changeType
                    - computeResource
                  properties:
                    id:
                      description: >
                        An identifier that is unique for the respective type
                        within a VNF instance, but may not be globally unique.
                      type: string
                    vduId:
                      description: |
                        An identifier that is unique within a VNF descriptor.
                      type: string
                    vnfdId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    changeType:
                      description: >
                        Signals the type of change. Permitted values: * ADDED *
                        REMOVED * MODIFIED * TEMPORARY For a temporary resource,
                        an AffectedVnfc structure exists as long as the
                        temporary resource exists.
                      type: string
                      enum:
                        - ADDED
                        - REMOVED
                        - MODIFIED
                        - TEMPORARY
                    computeResource:
                      required:
                        - resourceId
                      type: object
                      description: >
                        This type represents the information that allows
                        addressing a virtualised resource that is used by a VNF
                        instance. Information about the resource is available
                        from the VIM.

                        * NOTE 1: The information about the VIM or CISM
                        connection referenced by the VIM connection id is known
                        to the
                                  VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.

                        * NOTE 2: The value set of the "vimLevelResourceType"
                        attribute is within the scope of the VIM or CISM or the
                        resource 
                                  provider and can be used as information that complements the ResourceHandle. When the container
                                  infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would 
                                  correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, 
                                  PersistentVolumeClaim, NetworkAttachmentDefinition.

                        * NOTE 3: When the container infrastructure service is a
                        Kubernetes® instance the resourceId shall be populated
                        in the 
                                  following way:
                                  - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide 
                                  per resource type.
                                  - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, 
                                  i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by 
                                  Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own 
                                  manifest.
                                  - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of 
                                  the 'metadata.name' field in Kubernetes® manifest.
                      properties:
                        vimConnectionId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        resourceProviderId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        resourceId:
                          description: >
                            An identifier maintained by the VIM  or the CISM or
                            other resource provider. It is expected to be unique
                            within the VIM instance.
                          type: string
                        vimLevelResourceType:
                          description: >
                            Type of the resource in the scope of the VIM or the
                            CISM or the resource provider. See note 2.
                          type: string
                        vimLevelAdditionalResourceInfo:
                          description: >
                            This type represents additional resource information
                            which resource and resource type specific, and which
                            is available from the VIM or the CISM or the
                            resource provider.

                            * NOTE: At least one attribute shall be present.
                          type: object
                          properties:
                            hostName:
                              description: >
                                Name of the host where the resource is
                                allocated. It shall be present for compute
                                resources in the scope of the CISM and shall be
                                absent otherwise. See note.
                              type: string
                            persistentVolume:
                              description: >
                                Name of the persistent volume to which the
                                persistent volume claim representing the storage
                                resource is bound. It may be present for storage
                                resources in the scope of the CISM and shall be
                                absent otherwise. See note.
                              type: string
                            additionalInfo:
                              description: >
                                This type represents a list of key-value pairs.
                                The order of the pairs in the list is not
                                significant. In JSON, a set of keyvalue pairs is
                                represented as an object. It shall comply with
                                the provisions defined in clause 4 of IETF RFC
                                8259. In the following example, a list of
                                key-value pairs with four keys ("aString",
                                "aNumber", "anArray" and "anObject") is provided
                                to illustrate that the values associated with
                                different keys can be of different type.
                              type: object
                        containerNamespace:
                          description: >
                            The value of the namespace in which the MCIO
                            corresponding to the resource is deployed. This
                            attribute shall be present if the resource is
                            managed by a CISM and it shall be absent otherwise.
                          type: string
                    metadata:
                      description: >
                        This type represents a list of key-value pairs. The
                        order of the pairs in the list is not significant. In
                        JSON, a set of keyvalue pairs is represented as an
                        object. It shall comply with the provisions defined in
                        clause 4 of IETF RFC 8259. In the following example, a
                        list of key-value pairs with four keys ("aString",
                        "aNumber", "anArray" and "anObject") is provided to
                        illustrate that the values associated with different
                        keys can be of different type.
                      type: object
                    affectedVnfcCpIds:
                      description: >
                        Identifiers of CP(s) of the VNFC instance that were
                        affected by the change. Shall be present for those
                        affected CPs of the VNFC instance that are associated to
                        an external CP of the VNF instance. May be present for
                        further affected CPs of the VNFC instance.
                      type: array
                      items:
                        description: >
                          An identifier that is unique for the respective type
                          within a VNF instance, but may not be globally unique.
                        type: string
                    addedStorageResourceIds:
                      description: >
                        References to VirtualStorage resources that have been
                        added. Each value refers to a VirtualStorageResourceInfo
                        item in the VnfInstance that was added to the VNFC. It
                        shall be provided if at least one storage resource was
                        added to the VNFC.
                      type: array
                      items:
                        description: >
                          An identifier that is unique for the respective type
                          within a VNF instance, but may not be globally unique.
                        type: string
                    removedStorageResourceIds:
                      description: >
                        References to VirtualStorage resources that have been
                        removed. The value contains the identifier of a
                        VirtualStorageResourceInfo item that has been removed
                        from the VNFC, and might no longer exist in the
                        VnfInstance. It shall be provided if at least one
                        storage resource was removed from the VNFC.
                      type: array
                      items:
                        description: >
                          An identifier that is unique for the respective type
                          within a VNF instance, but may not be globally unique.
                        type: string
              affectedVirtualLinks:
                description: >
                  Information about VL instances that were affected during the
                  lifecycle operation. See note 1 and note 2.
                type: array
                items:
                  description: "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\nNOTE:\tWhen signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, \n      the \"networkResource\" attribute refers to the affected virtual link instance, not the link port \n      instance. The resource handles of the affected VNF link ports can be found by dereferencing the \n      identifiers in the \"vnfLinkPortIds\" attribute.\n"
                  type: object
                  required:
                    - id
                    - vnfVirtualLinkDescId
                    - changeType
                    - networkResource
                  properties:
                    id:
                      description: >
                        An identifier that is unique for the respective type
                        within a VNF instance, but may not be globally unique.
                      type: string
                    vnfVirtualLinkDescId:
                      description: |
                        An identifier that is unique within a VNF descriptor.
                      type: string
                    vnfdId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    changeType:
                      description: >
                        Signals the type of change. Permitted values: * ADDED *
                        REMOVED * MODIFIED * TEMPORARY * LINK_PORT_ADDED *
                        LINK_PORT_REMOVED For a temporary resource, an
                        AffectedVirtualLink structure exists as long as the
                        temporary resource exists. When signalling the addition
                        (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF
                        link ports, the "networkResource" attribute refers to
                        the affected virtual link instance, not the link port
                        instance. The resource handles of the affected VNF link
                        ports can be found by dereferencing the identifiers in
                        the "vnfLinkPortIds" attribute.
                      type: string
                      enum:
                        - ADDED
                        - REMOVED
                        - MODIFIED
                        - TEMPORARY
                        - LINK_PORT_ADDED
                        - LINK_PORT_REMOVED
                    networkResource:
                      required:
                        - resourceId
                      type: object
                      description: >
                        This type represents the information that allows
                        addressing a virtualised resource that is used by a VNF
                        instance. Information about the resource is available
                        from the VIM.

                        * NOTE 1: The information about the VIM or CISM
                        connection referenced by the VIM connection id is known
                        to the
                                  VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.

                        * NOTE 2: The value set of the "vimLevelResourceType"
                        attribute is within the scope of the VIM or CISM or the
                        resource 
                                  provider and can be used as information that complements the ResourceHandle. When the container
                                  infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would 
                                  correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, 
                                  PersistentVolumeClaim, NetworkAttachmentDefinition.

                        * NOTE 3: When the container infrastructure service is a
                        Kubernetes® instance the resourceId shall be populated
                        in the 
                                  following way:
                                  - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide 
                                  per resource type.
                                  - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, 
                                  i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by 
                                  Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own 
                                  manifest.
                                  - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of 
                                  the 'metadata.name' field in Kubernetes® manifest.
                      properties:
                        vimConnectionId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        resourceProviderId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        resourceId:
                          description: >
                            An identifier maintained by the VIM  or the CISM or
                            other resource provider. It is expected to be unique
                            within the VIM instance.
                          type: string
                        vimLevelResourceType:
                          description: >
                            Type of the resource in the scope of the VIM or the
                            CISM or the resource provider. See note 2.
                          type: string
                        vimLevelAdditionalResourceInfo:
                          description: >
                            This type represents additional resource information
                            which resource and resource type specific, and which
                            is available from the VIM or the CISM or the
                            resource provider.

                            * NOTE: At least one attribute shall be present.
                          type: object
                          properties:
                            hostName:
                              description: >
                                Name of the host where the resource is
                                allocated. It shall be present for compute
                                resources in the scope of the CISM and shall be
                                absent otherwise. See note.
                              type: string
                            persistentVolume:
                              description: >
                                Name of the persistent volume to which the
                                persistent volume claim representing the storage
                                resource is bound. It may be present for storage
                                resources in the scope of the CISM and shall be
                                absent otherwise. See note.
                              type: string
                            additionalInfo:
                              description: >
                                This type represents a list of key-value pairs.
                                The order of the pairs in the list is not
                                significant. In JSON, a set of keyvalue pairs is
                                represented as an object. It shall comply with
                                the provisions defined in clause 4 of IETF RFC
                                8259. In the following example, a list of
                                key-value pairs with four keys ("aString",
                                "aNumber", "anArray" and "anObject") is provided
                                to illustrate that the values associated with
                                different keys can be of different type.
                              type: object
                        containerNamespace:
                          description: >
                            The value of the namespace in which the MCIO
                            corresponding to the resource is deployed. This
                            attribute shall be present if the resource is
                            managed by a CISM and it shall be absent otherwise.
                          type: string
                    vnfLinkPortIds:
                      description: >
                        Identifiers of the link ports of the affected VL related
                        to the change. Each identifier references a 
                        "VnfLinkPortInfo" structure.

                        Shall be set when changeType is equal to
                        "LINK_PORT_ADDED" or "LINK_PORT_REMOVED", and the
                        related  "VnfLinkPortInfo" structures are present (case
                        "added") or have been present (case "removed") in the 
                        "VnfVirtualLinkResourceInfo" or
                        "ExtManagedVirtualLinkInfo" structures that are
                        represented by the  "vnfVirtualLinkResourceInfo" or
                        "extManagedVirtualLinkInfo" attribute in the
                        "VnfInstance" structure.  See note.
                      type: array
                      items:
                        description: |
                          An identifier that is unique within a VNF descriptor.
                        type: string
                    metadata:
                      description: >
                        This type represents a list of key-value pairs. The
                        order of the pairs in the list is not significant. In
                        JSON, a set of keyvalue pairs is represented as an
                        object. It shall comply with the provisions defined in
                        clause 4 of IETF RFC 8259. In the following example, a
                        list of key-value pairs with four keys ("aString",
                        "aNumber", "anArray" and "anObject") is provided to
                        illustrate that the values associated with different
                        keys can be of different type.
                      type: object
              affectedExtLinkPorts:
                description: >
                  Information about external VNF link ports that were affected
                  during the lifecycle operation. See note 1.
                type: array
                items:
                  description: >
                    This type provides information about added and deleted
                    external link ports (link ports attached to external virtual
                    links).
                  type: object
                  required:
                    - id
                    - changeType
                    - extCpInstanceId
                    - resourceHandle
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    changeType:
                      description: "Signals the type of change. Permitted values: -\tADDED - MODIFIED -\tREMOVED\n"
                      type: string
                      enum:
                        - ADDED
                        - MODIFIED
                        - REMOVED
                    extCpInstanceId:
                      description: >
                        An identifier that is unique for the respective type
                        within a VNF instance, but may not be globally unique.
                      type: string
                    resourceHandle:
                      required:
                        - resourceId
                      type: object
                      description: >
                        This type represents the information that allows
                        addressing a virtualised resource that is used by a VNF
                        instance. Information about the resource is available
                        from the VIM.

                        * NOTE 1: The information about the VIM or CISM
                        connection referenced by the VIM connection id is known
                        to the
                                  VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.

                        * NOTE 2: The value set of the "vimLevelResourceType"
                        attribute is within the scope of the VIM or CISM or the
                        resource 
                                  provider and can be used as information that complements the ResourceHandle. When the container
                                  infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would 
                                  correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, 
                                  PersistentVolumeClaim, NetworkAttachmentDefinition.

                        * NOTE 3: When the container infrastructure service is a
                        Kubernetes® instance the resourceId shall be populated
                        in the 
                                  following way:
                                  - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide 
                                  per resource type.
                                  - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, 
                                  i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by 
                                  Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own 
                                  manifest.
                                  - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of 
                                  the 'metadata.name' field in Kubernetes® manifest.
                      properties:
                        vimConnectionId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        resourceProviderId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        resourceId:
                          description: >
                            An identifier maintained by the VIM  or the CISM or
                            other resource provider. It is expected to be unique
                            within the VIM instance.
                          type: string
                        vimLevelResourceType:
                          description: >
                            Type of the resource in the scope of the VIM or the
                            CISM or the resource provider. See note 2.
                          type: string
                        vimLevelAdditionalResourceInfo:
                          description: >
                            This type represents additional resource information
                            which resource and resource type specific, and which
                            is available from the VIM or the CISM or the
                            resource provider.

                            * NOTE: At least one attribute shall be present.
                          type: object
                          properties:
                            hostName:
                              description: >
                                Name of the host where the resource is
                                allocated. It shall be present for compute
                                resources in the scope of the CISM and shall be
                                absent otherwise. See note.
                              type: string
                            persistentVolume:
                              description: >
                                Name of the persistent volume to which the
                                persistent volume claim representing the storage
                                resource is bound. It may be present for storage
                                resources in the scope of the CISM and shall be
                                absent otherwise. See note.
                              type: string
                            additionalInfo:
                              description: >
                                This type represents a list of key-value pairs.
                                The order of the pairs in the list is not
                                significant. In JSON, a set of keyvalue pairs is
                                represented as an object. It shall comply with
                                the provisions defined in clause 4 of IETF RFC
                                8259. In the following example, a list of
                                key-value pairs with four keys ("aString",
                                "aNumber", "anArray" and "anObject") is provided
                                to illustrate that the values associated with
                                different keys can be of different type.
                              type: object
                        containerNamespace:
                          description: >
                            The value of the namespace in which the MCIO
                            corresponding to the resource is deployed. This
                            attribute shall be present if the resource is
                            managed by a CISM and it shall be absent otherwise.
                          type: string
              affectedVirtualStorages:
                description: >
                  Information about virtualised storage instances that were
                  affected during the lifecycle operation. See note 1.
                type: array
                items:
                  description: >
                    This type provides information about added, deleted,
                    modified and temporary virtual storage resources.
                  type: object
                  required:
                    - id
                    - virtualStorageDescId
                    - changeType
                    - storageResource
                  properties:
                    id:
                      description: >
                        An identifier that is unique for the respective type
                        within a VNF instance, but may not be globally unique.
                      type: string
                    virtualStorageDescId:
                      description: |
                        An identifier that is unique within a VNF descriptor.
                      type: string
                    vnfdId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    changeType:
                      description: >
                        Signals the type of change. Permitted values: * ADDED *
                        REMOVED * MODIFIED * TEMPORARY For a temporary resource,
                        an AffectedVirtualStorage structure exists as long as
                        the temporary resource exists.
                      type: string
                      enum:
                        - ADDED
                        - REMOVED
                        - MODIFIED
                        - TEMPORARY
                    storageResource:
                      required:
                        - resourceId
                      type: object
                      description: >
                        This type represents the information that allows
                        addressing a virtualised resource that is used by a VNF
                        instance. Information about the resource is available
                        from the VIM.

                        * NOTE 1: The information about the VIM or CISM
                        connection referenced by the VIM connection id is known
                        to the
                                  VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.

                        * NOTE 2: The value set of the "vimLevelResourceType"
                        attribute is within the scope of the VIM or CISM or the
                        resource 
                                  provider and can be used as information that complements the ResourceHandle. When the container
                                  infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would 
                                  correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, 
                                  PersistentVolumeClaim, NetworkAttachmentDefinition.

                        * NOTE 3: When the container infrastructure service is a
                        Kubernetes® instance the resourceId shall be populated
                        in the 
                                  following way:
                                  - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide 
                                  per resource type.
                                  - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, 
                                  i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by 
                                  Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own 
                                  manifest.
                                  - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of 
                                  the 'metadata.name' field in Kubernetes® manifest.
                      properties:
                        vimConnectionId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        resourceProviderId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        resourceId:
                          description: >
                            An identifier maintained by the VIM  or the CISM or
                            other resource provider. It is expected to be unique
                            within the VIM instance.
                          type: string
                        vimLevelResourceType:
                          description: >
                            Type of the resource in the scope of the VIM or the
                            CISM or the resource provider. See note 2.
                          type: string
                        vimLevelAdditionalResourceInfo:
                          description: >
                            This type represents additional resource information
                            which resource and resource type specific, and which
                            is available from the VIM or the CISM or the
                            resource provider.

                            * NOTE: At least one attribute shall be present.
                          type: object
                          properties:
                            hostName:
                              description: >
                                Name of the host where the resource is
                                allocated. It shall be present for compute
                                resources in the scope of the CISM and shall be
                                absent otherwise. See note.
                              type: string
                            persistentVolume:
                              description: >
                                Name of the persistent volume to which the
                                persistent volume claim representing the storage
                                resource is bound. It may be present for storage
                                resources in the scope of the CISM and shall be
                                absent otherwise. See note.
                              type: string
                            additionalInfo:
                              description: >
                                This type represents a list of key-value pairs.
                                The order of the pairs in the list is not
                                significant. In JSON, a set of keyvalue pairs is
                                represented as an object. It shall comply with
                                the provisions defined in clause 4 of IETF RFC
                                8259. In the following example, a list of
                                key-value pairs with four keys ("aString",
                                "aNumber", "anArray" and "anObject") is provided
                                to illustrate that the values associated with
                                different keys can be of different type.
                              type: object
                        containerNamespace:
                          description: >
                            The value of the namespace in which the MCIO
                            corresponding to the resource is deployed. This
                            attribute shall be present if the resource is
                            managed by a CISM and it shall be absent otherwise.
                          type: string
                    metadata:
                      description: >
                        This type represents a list of key-value pairs. The
                        order of the pairs in the list is not significant. In
                        JSON, a set of keyvalue pairs is represented as an
                        object. It shall comply with the provisions defined in
                        clause 4 of IETF RFC 8259. In the following example, a
                        list of key-value pairs with four keys ("aString",
                        "aNumber", "anArray" and "anObject") is provided to
                        illustrate that the values associated with different
                        keys can be of different type.
                      type: object
              changedInfo:
                description: "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package. * NOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute)\n          was modified implicitly following a request to modify the \"vnfdId\" attribute, by\n          copying the value of this attribute from the VNFD in the VNF Package identified\n          by the \"vnfdId\" attribute.\n"
                type: object
                properties:
                  vnfInstanceName:
                    description: >
                      If present, this attribute signals modifications of the
                      "vnfInstanceName" attribute in "VnfInstance" as defined in
                      clause 5.5.2.12..
                    type: string
                  vnfInstanceDescription:
                    description: >
                      If present, this attribute signals modifications of the
                      "vnfInstanceDescription" attribute in "VnfInstance", as
                      defined in clause 5.5.2.12..
                    type: string
                  vnfConfigurableProperties:
                    description: >
                      This type represents a list of key-value pairs. The order
                      of the pairs in the list is not significant. In JSON, a
                      set of keyvalue pairs is represented as an object. It
                      shall comply with the provisions defined in clause 4 of
                      IETF RFC 8259. In the following example, a list of
                      key-value pairs with four keys ("aString", "aNumber",
                      "anArray" and "anObject") is provided to illustrate that
                      the values associated with different keys can be of
                      different type.
                    type: object
                  metadata:
                    description: >
                      This type represents a list of key-value pairs. The order
                      of the pairs in the list is not significant. In JSON, a
                      set of keyvalue pairs is represented as an object. It
                      shall comply with the provisions defined in clause 4 of
                      IETF RFC 8259. In the following example, a list of
                      key-value pairs with four keys ("aString", "aNumber",
                      "anArray" and "anObject") is provided to illustrate that
                      the values associated with different keys can be of
                      different type.
                    type: object
                  extensions:
                    description: >
                      This type represents a list of key-value pairs. The order
                      of the pairs in the list is not significant. In JSON, a
                      set of keyvalue pairs is represented as an object. It
                      shall comply with the provisions defined in clause 4 of
                      IETF RFC 8259. In the following example, a list of
                      key-value pairs with four keys ("aString", "aNumber",
                      "anArray" and "anObject") is provided to illustrate that
                      the values associated with different keys can be of
                      different type.
                    type: object
                  vnfdId:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  vnfProvider:
                    description: >
                      If present, this attribute signals modifications of the
                      "vnfProvider" attribute in "VnfInstance". See note.
                    type: string
                  vnfProductName:
                    description: >
                      If present, this attribute signals modifications of the
                      "vnfProductName" attribute in "VnfInstance". See note.
                    type: string
                  vnfSoftwareVersion:
                    description: |
                      A version.
                    type: string
                  vnfdVersion:
                    description: |
                      A version.
                    type: string
                  vnfcInfoModifications:
                    description: >
                      If present, this attribute signals modifications of
                      certain entries in the "vnfcInfo" attribute array in the
                      "instantiatedVnfInfo" attribute of "VnfInstance", as
                      defined in clause 5.5.2.12.
                    type: array
                    items:
                      description: "This type represents modifications of an entry in an array of \"VnfcInfo\" objects. * NOTE:\tThe attribute \"id\" in this data type represents the same identifier as the attribute\n          \"vnfcInstanceId\" in other related data types in the present document. For reasons of backward\n          compatibility, this misalignment is not corrected.\n"
                      type: object
                      required:
                        - id
                        - vnfcConfigurableProperties
                      properties:
                        id:
                          description: >
                            An identifier that is unique for the respective type
                            within a VNF instance, but may not be globally
                            unique.
                          type: string
                        vnfcConfigurableProperties:
                          description: >
                            This type represents a list of key-value pairs. The
                            order of the pairs in the list is not significant.
                            In JSON, a set of keyvalue pairs is represented as
                            an object. It shall comply with the provisions
                            defined in clause 4 of IETF RFC 8259. In the
                            following example, a list of key-value pairs with
                            four keys ("aString", "aNumber", "anArray" and
                            "anObject") is provided to illustrate that the
                            values associated with different keys can be of
                            different type.
                          type: object
              affectedVipCps:
                description: >
                  Information about virtual IP CP instances that were affected
                  during the execution of the lifecycle management operation, if
                  this notification represents the result of a lifecycle
                  management operation occurrence. Shall be present if the
                  "notificationStatus" is set to "RESULT", the "verbosity"
                  attribute is set to "FULL" and the operation has made any
                  changes to the VIP CP instances of the VNF instance. Shall be
                  absent otherwise. Only information about VIP CP instances that
                  have been added, deleted or modified shall be provided.
                type: array
                items:
                  description: >
                    This type provides information about added, deleted and
                    modified virtual IP CP instances.
                  type: object
                  required:
                    - cpInstanceId
                    - cpdId
                    - changeType
                  properties:
                    cpInstanceId:
                      description: >
                        An identifier that is unique for the respective type
                        within a VNF instance, but may not be globally unique.
                      type: string
                    cpdId:
                      description: |
                        An identifier that is unique within a VNF descriptor.
                      type: string
                    vnfdId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    changeType:
                      description: "Signals the type of change. Permitted values: -\tADDED -\tREMOVED -\tMODIFIED\n"
                      type: string
                      enum:
                        - ADDED
                        - REMOVED
                        - MODIFIED
              affectedVirtualCps:
                description: >
                  Information about virtual CP instances that were affected
                  during the execution of the  lifecycle management operation,
                  if this notification represents the result of a lifecycle 
                  management operation occurrence.

                  Shall be present if the "notificationStatus" is set to
                  "RESULT", the "verbosity" attribute is set to "FULL" and the
                  operation has made any changes to the virtual CP instances of
                  the VNF instance. Shall be absent otherwise. Only information
                  about virtual CP instances that have been added, deleted or
                  modified shall be provided.
                type: array
                items:
                  description: >
                    This type provides information about added, deleted and
                    modified virtual CP instances.
                  type: object
                  required:
                    - cpInstanceId
                    - cpdId
                    - changeType
                  properties:
                    cpInstanceId:
                      description: >
                        An identifier that is unique for the respective type
                        within a VNF instance, but may not be globally unique.
                      type: string
                    cpdId:
                      description: |
                        An identifier that is unique within a VNF descriptor.
                      type: string
                    vnfdId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    changeType:
                      description: |
                        Signals the type of change.
                        Permitted values:
                          - ADDED
                          - REMOVED
                          - MODIFIED
                      type: string
                      enum:
                        - ADDED
                        - REMOVED
                        - MODIFIED
              affectedCertificates:
                description: >
                  Information about certificate content that were affected
                  during the execution of the lifecycle management operation, if
                  this notification represents the result of a lifecycle
                  management operation occurrence. Shall be present when using
                  delegation mode, otherwise shall be absent. This attribute
                  shall be supported when delegation mode in certificate
                  management is applicable.
                type: array
                items:
                  description: >
                    This type provides input information about added, deleted
                    and modified certificate contents.
                  type: object
                  required:
                    - certificateInfoId
                    - changeType
                  properties:
                    certificateInfoId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    certificateBaseProfileId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    securityPolicyId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    cmfInfoId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    certificateContentId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    changeType:
                      description: |
                        Signals the type of change.
                      type: string
                      enum:
                        - ADD
                        - REMOVE
                        - MODIFY
              changedExtConnectivity:
                description: >
                  Information about changed external connectivity, if this
                  notification represents the result of a lifecycle operation
                  occurrence. Shall be present if the "notificationStatus" is
                  set to "RESULT" and the "operation" has made any change of the
                  external  connectivity of the VNF instance. Shall be absent
                  otherwise.
                type: array
                items:
                  description: "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n      the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n      most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n      or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n      \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n      parent data structure.\n"
                  type: object
                  required:
                    - id
                    - resourceHandle
                    - currentVnfExtCpData
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    resourceHandle:
                      required:
                        - resourceId
                      type: object
                      description: >
                        This type represents the information that allows
                        addressing a virtualised resource that is used by a VNF
                        instance. Information about the resource is available
                        from the VIM.

                        * NOTE 1: The information about the VIM or CISM
                        connection referenced by the VIM connection id is known
                        to the
                                  VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.

                        * NOTE 2: The value set of the "vimLevelResourceType"
                        attribute is within the scope of the VIM or CISM or the
                        resource 
                                  provider and can be used as information that complements the ResourceHandle. When the container
                                  infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would 
                                  correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, 
                                  PersistentVolumeClaim, NetworkAttachmentDefinition.

                        * NOTE 3: When the container infrastructure service is a
                        Kubernetes® instance the resourceId shall be populated
                        in the 
                                  following way:
                                  - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide 
                                  per resource type.
                                  - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, 
                                  i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by 
                                  Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own 
                                  manifest.
                                  - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of 
                                  the 'metadata.name' field in Kubernetes® manifest.
                      properties:
                        vimConnectionId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        resourceProviderId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        resourceId:
                          description: >
                            An identifier maintained by the VIM  or the CISM or
                            other resource provider. It is expected to be unique
                            within the VIM instance.
                          type: string
                        vimLevelResourceType:
                          description: >
                            Type of the resource in the scope of the VIM or the
                            CISM or the resource provider. See note 2.
                          type: string
                        vimLevelAdditionalResourceInfo:
                          description: >
                            This type represents additional resource information
                            which resource and resource type specific, and which
                            is available from the VIM or the CISM or the
                            resource provider.

                            * NOTE: At least one attribute shall be present.
                          type: object
                          properties:
                            hostName:
                              description: >
                                Name of the host where the resource is
                                allocated. It shall be present for compute
                                resources in the scope of the CISM and shall be
                                absent otherwise. See note.
                              type: string
                            persistentVolume:
                              description: >
                                Name of the persistent volume to which the
                                persistent volume claim representing the storage
                                resource is bound. It may be present for storage
                                resources in the scope of the CISM and shall be
                                absent otherwise. See note.
                              type: string
                            additionalInfo:
                              description: >
                                This type represents a list of key-value pairs.
                                The order of the pairs in the list is not
                                significant. In JSON, a set of keyvalue pairs is
                                represented as an object. It shall comply with
                                the provisions defined in clause 4 of IETF RFC
                                8259. In the following example, a list of
                                key-value pairs with four keys ("aString",
                                "aNumber", "anArray" and "anObject") is provided
                                to illustrate that the values associated with
                                different keys can be of different type.
                              type: object
                        containerNamespace:
                          description: >
                            The value of the namespace in which the MCIO
                            corresponding to the resource is deployed. This
                            attribute shall be present if the resource is
                            managed by a CISM and it shall be absent otherwise.
                          type: string
                    extLinkPorts:
                      description: |
                        Link ports of this VL.
                      type: array
                      items:
                        description: "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to  an NS VL.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n"
                        type: object
                        required:
                          - id
                          - resourceHandle
                        properties:
                          id:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                          resourceHandle:
                            required:
                              - resourceId
                            type: object
                            description: >
                              This type represents the information that allows
                              addressing a virtualised resource that is used by
                              a VNF instance. Information about the resource is
                              available from the VIM.

                              * NOTE 1: The information about the VIM or CISM
                              connection referenced by the VIM connection id is
                              known to the
                                        VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.

                              * NOTE 2: The value set of the
                              "vimLevelResourceType" attribute is within the
                              scope of the VIM or CISM or the resource 
                                        provider and can be used as information that complements the ResourceHandle. When the container
                                        infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would 
                                        correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, 
                                        PersistentVolumeClaim, NetworkAttachmentDefinition.

                              * NOTE 3: When the container infrastructure
                              service is a Kubernetes® instance the resourceId
                              shall be populated in the 
                                        following way:
                                        - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide 
                                        per resource type.
                                        - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, 
                                        i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by 
                                        Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own 
                                        manifest.
                                        - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of 
                                        the 'metadata.name' field in Kubernetes® manifest.
                            properties:
                              vimConnectionId:
                                description: >
                                  An identifier with the intention of being
                                  globally unique.
                                type: string
                              resourceProviderId:
                                description: >
                                  An identifier with the intention of being
                                  globally unique.
                                type: string
                              resourceId:
                                description: >
                                  An identifier maintained by the VIM  or the
                                  CISM or other resource provider. It is
                                  expected to be unique within the VIM instance.
                                type: string
                              vimLevelResourceType:
                                description: >
                                  Type of the resource in the scope of the VIM
                                  or the CISM or the resource provider. See note
                                  2.
                                type: string
                              vimLevelAdditionalResourceInfo:
                                description: >
                                  This type represents additional resource
                                  information which resource and resource type
                                  specific, and which is available from the VIM
                                  or the CISM or the resource provider.

                                  * NOTE: At least one attribute shall be
                                  present.
                                type: object
                                properties:
                                  hostName:
                                    description: >
                                      Name of the host where the resource is
                                      allocated. It shall be present for compute
                                      resources in the scope of the CISM and
                                      shall be absent otherwise. See note.
                                    type: string
                                  persistentVolume:
                                    description: >
                                      Name of the persistent volume to which the
                                      persistent volume claim representing the
                                      storage resource is bound. It may be
                                      present for storage resources in the scope
                                      of the CISM and shall be absent otherwise.
                                      See note.
                                    type: string
                                  additionalInfo:
                                    description: >
                                      This type represents a list of key-value
                                      pairs. The order of the pairs in the list
                                      is not significant. In JSON, a set of
                                      keyvalue pairs is represented as an
                                      object. It shall comply with the
                                      provisions defined in clause 4 of IETF RFC
                                      8259. In the following example, a list of
                                      key-value pairs with four keys ("aString",
                                      "aNumber", "anArray" and "anObject") is
                                      provided to illustrate that the values
                                      associated with different keys can be of
                                      different type.
                                    type: object
                              containerNamespace:
                                description: >
                                  The value of the namespace in which the MCIO
                                  corresponding to the resource is deployed.
                                  This attribute shall be present if the
                                  resource is managed by a CISM and it shall be
                                  absent otherwise.
                                type: string
                          cpInstanceId:
                            description: >
                              An identifier that is unique for the respective
                              type within a VNF instance, but may not be
                              globally unique.
                            type: string
                          secondaryCpInstanceId:
                            description: >
                              An identifier that is unique for the respective
                              type within a VNF instance, but may not be
                              globally unique.
                            type: string
                          trunkResourceId:
                            description: >
                              An identifier maintained by the VIM  or the CISM
                              or other resource provider. It is expected to be
                              unique within the VIM instance.
                            type: string
                    currentVnfExtCpData:
                      description: >
                        Allows the API consumer to read the current CP
                        configuration information for the connection of external
                        CPs  to the external virtual link. See note.
                      type: array
                      items:
                        description: "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n              from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n              connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n              \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n              a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n              all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n              connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n              by a particular key value from the map, i.e. for the disconnection of an existing external\n              CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n              virtual link, and deletion of that instance in case it represents a subport. Deleting the\n              last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n              its parent data structure.\n* NOTE 4:   If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n            \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value \n            is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig\n            map entry may be used by an external CP instance different than the one that has used it before the\n            operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\"\n            operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n* NOTE 5:   Subports need not be used for containerized VNFCs. The application container can send and receive IP\n            packets with any VLAN tag as long as the network interface to connect to the secondary container cluster\n            network has been configured appropriately. Thus, no individual cpConfig, except the one representing the\n            trunk, need be modelled to allow traffic tagged with a particular VLAN through the connection point.\n* NOTE 6:   In the case that the cloud native template included in the MCIOP describes the set of VNFC instances, for\n            containerized VNFCs individual connection points need not be configured for each VNFC instance. It is only\n            required to configure one \"cpConfig\" per \"cpdId\", not per VNFC instance. The case of using, for a scalable\n            VDU, a cloud native template in the MCIOP that describes one single VNFC instance is not specified in the\n            present document version.\n"
                        type: object
                        required:
                          - cpdId
                          - cpConfig
                        properties:
                          cpdId:
                            description: >
                              An identifier that is unique within a VNF
                              descriptor.
                            type: string
                          cpConfig:
                            description: >
                              Map of instance data that need to be configured on
                              the CP instances created from the respective CPD.
                              The key of the map which identifies the individual
                              VnfExtCpConfig entries is of type
                              "IdentifierInVnf" and is managed by the NFVO. The
                              entries shall be applied by the VNFM according to
                              the rules of JSON Merge Patch (see IETF RFC 7396).
                              See notes 2, 3, 4, 5 and 6. In case of deleting an
                              external CP, the list of instances to be deleted. 
                            type: object
                            additionalProperties:
                              description: >
                                This type represents an externally provided link
                                port, or a network attachment definition
                                resource of secondary container cluster network,
                                or network address information per instance of
                                an external connection point. In the case of
                                VM-based deployment of the VNFC exposing the
                                external CP:
                                  1.  In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the
                                      external VL.
                                  2.  In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port
                                      to connect the external CP to the external VL.
                                In the case of container-based deployment of the
                                VNFC exposing the external CP, the VNFM shall
                                use the network attachment definition resource
                                of secondary container cluster network when
                                connecting the CP to the external VL.

                                * NOTE 1: The following conditions apply to the
                                attributes "linkPortId" and "cpProtocolData" for
                                an external CP
                                          instance connected or to be connected to a virtual network not categorized as secondary container cluster network:
                                          1) Void.
                                          2) At least one of the "linkPortId" and "cpProtocolData" attributes shall be present for an external CP instance
                                          representing a subport that is to be created, or an external CP instance that is to be created by creating the
                                          corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing
                                          external CP instance that is to be re-configured or added to a particular external virtual link.
                                          3) If the "linkPortId" attribute is absent, the VNFM shall create a link port.
                                          4) If the "cpProtocolData" attribute is absent, the "linkPortId" attribute shall be provided referencing a
                                          precreated link port, and the VNFM can use means outside the scope of the present document to obtain the
                                          pre-configured address information for the connection point from the resource representing the link port.
                                          5) If both "cpProtocolData" and "linkportId" are provided, the NFVO shall ensure that the
                                          cpProtocolData can be used with the pre-created link port referenced by "linkPortId".

                                * NOTE 2: The following conditions apply to the
                                attributes “netAttDefResourceId” and
                                “cpProtocolData” for an external CP
                                          instance connected or to be connected to a secondary container cluster network:
                                          1) Void.
                                          2) The "netAttDefResourceId" attribute shall be present and the "cpProtocolData" attribute may be present for
                                          a to-be-created external CP instance or an existing external CP instance.
                                * NOTE 3: Cardinality greater than 1 is only
                                applicable for specific cases where more than
                                one network attachment
                                          definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link
                                          redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong
                                          to the same namespace as defined by the corresponding "containerNamespace" attribute in the "resourceHandle" attribute
                                          in the "NetAttDefResourceData".
                                * NOTE 4: Either linkPortId or
                                netAttDefResourceId may be included, but not
                                both.
                              anyOf:
                                - required:
                                    - linkPortId
                                - required:
                                    - cpProtocolData
                                - required:
                                    - netAttDefResourceId
                              type: object
                              properties:
                                parentCpConfigId:
                                  description: >
                                    An identifier that is unique for the
                                    respective type within a VNF instance, but
                                    may not be globally unique.
                                  type: string
                                linkPortId:
                                  description: >
                                    An identifier with the intention of being
                                    globally unique.
                                  type: string
                                createExtLinkPort:
                                  description: >
                                    Indicates to the VNFM the need to create a
                                    dedicated link port for the external CP. If
                                    set to True, the VNFM shall create a link
                                    port. If set to False, the VNFM shall not
                                    create a link port. This attribute is only
                                    applicable for external CP instances without
                                    a floating IP address that expose a VIP CP
                                    instance for which a dedicated IP address is
                                    allocated. It shall be present in that case
                                    and shall be absent otherwise.
                                  type: boolean
                                cpProtocolData:
                                  description: >
                                    Parameters for configuring the network
                                    protocols on the link port that connects the
                                    CP to a VL and the domain  names for the
                                    external CP. See notes 1 and 2.
                                  type: array
                                  items:
                                    description: "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n          in future versions of the present document in a backwards-compatible way. In the current\n          version of the present document, only IP over Ethernet is supported.\n"
                                    type: object
                                    required:
                                      - layerProtocol
                                    properties:
                                      layerProtocol:
                                        description: >
                                          Identifier of layer(s) and protocol(s).
                                          Permitted values:
                                            - IP_OVER_ETHERNET.
                                            - IP_FOR_VIRTUAL_CP
                                          See note
                                        type: string
                                        enum:
                                          - IP_OVER_ETHERNET
                                          - IP_FOR_VIRTUAL_CP
                                      ipOverEthernet:
                                        description: "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n          Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n          network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n          of the packets or it may be an identifier used between the application and the NFVI networking\n          infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n          case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n          actually used by the NFVI's transport technology.\n"
                                        type: object
                                        anyOf:
                                          - required:
                                              - macAddress
                                          - required:
                                              - ipAddresses
                                        properties:
                                          macAddress:
                                            description: >
                                              A MAC address. Representation: string
                                              that consists of groups of two
                                              hexadecimal digits, separated by hyphens
                                              or colons.
                                            type: string
                                            format: MAC
                                          segmentationType:
                                            description: "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n"
                                            type: string
                                            enum:
                                              - VLAN
                                              - INHERIT
                                          segmentationId:
                                            description: >
                                              Identification of the network segment to
                                              which the CP instance connects to. See
                                              note 3 and note 4.
                                            type: string
                                          ipAddresses:
                                            description: >
                                              List of IP addresses to assign to the CP
                                              instance. Each entry represents IP
                                              address data for fixed or dynamic IP
                                              address assignment per subnet. If this
                                              attribute is not present, no IP address
                                              shall be assigned. See note 1.
                                            type: array
                                            items:
                                              type: object
                                              required:
                                                - type
                                              oneOf:
                                                - required:
                                                    - fixedAddresses
                                                - required:
                                                    - numDynamicAddresses
                                                - required:
                                                    - addressRange
                                              properties:
                                                type:
                                                  description: >
                                                    The type of the IP addresses. Permitted
                                                    values: IPV4, IPV6.
                                                  type: string
                                                  enum:
                                                    - IPV4
                                                    - IPV6
                                                fixedAddresses:
                                                  description: >
                                                    Fixed addresses to assign (from the
                                                    subnet defined by "subnetId" if
                                                    provided). See note 2.
                                                  type: array
                                                  items:
                                                    description: >
                                                      An IPV4 or IPV6 address. Representation:
                                                      In case of an IPV4 address, string that
                                                      consists of four decimal integers
                                                      separated by dots, each integer ranging
                                                      from 0 to 255. In case of an IPV6
                                                      address, string that consists of groups
                                                      of zero to four hexadecimal digits,
                                                      separated by colons.
                                                    type: string
                                                    format: IP
                                                numDynamicAddresses:
                                                  description: >
                                                    Number of dynamic addresses to assign
                                                    (from the subnet defined by "subnetId"
                                                    if provided). See note 2.
                                                  type: integer
                                                addressRange:
                                                  description: >
                                                    An IP address range to be used, e.g. in
                                                    case of egress connections. In case this
                                                    attribute is present, IP addresses from
                                                    the range will be used. See note 2.
                                                  type: object
                                                  required:
                                                    - minAddress
                                                    - maxAddress
                                                  properties:
                                                    minAddress:
                                                      description: >
                                                        An IPV4 or IPV6 address. Representation:
                                                        In case of an IPV4 address, string that
                                                        consists of four decimal integers
                                                        separated by dots, each integer ranging
                                                        from 0 to 255. In case of an IPV6
                                                        address, string that consists of groups
                                                        of zero to four hexadecimal digits,
                                                        separated by colons.
                                                      type: string
                                                      format: IP
                                                    maxAddress:
                                                      description: >
                                                        An IPV4 or IPV6 address. Representation:
                                                        In case of an IPV4 address, string that
                                                        consists of four decimal integers
                                                        separated by dots, each integer ranging
                                                        from 0 to 255. In case of an IPV6
                                                        address, string that consists of groups
                                                        of zero to four hexadecimal digits,
                                                        separated by colons.
                                                      type: string
                                                      format: IP
                                                subnetId:
                                                  description: >
                                                    An identifier maintained by the VIM  or
                                                    the CISM or other resource provider. It
                                                    is expected to be unique within the VIM
                                                    instance.
                                                  type: string
                                      virtualCpAddress:
                                        description: >
                                          This type represents network address
                                          data for a virtual CP.

                                          * NOTE 1: The loadBalancerIp and the
                                          loadBalancerSourceRanges attributes are
                                          only used if the 
                                                    CIS cluster is set up to be able to configure an external load balancer. Otherwise, it shall be ignored.

                                          * NOTE 2: In case the cluster can
                                          configure an external load balancer but
                                          no loadBalancerIp is provided the
                                          container
                                                    cluster will assign an IP address.

                                          * NOTE 3: The attribute is only relevant
                                          if the virtual CP is instantiated in a
                                          cluster that supports configuration of
                                          IP 
                                                    address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for 
                                                    Kubernetes® that supports configuration of address pools for load balancer services.

                                          * NOTE 4: The loadBalancerIp,
                                          addressPoolName and the externalIp
                                          attributes shall not be present at the
                                          same time.
                                        type: object
                                        required:
                                          - type
                                        properties:
                                          type:
                                            description: >
                                              The type of the IP addresses. Permitted
                                              values: IPV4, IPV6.
                                            type: string
                                            enum:
                                              - IPV4
                                              - IPV6
                                          loadBalancerIp:
                                            description: >
                                              An IPV4 or IPV6 address. Representation:
                                              In case of an IPV4 address, string that
                                              consists of four decimal integers
                                              separated by dots, each integer ranging
                                              from 0 to 255. In case of an IPV6
                                              address, string that consists of groups
                                              of zero to four hexadecimal digits,
                                              separated by colons.
                                            type: string
                                            format: IP
                                          externalIp:
                                            description: >
                                              An IPV4 or IPV6 address. Representation:
                                              In case of an IPV4 address, string that
                                              consists of four decimal integers
                                              separated by dots, each integer ranging
                                              from 0 to 255. In case of an IPV6
                                              address, string that consists of groups
                                              of zero to four hexadecimal digits,
                                              separated by colons.
                                            type: string
                                            format: IP
                                          addressPoolName:
                                            description: >
                                              Name of an address pool from which the
                                              CIS cluster will assign an IP address to
                                              the virtual CP. See notes 3 and 4.
                                            type: string
                                          loadBalancerSourceRanges:
                                            description: >
                                              List of client IP address ranges allowed
                                              to access an external load balancer. See
                                              note 1.
                                            type: object
                                            required:
                                              - minAddress
                                              - maxAddress
                                            properties:
                                              minAddress:
                                                description: >
                                                  An IPV4 or IPV6 address. Representation:
                                                  In case of an IPV4 address, string that
                                                  consists of four decimal integers
                                                  separated by dots, each integer ranging
                                                  from 0 to 255. In case of an IPV6
                                                  address, string that consists of groups
                                                  of zero to four hexadecimal digits,
                                                  separated by colons.
                                                type: string
                                                format: IP
                                              maxAddress:
                                                description: >
                                                  An IPV4 or IPV6 address. Representation:
                                                  In case of an IPV4 address, string that
                                                  consists of four decimal integers
                                                  separated by dots, each integer ranging
                                                  from 0 to 255. In case of an IPV6
                                                  address, string that consists of groups
                                                  of zero to four hexadecimal digits,
                                                  separated by colons.
                                                type: string
                                                format: IP
                                      fullyQualifiedDomainNames:
                                        description: >
                                          Specifies the fully qualified domain
                                          names (FQDN) to apply to the CP.
                                        type: string
                                      relativeDomainNames:
                                        description: >
                                          Specifies values of relative domain
                                          names to be considered when setting  the
                                          fully qualified domain names.
                                        type: string
                                netAttDefResourceId:
                                  description: >
                                    Identifier of the “NetAttDefResourceData”
                                    structure that provides the specification of
                                    the interface to attach the external CP to a
                                    secondary container cluster network. It is
                                    only applicable if the external CP is
                                    connected or to be connected to a secondary
                                    container cluster network. It shall not be
                                    present if the external CP is related to a
                                    virtual network not categorized as secondary
                                    container cluster network. See notes 2, 3
                                    and 4.
                                  type: array
                                  items:
                                    description: >
                                      An identifier with the intention of being
                                      globally unique.
                                    type: string
                    extNetAttDefResource:
                      description: >
                        Network attachment definition resources that provide the
                        specification of the interface to attach connection
                        points  to this VL.
                      type: array
                      items:
                        description: >
                          This type contains information related to a network
                          attachment definition resource that provides the 
                          specification of the interface used to connect one or
                          multiple connection points to a secondary container 
                          cluster network.
                        type: object
                        required:
                          - netAttDefResourceInfoId
                          - netAttDefResource
                        properties:
                          netAttDefResourceInfoId:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                          netAttDefResource:
                            required:
                              - resourceId
                            type: object
                            description: >
                              This type represents the information that allows
                              addressing a virtualised resource that is used by
                              a VNF instance. Information about the resource is
                              available from the VIM.

                              * NOTE 1: The information about the VIM or CISM
                              connection referenced by the VIM connection id is
                              known to the
                                        VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.

                              * NOTE 2: The value set of the
                              "vimLevelResourceType" attribute is within the
                              scope of the VIM or CISM or the resource 
                                        provider and can be used as information that complements the ResourceHandle. When the container
                                        infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would 
                                        correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, 
                                        PersistentVolumeClaim, NetworkAttachmentDefinition.

                              * NOTE 3: When the container infrastructure
                              service is a Kubernetes® instance the resourceId
                              shall be populated in the 
                                        following way:
                                        - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide 
                                        per resource type.
                                        - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, 
                                        i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by 
                                        Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own 
                                        manifest.
                                        - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of 
                                        the 'metadata.name' field in Kubernetes® manifest.
                            properties:
                              vimConnectionId:
                                description: >
                                  An identifier with the intention of being
                                  globally unique.
                                type: string
                              resourceProviderId:
                                description: >
                                  An identifier with the intention of being
                                  globally unique.
                                type: string
                              resourceId:
                                description: >
                                  An identifier maintained by the VIM  or the
                                  CISM or other resource provider. It is
                                  expected to be unique within the VIM instance.
                                type: string
                              vimLevelResourceType:
                                description: >
                                  Type of the resource in the scope of the VIM
                                  or the CISM or the resource provider. See note
                                  2.
                                type: string
                              vimLevelAdditionalResourceInfo:
                                description: >
                                  This type represents additional resource
                                  information which resource and resource type
                                  specific, and which is available from the VIM
                                  or the CISM or the resource provider.

                                  * NOTE: At least one attribute shall be
                                  present.
                                type: object
                                properties:
                                  hostName:
                                    description: >
                                      Name of the host where the resource is
                                      allocated. It shall be present for compute
                                      resources in the scope of the CISM and
                                      shall be absent otherwise. See note.
                                    type: string
                                  persistentVolume:
                                    description: >
                                      Name of the persistent volume to which the
                                      persistent volume claim representing the
                                      storage resource is bound. It may be
                                      present for storage resources in the scope
                                      of the CISM and shall be absent otherwise.
                                      See note.
                                    type: string
                                  additionalInfo:
                                    description: >
                                      This type represents a list of key-value
                                      pairs. The order of the pairs in the list
                                      is not significant. In JSON, a set of
                                      keyvalue pairs is represented as an
                                      object. It shall comply with the
                                      provisions defined in clause 4 of IETF RFC
                                      8259. In the following example, a list of
                                      key-value pairs with four keys ("aString",
                                      "aNumber", "anArray" and "anObject") is
                                      provided to illustrate that the values
                                      associated with different keys can be of
                                      different type.
                                    type: object
                              containerNamespace:
                                description: >
                                  The value of the namespace in which the MCIO
                                  corresponding to the resource is deployed.
                                  This attribute shall be present if the
                                  resource is managed by a CISM and it shall be
                                  absent otherwise.
                                type: string
                          associatedExtCpId:
                            description: >
                              Identifier of the external CP associated to this
                              network attachment definition resource. Shall be
                              present  when the network attachment definition
                              resource is used for external connectivity by the
                              VNF.
                            type: array
                            items:
                              description: >
                                An identifier that is unique for the respective
                                type within a VNF instance, but may not be
                                globally unique.
                              type: string
                          associatedVnfcCpId:
                            description: >
                              Identifier of the VNFC CP associated to this
                              network attachment definition resource. May be
                              present when  the network attachment definition
                              resource is used for internal connectivity by the
                              VNF.
                            type: array
                            items:
                              description: >
                                An identifier that is unique for the respective
                                type within a VNF instance, but may not be
                                globally unique.
                              type: string
                    routingResource:
                      description: >
                        Network resources that provide the forwarding/routing
                        capabilities associated to the network resource
                        realizing this VL.
                      type: array
                      items:
                        required:
                          - resourceId
                        type: object
                        description: >
                          This type represents the information that allows
                          addressing a virtualised resource that is used by a
                          VNF instance. Information about the resource is
                          available from the VIM.

                          * NOTE 1: The information about the VIM or CISM
                          connection referenced by the VIM connection id is
                          known to the
                                    VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.

                          * NOTE 2: The value set of the "vimLevelResourceType"
                          attribute is within the scope of the VIM or CISM or
                          the resource 
                                    provider and can be used as information that complements the ResourceHandle. When the container
                                    infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would 
                                    correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, 
                                    PersistentVolumeClaim, NetworkAttachmentDefinition.

                          * NOTE 3: When the container infrastructure service is
                          a Kubernetes® instance the resourceId shall be
                          populated in the 
                                    following way:
                                    - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide 
                                    per resource type.
                                    - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, 
                                    i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by 
                                    Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own 
                                    manifest.
                                    - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of 
                                    the 'metadata.name' field in Kubernetes® manifest.
                        properties:
                          vimConnectionId:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                          resourceProviderId:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                          resourceId:
                            description: >
                              An identifier maintained by the VIM  or the CISM
                              or other resource provider. It is expected to be
                              unique within the VIM instance.
                            type: string
                          vimLevelResourceType:
                            description: >
                              Type of the resource in the scope of the VIM or
                              the CISM or the resource provider. See note 2.
                            type: string
                          vimLevelAdditionalResourceInfo:
                            description: >
                              This type represents additional resource
                              information which resource and resource type
                              specific, and which is available from the VIM or
                              the CISM or the resource provider.

                              * NOTE: At least one attribute shall be present.
                            type: object
                            properties:
                              hostName:
                                description: >
                                  Name of the host where the resource is
                                  allocated. It shall be present for compute
                                  resources in the scope of the CISM and shall
                                  be absent otherwise. See note.
                                type: string
                              persistentVolume:
                                description: >
                                  Name of the persistent volume to which the
                                  persistent volume claim representing the
                                  storage resource is bound. It may be present
                                  for storage resources in the scope of the CISM
                                  and shall be absent otherwise. See note.
                                type: string
                              additionalInfo:
                                description: >
                                  This type represents a list of key-value
                                  pairs. The order of the pairs in the list is
                                  not significant. In JSON, a set of keyvalue
                                  pairs is represented as an object. It shall
                                  comply with the provisions defined in clause 4
                                  of IETF RFC 8259. In the following example, a
                                  list of key-value pairs with four keys
                                  ("aString", "aNumber", "anArray" and
                                  "anObject") is provided to illustrate that the
                                  values associated with different keys can be
                                  of different type.
                                type: object
                          containerNamespace:
                            description: >
                              The value of the namespace in which the MCIO
                              corresponding to the resource is deployed. This
                              attribute shall be present if the resource is
                              managed by a CISM and it shall be absent
                              otherwise.
                            type: string
              modificationsTriggeredByVnfPkgChange:
                description: "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource  when changing the current VNF package. The attributes that can be included consist of those requested to  be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the  \"VnfInstance\" data structure that were modified implicitly during the operation.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n        of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n        at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n        during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n        VNF Package identified by the \"vnfdId\" attribute.\n"
                type: object
                properties:
                  vnfConfigurableProperties:
                    description: >
                      This type represents a list of key-value pairs. The order
                      of the pairs in the list is not significant. In JSON, a
                      set of keyvalue pairs is represented as an object. It
                      shall comply with the provisions defined in clause 4 of
                      IETF RFC 8259. In the following example, a list of
                      key-value pairs with four keys ("aString", "aNumber",
                      "anArray" and "anObject") is provided to illustrate that
                      the values associated with different keys can be of
                      different type.
                    type: object
                  metadata:
                    description: >
                      This type represents a list of key-value pairs. The order
                      of the pairs in the list is not significant. In JSON, a
                      set of keyvalue pairs is represented as an object. It
                      shall comply with the provisions defined in clause 4 of
                      IETF RFC 8259. In the following example, a list of
                      key-value pairs with four keys ("aString", "aNumber",
                      "anArray" and "anObject") is provided to illustrate that
                      the values associated with different keys can be of
                      different type.
                    type: object
                  extensions:
                    description: >
                      This type represents a list of key-value pairs. The order
                      of the pairs in the list is not significant. In JSON, a
                      set of keyvalue pairs is represented as an object. It
                      shall comply with the provisions defined in clause 4 of
                      IETF RFC 8259. In the following example, a list of
                      key-value pairs with four keys ("aString", "aNumber",
                      "anArray" and "anObject") is provided to illustrate that
                      the values associated with different keys can be of
                      different type.
                    type: object
                  vnfdId:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  vnfProvider:
                    description: >
                      If present, this attribute signals the new value of the
                      "vnfProvider" attribute in "VnfInstance". See note 2.
                    type: string
                  vnfProductName:
                    description: >
                      If present, this attribute signals the new value of the
                      "vnfProductName" attribute in "VnfInstance". See note 2.
                    type: string
                  vnfSoftwareVersion:
                    description: |
                      A version.
                    type: string
                  vnfdVersion:
                    description: |
                      A version.
                    type: string
              error:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 is reproduced inthis structure. Compared to
                  the general framework defined in IETF RFC 7807, the "status"
                  and "detail" attributes are mandated to be included by the
                  present document, to ensure that the response contains
                  additional textual information about an error. IETF RFC 7807
                  foresees extensibility of the "ProblemDetails" type. It is
                  possible that particular APIs in the present document, or
                  particular implementations, define extensions to define
                  additional attributes that provide more information about the
                  error. The description column only provides some explanation
                  of the meaning to Facilitate understanding of the design. For
                  a full description, see IETF RFC 7807.
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 that identifies
                      the problem type. It is encouraged that the URI provides
                      human-readable documentation for the problem (e.g. using
                      HTML) when dereferenced. When this member is not present,
                      its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
              _links:
                description: >
                  This type represents the links to resources that a
                  notification can contain.
                type: object
                required:
                  - vnfInstance
                  - subscription
                properties:
                  vnfInstance:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  subscription:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  vnfLcmOpOcc:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
      required: true
    VnfIdentifierCreationNotification:
      description: >
        A notification about lifecycle changes triggered by a VNF LCM operation
        occurrence.
      content:
        application/json:
          schema:
            description: >
              This type represents a VNF identifier creation notification, which
              informs the receiver of the creation of a new "Individual VNF
              instance" resource and the associated VNF instance identifier.
              This notification shall be triggered by the VNFM when it has
              created an "Individual VNF instance" resource and the associated
              VNF instance identifier.
            type: object
            required:
              - id
              - notificationType
              - subscriptionId
              - timeStamp
              - vnfInstanceId
              - _links
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              notificationType:
                description: >
                  Discriminator for the different notification types. Shall be
                  set to "VnfIdentifierCreationNotification" for this
                  notification type.
                type: string
                enum:
                  - VnfIdentifierCreationNotification
              subscriptionId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              timeStamp:
                description: >
                  Date-time stamp. Representation: String formatted according to
                  IETF RFC 3339.
                type: string
                format: date-time
              vnfInstanceId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              _links:
                description: >
                  This type represents the links to resources that a
                  notification can contain.
                type: object
                required:
                  - vnfInstance
                  - subscription
                properties:
                  vnfInstance:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  subscription:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  vnfLcmOpOcc:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
      required: true
    VnfIdentifierDeletionNotification:
      description: >
        A notification about the deletion of a VNF identifier and the related
        "Individual VNF instance" resource.
      content:
        application/json:
          schema:
            description: >
              This type represents a VNF identifier creation notification, which
              informs the receiver of the creation of a new "Individual VNF
              instance" resource and the associated VNF instance identifier.
              This notification shall be triggered by the VNFM when it has
              created an "Individual VNF instance" resource and the associated
              VNF instance identifier.
            type: object
            required:
              - id
              - notificationType
              - subscriptionId
              - timeStamp
              - vnfInstanceId
              - _links
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              notificationType:
                description: >
                  Discriminator for the different notification types. Shall be
                  set to "VnfIdentifierCreationNotification" for this
                  notification type.
                type: string
                enum:
                  - VnfIdentifierCreationNotification
              subscriptionId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              timeStamp:
                description: >
                  Date-time stamp. Representation: String formatted according to
                  IETF RFC 3339.
                type: string
                format: date-time
              vnfInstanceId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              _links:
                description: >
                  This type represents the links to resources that a
                  notification can contain.
                type: object
                required:
                  - vnfInstance
                  - subscription
                properties:
                  vnfInstance:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  subscription:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  vnfLcmOpOcc:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
      required: true
  responses:
    VNFLCMNotification.Get.204:
      description: >
        204 NO CONTENT

        Shall be returned to indicate the notification endpoint has been  tested
        successfully. The response body

        shall be empty.
      headers:
        Version:
          description: |
            Version of the API used in the response.
          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
      content: {}
    VNFLCMNotification.Post.204:
      description: >
        204 NO CONTENT

        Shall be returned when the notification has been delivered successfully.
        The response body shall be empty.
      headers:
        Version:
          description: |
            Version of the API used in the response.
          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
      content: {}

