openapi: 3.0.2
info:
  title: SOL003 - VNF Indicator Notification interface
  description: |
    SOL003 - VNF Indicator 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: '1.13.0-impl:etsi.org:ETSI_NFV_OpenAPI:1'
externalDocs:
  description: ETSI GS NFV-SOL 003 V5.1.1
  url: >-
    https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/05.01.01_60/gs_NFV-SOL003v050101p.pdf
servers:
  - url: 'http://127.0.0.1/callback/v1'
  - url: 'https://127.0.0.1/callback/v1'
paths:
  /URI_is_provided_by_the_client_when_creating_the_subscription-VnfIndicatorValueChangeNotification:
    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 8.4.7.3.1.
      parameters:
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
      requestBody:
        $ref: '#/components/requestBodies/AlarmListRebuiltNotification'
      responses:
        '204':
          $ref: '#/components/responses/VNFINDNotification.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
    get:
      description: >
        The GET method allows the API producer to test the notification endpoint
        that is provided by the API consumer,

        e.g. during subscription. See clause 8.4.7.3.2.
      parameters:
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
      responses:
        '204':
          $ref: '#/components/responses/VNFINDNotification.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
components:
  requestBodies:
    AlarmListRebuiltNotification:
      description: Information that the alarm list has been rebuilt by the VNFM.
      content:
        application/json:
          schema:
            oneOf:
              - description: "This type represents a VNF indicator value change notification.\nThe notification shall be triggered by the VNFM when the value of an indicator has changed.\nNOTE:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n"
                type: object
                required:
                  - id
                  - notificationType
                  - subscriptionId
                  - timeStamp
                  - vnfIndicatorId
                  - value
                  - 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 "VnfIndicatorValueChangeNotification" for this
                      notification type.
                    type: string
                    enum:
                      - VnfIndicatorValueChangeNotification
                  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
                  vnfIndicatorId:
                    description: |
                      An identifier that is unique within a VNF descriptor.
                    type: string
                  name:
                    description: >
                      Human readable name of the VNF indicator. Shall be present
                      if defined in the VNFD.
                    type: string
                  value:
                    description: >
                      Provides the value of the VNF indicator. The value format
                      is defined in the VNFD. See note.
                    type: object
                  vnfInstanceId:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  _links:
                    description: |
                      Links for this resource.
                    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
              - description: "This type represents a notification to inform the receiver that the set of indicators supported  by a VNF instance has changed.\nThe notification shall be triggered by the VNFM when the set of supported VNF indicators has changed  as a side effect of the \"Change current VNF package\" operation. It may be triggered by the VNFM when  a VNF has been instantiated.\nNOTE:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n"
                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  "SupportedIndicatorsChangeNotification" for
                      this notification type.
                    type: string
                    enum:
                      - VnfIndicatorValueChangeNotification
                  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
                  supportedIndicators:
                    description: |
                      Set of VNF indicators supported by the VNF instance.
                    type: array
                    items:
                      type: object
                      required:
                        - vnfIndicatorId
                      properties:
                        vnfIndicatorId:
                          description: >
                            An identifier that is unique within a VNF
                            descriptor.
                          type: string
                        name:
                          description: >
                            Human readable name of the VNF indicator. Shall be
                            present if defined in the VNFD. See note.
                          type: string
                  _links:
                    description: |
                      Links for this resource.
                    type: object
                    required:
                      - 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
      required: true
  responses:
    VNFINDNotification.Post.204:
      description: |
        204 NO CONTENT

        Shall be returned when the notification has been delivered successfully.
        The response body shall be empty.
      headers:
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the

            corresponding HTTP request has provided an invalid authorization
            token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
    VNFINDNotification.Get.204:
      description: >
        204 NO CONTENT

        Shall be returned to indicate that the notification endpoint has been
        tested successfully.

        The response body shall be empty.
      headers:
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the

            corresponding HTTP request has provided an invalid authorization
            token.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

