openapi: 3.0.2
info:
  version: '1.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1'
  title: SOL009 - NFV-MANO Configuration and Information Management Interface
  description: >
    SOL009 - NFV-MANO Configuration and Information Management Interface

    IMPORTANT: Please note that this file might be not aligned to the current
    version of the ETSI Group Specification it refers to and has not been
    approved by the ETSI NFV ISG. In case of discrepancies the published ETSI
    Group Specification takes precedence. Please report bugs to
    https://forge.etsi.org/bugzilla/buglist.cgi?component=Nfv-Openapis
  license:
    name: ETSI Forge copyright notice
    url: 'https://forge.etsi.org/etsi-forge-copyright-notice.txt'
  contact:
    name: NFV-SOL WG
externalDocs:
  description: ETSI GS NFV-SOL 009 V3.3.1
  url: >-
    https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.03.01_60/gs_NFV-SOL009v030301p.pdf
servers:
  - url: 'http://0.0.0.0/nfvmanocim/v1'
    description: |
      API HTTP Server
  - url: 'https://0.0.0.0/nfvmanocim/v1'
    description: |
      API HTTPS Server
paths:
  /api_versions:
    parameters:
      - name: Version
        description: |
          Version of the API requested to use when responding to this request.
        in: header
        required: false
        schema:
          type: string
      - name: Authorization
        description: 'The authorization token for the request. Reference: IETF RFC 7235'
        in: header
        required: false
        schema:
          type: string
    get:
      summary: Retrieve API version information
      description: >
        The GET method reads API version information. This method shall follow
        the provisions specified in table 4.6.3.3.3.2-1 for request and response
        data structures, and response codes. URI query parameters are not
        supported.
      responses:
        '200':
          description: >
            200 OK

            API version information was read successfully. The response body
            shall contain 4.4 API version information, as defined in clause
            4.4.1.13.
          content:
            application/json:
              schema:
                description: |
                  This type represents API version information.
                type: object
                required:
                  - uriPrefix
                  - apiVersions
                properties:
                  uriPrefix:
                    description: >
                      Specifies the URI prefix for the API, in the following
                      form {apiRoot}/{apiName}/{apiMajorVersion}/.
                    type: string
                  apiVersions:
                    description: >
                      Version(s) supported for the API signaled by the uriPrefix
                      attribute.
                    type: array
                    items:
                      type: object
                      required:
                        - version
                      properties:
                        version:
                          description: >
                            Identifies a supported version. The value of the
                            version attribute shall be a version identifier as
                            specified in clause 9.1 (SOL013).
                          type: string
                        isDeprecated:
                          description: >
                            If such information is available, this attribute
                            indicates whether use of the version signaled by the
                            version attribute is deprecated (true) or not
                            (false).

                            A deprecated version is still supported by the API
                            producer but is recommended not to be used any
                            longer. When a version is no longer supported, it
                            does not appear in the response body.
                          type: boolean
                        retirementDate:
                          description: >
                            Date-time stamp. Representation: String formatted
                            according to IETF RFC 3339.
                          type: string
                          format: date-time
          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: The used API version.
              schema:
                type: string
                maximum: 1
                minimum: 1
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '413':
          description: >
            413 PAYLOAD TOO LARGE

            If the payload body of a request is larger than the amount of data
            the API producer is willing or able to process, it shall respond
            with this response code, following the provisions in IETF RFC 7231
            for the use of the "Retry-After" HTTP header and for closing 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '414':
          description: >
            414 URI TOO LONG

            If the request URI of a request is longer than the API producer is
            willing or able to process, it shall respond with this response
            code. This condition can e.g. be caused by passing long queries in
            the request URI of a GET request. 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '416':
          description: |
            416 Range Not Satisfiable
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '429':
          description: >
            429 TOO MANY REQUESTS

            If the API consumer has sent too many requests in a defined period
            of time and the API producer is able to detect that condition ("rate
            limiting"), the API producer shall respond with this response code,
            following the provisions in IETF RFC 6585 [17] for the use of the
            "Retry-After" HTTP header. The "ProblemDetails" structure shall be
            provided and shall include in the "detail" attribute more
            information about the source of the problem.

            The period of time and allowed number of requests are configured
            within the API producer by means outside the scope of the present
            document.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
  /mano_entity:
    get:
      description: >
        Retrives information about an NFV-MANO functional entity  by reading the
        NFV-MANO entity resource. This method shall follow the provisions
        specified in the  tables 5.5.3.3.2-1 and 5.5.3.3.2-2 for URI query
        parameters,  request and response data structures, and response
        codes.       
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when configuration and information about  the
            NFV-MANO functional entity has been read successfully. The response
            body shall contain a representation of the NFV-MANO functional
            entity, as defined in clause 5.6.2.2.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: |
                  This type represents an NFV-MANO functional entity.
                type: object
                required:
                  - id
                  - type
                  - name
                  - description
                  - provider
                  - softwareVersion
                  - manoConfigurableParams
                  - manoApplicationState
                  - _links
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  type:
                    description: "The enumeration ManoEntityEnumType defines the permitted values to  represent NFV-MANO functional entities. It shall comply with  the provisions :\n  - NFVO\tThe NFV-MANO functional entity is an NFVO.\n  - VNFM\tThe NFV-MANO functional entity is a VNFM.\n  - VIM\tThe NFV-MANO functional entity is a VIM.\n"
                    type: string
                    enum:
                      - NFVO
                      - VNFM
                      - VIM
                  name:
                    description: |
                      Human-readable name of the NFV-MANO functional entity.
                      This attribute can be modified with the PATCH method.
                    type: string
                  description:
                    description: >
                      Human-readable description of the NFV-MANO functional
                      entity.

                      This attribute can be modified with the PATCH method.
                    type: string
                  provider:
                    description: >
                      Information about the provider of the NFV-MANO functional
                      entity.  It typically includes the name of the provider.
                    type: string
                  softwareVersion:
                    description: >
                      The version of the software of the NFV-MANO functional
                      entity. $ref:
                      "../components/SOL009_schemas.yaml#/components/schemas/Version"
                  manoEntityComponents:
                    description: "The deployed NFV-MANO functional entity components which realize the  NFV-MANO functional entity. \nNOTE:\tIt is optional for the API producer to support the \"manoEntityComponents\"  attribute.\n"
                    type: array
                    items:
                      description: >
                        This type represents information of a deployed component
                        realizing part of an  NFV-MANO functional entity. It is
                        optional for the API producer to support  this type. 
                      type: object
                      properties:
                        id:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                        manoServiceIds:
                          description: >
                            References to the NFV-MANO services that depend on
                            the NFV-MANO functional  entity component. The
                            identifier of the ManoService is referred. A
                            service  may depend on multiple components. Multiple
                            services may depend on the same  component.
                          type: array
                          items:
                            description: >
                              An identifier that is unique for the respective
                              type within a NFV-MANO functional entity, but that
                              need not be globally unique. Representation:
                              string of variable length..
                            type: string
                      required:
                        - id
                  manoServices:
                    description: >
                      Information about the NFV-MANO services provided by the
                      NFV-MANO  functional entity.
                    type: array
                    items:
                      description: >
                        This type represents information about an NFV-MANO
                        service provided by the  NFV-MANO functional entity.
                      type: object
                      properties:
                        id:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                        name:
                          description: >
                            Human-readable name of the NFV-MANO service.

                            This attribute can be modified with the PATCH
                            method.
                          type: string
                        description:
                          description: >
                            Human-readable description of the NFV-MANO service.

                            This attribute can be modified with the PATCH
                            method.
                          type: string
                        manoServiceInterfaceIds:
                          description: "Reference to the NFV-MANO interfaces associated to the NFV-MANO service.  If cardinality is greater than one, the type of ManoServiceInterface  (see clause 5.6.3.3) shall be the same. The identifier of the  ManoServiceInterface is referred. \nNOTE:\tA cardinality greater than one supports having different interface  versions or apiEndpoints to be used for accessing the same instance of a  NFV-MANO service.\n"
                          type: array
                          items:
                            description: >
                              An identifier that is unique for the respective
                              type within a NFV-MANO functional entity, but that
                              need not be globally unique. Representation:
                              string of variable length..
                            type: string
                          minItems: 1
                        _links:
                          description: |
                            Links to resources related to this resource.
                          type: object
                          properties:
                            manoServiceInterfaces:
                              description: >
                                Link to the "individual NFV-MANO service
                                interface" resources with  information about the
                                associated interfaces to the NFV-MANO service.
                              type: array
                              items:
                                description: >
                                  This type represents a link to a resource
                                  using an absolute URI.
                                type: object
                                required:
                                  - href
                                properties:
                                  href:
                                    description: >
                                      String formatted according to IETF RFC
                                      3986.
                                    type: string
                              minItems: 1
                          required:
                            - manoServiceInterfaces
                      required:
                        - id
                        - name
                        - description
                        - manoServiceInterfaceIds
                        - _links
                  manoConfigurableParams:
                    description: >
                      # Warning: No definition found in the document
                      ManoConfigurableParams
                  manoApplicationState:
                    description: >
                      Information and current values of the NFV-MANO functional
                      entity’s application state. 
                    type: object
                    required:
                      - operationalState
                      - administrativeState
                      - usageState
                    properties:
                      operationalState:
                        description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                        type: string
                        enum:
                          - STARTED
                          - STOPPED
                          - STOPPING
                          - STARTING
                          - RESTARTING
                      administrativeState:
                        description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                        type: string
                        enum:
                          - LOCKED
                          - UNLOCKED
                          - LOCKING
                      usageState:
                        description: "The enumeration UsageStateEnumType defines values representing the usage  state of a managed entity.  The UsageStateEnumType shall comply with the provisions:\n  - IN_USE\tThe managed entity is currently being used.\n  - NOT_IN_USE\tThe managed entity is currently not being used.\n"
                        type: string
                        enum:
                          - IN_USE
                          - NOT_IN_USE
                  nfvoSpecificInfo:
                    description: >
                      This type represents information attributes specific to an
                      NFVO entity,  and that can be relevant to more than one
                      NFV-MANO service offered by an  NFVO entity. 
                    type: object
                    properties:
                      maxOnboardedNsdNum:
                        description: >
                          Maximum number of NSDs that can be on-boarded on the
                          NFVO. 

                          NOTE: If this attribute is not present, the value of
                          this parameter  is undefined.
                        type: integer
                      maxOnboardedVnfPkgNum:
                        description: >
                          Maximum number of VNF Packages that can be on-boarded
                          on the NFVO. 

                          NOTE: If this attribute is not present, the value of
                          this parameter  is undefined.
                        type: integer
                      supportedVnfdFormats:
                        description: |
                          Supported VNFD data formats.
                        type: object
                        properties:
                          vnfdFormat:
                            description: |
                              Name of the VNFD format.
                              Permitted values:
                                - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                                GS NFV-SOL 001 standard.
                                - YANG: The VNFD follows YANG definition according to ETSI 
                                GS NFV-SOL 006 standard.
                            type: string
                            enum:
                              - TOSCA
                              - YANG
                          standardVersion:
                            description: |
                              A version.
                            type: string
                        required:
                          - vnfdFormat
                          - standardVersion
                      supportedNsdFormats:
                        description: |
                          Supported NSD data formats.
                        type: object
                        properties:
                          nsdFormat:
                            description: |
                              Name of the NSD format.
                              Permitted values:
                                - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                                GS NFV-SOL 001 standard.
                                - YANG: The VNFD follows YANG definition according to ETSI 
                                GS NFV-SOL 006 standard.
                            type: string
                            enum:
                              - TOSCA
                              - YANG
                          standardVersion:
                            description: |
                              A version.
                            type: string
                        required:
                          - nsdFormat
                          - standardVersion
                    required:
                      - supportedVnfdFormats
                      - supportedNsdFormats
                  vnfmSpecificInfo:
                    description: >
                      This type represents information attributes specific to a
                      VNFM entity,  and that can be relevant to more than one
                      NFV-MANO service offered by  a VNFM entity.
                    type: object
                    properties:
                      resoruceMgmtModeSupport:
                        description: |
                          The supported resource management modes of the VNFM.
                          Permitted values:
                            - DIRECT: The VNFM supports direct mode only.
                            - INDIRECT: The VNFM supports indirect mode only.
                            - BOTH: The VNFM supports both direct and indirect mode.
                        type: string
                        enum:
                          - DIRECT
                          - INDIRECT
                          - BOTH
                      managedVnfInstanceInfos:
                        description: >
                          The kinds of VNF instances that can be managed, e.g.
                          to determine the  compatibility of a VNF with certain
                          VNFM according to the vnfmInfo  attribute in the VNFD
                          (see table 7.1.2.2-1 in ETSI GS NFV-IFA 011).
                        type: array
                        items:
                          type: string
                        minItems: 1
                      supportedVnfdFormats:
                        description: |
                          Supported VNFD data formats.
                        type: array
                        items:
                          type: object
                          properties:
                            vnfdFormat:
                              description: |
                                Name of the VNFD format.
                                Permitted values:
                                  - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                                  GS NFV-SOL 001 standard.
                                  - YANG: The VNFD follows YANG definition according to ETSI 
                                  GS NFV-SOL 006 standard.
                              type: string
                              enum:
                                - TOSCA
                                - YANG
                            standardVersion:
                              description: |
                                A version.
                              type: string
                          required:
                            - vnfdFormat
                            - standardVersion
                        minItems: 1
                    required:
                      - resoruceMgmtModeSupport
                      - managedVnfInstanceInfos
                      - supportedVnfdFormats
                  vimSpecificInfo:
                    description: >
                      This type represents information attributes specific to a
                      VIM entity,  and that can be relevant to more than one
                      NFV-MANO service offered by  a VIM entity.
                    type: object
                  _links:
                    description: |
                      Links to resources related to this resource.
                    type: object
                    required:
                      - self
                      - manoServiceInterfaces
                      - peerEntities
                      - changeState
                      - changeStateOpOccs
                    properties:
                      self:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                      manoServiceInterfaces:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                      peerEntities:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                      changeState:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                      changeStateOpOccs:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
    patch:
      description: >
        Modifies the NFV-MANO entity resource. Changes to the various
        configuration and information  attributes are applied to the NFV-MANO
        functional entity,  and are reflected in the representation of this
        resource. This method shall follow the provisions specified in the 
        tables 5.5.3.3.4-1 and 5.5.3.3.4-2 for URI query parameters,  request
        and response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      requestBody:
        description: >
          Parameters for the NFV-MANO configuration and information 
          modification, as defined in clause 5.6.2.3. The Content-Type header
          shall be set to "application/merge-patch+json"  according to IETF RFC
          7396.
        content:
          application/merge-patch+json:
            schema:
              description: >
                This type represents attribute modifications for configuration
                parameters  of an NFV-MANO functional entity. 
              type: object
              properties:
                name:
                  description: |
                    New value of the "name" attribute in "ManoEntity".
                  type: string
                description:
                  description: |
                    New value of the "description" attribute in "ManoEntity".
                  type: string
                clockSyncs:
                  description: >
                    Modifications of the "clockSyncs" attribute in the
                    "ManoEntityConfigurableParams". If present, these
                    modifications shall be applied according to the rules of
                    JSON Merge PATCH (see IETF RFC 7396).
                  type: object
                  additionalProperties:
                    description: >
                      This type represents parameters for connecting to an NTP
                      server. 
                    type: object
                    properties:
                      type:
                        description: |
                          Type of clock synchronization.
                          Permitted values:
                            - NTP: For Network Time Protocol (NTP) based clock synchronization.
                            - OTHER: For other types of clock synchronization.
                        type: string
                        enum:
                          - NTP
                          - OTHER
                      ntpServerInfo:
                        description: >
                          Information for the NTP based clock synchronization. 
                          Shall be present if type = "NTP".
                        type: object
                        properties:
                          ipAddress:
                            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
                          hostname:
                            description: "Indicates the hostname of the NTP server. \nNOTE:\tEither ipAddress or hostname shall be set, but not both  at the same time.\n"
                            type: string
                      otherClockSyncParams:
                        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
                    required:
                      - type
                defaultLogCompileBySizeValue:
                  description: |
                    Unsigned integer
                  type: number
                defaultLogCompileByTimerValue:
                  description: |
                    Unsigned integer
                  type: number
                manoServiceModifications:
                  description: >
                    New content of certain entries in the "manoServices"
                    attribute array  in the "ManoEntity", as defined below this
                    table.
                  type: array
                  items:
                    type: object
                    properties:
                      id:
                        description: >
                          An identifier that is unique for the respective type
                          within a NFV-MANO functional entity, but that need not
                          be globally unique. Representation: string of variable
                          length..
                        type: string
                      name:
                        description: "New value for the \"name\" attribute in the \"ManoService\". \nNOTE:\tAt least one of these attributes shall be provided if requesting  a modification of the NFV-MANO service identified by \"id\".\n"
                        type: string
                      description:
                        description: "New value for the \"description\" attribute in the \"ManoService\".\nNOTE:\tAt least one of these attributes shall be provided if requesting  a modification of the NFV-MANO service identified by \"id\".\n"
                        type: string
                    required:
                      - id
        required: true
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when the modification of configuration on the 
            NFV-MANO functional entity has been accepted and completed.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  This type represents attribute modifications that were
                  performed on the  "NFV-MANO entity" resource of the producer
                  NFV-MANO functional entity.  The attributes that can be
                  included consist of those requested to be  modified explicitly
                  in the "ManoConfigModificationRequest" data structure. 
                type: object
                properties:
                  name:
                    description: >
                      If present, this attribute signals modifications of the
                      "name"  attribute in "ManoEntity", as defined in clause
                      5.6.2.3
                    type: string
                  description:
                    description: >
                      If present, this attribute signals modifications of the
                      "description"  attribute in "ManoEntity", as defined in
                      clause 5.6.2.3.
                    type: string
                  clockSyncs:
                    description: >
                      If present, this attribute signals modifications of the
                      "clockSyncs" attribute in "ManoEntityConfigurableParams",
                      as defined in clause 5.6.2.3.
                    type: object
                    additionalProperties:
                      description: >
                        This type represents parameters for connecting to an NTP
                        server. 
                      type: object
                      properties:
                        type:
                          description: |
                            Type of clock synchronization.
                            Permitted values:
                              - NTP: For Network Time Protocol (NTP) based clock synchronization.
                              - OTHER: For other types of clock synchronization.
                          type: string
                          enum:
                            - NTP
                            - OTHER
                        ntpServerInfo:
                          description: >
                            Information for the NTP based clock
                            synchronization.  Shall be present if type = "NTP".
                          type: object
                          properties:
                            ipAddress:
                              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
                            hostname:
                              description: "Indicates the hostname of the NTP server. \nNOTE:\tEither ipAddress or hostname shall be set, but not both  at the same time.\n"
                              type: string
                        otherClockSyncParams:
                          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
                      required:
                        - type
                  defaultLogCompileBySizeValue:
                    description: |
                      Unsigned integer
                    type: number
                  defaultLogCompileByTimerValue:
                    description: |
                      Unsigned integer
                    type: number
                  manoServiceModifications:
                    description: >
                      If present, this attribute signals modifications of the
                      "manoServices"  attribute array in the "ManoEntity", as
                      defined in clause 5.6.2.3.
                    type: array
                    items:
                      type: object
                      properties:
                        id:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                        name:
                          description: >
                            If present, this attribute signals modification of
                            the "name"  attribute in the "ManoService".
                          type: string
                        description:
                          description: >
                            If present, this attribute signals modification of
                            the  "description" attribute in the "ManoService".
                          type: string
                      required:
                        - id
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '409':
          description: >
            409 CONFLICT

            Shall be returned upon the following error: The operation cannot  be
            executed currently, due to a conflict with the state of the 
            "NFV-MANO entity" resource.

            Typically, this is due to the fact that another configuration and 
            information modification is ongoing.

            The response body shall contain a ProblemDetails structure, in
            which  the "detail" attribute should convey more information about
            the error.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '412':
          description: >
            412 PRECONDITION FAILED

            Shall be returned upon the following error: A precondition given in 
            an HTTP request header is not fulfilled.

            Typically, this is due to an ETag mismatch, indicating that the
            resource  was modified by another entity.

            The response body should contain a ProblemDetails structure, in
            which  the "detail" attribute should convey more information about
            the error
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
  /mano_entity/change_state:
    post:
      description: >
        Requests to change the state of the NFV-MANO functional  entity
        application.

        This method shall follow the provisions specified in the tables 
        5.5.7.3.1-1 and 5.5.7.3.1-2 for URI query parameters, request and 
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      requestBody:
        description: >
          Parameters for the change state operation, as defined in clause
          5.6.2.8.
        content:
          application/json:
            schema:
              description: >
                This type represents request parameters for changing the state
                of a managed entity. 
              type: object
              properties:
                operationalStateChange:
                  description: "A change of operational state. Shall be present if the state change request refers to the operational state.  NOTE:\tIn the present document version, a request shall only include an  operational state change (attribute \"operationalStateChange\") or an  administrative state change request (attribute \"administrativeStateChange\"),  but not both.\n"
                  type: object
                  properties:
                    operationalStateAction:
                      description: "The enumeration ChangeOperationalStateEnumType defines permitted values  for the change state operation.  The ChangeOperationalStateEnumType shall comply with the provisions:\n  - START\tTo start the managed entity.\n  - STOP\tTo stop the managed entity.\n  - RESTART\tTo stop and start again the managed entity.\n"
                      type: string
                      enum:
                        - START
                        - STOP
                        - RESTART
                    stopType:
                      description: "The enumeration ChangeStateOpOccStateEnumType defines permitted values  for the change state operation. It shall comply with the provisions:\n  - GRACEFUL\tTo stop the managed entity immediately after accepting the request.\n  - FORCEFUL\tTo stop the managed entity attempting to gracefully discharge the entity from service.\n"
                      type: string
                      enum:
                        - GRACEFUL
                        - FORCEFUL
                    gracefulStopTimeout:
                      description: "The time internal (in seconds) to wait for the entity to be taken out  of service during graceful stop. \nNOTE:\tThe \"stopType\" shall only be provided when the \"operationalStateAction\"  attribute is equal to \"STOP\" or \"RESTART\".  The \"gracefulStopTimeout\" shall  be absent when the \"stopType\" attribute is equal to \"FORCEFUL\", and may  be provided otherwise.\n"
                      type: integer
                  required:
                    - operationalStateAction
                administrativeStateChange:
                  description: "A change of administrative state. Shall be present if the state change request refers to the administrative state. \nNOTE:\tIn the present document version, a request shall only include an  operational state change (attribute \"operationalStateChange\") or an  administrative state change request (attribute \"administrativeStateChange\"),  but not both.\n"
                  type: object
                  properties:
                    administrativeStateAction:
                      description: "The enumeration ChangeAdministrativeStateEnumType defines permitted values  for the change of administrative state operation.  The ChangeAdministrativeStateEnumType shall comply with the provisions:\n  - LOCK\tTo lock the managed entity.\n  - UNLOCK\tTo unlock the managed entity.\n"
                      type: string
                      enum:
                        - LOCK
                        - UNLOCK
                  required:
                    - administrativeStateAction
        required: true
      responses:
        '202':
          description: >
            202 ACCEPTED

            Shall be returned when the request has been accepted for processing.

            The response body shall be empty.

            The HTTP response shall include a "Location" HTTP header that
            contains  the URI of the newly-created "Individual change state
            operation occurrence" resource corresponding to the operation.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Location:
              description: >
                The resource URI of the created "Individual change state
                operation occurence" resource.
              schema:
                type: string
                format: url
                minimum: 1
                maximum: 1
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '409':
          description: >
            409 CONFLICT

            Shall be returned upon the following error: The operation cannot be 
            executed currently, due to a conflict with the state of the
            resource.

            Typically, this is due to the fact that the resource is in an
            incompatible  state, or that another change state operation is
            ongoing.

            The response body shall contain a ProblemDetails structure, in which
            the  "detail" attribute shall convey more information about the
            error.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
  /mano_entity/mano_interfaces:
    get:
      description: >
        Queries information about multiple NFV-MANO service interfaces of  the
        NFV-MANO functional entity. This method shall follow the provisions
        specified in the tables  5.5.10.3.2-1 and 5.5.10.3.2-2 for URI query
        parameters, request  and response data structures, and response codes.
      parameters:
        - name: filter
          description: >
            Attribute-based filtering expression according to clause 5.2 of 
            ETSI GS NFV-SOL 013. 

            The NFV-MANO functional entity shall support receiving this
            parameter  as part of the URI query string. The API consumer may
            supply this  parameter. 

            All attribute names that appear in the ManoServiceInterface and in
            data  types referenced from it shall be supported by the NFV-MANO
            functional  entity in the expression. 
          in: query
          required: false
          schema:
            type: string
        - name: all_fields
          description: >
            Include all complex attributes in the response. See clause  5.3 of
            ETSI GS NFV-SOL 013. The NFV-MANO functional entity  shall support
            this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: fields
          description: >
            Complex attributes to be included into the response. See clause  5.3
            of ETSI GS NFV-SOL 013 for details. The NFV-MANO functional  entity
            should support this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: exclude_fields
          description: >
            Complex attributes to be excluded from the response. See clause  5.3
            of ETSI GS NFV-SOL 013 for details. The NFV-MANO functional  entity
            should support this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: exclude_default
          description: >
            Indicates to exclude the following complex attributes from the 
            response. See clause 5.3 of ETSI GS NFV-SOL 013 for details.  The
            NFV-MANO functional entity shall support this parameter.

            The following attributes shall be excluded from the
            ManoServiceInterface  structure in the response body if this
            parameter is provided, or none of  the parameters "all_fields,"
            "fields", "exclude_fields", "exclude_default"  are provided: - none
          in: query
          required: false
          schema:
            type: string
        - name: nextpage_opaque_marker
          description: >
            Marker to obtain the next page of a paged response. Shall be
            supported by  the NFV-MANO functional entity if the entity supports
            alternative 2 (paging)  according to clause 5.4.2.1 of ETSI GS
            NFV-SOL 013 for this resource.
          in: query
          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
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when information about zero or more NFV-MANO 
            service interfaces has been queried successfully.

            The response body shall contain in an array the representations  of
            zero or more NFV-MANO service interfaces, as defined in  clause
            5.6.2.11.

            If the “filter" URI parameter or one of the "all_fields", "fields" 
            (if supported), "exclude_fields" (if supported) or
            "exclude_default"  URI parameters was supplied in the request, the
            data in the response  body shall have been transformed according to
            the rules specified in  clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL
            013, respectively.

            If the NFV-MANO functional entity supports alternative N°2 (paging) 
            according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this
            resource,  inclusion of the Link HTTP header in this response shall
            follow the  provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
          headers:
            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
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Link:
              description: >
                Reference to other resources. Link HTTP header in this response 
                shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL
                013.
              schema:
                type: string
                minimum: 0
                maximum: 1
          content:
            application/json:
              schema:
                type: array
                items:
                  description: >
                    This type represents an individual NFV-MANO service
                    interface produced by  an NFV-MANO functional entity. 
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier that is unique for the respective type
                        within a NFV-MANO functional entity, but that need not
                        be globally unique. Representation: string of variable
                        length..
                      type: string
                    name:
                      description: >
                        Human-readable name of the NFV-MANO functional entity
                        interface.

                        This attribute can be modified with the PATCH method.
                      type: string
                    type:
                      description: >
                        Type of the NFV-MANO service interface produced by the
                        NFV-MANO functional  entity. Valid values are defined in
                        clause 5.6.4.3.
                      type: string
                    standardVersion:
                      description: |
                        A version.
                      type: string
                    providerSpecificApiVersion:
                      description: |
                        A version.
                      type: string
                    apiVersion:
                      description: |
                        A version.
                      type: string
                    apiEndpoint:
                      description: |
                        Exposed API endpoint of the interface.
                      type: object
                      properties:
                        apiRoot:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                        apiName:
                          description: >
                            Indicates the interface name in an abbreviated form.
                            Shall be present  for ETSI NFV specified RESTful
                            NFV-MANO APIs. The {apiName} of each  interface is
                            defined in the standard the interface is compliant
                            to  (see also clause 4.1 of ETSI GS NFV-SOL 013).
                            May be present otherwise.
                          type: string
                        apiMajorVersion:
                          description: >
                            Indicates the current major version of the API.
                            Shall be present for  ETSI NFV specified RESTful
                            NFV-MANO APIs. The major version is defined  in the
                            standard the interface is compliant to (see also
                            clause 4.1 of  ETSI GS NFV-SOL 013). May be present
                            otherwise.
                          type: string
                        apiUri:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                      required:
                        - apiUri
                    maxConcurrentIntOpNumber:
                      description: "Maximum number of concurrent operation requests supported on this interface. \nNOTE:\tIf this attribute is not present, the value of this parameter  is undefined. Overload is handled by the error handling schemes defined  by the applicable API specification.\n"
                      type: integer
                    supportedOperations:
                      description: >
                        Information about supported operations of this
                        interface.
                      type: array
                      items:
                        type: object
                        properties:
                          operationName:
                            description: |
                              Name of the operation supported on the interface.
                            type: string
                          maxConcurrentOpNumber:
                            description: "Maximum number of concurrent requests supported by the interface operation. \nNOTE:\tIf this attribute is not present, the value of this parameter  is undefined. Overload is handled by the error handling schemes defined  by the applicable API specification.\n"
                            type: integer
                        required:
                          - operationName
                      minItems: 1
                    interfaceState:
                      description: |
                        State of the NFV-MANO service interface.
                      properties:
                        operationalState:
                          description: "The enumeration InterfaceOperationalStateEnumType defines values representing  the operational state of an NFV-MANO service interface type of managed entity.  The InterfaceOperationalStateEnumType shall comply with the provisions :\n   - STARTED\tThe managed entity is operational.\n   - STOPPED\tThe managed entity is not operational.\n   - STOPPING\tThe managed entity is in the transition to stop.\n   - STARTING\tThe managed entity is in the transition to start and become operational.\n"
                          type: string
                          enum:
                            - STARTED
                            - STOPPED
                            - STOPPING
                            - STARTING
                        administrativeState:
                          description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                          type: string
                          enum:
                            - LOCKED
                            - UNLOCKED
                            - LOCKING
                        usageState:
                          description: "The enumeration UsageStateEnumType defines values representing the usage  state of a managed entity.  The UsageStateEnumType shall comply with the provisions:\n  - IN_USE\tThe managed entity is currently being used.\n  - NOT_IN_USE\tThe managed entity is currently not being used.\n"
                          type: string
                          enum:
                            - IN_USE
                            - NOT_IN_USE
                      required:
                        - operationalState
                        - administrativeState
                        - usageState
                    securityInfo:
                      description: >
                        This type represents security related information of an
                        NFV-MANO  service interface produced by an NFV-MANO
                        functional entity. 
                      type: object
                      properties:
                        authType:
                          description: >
                            Type of API request authorization to be used by the
                            API producer.

                            The support of authorization methods for the API
                            producer is specified  in clause 8.3.6 of ETSI GS
                            NFV-SOL 013.

                            Permitted values:
                              - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                              - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
                              in IETF RFC 6749. 
                          type: array
                          items:
                            type: string
                            enum:
                              - TLS_TUNNEL
                              - OAUTH2
                          minItems: 1
                        oauthServerInfo:
                          description: >
                            OAuth 2.0 authorization server information and
                            configuration.
                          type: object
                          properties:
                            dynamicDiscovery:
                              description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                              type: object
                              properties:
                                webFingerHost:
                                  description: |
                                    String formatted according to IETF RFC 3986.
                                  type: string
                              required:
                                - webFingerHost
                            providedConfiguration:
                              description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                              type: object
                              properties:
                                authServerId:
                                  description: |
                                    String formatted according to IETF RFC 3986.
                                  type: string
                              required:
                                - authServerId
                            tlsCipherSuites:
                              description: >
                                List of cipher suites that shall be declared as
                                supported by the  API producer when performing
                                the SSL or TLS negotiation with the 
                                authorization server. Valid values of cipher
                                suites are defined  in IETF RFC 8447.
                              type: array
                              items:
                                type: string
                              minItems: 1
                          required:
                            - providedConfiguration
                            - tlsCipherSuites
                        tlsTunnelInfo:
                          description: >
                            Information and configuration related to the use of
                            TLS tunnel.  Shall be present if authType contains
                            "TLS_TUNNEL".
                          type: object
                          properties:
                            tlsTunnelCipherSuites:
                              description: >-
                                List of cipher suites that shall be declared as
                                supported by the API producer when performing
                                the SSL or TLS negotiation with the API client.
                                Valid values of cipher suites are defined in
                                IETF RFC 8447.
                              type: array
                              items:
                                type: string
                              minItems: 1
                          required:
                            - tlsTunnelCipherSuites
                      required:
                        - authType
                        - oauthServerInfo
                    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
                  required:
                    - id
                    - name
                    - type
                    - standardVersion
                    - providerSpecificApiVersion
                    - apiVersion
                    - apiEndpoint
                    - supportedOperations
                    - interfaceState
        '400':
          description: |
            400 BAD REQUEST
            Shall be returned upon the following errors: 
              - Invalid attribute-based filtering expression.
                The response body shall contain a ProblemDetails structure, in which 
                the "detail" attribute should convey more information about the error.
              - Invalid attribute selector.
                The response body shall contain a ProblemDetails structure, in which 
                the "detail" attribute should convey more information about the error.
              - Response too big.
                If the NFV-MANO functional entity supports alternative N°1 (error) 
                according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
                this error response shall follow the provisions in clause 5.4.2.2 of 
                ETSI GS NFV-SOL 013.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
  '/mano_entity/mano_interfaces/{manoServiceInterfaceId}':
    parameters:
      - name: manoServiceInterfaceId
        in: path
        description: Identifier of the MANO service interface.
        required: true
        schema:
          description: |
            An identifier with the intention of being globally unique.
          type: string
    get:
      description: >
        retrieves information about an NFV-MANO service interface of the 
        producer NFV-MANO functional entity by reading an "Individual  NFV-MANO
        service interface" resource.

        This method shall follow the provisions specified in the tables 
        5.5.11.3.2-1 and 5.5.11.3.2-2 for URI query parameters, request  and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when information about an individual NFV-MANO 
            service interface has been read successfully.

            The response body shall contain a representation of the NFV-MANO 
            service interface, as defined in clause 5.6.2.11.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  This type represents an individual NFV-MANO service interface
                  produced by  an NFV-MANO functional entity. 
                type: object
                properties:
                  id:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                  name:
                    description: >
                      Human-readable name of the NFV-MANO functional entity
                      interface.

                      This attribute can be modified with the PATCH method.
                    type: string
                  type:
                    description: >
                      Type of the NFV-MANO service interface produced by the
                      NFV-MANO functional  entity. Valid values are defined in
                      clause 5.6.4.3.
                    type: string
                  standardVersion:
                    description: |
                      A version.
                    type: string
                  providerSpecificApiVersion:
                    description: |
                      A version.
                    type: string
                  apiVersion:
                    description: |
                      A version.
                    type: string
                  apiEndpoint:
                    description: |
                      Exposed API endpoint of the interface.
                    type: object
                    properties:
                      apiRoot:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                      apiName:
                        description: >
                          Indicates the interface name in an abbreviated form.
                          Shall be present  for ETSI NFV specified RESTful
                          NFV-MANO APIs. The {apiName} of each  interface is
                          defined in the standard the interface is compliant to 
                          (see also clause 4.1 of ETSI GS NFV-SOL 013). May be
                          present otherwise.
                        type: string
                      apiMajorVersion:
                        description: >
                          Indicates the current major version of the API. Shall
                          be present for  ETSI NFV specified RESTful NFV-MANO
                          APIs. The major version is defined  in the standard
                          the interface is compliant to (see also clause 4.1 of 
                          ETSI GS NFV-SOL 013). May be present otherwise.
                        type: string
                      apiUri:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                    required:
                      - apiUri
                  maxConcurrentIntOpNumber:
                    description: "Maximum number of concurrent operation requests supported on this interface. \nNOTE:\tIf this attribute is not present, the value of this parameter  is undefined. Overload is handled by the error handling schemes defined  by the applicable API specification.\n"
                    type: integer
                  supportedOperations:
                    description: |
                      Information about supported operations of this interface.
                    type: array
                    items:
                      type: object
                      properties:
                        operationName:
                          description: |
                            Name of the operation supported on the interface.
                          type: string
                        maxConcurrentOpNumber:
                          description: "Maximum number of concurrent requests supported by the interface operation. \nNOTE:\tIf this attribute is not present, the value of this parameter  is undefined. Overload is handled by the error handling schemes defined  by the applicable API specification.\n"
                          type: integer
                      required:
                        - operationName
                    minItems: 1
                  interfaceState:
                    description: |
                      State of the NFV-MANO service interface.
                    properties:
                      operationalState:
                        description: "The enumeration InterfaceOperationalStateEnumType defines values representing  the operational state of an NFV-MANO service interface type of managed entity.  The InterfaceOperationalStateEnumType shall comply with the provisions :\n   - STARTED\tThe managed entity is operational.\n   - STOPPED\tThe managed entity is not operational.\n   - STOPPING\tThe managed entity is in the transition to stop.\n   - STARTING\tThe managed entity is in the transition to start and become operational.\n"
                        type: string
                        enum:
                          - STARTED
                          - STOPPED
                          - STOPPING
                          - STARTING
                      administrativeState:
                        description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                        type: string
                        enum:
                          - LOCKED
                          - UNLOCKED
                          - LOCKING
                      usageState:
                        description: "The enumeration UsageStateEnumType defines values representing the usage  state of a managed entity.  The UsageStateEnumType shall comply with the provisions:\n  - IN_USE\tThe managed entity is currently being used.\n  - NOT_IN_USE\tThe managed entity is currently not being used.\n"
                        type: string
                        enum:
                          - IN_USE
                          - NOT_IN_USE
                    required:
                      - operationalState
                      - administrativeState
                      - usageState
                  securityInfo:
                    description: >
                      This type represents security related information of an
                      NFV-MANO  service interface produced by an NFV-MANO
                      functional entity. 
                    type: object
                    properties:
                      authType:
                        description: >
                          Type of API request authorization to be used by the
                          API producer.

                          The support of authorization methods for the API
                          producer is specified  in clause 8.3.6 of ETSI GS
                          NFV-SOL 013.

                          Permitted values:
                            - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                            - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
                            in IETF RFC 6749. 
                        type: array
                        items:
                          type: string
                          enum:
                            - TLS_TUNNEL
                            - OAUTH2
                        minItems: 1
                      oauthServerInfo:
                        description: >
                          OAuth 2.0 authorization server information and
                          configuration.
                        type: object
                        properties:
                          dynamicDiscovery:
                            description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                            type: object
                            properties:
                              webFingerHost:
                                description: |
                                  String formatted according to IETF RFC 3986.
                                type: string
                            required:
                              - webFingerHost
                          providedConfiguration:
                            description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                            type: object
                            properties:
                              authServerId:
                                description: |
                                  String formatted according to IETF RFC 3986.
                                type: string
                            required:
                              - authServerId
                          tlsCipherSuites:
                            description: >
                              List of cipher suites that shall be declared as
                              supported by the  API producer when performing the
                              SSL or TLS negotiation with the  authorization
                              server. Valid values of cipher suites are defined 
                              in IETF RFC 8447.
                            type: array
                            items:
                              type: string
                            minItems: 1
                        required:
                          - providedConfiguration
                          - tlsCipherSuites
                      tlsTunnelInfo:
                        description: >
                          Information and configuration related to the use of
                          TLS tunnel.  Shall be present if authType contains
                          "TLS_TUNNEL".
                        type: object
                        properties:
                          tlsTunnelCipherSuites:
                            description: >-
                              List of cipher suites that shall be declared as
                              supported by the API producer when performing the
                              SSL or TLS negotiation with the API client. Valid
                              values of cipher suites are defined in IETF RFC
                              8447.
                            type: array
                            items:
                              type: string
                            minItems: 1
                        required:
                          - tlsTunnelCipherSuites
                    required:
                      - authType
                      - oauthServerInfo
                  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
                required:
                  - id
                  - name
                  - type
                  - standardVersion
                  - providerSpecificApiVersion
                  - apiVersion
                  - apiEndpoint
                  - supportedOperations
                  - interfaceState
        '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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
    patch:
      description: >
        Modifies an "Individual NFV-MANO service interface" resource.

        Changes to the configurable parameters of the corresponding  NFV-MANO
        service interface are applied to the information managed  by the
        producer NFV-MANO functional entity and reflected in the  representation
        of this resource.

        This method shall follow the provisions specified in the tables 
        5.5.11.3.4-1 and 5.5.11.3.4-2 for URI query parameters, request  and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      requestBody:
        description: >
          Parameters for the modification of configuration parameters of  the
          NFV-MANO service interface, as defined in clause 5.6.2.12.

          The Content-Type header shall be set to "application/merge-patch+json"
          according to IETF RFC 7396.
        content:
          application/merge-patch+json:
            schema:
              description: >
                This type represents attribute modifications for configuration
                parameters of  an NFV-MANO service interface of the producer
                NFV-MANO functional entity. 
              type: object
              properties:
                name:
                  description: "New value of the \"name\" attribute in \"ManoServiceInterface\". \nNOTE:\tChanging the name does not change the corresponding standardized  API name in the resource URI (refer to \"{apiName}\" defined in clause 4.1  of ETSI GS NFV-SOL 013).\n"
                  type: string
                apiRoot:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
                apiUri:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
                securityInfo:
                  description: >
                    This type represents security related information of an
                    NFV-MANO  service interface produced by an NFV-MANO
                    functional entity. 
                  type: object
                  properties:
                    authType:
                      description: >
                        Type of API request authorization to be used by the API
                        producer.

                        The support of authorization methods for the API
                        producer is specified  in clause 8.3.6 of ETSI GS
                        NFV-SOL 013.

                        Permitted values:
                          - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                          - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
                          in IETF RFC 6749. 
                      type: array
                      items:
                        type: string
                        enum:
                          - TLS_TUNNEL
                          - OAUTH2
                      minItems: 1
                    oauthServerInfo:
                      description: >
                        OAuth 2.0 authorization server information and
                        configuration.
                      type: object
                      properties:
                        dynamicDiscovery:
                          description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                          type: object
                          properties:
                            webFingerHost:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                          required:
                            - webFingerHost
                        providedConfiguration:
                          description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                          type: object
                          properties:
                            authServerId:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                          required:
                            - authServerId
                        tlsCipherSuites:
                          description: >
                            List of cipher suites that shall be declared as
                            supported by the  API producer when performing the
                            SSL or TLS negotiation with the  authorization
                            server. Valid values of cipher suites are defined 
                            in IETF RFC 8447.
                          type: array
                          items:
                            type: string
                          minItems: 1
                      required:
                        - providedConfiguration
                        - tlsCipherSuites
                    tlsTunnelInfo:
                      description: >
                        Information and configuration related to the use of TLS
                        tunnel.  Shall be present if authType contains
                        "TLS_TUNNEL".
                      type: object
                      properties:
                        tlsTunnelCipherSuites:
                          description: >-
                            List of cipher suites that shall be declared as
                            supported by the API producer when performing the
                            SSL or TLS negotiation with the API client. Valid
                            values of cipher suites are defined in IETF RFC
                            8447.
                          type: array
                          items:
                            type: string
                          minItems: 1
                      required:
                        - tlsTunnelCipherSuites
                  required:
                    - authType
                    - oauthServerInfo
                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
        required: true
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when the request has been accepted and completed.

            The response body shall contain a representation of the attribute 
            modifications for the "Individual NFV-MANO service interface"
            resource, as defined in clause 5.6.2.13.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  This type represents attribute modifications that were
                  performed on an  Individual NFV-MANO service interface"
                  resource. The attributes that can  be included consist of
                  those requested to be modified explicitly in the 
                  "ManoServiceInterfaceModificationRequest" data structure. If
                  applicable,  additional attributes of the
                  "ManoServiceInterface" data structure that  were modified
                  implicitly shall also be provided. 
                type: object
                properties:
                  name:
                    description: >
                      If present, this attribute signals modifications of the
                      "name" attribute in  "ManoServiceInterface", as defined in
                      clause 5.6.2.11.
                    type: string
                  apiRoot:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                  apiUri:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                  securityInfo:
                    description: >
                      This type represents security related information of an
                      NFV-MANO  service interface produced by an NFV-MANO
                      functional entity. 
                    type: object
                    properties:
                      authType:
                        description: >
                          Type of API request authorization to be used by the
                          API producer.

                          The support of authorization methods for the API
                          producer is specified  in clause 8.3.6 of ETSI GS
                          NFV-SOL 013.

                          Permitted values:
                            - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                            - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
                            in IETF RFC 6749. 
                        type: array
                        items:
                          type: string
                          enum:
                            - TLS_TUNNEL
                            - OAUTH2
                        minItems: 1
                      oauthServerInfo:
                        description: >
                          OAuth 2.0 authorization server information and
                          configuration.
                        type: object
                        properties:
                          dynamicDiscovery:
                            description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                            type: object
                            properties:
                              webFingerHost:
                                description: |
                                  String formatted according to IETF RFC 3986.
                                type: string
                            required:
                              - webFingerHost
                          providedConfiguration:
                            description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                            type: object
                            properties:
                              authServerId:
                                description: |
                                  String formatted according to IETF RFC 3986.
                                type: string
                            required:
                              - authServerId
                          tlsCipherSuites:
                            description: >
                              List of cipher suites that shall be declared as
                              supported by the  API producer when performing the
                              SSL or TLS negotiation with the  authorization
                              server. Valid values of cipher suites are defined 
                              in IETF RFC 8447.
                            type: array
                            items:
                              type: string
                            minItems: 1
                        required:
                          - providedConfiguration
                          - tlsCipherSuites
                      tlsTunnelInfo:
                        description: >
                          Information and configuration related to the use of
                          TLS tunnel.  Shall be present if authType contains
                          "TLS_TUNNEL".
                        type: object
                        properties:
                          tlsTunnelCipherSuites:
                            description: >-
                              List of cipher suites that shall be declared as
                              supported by the API producer when performing the
                              SSL or TLS negotiation with the API client. Valid
                              values of cipher suites are defined in IETF RFC
                              8447.
                            type: array
                            items:
                              type: string
                            minItems: 1
                        required:
                          - tlsTunnelCipherSuites
                    required:
                      - authType
                      - oauthServerInfo
                  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
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '409':
          description: >
            409 CONFLICT

            Shall be returned upon the following error: The operation cannot  be
            executed currently, due to a conflict with the state of the 
            "Individual NFV-MANO service interface" resource.

            Typically, this is due to the fact that another operation is 
            ongoing.

            The response body shall contain a ProblemDetails structure,  in
            which the "detail" attribute should convey more information  about
            the error.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '412':
          description: >
            412 PRECONDITION FAILED

            Shall be returned upon the following error: A precondition given  in
            an HTTP request header is not fulfilled.

            Typically, this is due to an ETag mismatch, indicating that the 
            resource was modified by another entity.

            The response body should contain a ProblemDetails structure,  in
            which the "detail" attribute should convey more information  about
            the error.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
  '/mano_entity/mano_interfaces/{manoServiceInterfaceId}/change_state':
    parameters:
      - name: manoServiceInterfaceId
        in: path
        description: Identifier of the MANO service interface.
        required: true
        schema:
          description: |
            An identifier with the intention of being globally unique.
          type: string
    post:
      description: >
        Requests to change the state of the NFV-MANO service interface  produced
        by the NFV-MANO functional entity.

        This method shall follow the provisions specified in the tables 
        5.5.12.3.1-1 and 5.5.12.3.1-2 for URI query parameters, request  and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      requestBody:
        description: >
          Parameters for the change state operation, as defined in  clause
          5.6.2.8.
        content:
          application/json:
            schema:
              description: >
                This type represents request parameters for changing the state
                of a managed entity. 
              type: object
              properties:
                operationalStateChange:
                  description: "A change of operational state. Shall be present if the state change request refers to the operational state.  NOTE:\tIn the present document version, a request shall only include an  operational state change (attribute \"operationalStateChange\") or an  administrative state change request (attribute \"administrativeStateChange\"),  but not both.\n"
                  type: object
                  properties:
                    operationalStateAction:
                      description: "The enumeration ChangeOperationalStateEnumType defines permitted values  for the change state operation.  The ChangeOperationalStateEnumType shall comply with the provisions:\n  - START\tTo start the managed entity.\n  - STOP\tTo stop the managed entity.\n  - RESTART\tTo stop and start again the managed entity.\n"
                      type: string
                      enum:
                        - START
                        - STOP
                        - RESTART
                    stopType:
                      description: "The enumeration ChangeStateOpOccStateEnumType defines permitted values  for the change state operation. It shall comply with the provisions:\n  - GRACEFUL\tTo stop the managed entity immediately after accepting the request.\n  - FORCEFUL\tTo stop the managed entity attempting to gracefully discharge the entity from service.\n"
                      type: string
                      enum:
                        - GRACEFUL
                        - FORCEFUL
                    gracefulStopTimeout:
                      description: "The time internal (in seconds) to wait for the entity to be taken out  of service during graceful stop. \nNOTE:\tThe \"stopType\" shall only be provided when the \"operationalStateAction\"  attribute is equal to \"STOP\" or \"RESTART\".  The \"gracefulStopTimeout\" shall  be absent when the \"stopType\" attribute is equal to \"FORCEFUL\", and may  be provided otherwise.\n"
                      type: integer
                  required:
                    - operationalStateAction
                administrativeStateChange:
                  description: "A change of administrative state. Shall be present if the state change request refers to the administrative state. \nNOTE:\tIn the present document version, a request shall only include an  operational state change (attribute \"operationalStateChange\") or an  administrative state change request (attribute \"administrativeStateChange\"),  but not both.\n"
                  type: object
                  properties:
                    administrativeStateAction:
                      description: "The enumeration ChangeAdministrativeStateEnumType defines permitted values  for the change of administrative state operation.  The ChangeAdministrativeStateEnumType shall comply with the provisions:\n  - LOCK\tTo lock the managed entity.\n  - UNLOCK\tTo unlock the managed entity.\n"
                      type: string
                      enum:
                        - LOCK
                        - UNLOCK
                  required:
                    - administrativeStateAction
        required: true
      responses:
        '202':
          description: >
            202 ACCEPTED

            Shall be returned when the request has been accepted for 
            processing.

            The response body shall be empty.

            The HTTP response shall include a “Location” HTTP header that 
            contains the URI of the newly-created "Individual change state 
            operation occurrence" resource corresponding to the operation.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Location:
              description: >
                The resource URI of the created "Individual change state 
                operation occurence" resource.
              schema:
                type: string
                format: url
                minimum: 1
                maximum: 1
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '409':
          description: >
            409 CONFLICT

            Shall be returned upon the following error: The operation cannot be 
            executed currently, due to a conflict with the state of the
            resource.

            Typically, this is due to the fact that the resource is in an
            incompatible  state, or that another change state operation is
            ongoing.

            The response body shall contain a ProblemDetails structure, in which
            the  "detail" attribute shall convey more information about the
            error.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
  /subscriptions:
    post:
      description: >
        Creates a new subscription.

        This method shall follow the provisions specified in the tables 
        5.5.4.3.1-1 and 5.5.4.3.1-2 for URI query parameters, request and 
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      requestBody:
        description: >
          Details of the subscription to be created, as defined in  clause
          5.6.2.5-1.
        content:
          application/json:
            schema:
              description: >
                This type represents a subscription request related to
                notifications  about NFV-MANO configuration and information
                management changes. 
              type: object
              properties:
                filter:
                  description: >
                    This type represents a subscription filter related to
                    notifications  about NFV-MANO configuration and information
                    management. 
                  type: object
                  properties:
                    manoEntitySubscriptionFilter:
                      description: >
                        This type represents subscription filter criteria to
                        match NFV-MANO functional  entities and their associated
                        managed objects. 
                      type: object
                      properties:
                        manoEntityId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        manoServiceIds:
                          description: "manoServiceIds\tIdentifierInManoEntity\t0..N\tIf present, match NFV-MANO  services with an instance identifier listed in this attribute.\nThe attributes \"manoServiceIds\" and \"manoServiceNames\" are alternatives  to reference to NFV-MANO services in a filter. They should not be used  together in the same filter instance, but one alternative should be chosen.\n"
                          type: array
                          items:
                            description: >
                              An identifier that is unique for the respective
                              type within a NFV-MANO functional entity, but that
                              need not be globally unique. Representation:
                              string of variable length..
                            type: string
                        manoServiceNames:
                          description: >
                            If present, match NFV-MANO services with an NFV-MANO
                            service name listed  in this attribute.

                            The attributes "manoServiceIds" and
                            "manoServiceNames" are alternatives  to reference to
                            NFV-MANO services in a filter. They should not be
                            used  together in the same filter instance, but one
                            alternative should be chosen.
                          type: array
                          items:
                            type: string
                        manoServiceInterfaceIds:
                          description: >
                            If present, match NFV-MANO functional entity
                            produced interfaces with an  instance identifier
                            listed in this attribute.

                            The attributes "manoServiceInterfaceIds" and
                            "manoServiceInterfaceNames"  are alternatives to
                            reference to NFV-MANO functional entity produced 
                            interfaces in a filter. They should not be used both
                            in the same filter  instance, but one alternative
                            should be chosen.
                          type: array
                          items:
                            description: >
                              An identifier that is unique for the respective
                              type within a NFV-MANO functional entity, but that
                              need not be globally unique. Representation:
                              string of variable length..
                            type: string
                        manoServiceInterfaceNames:
                          description: >
                            If present, match NFV-MANO functional entity
                            produced interfaces with an  instance Name listed in
                            this attribute.

                            The attributes "manoServiceInterfaceIds" and
                            "manoServiceInterfaceNames"  are alternatives to
                            reference to NFV-MANO functional entity produced 
                            interfaces in a filter. They should not be used both
                            in the same filter  instance, but one alternative
                            should be chosen.
                          type: array
                          items:
                            type: string
                        consumedManoInterfaceIds:
                          description: >
                            If present, match NFV-MANO functional entity
                            consumed interfaces with an  instance identifier
                            listed in this attribute.

                            The attributes "consumedManoInterfaceIds" and
                            "consumedManoInterfaceNames"  are alternatives to
                            reference to NFV-MANO functional entity consumed 
                            interfaces in a filter. They should not be used both
                            in the same filter  instance, but one alternative
                            should be chosen.
                          type: array
                          items:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                        consumedManoInterfaceNames:
                          description: >
                            If present, match NFV-MANO functional entity
                            consumed interfaces with an  instance Name listed in
                            this attribute.

                            The attributes "consumedManoInterfaceIds" and
                            "consumedManoInterfaceNames"  are alternatives to
                            reference to NFV-MANO functional entity consumed 
                            interfaces in a filter. They should not be used both
                            in the same filter  instance, but one alternative
                            should be chosen.
                          type: array
                          items:
                            type: string
                    notificationTypes:
                      description: "Match particular notification types. \nPermitted values:\n  - InformationChangedNotification\n  - ChangeStateNotification\n\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are  spelled exactly as the names of the notification types to facilitate  automated code generation systems.\n"
                      type: array
                      items:
                        type: string
                        enum:
                          - InformationChangedNotification
                          - ChangeStateNotification
                callbackUri:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
                authentication:
                  type: object
                  required:
                    - authType
                  properties:
                    authType:
                      description: >
                        Defines the types of Authentication / Authorization
                        which the API consumer is willing to accept when
                        receiving a notification. Permitted values: * BASIC: In
                        every HTTP request to the notification endpoint, use
                          HTTP Basic authentication with the client credentials.
                        * OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to
                        the
                          notification endpoint, use an OAuth 2.0 Bearer token, obtained
                          using the client credentials grant type.
                        * TLS_CERT: Every HTTP request to the notification
                        endpoint is sent
                          over a mutually authenticated TLS session, i.e. not only the
                          server is authenticated, but also the client is authenticated
                          during the TLS tunnel setup.
                      type: array
                      items:
                        type: string
                        enum:
                          - BASIC
                          - OAUTH2_CLIENT_CREDENTIALS
                          - TLS_CERT
                    paramsBasic:
                      description: >
                        Parameters for authentication/authorization using BASIC.
                        Shall be present if authType is "BASIC" and the
                        contained information has not been provisioned out of
                        band. Shall be absent otherwise.
                      type: object
                      properties:
                        userName:
                          description: >
                            Username to be used in HTTP Basic authentication.
                            Shall be present if it has not been provisioned out
                            of band.
                          type: string
                        password:
                          description: >
                            Password to be used in HTTP Basic authentication.
                            Shall be present if it has not been provisioned out
                            of band.
                          type: string
                    paramsOauth2ClientCredentials:
                      description: >
                        Parameters for authentication/authorization using
                        OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType
                        is "OAUTH2_CLIENT_CREDENTIALS" and the contained
                        information has not been provisioned out of band. Shall
                        be absent otherwise.
                      type: object
                      properties:
                        clientId:
                          description: >
                            Client identifier to be used in the access token
                            request of the OAuth 2.0 client credentials grant
                            type. Shall be present if it has not been
                            provisioned out of band. The clientId and
                            clientPassword passed in a subscription shall not be
                            the same as the clientId and clientPassword that are
                            used to obtain authorization for API requests.
                            Client credentials may differ between subscriptions.
                            The value of clientPassword should be generated by a
                            random process.
                          type: string
                        clientPassword:
                          description: >
                            Client password to be used in the access token
                            request of the OAuth 2.0 client credentials grant
                            type. Shall be present if it has not been
                            provisioned out of band. The clientId and
                            clientPassword passed in a subscription shall not be
                            the same as the clientId and clientPassword that are
                            used to obtain authorization for API requests.
                            Client credentials may differ between subscriptions.
                            The value of clientPassword should be generated by a
                            random process.
                          type: string
                        tokenEndpoint:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
              required:
                - callbackUri
        required: true
      responses:
        '201':
          description: >
            201 CREATED

            Shall be returned when the subscription has been created 
            successfully.

            The response body shall contain a representation of the  created
            "Individual subscription" resource.

            The HTTP response shall include a "Location" HTTP header  that
            points to the created "Individual subscription" resource.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Location:
              description: >
                The resource URI of the created "Individual subscription"
                resource.
              schema:
                type: string
                format: url
                minimum: 1
                maximum: 1
          content:
            application/json:
              schema:
                description: >
                  This type represents a subscription related to notifications
                  about  NFV-MANO configuration and information management
                  changes
                type: object
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  filter:
                    description: >
                      This type represents a subscription filter related to
                      notifications  about NFV-MANO configuration and
                      information management. 
                    type: object
                    properties:
                      manoEntitySubscriptionFilter:
                        description: >
                          This type represents subscription filter criteria to
                          match NFV-MANO functional  entities and their
                          associated managed objects. 
                        type: object
                        properties:
                          manoEntityId:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                          manoServiceIds:
                            description: "manoServiceIds\tIdentifierInManoEntity\t0..N\tIf present, match NFV-MANO  services with an instance identifier listed in this attribute.\nThe attributes \"manoServiceIds\" and \"manoServiceNames\" are alternatives  to reference to NFV-MANO services in a filter. They should not be used  together in the same filter instance, but one alternative should be chosen.\n"
                            type: array
                            items:
                              description: >
                                An identifier that is unique for the respective
                                type within a NFV-MANO functional entity, but
                                that need not be globally unique.
                                Representation: string of variable length..
                              type: string
                          manoServiceNames:
                            description: >
                              If present, match NFV-MANO services with an
                              NFV-MANO service name listed  in this attribute.

                              The attributes "manoServiceIds" and
                              "manoServiceNames" are alternatives  to reference
                              to NFV-MANO services in a filter. They should not
                              be used  together in the same filter instance, but
                              one alternative should be chosen.
                            type: array
                            items:
                              type: string
                          manoServiceInterfaceIds:
                            description: >
                              If present, match NFV-MANO functional entity
                              produced interfaces with an  instance identifier
                              listed in this attribute.

                              The attributes "manoServiceInterfaceIds" and
                              "manoServiceInterfaceNames"  are alternatives to
                              reference to NFV-MANO functional entity produced 
                              interfaces in a filter. They should not be used
                              both in the same filter  instance, but one
                              alternative should be chosen.
                            type: array
                            items:
                              description: >
                                An identifier that is unique for the respective
                                type within a NFV-MANO functional entity, but
                                that need not be globally unique.
                                Representation: string of variable length..
                              type: string
                          manoServiceInterfaceNames:
                            description: >
                              If present, match NFV-MANO functional entity
                              produced interfaces with an  instance Name listed
                              in this attribute.

                              The attributes "manoServiceInterfaceIds" and
                              "manoServiceInterfaceNames"  are alternatives to
                              reference to NFV-MANO functional entity produced 
                              interfaces in a filter. They should not be used
                              both in the same filter  instance, but one
                              alternative should be chosen.
                            type: array
                            items:
                              type: string
                          consumedManoInterfaceIds:
                            description: >
                              If present, match NFV-MANO functional entity
                              consumed interfaces with an  instance identifier
                              listed in this attribute.

                              The attributes "consumedManoInterfaceIds" and
                              "consumedManoInterfaceNames"  are alternatives to
                              reference to NFV-MANO functional entity consumed 
                              interfaces in a filter. They should not be used
                              both in the same filter  instance, but one
                              alternative should be chosen.
                            type: array
                            items:
                              description: >
                                An identifier with the intention of being
                                globally unique.
                              type: string
                          consumedManoInterfaceNames:
                            description: >
                              If present, match NFV-MANO functional entity
                              consumed interfaces with an  instance Name listed
                              in this attribute.

                              The attributes "consumedManoInterfaceIds" and
                              "consumedManoInterfaceNames"  are alternatives to
                              reference to NFV-MANO functional entity consumed 
                              interfaces in a filter. They should not be used
                              both in the same filter  instance, but one
                              alternative should be chosen.
                            type: array
                            items:
                              type: string
                      notificationTypes:
                        description: "Match particular notification types. \nPermitted values:\n  - InformationChangedNotification\n  - ChangeStateNotification\n\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are  spelled exactly as the names of the notification types to facilitate  automated code generation systems.\n"
                        type: array
                        items:
                          type: string
                          enum:
                            - InformationChangedNotification
                            - ChangeStateNotification
                  callbackUri:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                  _links:
                    description: |
                      Links to resources related to this resource.
                    type: object
                    properties:
                      self:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                    required:
                      - self
                required:
                  - id
                  - callbackUri
                  - _links
        '303':
          description: >
            303 SEE OTHER

            SShall be returned when a subscription with the same  callbackURI
            and the same filter already exists and the  policy of NFV-MANO
            functional entity is to not create  redundant subscriptions.

            The HTTP response shall include a "Location" HTTP header  that
            contains the resource URI of the existing "Individual  subscription"
            resource.

            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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Location:
              description: >
                The resource URI of the created "Individual subscription"
                resource.
              schema:
                type: string
                format: url
                minimum: 1
                maximum: 1
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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: >
        queries the list of active subscriptions of the API consumer that 
        invokes the method. It can be used, e.g., for resynchronization  after
        error situations.

        This method shall follow the provisions specified in the tables 
        5.5.4.3.2-1 and 5.5.4.3.2-2 for URI query parameters, request  and
        response data structures, and response codes.
      parameters:
        - name: filter
          description: >
            Attribute-based filtering expression according to clause 5.2 of 
            ETSI GS NFV-SOL 013. 

            The NFV-MANO functional entity shall support receiving this
            parameter  as part of the URI query string. The API consumer may
            supply this  parameter. 

            All attribute names that appear in the CimSubscription and in data 
            types referenced from it shall be supported by the NFV-MANO
            functional  entity in the expression. 
          in: query
          required: false
          schema:
            type: string
        - name: nextpage_opaque_marker
          description: >
            Marker to obtain the next page of a paged response. Shall be
            supported by  the NFV-MANO functional entity if the entity supports
            alternative 2 (paging)  according to clause 5.4.2.1 of ETSI GS
            NFV-SOL 013 for this resource.
          in: query
          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
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when the list of subscriptions has been queried 
            successfully.

            The response body shall contain in an array the representations of 
            all active subscriptions of the functional block that invokes the 
            method, i.e., zero or more representations of NFV-MANO
            configuration  and information management subscriptions as defined
            in clause 5.6.2.6.

            If the "filter" URI parameter was supplied in the request, the data
            in  the response body shall have been transformed according to the
            rules  specified in clause 5.2.2 of ETSI GS NFV-SOL 013.

            If the NFV-MANO functional entity supports alternative N°2 (paging) 
            according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this
            resource,  inclusion of the Link HTTP header in this response shall
            follow the  provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
          headers:
            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
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Link:
              description: >
                Reference to other resources. Link HTTP header in this response 
                shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL
                013.
              schema:
                type: string
                minimum: 0
                maximum: 1
          content:
            application/json:
              schema:
                type: array
                items:
                  description: >
                    This type represents a subscription related to notifications
                    about  NFV-MANO configuration and information management
                    changes
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    filter:
                      description: >
                        This type represents a subscription filter related to
                        notifications  about NFV-MANO configuration and
                        information management. 
                      type: object
                      properties:
                        manoEntitySubscriptionFilter:
                          description: >
                            This type represents subscription filter criteria to
                            match NFV-MANO functional  entities and their
                            associated managed objects. 
                          type: object
                          properties:
                            manoEntityId:
                              description: >
                                An identifier with the intention of being
                                globally unique.
                              type: string
                            manoServiceIds:
                              description: "manoServiceIds\tIdentifierInManoEntity\t0..N\tIf present, match NFV-MANO  services with an instance identifier listed in this attribute.\nThe attributes \"manoServiceIds\" and \"manoServiceNames\" are alternatives  to reference to NFV-MANO services in a filter. They should not be used  together in the same filter instance, but one alternative should be chosen.\n"
                              type: array
                              items:
                                description: >
                                  An identifier that is unique for the
                                  respective type within a NFV-MANO functional
                                  entity, but that need not be globally unique.
                                  Representation: string of variable length..
                                type: string
                            manoServiceNames:
                              description: >
                                If present, match NFV-MANO services with an
                                NFV-MANO service name listed  in this attribute.

                                The attributes "manoServiceIds" and
                                "manoServiceNames" are alternatives  to
                                reference to NFV-MANO services in a filter. They
                                should not be used  together in the same filter
                                instance, but one alternative should be chosen.
                              type: array
                              items:
                                type: string
                            manoServiceInterfaceIds:
                              description: >
                                If present, match NFV-MANO functional entity
                                produced interfaces with an  instance identifier
                                listed in this attribute.

                                The attributes "manoServiceInterfaceIds" and
                                "manoServiceInterfaceNames"  are alternatives to
                                reference to NFV-MANO functional entity
                                produced  interfaces in a filter. They should
                                not be used both in the same filter  instance,
                                but one alternative should be chosen.
                              type: array
                              items:
                                description: >
                                  An identifier that is unique for the
                                  respective type within a NFV-MANO functional
                                  entity, but that need not be globally unique.
                                  Representation: string of variable length..
                                type: string
                            manoServiceInterfaceNames:
                              description: >
                                If present, match NFV-MANO functional entity
                                produced interfaces with an  instance Name
                                listed in this attribute.

                                The attributes "manoServiceInterfaceIds" and
                                "manoServiceInterfaceNames"  are alternatives to
                                reference to NFV-MANO functional entity
                                produced  interfaces in a filter. They should
                                not be used both in the same filter  instance,
                                but one alternative should be chosen.
                              type: array
                              items:
                                type: string
                            consumedManoInterfaceIds:
                              description: >
                                If present, match NFV-MANO functional entity
                                consumed interfaces with an  instance identifier
                                listed in this attribute.

                                The attributes "consumedManoInterfaceIds" and
                                "consumedManoInterfaceNames"  are alternatives
                                to reference to NFV-MANO functional entity
                                consumed  interfaces in a filter. They should
                                not be used both in the same filter  instance,
                                but one alternative should be chosen.
                              type: array
                              items:
                                description: >
                                  An identifier with the intention of being
                                  globally unique.
                                type: string
                            consumedManoInterfaceNames:
                              description: >
                                If present, match NFV-MANO functional entity
                                consumed interfaces with an  instance Name
                                listed in this attribute.

                                The attributes "consumedManoInterfaceIds" and
                                "consumedManoInterfaceNames"  are alternatives
                                to reference to NFV-MANO functional entity
                                consumed  interfaces in a filter. They should
                                not be used both in the same filter  instance,
                                but one alternative should be chosen.
                              type: array
                              items:
                                type: string
                        notificationTypes:
                          description: "Match particular notification types. \nPermitted values:\n  - InformationChangedNotification\n  - ChangeStateNotification\n\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are  spelled exactly as the names of the notification types to facilitate  automated code generation systems.\n"
                          type: array
                          items:
                            type: string
                            enum:
                              - InformationChangedNotification
                              - ChangeStateNotification
                    callbackUri:
                      description: |
                        String formatted according to IETF RFC 3986.
                      type: string
                    _links:
                      description: |
                        Links to resources related to this resource.
                      type: object
                      properties:
                        self:
                          description: >
                            This type represents a link to a resource using an
                            absolute URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                      required:
                        - self
                  required:
                    - id
                    - callbackUri
                    - _links
        '400':
          description: |
            400 BAD REQUEST
            Shall be returned upon the following errors: 
              - Invalid attribute-based filtering expression.
                The response body shall contain a ProblemDetails structure, in which 
                the "detail" attribute should convey more information about the error.
              - Response too big.
                If the NFV-MANO functional entity supports alternative N°1 (error) 
                according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
                this error response shall follow the provisions in clause 5.4.2.2 of 
                ETSI GS NFV-SOL 013.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
  '/subscriptions/{subscriptionId}':
    parameters:
      - name: subscriptionId
        in: path
        description: Identifier of the subscription
        required: true
        schema:
          description: |
            An identifier with the intention of being globally unique.
          type: string
    get:
      description: >
        Retrieves information about a subscription by reading an "Individual 
        subscription" resource.

        This method shall follow the provisions specified in the tables 
        5.5.5.3.2-1 and 5.5.5.3.2-2 for URI query parameters, request and 
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when information about an individual subscription 
            has been read successfully.

            The response body shall contain a representation of the "Individual 
            subscription" resource.
                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.
              schema:
                type: string
            Version:
              description: >
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  This type represents a subscription related to notifications
                  about  NFV-MANO configuration and information management
                  changes
                type: object
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  filter:
                    description: >
                      This type represents a subscription filter related to
                      notifications  about NFV-MANO configuration and
                      information management. 
                    type: object
                    properties:
                      manoEntitySubscriptionFilter:
                        description: >
                          This type represents subscription filter criteria to
                          match NFV-MANO functional  entities and their
                          associated managed objects. 
                        type: object
                        properties:
                          manoEntityId:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                          manoServiceIds:
                            description: "manoServiceIds\tIdentifierInManoEntity\t0..N\tIf present, match NFV-MANO  services with an instance identifier listed in this attribute.\nThe attributes \"manoServiceIds\" and \"manoServiceNames\" are alternatives  to reference to NFV-MANO services in a filter. They should not be used  together in the same filter instance, but one alternative should be chosen.\n"
                            type: array
                            items:
                              description: >
                                An identifier that is unique for the respective
                                type within a NFV-MANO functional entity, but
                                that need not be globally unique.
                                Representation: string of variable length..
                              type: string
                          manoServiceNames:
                            description: >
                              If present, match NFV-MANO services with an
                              NFV-MANO service name listed  in this attribute.

                              The attributes "manoServiceIds" and
                              "manoServiceNames" are alternatives  to reference
                              to NFV-MANO services in a filter. They should not
                              be used  together in the same filter instance, but
                              one alternative should be chosen.
                            type: array
                            items:
                              type: string
                          manoServiceInterfaceIds:
                            description: >
                              If present, match NFV-MANO functional entity
                              produced interfaces with an  instance identifier
                              listed in this attribute.

                              The attributes "manoServiceInterfaceIds" and
                              "manoServiceInterfaceNames"  are alternatives to
                              reference to NFV-MANO functional entity produced 
                              interfaces in a filter. They should not be used
                              both in the same filter  instance, but one
                              alternative should be chosen.
                            type: array
                            items:
                              description: >
                                An identifier that is unique for the respective
                                type within a NFV-MANO functional entity, but
                                that need not be globally unique.
                                Representation: string of variable length..
                              type: string
                          manoServiceInterfaceNames:
                            description: >
                              If present, match NFV-MANO functional entity
                              produced interfaces with an  instance Name listed
                              in this attribute.

                              The attributes "manoServiceInterfaceIds" and
                              "manoServiceInterfaceNames"  are alternatives to
                              reference to NFV-MANO functional entity produced 
                              interfaces in a filter. They should not be used
                              both in the same filter  instance, but one
                              alternative should be chosen.
                            type: array
                            items:
                              type: string
                          consumedManoInterfaceIds:
                            description: >
                              If present, match NFV-MANO functional entity
                              consumed interfaces with an  instance identifier
                              listed in this attribute.

                              The attributes "consumedManoInterfaceIds" and
                              "consumedManoInterfaceNames"  are alternatives to
                              reference to NFV-MANO functional entity consumed 
                              interfaces in a filter. They should not be used
                              both in the same filter  instance, but one
                              alternative should be chosen.
                            type: array
                            items:
                              description: >
                                An identifier with the intention of being
                                globally unique.
                              type: string
                          consumedManoInterfaceNames:
                            description: >
                              If present, match NFV-MANO functional entity
                              consumed interfaces with an  instance Name listed
                              in this attribute.

                              The attributes "consumedManoInterfaceIds" and
                              "consumedManoInterfaceNames"  are alternatives to
                              reference to NFV-MANO functional entity consumed 
                              interfaces in a filter. They should not be used
                              both in the same filter  instance, but one
                              alternative should be chosen.
                            type: array
                            items:
                              type: string
                      notificationTypes:
                        description: "Match particular notification types. \nPermitted values:\n  - InformationChangedNotification\n  - ChangeStateNotification\n\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are  spelled exactly as the names of the notification types to facilitate  automated code generation systems.\n"
                        type: array
                        items:
                          type: string
                          enum:
                            - InformationChangedNotification
                            - ChangeStateNotification
                  callbackUri:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                  _links:
                    description: |
                      Links to resources related to this resource.
                    type: object
                    properties:
                      self:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                    required:
                      - self
                required:
                  - id
                  - callbackUri
                  - _links
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
    delete:
      description: >
        Terminates an individual subscription.

        This method shall follow the provisions specified in the tables 
        5.5.5.3.5-1 and 5.5.5.3.5-2 for URI query parameters, request  and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      responses:
        '204':
          description: >
            204 NO CONTENT

            Shall be returned when the "Individual subscription" resource  has
            been deleted successfully.

            The response body shall be empty.
          headers:
            WWW-Authenticate:
              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
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
  /change_state_ops:
    get:
      description: >
        The API consumer can use the GET method to query status information 
        about multiple change state operation occurrences.

        This method shall follow the provisions specified in the tables 
        5.5.8.3.2-1 and 5.5.8.3.2-2 for URI query parameters, request and 
        response data structures, and response codes.
      parameters:
        - name: filter
          description: >
            Attribute-based filtering expression according to clause 5.2 of 
            ETSI GS NFV-SOL 013. 

            The NFV-MANO functional entity shall support receiving this
            parameter  as part of the URI query string. The API consumer may
            supply this  parameter. 

            All attribute names that appear in the ChangeStateOpOcc and in data 
            types referenced from it shall be supported by the NFV-MANO
            functional  entity in the expression. 
          in: query
          required: false
          schema:
            type: string
        - name: all_fields
          description: >
            Include all complex attributes in the response. See clause  5.3 of
            ETSI GS NFV-SOL 013. The NFV-MANO functional entity  shall support
            this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: fields
          description: >
            Complex attributes to be included into the response. See clause  5.3
            of ETSI GS NFV-SOL 013 for details. The NFV-MANO functional  entity
            should support this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: exclude_fields
          description: >
            Complex attributes to be excluded from the response. See clause  5.3
            of ETSI GS NFV-SOL 013 for details. The NFV-MANO functional  entity
            should support this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: exclude_default
          description: >
            Indicates to exclude the following complex attributes from the 
            response. See clause 5.3 of ETSI GS NFV-SOL 013 for details.  The
            NFV-MANO functional entity shall support this parameter.

            The following attributes shall be excluded from the
            ChangeStateOpOcc  structure in the response body if this parameter
            is provided, or none of  the parameters "all_fields," "fields",
            "exclude_fields", "exclude_default"  are provided: - none
          in: query
          required: false
          schema:
            type: string
        - name: nextpage_opaque_marker
          description: >
            Marker to obtain the next page of a paged response. Shall be
            supported by  the NFV-MANO functional entity if the entity supports
            alternative 2 (paging)  according to clause 5.4.2.1 of ETSI GS
            NFV-SOL 013 for this resource.
          in: query
          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
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when status information for zero or more  "change
            state operation occurrences" has been queried successfully.

            The response body shall contain in an array the status information 
            about zero or more "Individual change state operation occurrences", 
            as defined in clause 5.6.2.9.

            If the “filter" URI parameter or one of the "all_fields", "fields" 
            (if supported), "exclude_fields" (if supported) or
            "exclude_default"  URI parameters was supplied in the request, the
            data in the response  body shall have been transformed according to
            the rules specified in  clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL
            013, respectively.

            If the NFV-MANO functional entity supports alternative N°2 (paging) 
            according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this
            resource,  inclusion of the Link HTTP header in this response shall
            follow the  provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
          headers:
            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
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Link:
              description: >
                Reference to other resources. Link HTTP header in this response 
                shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL
                013.
              schema:
                type: string
                minimum: 0
                maximum: 1
          content:
            application/json:
              schema:
                type: array
                items:
                  description: |
                    This type represents a Change state operation occurrence. 
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    operationState:
                      description: "The enumeration ChangeStateOpOccStateEnumType defines permitted values for the change state operation. It shall comply with the provisions :\n  - PROCESSING\tThe change state operation is currently in execution.\n  - COMPLETED\tThe change state operation has been completed successfully.\n  - FAILED\tThe change state operation has failed.\n"
                      type: string
                      enum:
                        - PROCESSING
                        - COMPLETED
                        - FAILED
                    stateEnteredTime:
                      description: >
                        Date-time stamp. Representation: String formatted
                        according to IETF RFC 3339.
                      type: string
                      format: date-time
                    startTime:
                      description: >
                        Date-time stamp. Representation: String formatted
                        according to IETF RFC 3339.
                      type: string
                      format: date-time
                    managedObjectRef:
                      description: >
                        This type represents the identifier to reference a
                        managed object of a  particular type. 
                      type: object
                      properties:
                        type:
                          description: >
                            Indicates the type of managed object. Permitted
                            values:
                              - MANO_ENTITY
                              - MANO_SERVICE
                              - MANO_SERVICE_IF
                              - CONSUMED_MANO_IF
                              - MANO_ENTITY_COMPONENT

                            The "MANO_ENTITY COMPONENT" is only applicable if
                            attribute "manoEntityComponents" in "ManoEntity" is
                            supported by the API producer.
                          type: string
                          enum:
                            - MANO_ENTITY
                            - MANO_SERVICE
                            - MANO_SERVICE_IF
                            - CONSUMED_MANO_IF
                            - MANO_ENTITY_COMPONENT
                        objectId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        subObjectId:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      required:
                        - type
                        - objectId
                    changeOperationalStateRequest:
                      description: "The enumeration ChangeOperationalStateEnumType defines permitted values  for the change state operation.  The ChangeOperationalStateEnumType shall comply with the provisions:\n  - START\tTo start the managed entity.\n  - STOP\tTo stop the managed entity.\n  - RESTART\tTo stop and start again the managed entity.\n"
                      type: string
                      enum:
                        - START
                        - STOP
                        - RESTART
                    changeAdministrativeStateRequest:
                      description: "The enumeration ChangeAdministrativeStateEnumType defines permitted values  for the change of administrative state operation.  The ChangeAdministrativeStateEnumType shall comply with the provisions:\n  - LOCK\tTo lock the managed entity.\n  - UNLOCK\tTo unlock the managed entity.\n"
                      type: string
                      enum:
                        - LOCK
                        - UNLOCK
                    operationParams:
                      description: >
                        Input parameters of the change state operation. This
                        attribute shall be  formatted according to the request
                        data type of the related change state  operation. 

                        The following mapping between operationType and the data
                        type of this  attribute shall apply:
                          - CHANGE_STATE: ChangeStateRequest
                          
                        This attribute shall be present if this data type is
                        returned in a response  to reading an individual
                        resource, and may be present according to the chosen 
                        attribute selector parameter if this data type is
                        returned in a response to  a query of a container
                        resource.
                  required:
                    - id
                    - operationState
                    - stateEnteredTime
                    - startTime
                    - managedObjectRef
        '400':
          description: |
            400 BAD REQUEST
            Shall be returned upon the following errors: 
              - Invalid attribute-based filtering expression.
                The response body shall contain a ProblemDetails structure, in which 
                the "detail" attribute should convey more information about the error.
              - Invalid attribute selector.
                The response body shall contain a ProblemDetails structure, in which 
                the "detail" attribute should convey more information about the error.
              - Response too big.
                If the NFV-MANO functional entity supports alternative N°1 (error) 
                according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
                this error response shall follow the provisions in clause 5.4.2.2 of 
                ETSI GS NFV-SOL 013.
                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.
              schema:
                type: string
            Version:
              description: >
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
  '/change_state_ops/{changeStateOpOccId}':
    parameters:
      - name: changeStateOpOccId
        in: path
        description: Identifier of the change state operation occurrence
        required: true
        schema:
          description: |
            An identifier with the intention of being globally unique.
          type: string
    get:
      description: >
        The API consumer can use the GET method to retrieve status  information
        about a change state operation occurrence by reading  an "Individual
        change state operation occurrence" resource.

        This method shall follow the provisions specified in the tables 
        5.5.9.3.2-1 and 5.5.9.3.2-2 for URI query parameters, request  and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when information about an "Individual change 
            state operation occurrence" resource has been read successfully.

            The response body shall contain status information about a change 
            state operation occurrence, as defined in clause 5.6.2.9.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: |
                  This type represents a Change state operation occurrence. 
                type: object
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  operationState:
                    description: "The enumeration ChangeStateOpOccStateEnumType defines permitted values for the change state operation. It shall comply with the provisions :\n  - PROCESSING\tThe change state operation is currently in execution.\n  - COMPLETED\tThe change state operation has been completed successfully.\n  - FAILED\tThe change state operation has failed.\n"
                    type: string
                    enum:
                      - PROCESSING
                      - COMPLETED
                      - FAILED
                  stateEnteredTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  startTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  managedObjectRef:
                    description: >
                      This type represents the identifier to reference a managed
                      object of a  particular type. 
                    type: object
                    properties:
                      type:
                        description: >
                          Indicates the type of managed object. Permitted
                          values:
                            - MANO_ENTITY
                            - MANO_SERVICE
                            - MANO_SERVICE_IF
                            - CONSUMED_MANO_IF
                            - MANO_ENTITY_COMPONENT

                          The "MANO_ENTITY COMPONENT" is only applicable if
                          attribute "manoEntityComponents" in "ManoEntity" is
                          supported by the API producer.
                        type: string
                        enum:
                          - MANO_ENTITY
                          - MANO_SERVICE
                          - MANO_SERVICE_IF
                          - CONSUMED_MANO_IF
                          - MANO_ENTITY_COMPONENT
                      objectId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      subObjectId:
                        description: >
                          An identifier that is unique for the respective type
                          within a NFV-MANO functional entity, but that need not
                          be globally unique. Representation: string of variable
                          length..
                        type: string
                    required:
                      - type
                      - objectId
                  changeOperationalStateRequest:
                    description: "The enumeration ChangeOperationalStateEnumType defines permitted values  for the change state operation.  The ChangeOperationalStateEnumType shall comply with the provisions:\n  - START\tTo start the managed entity.\n  - STOP\tTo stop the managed entity.\n  - RESTART\tTo stop and start again the managed entity.\n"
                    type: string
                    enum:
                      - START
                      - STOP
                      - RESTART
                  changeAdministrativeStateRequest:
                    description: "The enumeration ChangeAdministrativeStateEnumType defines permitted values  for the change of administrative state operation.  The ChangeAdministrativeStateEnumType shall comply with the provisions:\n  - LOCK\tTo lock the managed entity.\n  - UNLOCK\tTo unlock the managed entity.\n"
                    type: string
                    enum:
                      - LOCK
                      - UNLOCK
                  operationParams:
                    description: >
                      Input parameters of the change state operation. This
                      attribute shall be  formatted according to the request
                      data type of the related change state  operation. 

                      The following mapping between operationType and the data
                      type of this  attribute shall apply:
                        - CHANGE_STATE: ChangeStateRequest
                        
                      This attribute shall be present if this data type is
                      returned in a response  to reading an individual resource,
                      and may be present according to the chosen  attribute
                      selector parameter if this data type is returned in a
                      response to  a query of a container resource.
                required:
                  - id
                  - operationState
                  - stateEnteredTime
                  - startTime
                  - managedObjectRef
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
  /peer_entities:
    post:
      description: >
        Creates in the producer NFV-MANO functional entity a new peer  entity
        resource which contains configuration and information  with regards to
        the peer functional entity.

        This method shall follow the provisions specified in the tables 
        5.5.13.3.1-1 and 5.5.13.3.1-2 for URI query parameters, request  and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      requestBody:
        description: |
          The peer entity creation parameters, as defined in clause 5.6.2.14.
        content:
          application/json:
            schema:
              description: >
                This type represents request parameters for the creation of a
                new peer entity resource. 
              type: object
              properties:
                peerEntityId:
                  description: |
                    An identifier with the intention of being globally unique.
                  type: string
                name:
                  description: |
                    Human-readable name of the peer functional entity.
                  type: string
                type:
                  description: "The enumeration PeerEntityEnumType defines the permitted values  to represent peer functional entities. it shall complains with  the provisions :  - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t  The peer functional entity is a VIM. - WIM\t  The peer functional entity is a WIM. - EM\t  The peer functional entity is an EM. - OSS\t  The peer functional entity is an OSS/BSS.\n"
                  type: string
                  enum:
                    - NFVO
                    - VNFM
                    - VIM
                    - WIM
                    - EM
                    - OSS
                description:
                  description: |
                    Human-readable description of the peer functional entity.
                  type: string
                consumedManoInterfaces:
                  description: >
                    Initial information of the interface consumed by the
                    NFV-MANO functional entity from the peer functional entity.
                  type: object
                  additionalProperties:
                    description: >
                      This type represents an interface consumed by the producer
                      NFV MANO  functional entity from another peer functional
                      entity. 
                    type: object
                    properties:
                      id:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      name:
                        description: |
                          Human-readable name of the NFV-MANO interface.
                        type: string
                      type:
                        description: >
                          Type of the NFV-MANO service interface consumed by the
                          NFV-MANO  functional entity. Valid values are defined
                          in clause 5.6.4.3.
                        type: string
                      standardVersion:
                        description: |
                          A version.
                        type: string
                      apiVersion:
                        description: |
                          A version.
                        type: string
                      apiEndpoint:
                        description: >
                          Consumable API endpoint of the interface. It provides
                          the information relevant about the protocol, host and
                          port,  and path where the interface API can be
                          accessed.
                        type: object
                        properties:
                          apiRoot:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                          apiName:
                            description: >
                              Indicates the interface name in an abbreviated
                              form. Shall be present  for ETSI NFV specified
                              RESTful NFV-MANO APIs. The {apiName} of each 
                              interface is defined in the standard the interface
                              is compliant to  (see also clause 4.1 of ETSI GS
                              NFV-SOL 013). May be present otherwise.
                            type: string
                          apiMajorVersion:
                            description: >
                              Indicates the current major version of the API.
                              Shall be present for  ETSI NFV specified RESTful
                              NFV-MANO APIs. The major version is defined  in
                              the standard the interface is compliant to (see
                              also clause 4.1  of ETSI GS NFV-SOL 013). May be
                              present otherwise.
                            type: string
                          apiUri:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                        required:
                          - apiUri
                      securityInfo:
                        description: >
                          This type represents security related information for
                          accessing an NFV-MANO  service interface produced by
                          an NFV-MANO functional entity.
                        type: object
                        required:
                          - authType
                          - oauthServerInfo
                        properties:
                          authType:
                            description: >
                              Type of API request authorization to be used by
                              the API consumer accessing  the API.

                              The support of authorization methods for the API
                              consumer is specified in  clause 8.3.6 of ETSI GS
                              NFV-SOL 013.

                              Permitted values: - TLS_TUNNEL: Using TLS tunnel,
                              as defined by TLS 1.2 in IETF RFC 5246. - OAUTH2:
                              Using access token, as defined by the OAuth 2.0
                              specification  in IETF RFC 6749. 
                            type: array
                            items:
                              type: string
                              enum:
                                - TLS_TUNNEL
                                - OAUTH2
                            minItems: 1
                          oauthServerInfo:
                            description: >
                              OAuth 2.0 authorization server information and
                              configuration.
                            type: object
                            properties:
                              dynamicDiscovery:
                                description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                type: object
                                required:
                                  - webFingerHost
                                properties:
                                  webFingerHost:
                                    description: >
                                      Server where the WebFinger service is
                                      hosted. When used, the request to  the
                                      WebFinger resource shall conform as
                                      specified in clause 5.1.3 of  ETSI GS
                                      NFV-SEC 022.
                                    type: string
                                    format: uri
                              providedConfiguration:
                                description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                type: object
                                required:
                                  - authServerId
                                properties:
                                  authServerId:
                                    description: >
                                      Authorization server identifier as defined
                                      in ETSI GS NFV-SEC 022.
                                    type: string
                                    format: uri
                              tlsCipherSuites:
                                description: >
                                  List of cipher suites that shall be declared
                                  as supported by the API consumer when 
                                  performing the SSL or TLS negotiation with the
                                  authorization server. Valid values  of cipher
                                  suites are defined in IETF RFC 8447.
                                type: array
                                items:
                                  type: string
                                  minItems: 1
                          tlsTunnelInfo:
                            description: >
                              Information and configuration related to the use
                              of TLS tunnel. Shall be  present if authType
                              contains "TLS_TUNNEL".
                            type: object
                            properties:
                              tlsTunnelCipherSuites:
                                description: >
                                  List of cipher suites that shall be declared
                                  as supported by the API  consumer when
                                  performing the SSL or TLS negotiation with the
                                  API producer.  Valid values of cipher suites
                                  are defined in IETF RFC 8447.
                                type: array
                                items:
                                  type: string
                                  minItems: 1
                    required:
                      - id
                      - name
                      - type
                      - standardVersion
                      - apiVersion
                      - apiEndpoint
                peerEntityState:
                  description: |
                    Current values of the state of the peer functional entity.
                  type: object
                  properties:
                    operationalState:
                      description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                      type: string
                      enum:
                        - STARTED
                        - STOPPED
                        - STOPPING
                        - STARTING
                        - RESTARTING
                    administrativeState:
                      description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                      type: string
                      enum:
                        - LOCKED
                        - UNLOCKED
                        - LOCKING
                  required:
                    - operationalState
                    - administrativeState
              required:
                - peerEntityId
                - name
                - type
        required: true
      responses:
        '201':
          description: >
            201 CREATED

            Shall be returned when a new "Individual peer entity" resource  has
            been created successfully.

            The response body shall contain a representation of the created 
            resource with regards to a peer entity, as defined in  clause
            5.6.2.15.

            The HTTP response shall include a “Location” HTTP header that 
            points to the created "Individual peer entity" resource.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Location:
              description: >
                The resource URI of the created "Individual peer entity"
                resource.
              schema:
                type: string
                format: url
                minimum: 1
                maximum: 1
          content:
            application/json:
              schema:
                description: |
                  This type represents an individual peer entity. 
                type: object
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  peerEntityId:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  name:
                    description: |
                      Human-readable name of the peer functional entity.
                      This attribute can be modified with the PATCH method.
                    type: string
                  type:
                    description: "The enumeration PeerEntityEnumType defines the permitted values  to represent peer functional entities. it shall complains with  the provisions :  - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t  The peer functional entity is a VIM. - WIM\t  The peer functional entity is a WIM. - EM\t  The peer functional entity is an EM. - OSS\t  The peer functional entity is an OSS/BSS.\n"
                    type: string
                    enum:
                      - NFVO
                      - VNFM
                      - VIM
                      - WIM
                      - EM
                      - OSS
                  description:
                    description: |
                      Human-readable description of the peer functional entity.
                      This attribute can be modified with the PATCH method.
                    type: string
                  consumedManoInterfaces:
                    description: >
                      Information of the interface consumed by the NFV-MANO
                      functional entity  from the peer functional entity.

                      This attribute can be modified with the PATCH method.

                      The keys of the map, each of which identifies information
                      about a particular consumed NFV-MANO interface, are
                      managed by the API consumer and referenced from other data
                      structures via the "consumedManoInterfaceIds" attribute.
                    type: object
                    additionalProperties:
                      description: >
                        This type represents an interface consumed by the
                        producer NFV MANO  functional entity from another peer
                        functional entity. 
                      type: object
                      properties:
                        id:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        name:
                          description: |
                            Human-readable name of the NFV-MANO interface.
                          type: string
                        type:
                          description: >
                            Type of the NFV-MANO service interface consumed by
                            the NFV-MANO  functional entity. Valid values are
                            defined in clause 5.6.4.3.
                          type: string
                        standardVersion:
                          description: |
                            A version.
                          type: string
                        apiVersion:
                          description: |
                            A version.
                          type: string
                        apiEndpoint:
                          description: >
                            Consumable API endpoint of the interface. It
                            provides the information relevant about the
                            protocol, host and port,  and path where the
                            interface API can be accessed.
                          type: object
                          properties:
                            apiRoot:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                            apiName:
                              description: >
                                Indicates the interface name in an abbreviated
                                form. Shall be present  for ETSI NFV specified
                                RESTful NFV-MANO APIs. The {apiName} of each 
                                interface is defined in the standard the
                                interface is compliant to  (see also clause 4.1
                                of ETSI GS NFV-SOL 013). May be present
                                otherwise.
                              type: string
                            apiMajorVersion:
                              description: >
                                Indicates the current major version of the API.
                                Shall be present for  ETSI NFV specified RESTful
                                NFV-MANO APIs. The major version is defined  in
                                the standard the interface is compliant to (see
                                also clause 4.1  of ETSI GS NFV-SOL 013). May be
                                present otherwise.
                              type: string
                            apiUri:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                          required:
                            - apiUri
                        securityInfo:
                          description: >
                            This type represents security related information
                            for accessing an NFV-MANO  service interface
                            produced by an NFV-MANO functional entity.
                          type: object
                          required:
                            - authType
                            - oauthServerInfo
                          properties:
                            authType:
                              description: >
                                Type of API request authorization to be used by
                                the API consumer accessing  the API.

                                The support of authorization methods for the API
                                consumer is specified in  clause 8.3.6 of ETSI
                                GS NFV-SOL 013.

                                Permitted values: - TLS_TUNNEL: Using TLS
                                tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                                - OAUTH2: Using access token, as defined by the
                                OAuth 2.0 specification  in IETF RFC 6749. 
                              type: array
                              items:
                                type: string
                                enum:
                                  - TLS_TUNNEL
                                  - OAUTH2
                              minItems: 1
                            oauthServerInfo:
                              description: >
                                OAuth 2.0 authorization server information and
                                configuration.
                              type: object
                              properties:
                                dynamicDiscovery:
                                  description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                  type: object
                                  required:
                                    - webFingerHost
                                  properties:
                                    webFingerHost:
                                      description: >
                                        Server where the WebFinger service is
                                        hosted. When used, the request to  the
                                        WebFinger resource shall conform as
                                        specified in clause 5.1.3 of  ETSI GS
                                        NFV-SEC 022.
                                      type: string
                                      format: uri
                                providedConfiguration:
                                  description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                  type: object
                                  required:
                                    - authServerId
                                  properties:
                                    authServerId:
                                      description: >
                                        Authorization server identifier as
                                        defined in ETSI GS NFV-SEC 022.
                                      type: string
                                      format: uri
                                tlsCipherSuites:
                                  description: >
                                    List of cipher suites that shall be declared
                                    as supported by the API consumer when 
                                    performing the SSL or TLS negotiation with
                                    the authorization server. Valid values  of
                                    cipher suites are defined in IETF RFC 8447.
                                  type: array
                                  items:
                                    type: string
                                    minItems: 1
                            tlsTunnelInfo:
                              description: >
                                Information and configuration related to the use
                                of TLS tunnel. Shall be  present if authType
                                contains "TLS_TUNNEL".
                              type: object
                              properties:
                                tlsTunnelCipherSuites:
                                  description: >
                                    List of cipher suites that shall be declared
                                    as supported by the API  consumer when
                                    performing the SSL or TLS negotiation with
                                    the API producer.  Valid values of cipher
                                    suites are defined in IETF RFC 8447.
                                  type: array
                                  items:
                                    type: string
                                    minItems: 1
                      required:
                        - id
                        - name
                        - type
                        - standardVersion
                        - apiVersion
                        - apiEndpoint
                  peerEntityState:
                    description: >
                      State of the peer functional entity as provided by the API
                      consumer when  creating the resource or when updating it
                      with the PATCH method.
                    type: object
                    properties:
                      operationalState:
                        description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                        type: string
                        enum:
                          - STARTED
                          - STOPPED
                          - STOPPING
                          - STARTING
                          - RESTARTING
                      administrativeState:
                        description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                        type: string
                        enum:
                          - LOCKED
                          - UNLOCKED
                          - LOCKING
                    required:
                      - operationalState
                      - administrativeState
                required:
                  - id
                  - peerEntityId
                  - name
                  - type
                  - peerEntityState
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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: >
        Queries information and configuration in the producer NFV-MANO 
        functional entity with regards to multiple peer entities.

        This method shall follow the provisions specified in the tables 
        5.5.13.3.2-1 and 5.5.13.3.2-2 for URI query parameters, request  and
        response data structures, and response codes.
      parameters:
        - name: filter
          description: >
            Attribute-based filtering expression according to clause 5.2 of 
            ETSI GS NFV-SOL 013. 

            The NFV-MANO functional entity shall support receiving this
            parameter  as part of the URI query string. The API consumer may
            supply this  parameter. 

            All attribute names that appear in the PeerEntity and in data  types
            referenced from it shall be supported by the NFV-MANO functional 
            entity in the expression. 
          in: query
          required: false
          schema:
            type: string
        - name: all_fields
          description: >
            Include all complex attributes in the response. See clause  5.3 of
            ETSI GS NFV-SOL 013. The NFV-MANO functional entity  shall support
            this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: fields
          description: >
            Complex attributes to be included into the response. See clause  5.3
            of ETSI GS NFV-SOL 013 for details. The NFV-MANO functional  entity
            should support this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: exclude_fields
          description: >
            Complex attributes to be excluded from the response. See clause  5.3
            of ETSI GS NFV-SOL 013 for details. The NFV-MANO functional  entity
            should support this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: exclude_default
          description: >
            Indicates to exclude the following complex attributes from the 
            response. See clause 5.3 of ETSI GS NFV-SOL 013 for details.  The
            NFV-MANO functional entity shall support this parameter.

            The following attributes shall be excluded from the PeerEntity 
            structure in the response body if this parameter is provided, or
            none of  the parameters "all_fields," "fields", "exclude_fields",
            "exclude_default"  are provided: - none
          in: query
          required: false
          schema:
            type: string
        - name: nextpage_opaque_marker
          description: >
            Marker to obtain the next page of a paged response. Shall be
            supported by  the NFV-MANO functional entity if the entity supports
            alternative 2 (paging)  according to clause 5.4.2.1 of ETSI GS
            NFV-SOL 013 for this resource.
          in: query
          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
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when information about zero or more peer  entities
            has been queried successfully.

            The response body shall contain in an array the resource 
            representations of zero or more peer entities, as defined  in clause
            5.6.2.15.

            If the “filter" URI parameter or one of the "all_fields", "fields" 
            (if supported), "exclude_fields" (if supported) or
            "exclude_default"  URI parameters was supplied in the request, the
            data in the response  body shall have been transformed according to
            the rules specified in  clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL
            013, respectively.

            If the NFV-MANO functional entity supports alternative N°2 (paging) 
            according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this
            resource,  inclusion of the Link HTTP header in this response shall
            follow the  provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
          headers:
            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
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Link:
              description: >
                Reference to other resources. Link HTTP header in this response 
                shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL
                013.
              schema:
                type: string
                minimum: 0
                maximum: 1
          content:
            application/json:
              schema:
                type: array
                items:
                  description: |
                    This type represents an individual peer entity. 
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    peerEntityId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    name:
                      description: |
                        Human-readable name of the peer functional entity.
                        This attribute can be modified with the PATCH method.
                      type: string
                    type:
                      description: "The enumeration PeerEntityEnumType defines the permitted values  to represent peer functional entities. it shall complains with  the provisions :  - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t  The peer functional entity is a VIM. - WIM\t  The peer functional entity is a WIM. - EM\t  The peer functional entity is an EM. - OSS\t  The peer functional entity is an OSS/BSS.\n"
                      type: string
                      enum:
                        - NFVO
                        - VNFM
                        - VIM
                        - WIM
                        - EM
                        - OSS
                    description:
                      description: >
                        Human-readable description of the peer functional
                        entity.

                        This attribute can be modified with the PATCH method.
                      type: string
                    consumedManoInterfaces:
                      description: >
                        Information of the interface consumed by the NFV-MANO
                        functional entity  from the peer functional entity.

                        This attribute can be modified with the PATCH method.

                        The keys of the map, each of which identifies
                        information about a particular consumed NFV-MANO
                        interface, are managed by the API consumer and
                        referenced from other data structures via the
                        "consumedManoInterfaceIds" attribute.
                      type: object
                      additionalProperties:
                        description: >
                          This type represents an interface consumed by the
                          producer NFV MANO  functional entity from another peer
                          functional entity. 
                        type: object
                        properties:
                          id:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                          name:
                            description: |
                              Human-readable name of the NFV-MANO interface.
                            type: string
                          type:
                            description: >
                              Type of the NFV-MANO service interface consumed by
                              the NFV-MANO  functional entity. Valid values are
                              defined in clause 5.6.4.3.
                            type: string
                          standardVersion:
                            description: |
                              A version.
                            type: string
                          apiVersion:
                            description: |
                              A version.
                            type: string
                          apiEndpoint:
                            description: >
                              Consumable API endpoint of the interface. It
                              provides the information relevant about the
                              protocol, host and port,  and path where the
                              interface API can be accessed.
                            type: object
                            properties:
                              apiRoot:
                                description: |
                                  String formatted according to IETF RFC 3986.
                                type: string
                              apiName:
                                description: >
                                  Indicates the interface name in an abbreviated
                                  form. Shall be present  for ETSI NFV specified
                                  RESTful NFV-MANO APIs. The {apiName} of each 
                                  interface is defined in the standard the
                                  interface is compliant to  (see also clause
                                  4.1 of ETSI GS NFV-SOL 013). May be present
                                  otherwise.
                                type: string
                              apiMajorVersion:
                                description: >
                                  Indicates the current major version of the
                                  API. Shall be present for  ETSI NFV specified
                                  RESTful NFV-MANO APIs. The major version is
                                  defined  in the standard the interface is
                                  compliant to (see also clause 4.1  of ETSI GS
                                  NFV-SOL 013). May be present otherwise.
                                type: string
                              apiUri:
                                description: |
                                  String formatted according to IETF RFC 3986.
                                type: string
                            required:
                              - apiUri
                          securityInfo:
                            description: >
                              This type represents security related information
                              for accessing an NFV-MANO  service interface
                              produced by an NFV-MANO functional entity.
                            type: object
                            required:
                              - authType
                              - oauthServerInfo
                            properties:
                              authType:
                                description: >
                                  Type of API request authorization to be used
                                  by the API consumer accessing  the API.

                                  The support of authorization methods for the
                                  API consumer is specified in  clause 8.3.6 of
                                  ETSI GS NFV-SOL 013.

                                  Permitted values: - TLS_TUNNEL: Using TLS
                                  tunnel, as defined by TLS 1.2 in IETF RFC
                                  5246. - OAUTH2: Using access token, as defined
                                  by the OAuth 2.0 specification  in IETF RFC
                                  6749. 
                                type: array
                                items:
                                  type: string
                                  enum:
                                    - TLS_TUNNEL
                                    - OAUTH2
                                minItems: 1
                              oauthServerInfo:
                                description: >
                                  OAuth 2.0 authorization server information and
                                  configuration.
                                type: object
                                properties:
                                  dynamicDiscovery:
                                    description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                    type: object
                                    required:
                                      - webFingerHost
                                    properties:
                                      webFingerHost:
                                        description: >
                                          Server where the WebFinger service is
                                          hosted. When used, the request to  the
                                          WebFinger resource shall conform as
                                          specified in clause 5.1.3 of  ETSI GS
                                          NFV-SEC 022.
                                        type: string
                                        format: uri
                                  providedConfiguration:
                                    description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                    type: object
                                    required:
                                      - authServerId
                                    properties:
                                      authServerId:
                                        description: >
                                          Authorization server identifier as
                                          defined in ETSI GS NFV-SEC 022.
                                        type: string
                                        format: uri
                                  tlsCipherSuites:
                                    description: >
                                      List of cipher suites that shall be
                                      declared as supported by the API consumer
                                      when  performing the SSL or TLS
                                      negotiation with the authorization server.
                                      Valid values  of cipher suites are defined
                                      in IETF RFC 8447.
                                    type: array
                                    items:
                                      type: string
                                      minItems: 1
                              tlsTunnelInfo:
                                description: >
                                  Information and configuration related to the
                                  use of TLS tunnel. Shall be  present if
                                  authType contains "TLS_TUNNEL".
                                type: object
                                properties:
                                  tlsTunnelCipherSuites:
                                    description: >
                                      List of cipher suites that shall be
                                      declared as supported by the API  consumer
                                      when performing the SSL or TLS negotiation
                                      with the API producer.  Valid values of
                                      cipher suites are defined in IETF RFC
                                      8447.
                                    type: array
                                    items:
                                      type: string
                                      minItems: 1
                        required:
                          - id
                          - name
                          - type
                          - standardVersion
                          - apiVersion
                          - apiEndpoint
                    peerEntityState:
                      description: >
                        State of the peer functional entity as provided by the
                        API consumer when  creating the resource or when
                        updating it with the PATCH method.
                      type: object
                      properties:
                        operationalState:
                          description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                          type: string
                          enum:
                            - STARTED
                            - STOPPED
                            - STOPPING
                            - STARTING
                            - RESTARTING
                        administrativeState:
                          description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                          type: string
                          enum:
                            - LOCKED
                            - UNLOCKED
                            - LOCKING
                      required:
                        - operationalState
                        - administrativeState
                  required:
                    - id
                    - peerEntityId
                    - name
                    - type
                    - peerEntityState
        '400':
          description: |
            400 BAD REQUEST
            Shall be returned upon the following errors: 
              - Invalid attribute-based filtering expression.
                The response body shall contain a ProblemDetails structure, in which 
                the "detail" attribute should convey more information about the error.
              - Invalid attribute selector.
                The response body shall contain a ProblemDetails structure, in which 
                the "detail" attribute should convey more information about the error.
              - Response too big.
                If the NFV-MANO functional entity supports alternative N°1 (error) 
                according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
                this error response shall follow the provisions in clause 5.4.2.2 of 
                ETSI GS NFV-SOL 013.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
  '/peer_entities/{peerEntityId}':
    parameters:
      - name: peerEntityId
        in: path
        description: Identifier of the peer entity
        required: true
        schema:
          description: |
            An identifier with the intention of being globally unique.
          type: string
    get:
      description: >
        Retrieves information and configuration hold in the producer NFV-MANO 
        functional entity with regards to a peer entity by reading an
        individual  peer entity resource.

        This method shall follow the provisions specified in the tables 
        5.5.14.3.2-1 and 5.5.14.3.2-2 for URI query parameters, request  and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when information about an individual peer 
            functional entity has been read successfully.

            The response body shall contain a resource representation of  the
            peer functional entity, as defined in clause 5.6.2.15.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: |
                  This type represents an individual peer entity. 
                type: object
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  peerEntityId:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  name:
                    description: |
                      Human-readable name of the peer functional entity.
                      This attribute can be modified with the PATCH method.
                    type: string
                  type:
                    description: "The enumeration PeerEntityEnumType defines the permitted values  to represent peer functional entities. it shall complains with  the provisions :  - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t  The peer functional entity is a VIM. - WIM\t  The peer functional entity is a WIM. - EM\t  The peer functional entity is an EM. - OSS\t  The peer functional entity is an OSS/BSS.\n"
                    type: string
                    enum:
                      - NFVO
                      - VNFM
                      - VIM
                      - WIM
                      - EM
                      - OSS
                  description:
                    description: |
                      Human-readable description of the peer functional entity.
                      This attribute can be modified with the PATCH method.
                    type: string
                  consumedManoInterfaces:
                    description: >
                      Information of the interface consumed by the NFV-MANO
                      functional entity  from the peer functional entity.

                      This attribute can be modified with the PATCH method.

                      The keys of the map, each of which identifies information
                      about a particular consumed NFV-MANO interface, are
                      managed by the API consumer and referenced from other data
                      structures via the "consumedManoInterfaceIds" attribute.
                    type: object
                    additionalProperties:
                      description: >
                        This type represents an interface consumed by the
                        producer NFV MANO  functional entity from another peer
                        functional entity. 
                      type: object
                      properties:
                        id:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        name:
                          description: |
                            Human-readable name of the NFV-MANO interface.
                          type: string
                        type:
                          description: >
                            Type of the NFV-MANO service interface consumed by
                            the NFV-MANO  functional entity. Valid values are
                            defined in clause 5.6.4.3.
                          type: string
                        standardVersion:
                          description: |
                            A version.
                          type: string
                        apiVersion:
                          description: |
                            A version.
                          type: string
                        apiEndpoint:
                          description: >
                            Consumable API endpoint of the interface. It
                            provides the information relevant about the
                            protocol, host and port,  and path where the
                            interface API can be accessed.
                          type: object
                          properties:
                            apiRoot:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                            apiName:
                              description: >
                                Indicates the interface name in an abbreviated
                                form. Shall be present  for ETSI NFV specified
                                RESTful NFV-MANO APIs. The {apiName} of each 
                                interface is defined in the standard the
                                interface is compliant to  (see also clause 4.1
                                of ETSI GS NFV-SOL 013). May be present
                                otherwise.
                              type: string
                            apiMajorVersion:
                              description: >
                                Indicates the current major version of the API.
                                Shall be present for  ETSI NFV specified RESTful
                                NFV-MANO APIs. The major version is defined  in
                                the standard the interface is compliant to (see
                                also clause 4.1  of ETSI GS NFV-SOL 013). May be
                                present otherwise.
                              type: string
                            apiUri:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                          required:
                            - apiUri
                        securityInfo:
                          description: >
                            This type represents security related information
                            for accessing an NFV-MANO  service interface
                            produced by an NFV-MANO functional entity.
                          type: object
                          required:
                            - authType
                            - oauthServerInfo
                          properties:
                            authType:
                              description: >
                                Type of API request authorization to be used by
                                the API consumer accessing  the API.

                                The support of authorization methods for the API
                                consumer is specified in  clause 8.3.6 of ETSI
                                GS NFV-SOL 013.

                                Permitted values: - TLS_TUNNEL: Using TLS
                                tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                                - OAUTH2: Using access token, as defined by the
                                OAuth 2.0 specification  in IETF RFC 6749. 
                              type: array
                              items:
                                type: string
                                enum:
                                  - TLS_TUNNEL
                                  - OAUTH2
                              minItems: 1
                            oauthServerInfo:
                              description: >
                                OAuth 2.0 authorization server information and
                                configuration.
                              type: object
                              properties:
                                dynamicDiscovery:
                                  description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                  type: object
                                  required:
                                    - webFingerHost
                                  properties:
                                    webFingerHost:
                                      description: >
                                        Server where the WebFinger service is
                                        hosted. When used, the request to  the
                                        WebFinger resource shall conform as
                                        specified in clause 5.1.3 of  ETSI GS
                                        NFV-SEC 022.
                                      type: string
                                      format: uri
                                providedConfiguration:
                                  description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                  type: object
                                  required:
                                    - authServerId
                                  properties:
                                    authServerId:
                                      description: >
                                        Authorization server identifier as
                                        defined in ETSI GS NFV-SEC 022.
                                      type: string
                                      format: uri
                                tlsCipherSuites:
                                  description: >
                                    List of cipher suites that shall be declared
                                    as supported by the API consumer when 
                                    performing the SSL or TLS negotiation with
                                    the authorization server. Valid values  of
                                    cipher suites are defined in IETF RFC 8447.
                                  type: array
                                  items:
                                    type: string
                                    minItems: 1
                            tlsTunnelInfo:
                              description: >
                                Information and configuration related to the use
                                of TLS tunnel. Shall be  present if authType
                                contains "TLS_TUNNEL".
                              type: object
                              properties:
                                tlsTunnelCipherSuites:
                                  description: >
                                    List of cipher suites that shall be declared
                                    as supported by the API  consumer when
                                    performing the SSL or TLS negotiation with
                                    the API producer.  Valid values of cipher
                                    suites are defined in IETF RFC 8447.
                                  type: array
                                  items:
                                    type: string
                                    minItems: 1
                      required:
                        - id
                        - name
                        - type
                        - standardVersion
                        - apiVersion
                        - apiEndpoint
                  peerEntityState:
                    description: >
                      State of the peer functional entity as provided by the API
                      consumer when  creating the resource or when updating it
                      with the PATCH method.
                    type: object
                    properties:
                      operationalState:
                        description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                        type: string
                        enum:
                          - STARTED
                          - STOPPED
                          - STOPPING
                          - STARTING
                          - RESTARTING
                      administrativeState:
                        description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                        type: string
                        enum:
                          - LOCKED
                          - UNLOCKED
                          - LOCKING
                    required:
                      - operationalState
                      - administrativeState
                required:
                  - id
                  - peerEntityId
                  - name
                  - type
                  - peerEntityState
        '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 payload body
            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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
    patch:
      description: >
        Modifies configuration and information of the producer NFV-MANO 
        functional entity with regards to a peer functional entity by  updating
        the corresponding "Individual peer entity" resource.

        Changes to the configurable parameters of the corresponding peer  entity
        are applied to the information managed by the producer  NFV-MANO
        functional entity and reflected in the representation  of this resource.

        This method shall follow the provisions specified in the tables 
        5.5.14.3.4-1 and 5.5.14.3.4-2 for URI query parameters, request  and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      requestBody:
        description: >
          Parameters for the modification of configuration parameters of  the
          peer functional entity, as defined in clause 5.6.2.16

          The Content-Type header shall be set to
          "application/merge-patch+json"  according to IETF RFC 7396.
        content:
          application/merge-patch+json:
            schema:
              description: >
                This type represents attribute modifications for configuration
                parameters  of a peer entity. 
              type: object
              properties:
                name:
                  description: |
                    New value of the "name" attribute in "PeerEntity".
                  type: string
                description:
                  description: >
                    New value of the "description" attribute in "PeerEntity", or
                    "null" to  remove the attribute.
                  type: string
                consumedManoInterfaces:
                  description: "Modification of the \"consumedManoInterfaces\" attribute in the \"PeerEntity\", as defined below this table.\nIf present, these modifications shall be applied according to the rules of JSON Merge PATCH (see IETF RFC 7396).\nNOTE:\tDue to the security sensitive information contained within the attribute  (refer to \"securityInfo\" within the \"ConsumedManoInterfaceInfo\"), based on  access control policies, the API consumer might have read only, write only,  read/write, or no access at all to the attribute’s value. In case the  API consumer is not allowed to modify the value of the security sensitive  attribute, and the modification request includes new attribute values,  the whole modification request shall be rejected, and proper error information  returned.\n"
                  type: object
                  additionalProperties:
                    description: >
                      This type represents an interface consumed by the producer
                      NFV MANO  functional entity from another peer functional
                      entity. 
                    type: object
                    properties:
                      id:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      name:
                        description: |
                          Human-readable name of the NFV-MANO interface.
                        type: string
                      type:
                        description: >
                          Type of the NFV-MANO service interface consumed by the
                          NFV-MANO  functional entity. Valid values are defined
                          in clause 5.6.4.3.
                        type: string
                      standardVersion:
                        description: |
                          A version.
                        type: string
                      apiVersion:
                        description: |
                          A version.
                        type: string
                      apiEndpoint:
                        description: >
                          Consumable API endpoint of the interface. It provides
                          the information relevant about the protocol, host and
                          port,  and path where the interface API can be
                          accessed.
                        type: object
                        properties:
                          apiRoot:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                          apiName:
                            description: >
                              Indicates the interface name in an abbreviated
                              form. Shall be present  for ETSI NFV specified
                              RESTful NFV-MANO APIs. The {apiName} of each 
                              interface is defined in the standard the interface
                              is compliant to  (see also clause 4.1 of ETSI GS
                              NFV-SOL 013). May be present otherwise.
                            type: string
                          apiMajorVersion:
                            description: >
                              Indicates the current major version of the API.
                              Shall be present for  ETSI NFV specified RESTful
                              NFV-MANO APIs. The major version is defined  in
                              the standard the interface is compliant to (see
                              also clause 4.1  of ETSI GS NFV-SOL 013). May be
                              present otherwise.
                            type: string
                          apiUri:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                        required:
                          - apiUri
                      securityInfo:
                        description: >
                          This type represents security related information for
                          accessing an NFV-MANO  service interface produced by
                          an NFV-MANO functional entity.
                        type: object
                        required:
                          - authType
                          - oauthServerInfo
                        properties:
                          authType:
                            description: >
                              Type of API request authorization to be used by
                              the API consumer accessing  the API.

                              The support of authorization methods for the API
                              consumer is specified in  clause 8.3.6 of ETSI GS
                              NFV-SOL 013.

                              Permitted values: - TLS_TUNNEL: Using TLS tunnel,
                              as defined by TLS 1.2 in IETF RFC 5246. - OAUTH2:
                              Using access token, as defined by the OAuth 2.0
                              specification  in IETF RFC 6749. 
                            type: array
                            items:
                              type: string
                              enum:
                                - TLS_TUNNEL
                                - OAUTH2
                            minItems: 1
                          oauthServerInfo:
                            description: >
                              OAuth 2.0 authorization server information and
                              configuration.
                            type: object
                            properties:
                              dynamicDiscovery:
                                description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                type: object
                                required:
                                  - webFingerHost
                                properties:
                                  webFingerHost:
                                    description: >
                                      Server where the WebFinger service is
                                      hosted. When used, the request to  the
                                      WebFinger resource shall conform as
                                      specified in clause 5.1.3 of  ETSI GS
                                      NFV-SEC 022.
                                    type: string
                                    format: uri
                              providedConfiguration:
                                description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                type: object
                                required:
                                  - authServerId
                                properties:
                                  authServerId:
                                    description: >
                                      Authorization server identifier as defined
                                      in ETSI GS NFV-SEC 022.
                                    type: string
                                    format: uri
                              tlsCipherSuites:
                                description: >
                                  List of cipher suites that shall be declared
                                  as supported by the API consumer when 
                                  performing the SSL or TLS negotiation with the
                                  authorization server. Valid values  of cipher
                                  suites are defined in IETF RFC 8447.
                                type: array
                                items:
                                  type: string
                                  minItems: 1
                          tlsTunnelInfo:
                            description: >
                              Information and configuration related to the use
                              of TLS tunnel. Shall be  present if authType
                              contains "TLS_TUNNEL".
                            type: object
                            properties:
                              tlsTunnelCipherSuites:
                                description: >
                                  List of cipher suites that shall be declared
                                  as supported by the API  consumer when
                                  performing the SSL or TLS negotiation with the
                                  API producer.  Valid values of cipher suites
                                  are defined in IETF RFC 8447.
                                type: array
                                items:
                                  type: string
                                  minItems: 1
                    required:
                      - id
                      - name
                      - type
                      - standardVersion
                      - apiVersion
                      - apiEndpoint
                operationalState:
                  description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                  type: string
                  enum:
                    - STARTED
                    - STOPPED
                    - STOPPING
                    - STARTING
                    - RESTARTING
                administrativeState:
                  description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                  type: string
                  enum:
                    - LOCKED
                    - UNLOCKED
                    - LOCKING
        required: true
      responses:
        '200':
          description: >
            200 OK

            Shall be returned when the request has been accepted and completed.

            The response body shall contain a representation of the attribute 
            modifications for the "Individual peer entity" resource, as defined 
            in clause 5.6.2.17.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  This type represents attribute modifications that were
                  performed on an  "Individual peer entity" resource. The
                  attributes that can be included  consist of those requested to
                  be modified explicitly in the 
                  "PeerEntityConfigModificationRequest" data structure. If
                  applicable,  additional attributes of the "PeerEntity" data
                  structure that were  modified implicitly shall also be
                  provided.
                type: object
                properties:
                  name:
                    description: >
                      If present, this attribute signals modifications of the
                      "name" attribute  in "PeerEntity", as defined in clause
                      5.6.2.15.
                    type: string
                  description:
                    description: >
                      If present, this attribute signals modifications of the
                      "description"  attribute in "PeerEntity", as defined in
                      clause 5.6.2.15.
                    type: string
                  consumedManoInterfaces:
                    description: "If present, this attribute signals modifications of the \"consumedManoInterfaces\" attribute in \"PeerEntity\", as defined in  clause 5.6.2.15. \nNOTE:\tDue to the security sensitive information contained within the  attribute (refer to \"securityInfo\" within the \"ConsumedManoInterfaceInfo\"),  based on access control policies, the API consumer might have read only,  write only, read/write, or no access at all to the attribute’s value.  In case the API consumer is not allowed to read the value of the security  sensitive attribute, the attribute shall be omitted when the information  is to be provided in a response message.\n"
                    type: object
                    additionalProperties:
                      description: >
                        This type represents an interface consumed by the
                        producer NFV MANO  functional entity from another peer
                        functional entity. 
                      type: object
                      properties:
                        id:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        name:
                          description: |
                            Human-readable name of the NFV-MANO interface.
                          type: string
                        type:
                          description: >
                            Type of the NFV-MANO service interface consumed by
                            the NFV-MANO  functional entity. Valid values are
                            defined in clause 5.6.4.3.
                          type: string
                        standardVersion:
                          description: |
                            A version.
                          type: string
                        apiVersion:
                          description: |
                            A version.
                          type: string
                        apiEndpoint:
                          description: >
                            Consumable API endpoint of the interface. It
                            provides the information relevant about the
                            protocol, host and port,  and path where the
                            interface API can be accessed.
                          type: object
                          properties:
                            apiRoot:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                            apiName:
                              description: >
                                Indicates the interface name in an abbreviated
                                form. Shall be present  for ETSI NFV specified
                                RESTful NFV-MANO APIs. The {apiName} of each 
                                interface is defined in the standard the
                                interface is compliant to  (see also clause 4.1
                                of ETSI GS NFV-SOL 013). May be present
                                otherwise.
                              type: string
                            apiMajorVersion:
                              description: >
                                Indicates the current major version of the API.
                                Shall be present for  ETSI NFV specified RESTful
                                NFV-MANO APIs. The major version is defined  in
                                the standard the interface is compliant to (see
                                also clause 4.1  of ETSI GS NFV-SOL 013). May be
                                present otherwise.
                              type: string
                            apiUri:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                          required:
                            - apiUri
                        securityInfo:
                          description: >
                            This type represents security related information
                            for accessing an NFV-MANO  service interface
                            produced by an NFV-MANO functional entity.
                          type: object
                          required:
                            - authType
                            - oauthServerInfo
                          properties:
                            authType:
                              description: >
                                Type of API request authorization to be used by
                                the API consumer accessing  the API.

                                The support of authorization methods for the API
                                consumer is specified in  clause 8.3.6 of ETSI
                                GS NFV-SOL 013.

                                Permitted values: - TLS_TUNNEL: Using TLS
                                tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                                - OAUTH2: Using access token, as defined by the
                                OAuth 2.0 specification  in IETF RFC 6749. 
                              type: array
                              items:
                                type: string
                                enum:
                                  - TLS_TUNNEL
                                  - OAUTH2
                              minItems: 1
                            oauthServerInfo:
                              description: >
                                OAuth 2.0 authorization server information and
                                configuration.
                              type: object
                              properties:
                                dynamicDiscovery:
                                  description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                  type: object
                                  required:
                                    - webFingerHost
                                  properties:
                                    webFingerHost:
                                      description: >
                                        Server where the WebFinger service is
                                        hosted. When used, the request to  the
                                        WebFinger resource shall conform as
                                        specified in clause 5.1.3 of  ETSI GS
                                        NFV-SEC 022.
                                      type: string
                                      format: uri
                                providedConfiguration:
                                  description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                  type: object
                                  required:
                                    - authServerId
                                  properties:
                                    authServerId:
                                      description: >
                                        Authorization server identifier as
                                        defined in ETSI GS NFV-SEC 022.
                                      type: string
                                      format: uri
                                tlsCipherSuites:
                                  description: >
                                    List of cipher suites that shall be declared
                                    as supported by the API consumer when 
                                    performing the SSL or TLS negotiation with
                                    the authorization server. Valid values  of
                                    cipher suites are defined in IETF RFC 8447.
                                  type: array
                                  items:
                                    type: string
                                    minItems: 1
                            tlsTunnelInfo:
                              description: >
                                Information and configuration related to the use
                                of TLS tunnel. Shall be  present if authType
                                contains "TLS_TUNNEL".
                              type: object
                              properties:
                                tlsTunnelCipherSuites:
                                  description: >
                                    List of cipher suites that shall be declared
                                    as supported by the API  consumer when
                                    performing the SSL or TLS negotiation with
                                    the API producer.  Valid values of cipher
                                    suites are defined in IETF RFC 8447.
                                  type: array
                                  items:
                                    type: string
                                    minItems: 1
                      required:
                        - id
                        - name
                        - type
                        - standardVersion
                        - apiVersion
                        - apiEndpoint
                  operationalState:
                    description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                    type: string
                    enum:
                      - STARTED
                      - STOPPED
                      - STOPPING
                      - STARTING
                      - RESTARTING
                  administrativeState:
                    description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                    type: string
                    enum:
                      - LOCKED
                      - UNLOCKED
                      - LOCKING
        '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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '409':
          description: >
            409 CONFLICT.

            Shall be returned upon the following error: The operation cannot be 
            executed currently, due to a conflict with the state of the 
            "Individual peer entity" resource.

            Typically, this is due to the fact that another operation is
            ongoing.

            The response body shall contain a ProblemDetails structure, in
            which  the "detail" attribute should convey more information about
            the error.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '412':
          description: >
            412 PRECONDITION FAILED

            Shall be returned upon the following error: A precondition given in 
            an HTTP request header is not fulfilled.

            Typically, this is due to an ETag mismatch, indicating that the 
            resource was modified by another entity.

            The response body should contain a ProblemDetails structure, in
            which  the "detail" attribute should convey more information about
            the error.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
    delete:
      description: >
        Ddeletes an individual peer entity resource. By deleting such  a
        resource in the producer NFV-MANO functional entity representing  a peer
        NFV-MANO entity, the configuration and information with  regards to such
        peer entity is deleted. Consequently, the peering  relationship between
        the producer NFV-MANO functional entity and  the peer entity is
        terminated, i.e., the producer NFV-MANO functional  entity does not have
        the necessary information to communicate/interact  with the peer entity.

        This method shall follow the provisions specified in the tables 
        5.5.14.3.5-1 and 5.5.14.3.5-2 for URI query parameters, request  and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          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
      responses:
        '204':
          description: >
            204 NO CONTENT

            Shall be returned when the "Individual peer entity" resource  has
            been deleted 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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
        '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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '409':
          description: >
            409 CONFLICT.

            Shall be returned upon the following error: The operation cannot be 
            executed currently, due to a conflict with the state of the 
            "Individual peer entity" resource.

            Typically, this is due to the fact that another operation is
            ongoing.

            The response body shall contain a ProblemDetails structure, in
            which  the "detail" attribute should convey more information about
            the error.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '412':
          description: >
            412 PRECONDITION FAILED

            Shall be returned upon the following error: A precondition given in 
            an HTTP request header is not fulfilled.

            Typically, this is due to an ETag mismatch, indicating that the 
            resource was modified by another entity.

            The response body should contain a ProblemDetails structure, in
            which  the "detail" attribute should convey more information about
            the error.
          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.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), 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.

            This error response code is only applicable for methods that have a
            request body.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          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 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], 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 [19] 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 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] 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:
  schemas:
    ManoEntity:
      description: |
        This type represents an NFV-MANO functional entity.
      type: object
      required:
        - id
        - type
        - name
        - description
        - provider
        - softwareVersion
        - manoConfigurableParams
        - manoApplicationState
        - _links
      properties:
        id:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        type:
          description: "The enumeration ManoEntityEnumType defines the permitted values to  represent NFV-MANO functional entities. It shall comply with  the provisions :\n  - NFVO\tThe NFV-MANO functional entity is an NFVO.\n  - VNFM\tThe NFV-MANO functional entity is a VNFM.\n  - VIM\tThe NFV-MANO functional entity is a VIM.\n"
          type: string
          enum:
            - NFVO
            - VNFM
            - VIM
        name:
          description: |
            Human-readable name of the NFV-MANO functional entity.
            This attribute can be modified with the PATCH method.
          type: string
        description:
          description: |
            Human-readable description of the NFV-MANO functional entity.
            This attribute can be modified with the PATCH method.
          type: string
        provider:
          description: >
            Information about the provider of the NFV-MANO functional entity. 
            It typically includes the name of the provider.
          type: string
        softwareVersion:
          description: >
            The version of the software of the NFV-MANO functional entity. $ref:
            "../components/SOL009_schemas.yaml#/components/schemas/Version"
        manoEntityComponents:
          description: "The deployed NFV-MANO functional entity components which realize the  NFV-MANO functional entity. \nNOTE:\tIt is optional for the API producer to support the \"manoEntityComponents\"  attribute.\n"
          type: array
          items:
            description: >
              This type represents information of a deployed component realizing
              part of an  NFV-MANO functional entity. It is optional for the API
              producer to support  this type. 
            type: object
            properties:
              id:
                description: >
                  An identifier that is unique for the respective type within a
                  NFV-MANO functional entity, but that need not be globally
                  unique. Representation: string of variable length..
                type: string
              manoServiceIds:
                description: >
                  References to the NFV-MANO services that depend on the
                  NFV-MANO functional  entity component. The identifier of the
                  ManoService is referred. A service  may depend on multiple
                  components. Multiple services may depend on the same 
                  component.
                type: array
                items:
                  description: >
                    An identifier that is unique for the respective type within
                    a NFV-MANO functional entity, but that need not be globally
                    unique. Representation: string of variable length..
                  type: string
            required:
              - id
        manoServices:
          description: >
            Information about the NFV-MANO services provided by the NFV-MANO 
            functional entity.
          type: array
          items:
            description: >
              This type represents information about an NFV-MANO service
              provided by the  NFV-MANO functional entity.
            type: object
            properties:
              id:
                description: >
                  An identifier that is unique for the respective type within a
                  NFV-MANO functional entity, but that need not be globally
                  unique. Representation: string of variable length..
                type: string
              name:
                description: |
                  Human-readable name of the NFV-MANO service.
                  This attribute can be modified with the PATCH method.
                type: string
              description:
                description: |
                  Human-readable description of the NFV-MANO service.
                  This attribute can be modified with the PATCH method.
                type: string
              manoServiceInterfaceIds:
                description: "Reference to the NFV-MANO interfaces associated to the NFV-MANO service.  If cardinality is greater than one, the type of ManoServiceInterface  (see clause 5.6.3.3) shall be the same. The identifier of the  ManoServiceInterface is referred. \nNOTE:\tA cardinality greater than one supports having different interface  versions or apiEndpoints to be used for accessing the same instance of a  NFV-MANO service.\n"
                type: array
                items:
                  description: >
                    An identifier that is unique for the respective type within
                    a NFV-MANO functional entity, but that need not be globally
                    unique. Representation: string of variable length..
                  type: string
                minItems: 1
              _links:
                description: |
                  Links to resources related to this resource.
                type: object
                properties:
                  manoServiceInterfaces:
                    description: >
                      Link to the "individual NFV-MANO service interface"
                      resources with  information about the associated
                      interfaces to the NFV-MANO service.
                    type: array
                    items:
                      description: >
                        This type represents a link to a resource using an
                        absolute URI.
                      type: object
                      required:
                        - href
                      properties:
                        href:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                    minItems: 1
                required:
                  - manoServiceInterfaces
            required:
              - id
              - name
              - description
              - manoServiceInterfaceIds
              - _links
        manoConfigurableParams:
          description: >
            # Warning: No definition found in the document
            ManoConfigurableParams
        manoApplicationState:
          description: >
            Information and current values of the NFV-MANO functional entity’s
            application state. 
          type: object
          required:
            - operationalState
            - administrativeState
            - usageState
          properties:
            operationalState:
              description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
              type: string
              enum:
                - STARTED
                - STOPPED
                - STOPPING
                - STARTING
                - RESTARTING
            administrativeState:
              description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
              type: string
              enum:
                - LOCKED
                - UNLOCKED
                - LOCKING
            usageState:
              description: "The enumeration UsageStateEnumType defines values representing the usage  state of a managed entity.  The UsageStateEnumType shall comply with the provisions:\n  - IN_USE\tThe managed entity is currently being used.\n  - NOT_IN_USE\tThe managed entity is currently not being used.\n"
              type: string
              enum:
                - IN_USE
                - NOT_IN_USE
        nfvoSpecificInfo:
          description: >
            This type represents information attributes specific to an NFVO
            entity,  and that can be relevant to more than one NFV-MANO service
            offered by an  NFVO entity. 
          type: object
          properties:
            maxOnboardedNsdNum:
              description: >
                Maximum number of NSDs that can be on-boarded on the NFVO. 

                NOTE: If this attribute is not present, the value of this
                parameter  is undefined.
              type: integer
            maxOnboardedVnfPkgNum:
              description: >
                Maximum number of VNF Packages that can be on-boarded on the
                NFVO. 

                NOTE: If this attribute is not present, the value of this
                parameter  is undefined.
              type: integer
            supportedVnfdFormats:
              description: |
                Supported VNFD data formats.
              type: object
              properties:
                vnfdFormat:
                  description: |
                    Name of the VNFD format.
                    Permitted values:
                      - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                      GS NFV-SOL 001 standard.
                      - YANG: The VNFD follows YANG definition according to ETSI 
                      GS NFV-SOL 006 standard.
                  type: string
                  enum:
                    - TOSCA
                    - YANG
                standardVersion:
                  description: |
                    A version.
                  type: string
              required:
                - vnfdFormat
                - standardVersion
            supportedNsdFormats:
              description: |
                Supported NSD data formats.
              type: object
              properties:
                nsdFormat:
                  description: |
                    Name of the NSD format.
                    Permitted values:
                      - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                      GS NFV-SOL 001 standard.
                      - YANG: The VNFD follows YANG definition according to ETSI 
                      GS NFV-SOL 006 standard.
                  type: string
                  enum:
                    - TOSCA
                    - YANG
                standardVersion:
                  description: |
                    A version.
                  type: string
              required:
                - nsdFormat
                - standardVersion
          required:
            - supportedVnfdFormats
            - supportedNsdFormats
        vnfmSpecificInfo:
          description: >
            This type represents information attributes specific to a VNFM
            entity,  and that can be relevant to more than one NFV-MANO service
            offered by  a VNFM entity.
          type: object
          properties:
            resoruceMgmtModeSupport:
              description: |
                The supported resource management modes of the VNFM.
                Permitted values:
                  - DIRECT: The VNFM supports direct mode only.
                  - INDIRECT: The VNFM supports indirect mode only.
                  - BOTH: The VNFM supports both direct and indirect mode.
              type: string
              enum:
                - DIRECT
                - INDIRECT
                - BOTH
            managedVnfInstanceInfos:
              description: >
                The kinds of VNF instances that can be managed, e.g. to
                determine the  compatibility of a VNF with certain VNFM
                according to the vnfmInfo  attribute in the VNFD (see table
                7.1.2.2-1 in ETSI GS NFV-IFA 011).
              type: array
              items:
                type: string
              minItems: 1
            supportedVnfdFormats:
              description: |
                Supported VNFD data formats.
              type: array
              items:
                type: object
                properties:
                  vnfdFormat:
                    description: |
                      Name of the VNFD format.
                      Permitted values:
                        - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                        GS NFV-SOL 001 standard.
                        - YANG: The VNFD follows YANG definition according to ETSI 
                        GS NFV-SOL 006 standard.
                    type: string
                    enum:
                      - TOSCA
                      - YANG
                  standardVersion:
                    description: |
                      A version.
                    type: string
                required:
                  - vnfdFormat
                  - standardVersion
              minItems: 1
          required:
            - resoruceMgmtModeSupport
            - managedVnfInstanceInfos
            - supportedVnfdFormats
        vimSpecificInfo:
          description: >
            This type represents information attributes specific to a VIM
            entity,  and that can be relevant to more than one NFV-MANO service
            offered by  a VIM entity.
          type: object
        _links:
          description: |
            Links to resources related to this resource.
          type: object
          required:
            - self
            - manoServiceInterfaces
            - peerEntities
            - changeState
            - changeStateOpOccs
          properties:
            self:
              description: |
                This type represents a link to a resource using an absolute URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
            manoServiceInterfaces:
              description: |
                This type represents a link to a resource using an absolute URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
            peerEntities:
              description: |
                This type represents a link to a resource using an absolute URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
            changeState:
              description: |
                This type represents a link to a resource using an absolute URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
            changeStateOpOccs:
              description: |
                This type represents a link to a resource using an absolute URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
    ManoConfigModificationRequest:
      description: >
        This type represents attribute modifications for configuration
        parameters  of an NFV-MANO functional entity. 
      type: object
      properties:
        name:
          description: |
            New value of the "name" attribute in "ManoEntity".
          type: string
        description:
          description: |
            New value of the "description" attribute in "ManoEntity".
          type: string
        clockSyncs:
          description: >
            Modifications of the "clockSyncs" attribute in the
            "ManoEntityConfigurableParams". If present, these modifications
            shall be applied according to the rules of JSON Merge PATCH (see
            IETF RFC 7396).
          type: object
          additionalProperties:
            description: |
              This type represents parameters for connecting to an NTP server. 
            type: object
            properties:
              type:
                description: |
                  Type of clock synchronization.
                  Permitted values:
                    - NTP: For Network Time Protocol (NTP) based clock synchronization.
                    - OTHER: For other types of clock synchronization.
                type: string
                enum:
                  - NTP
                  - OTHER
              ntpServerInfo:
                description: >
                  Information for the NTP based clock synchronization.  Shall be
                  present if type = "NTP".
                type: object
                properties:
                  ipAddress:
                    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
                  hostname:
                    description: "Indicates the hostname of the NTP server. \nNOTE:\tEither ipAddress or hostname shall be set, but not both  at the same time.\n"
                    type: string
              otherClockSyncParams:
                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
            required:
              - type
        defaultLogCompileBySizeValue:
          description: |
            Unsigned integer
          type: number
        defaultLogCompileByTimerValue:
          description: |
            Unsigned integer
          type: number
        manoServiceModifications:
          description: >
            New content of certain entries in the "manoServices" attribute
            array  in the "ManoEntity", as defined below this table.
          type: array
          items:
            type: object
            properties:
              id:
                description: >
                  An identifier that is unique for the respective type within a
                  NFV-MANO functional entity, but that need not be globally
                  unique. Representation: string of variable length..
                type: string
              name:
                description: "New value for the \"name\" attribute in the \"ManoService\". \nNOTE:\tAt least one of these attributes shall be provided if requesting  a modification of the NFV-MANO service identified by \"id\".\n"
                type: string
              description:
                description: "New value for the \"description\" attribute in the \"ManoService\".\nNOTE:\tAt least one of these attributes shall be provided if requesting  a modification of the NFV-MANO service identified by \"id\".\n"
                type: string
            required:
              - id
    ManoConfigModifications:
      description: >
        This type represents attribute modifications that were performed on the 
        "NFV-MANO entity" resource of the producer NFV-MANO functional entity. 
        The attributes that can be included consist of those requested to be 
        modified explicitly in the "ManoConfigModificationRequest" data
        structure. 
      type: object
      properties:
        name:
          description: >
            If present, this attribute signals modifications of the "name" 
            attribute in "ManoEntity", as defined in clause 5.6.2.3
          type: string
        description:
          description: >
            If present, this attribute signals modifications of the
            "description"  attribute in "ManoEntity", as defined in clause
            5.6.2.3.
          type: string
        clockSyncs:
          description: >
            If present, this attribute signals modifications of the "clockSyncs"
            attribute in "ManoEntityConfigurableParams", as defined in clause
            5.6.2.3.
          type: object
          additionalProperties:
            description: |
              This type represents parameters for connecting to an NTP server. 
            type: object
            properties:
              type:
                description: |
                  Type of clock synchronization.
                  Permitted values:
                    - NTP: For Network Time Protocol (NTP) based clock synchronization.
                    - OTHER: For other types of clock synchronization.
                type: string
                enum:
                  - NTP
                  - OTHER
              ntpServerInfo:
                description: >
                  Information for the NTP based clock synchronization.  Shall be
                  present if type = "NTP".
                type: object
                properties:
                  ipAddress:
                    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
                  hostname:
                    description: "Indicates the hostname of the NTP server. \nNOTE:\tEither ipAddress or hostname shall be set, but not both  at the same time.\n"
                    type: string
              otherClockSyncParams:
                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
            required:
              - type
        defaultLogCompileBySizeValue:
          description: |
            Unsigned integer
          type: number
        defaultLogCompileByTimerValue:
          description: |
            Unsigned integer
          type: number
        manoServiceModifications:
          description: >
            If present, this attribute signals modifications of the
            "manoServices"  attribute array in the "ManoEntity", as defined in
            clause 5.6.2.3.
          type: array
          items:
            type: object
            properties:
              id:
                description: >
                  An identifier that is unique for the respective type within a
                  NFV-MANO functional entity, but that need not be globally
                  unique. Representation: string of variable length..
                type: string
              name:
                description: >
                  If present, this attribute signals modification of the "name" 
                  attribute in the "ManoService".
                type: string
              description:
                description: >
                  If present, this attribute signals modification of the 
                  "description" attribute in the "ManoService".
                type: string
            required:
              - id
    CimSubscriptionRequest:
      description: >
        This type represents a subscription request related to notifications 
        about NFV-MANO configuration and information management changes. 
      type: object
      properties:
        filter:
          description: >
            This type represents a subscription filter related to notifications 
            about NFV-MANO configuration and information management. 
          type: object
          properties:
            manoEntitySubscriptionFilter:
              description: >
                This type represents subscription filter criteria to match
                NFV-MANO functional  entities and their associated managed
                objects. 
              type: object
              properties:
                manoEntityId:
                  description: |
                    An identifier with the intention of being globally unique.
                  type: string
                manoServiceIds:
                  description: "manoServiceIds\tIdentifierInManoEntity\t0..N\tIf present, match NFV-MANO  services with an instance identifier listed in this attribute.\nThe attributes \"manoServiceIds\" and \"manoServiceNames\" are alternatives  to reference to NFV-MANO services in a filter. They should not be used  together in the same filter instance, but one alternative should be chosen.\n"
                  type: array
                  items:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                manoServiceNames:
                  description: >
                    If present, match NFV-MANO services with an NFV-MANO service
                    name listed  in this attribute.

                    The attributes "manoServiceIds" and "manoServiceNames" are
                    alternatives  to reference to NFV-MANO services in a filter.
                    They should not be used  together in the same filter
                    instance, but one alternative should be chosen.
                  type: array
                  items:
                    type: string
                manoServiceInterfaceIds:
                  description: >
                    If present, match NFV-MANO functional entity produced
                    interfaces with an  instance identifier listed in this
                    attribute.

                    The attributes "manoServiceInterfaceIds" and
                    "manoServiceInterfaceNames"  are alternatives to reference
                    to NFV-MANO functional entity produced  interfaces in a
                    filter. They should not be used both in the same filter 
                    instance, but one alternative should be chosen.
                  type: array
                  items:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                manoServiceInterfaceNames:
                  description: >
                    If present, match NFV-MANO functional entity produced
                    interfaces with an  instance Name listed in this attribute.

                    The attributes "manoServiceInterfaceIds" and
                    "manoServiceInterfaceNames"  are alternatives to reference
                    to NFV-MANO functional entity produced  interfaces in a
                    filter. They should not be used both in the same filter 
                    instance, but one alternative should be chosen.
                  type: array
                  items:
                    type: string
                consumedManoInterfaceIds:
                  description: >
                    If present, match NFV-MANO functional entity consumed
                    interfaces with an  instance identifier listed in this
                    attribute.

                    The attributes "consumedManoInterfaceIds" and
                    "consumedManoInterfaceNames"  are alternatives to reference
                    to NFV-MANO functional entity consumed  interfaces in a
                    filter. They should not be used both in the same filter 
                    instance, but one alternative should be chosen.
                  type: array
                  items:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                consumedManoInterfaceNames:
                  description: >
                    If present, match NFV-MANO functional entity consumed
                    interfaces with an  instance Name listed in this attribute.

                    The attributes "consumedManoInterfaceIds" and
                    "consumedManoInterfaceNames"  are alternatives to reference
                    to NFV-MANO functional entity consumed  interfaces in a
                    filter. They should not be used both in the same filter 
                    instance, but one alternative should be chosen.
                  type: array
                  items:
                    type: string
            notificationTypes:
              description: "Match particular notification types. \nPermitted values:\n  - InformationChangedNotification\n  - ChangeStateNotification\n\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are  spelled exactly as the names of the notification types to facilitate  automated code generation systems.\n"
              type: array
              items:
                type: string
                enum:
                  - InformationChangedNotification
                  - ChangeStateNotification
        callbackUri:
          description: |
            String formatted according to IETF RFC 3986.
          type: string
        authentication:
          type: object
          required:
            - authType
          properties:
            authType:
              description: >
                Defines the types of Authentication / Authorization which the
                API consumer is willing to accept when receiving a notification.
                Permitted values: * BASIC: In every HTTP request to the
                notification endpoint, use
                  HTTP Basic authentication with the client credentials.
                * OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the
                  notification endpoint, use an OAuth 2.0 Bearer token, obtained
                  using the client credentials grant type.
                * TLS_CERT: Every HTTP request to the notification endpoint is
                sent
                  over a mutually authenticated TLS session, i.e. not only the
                  server is authenticated, but also the client is authenticated
                  during the TLS tunnel setup.
              type: array
              items:
                type: string
                enum:
                  - BASIC
                  - OAUTH2_CLIENT_CREDENTIALS
                  - TLS_CERT
            paramsBasic:
              description: >
                Parameters for authentication/authorization using BASIC. Shall
                be present if authType is "BASIC" and the contained information
                has not been provisioned out of band. Shall be absent otherwise.
              type: object
              properties:
                userName:
                  description: >
                    Username to be used in HTTP Basic authentication. Shall be
                    present if it has not been provisioned out of band.
                  type: string
                password:
                  description: >
                    Password to be used in HTTP Basic authentication. Shall be
                    present if it has not been provisioned out of band.
                  type: string
            paramsOauth2ClientCredentials:
              description: >
                Parameters for authentication/authorization using
                OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is
                "OAUTH2_CLIENT_CREDENTIALS" and the contained information has
                not been provisioned out of band. Shall be absent otherwise.
              type: object
              properties:
                clientId:
                  description: >
                    Client identifier to be used in the access token request of
                    the OAuth 2.0 client credentials grant type. Shall be
                    present if it has not been provisioned out of band. The
                    clientId and clientPassword passed in a subscription shall
                    not be the same as the clientId and clientPassword that are
                    used to obtain authorization for API requests. Client
                    credentials may differ between subscriptions. The value of
                    clientPassword should be generated by a random process.
                  type: string
                clientPassword:
                  description: >
                    Client password to be used in the access token request of
                    the OAuth 2.0 client credentials grant type. Shall be
                    present if it has not been provisioned out of band. The
                    clientId and clientPassword passed in a subscription shall
                    not be the same as the clientId and clientPassword that are
                    used to obtain authorization for API requests. Client
                    credentials may differ between subscriptions. The value of
                    clientPassword should be generated by a random process.
                  type: string
                tokenEndpoint:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
      required:
        - callbackUri
    CimSubscription:
      description: >
        This type represents a subscription related to notifications about 
        NFV-MANO configuration and information management changes
      type: object
      properties:
        id:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        filter:
          description: >
            This type represents a subscription filter related to notifications 
            about NFV-MANO configuration and information management. 
          type: object
          properties:
            manoEntitySubscriptionFilter:
              description: >
                This type represents subscription filter criteria to match
                NFV-MANO functional  entities and their associated managed
                objects. 
              type: object
              properties:
                manoEntityId:
                  description: |
                    An identifier with the intention of being globally unique.
                  type: string
                manoServiceIds:
                  description: "manoServiceIds\tIdentifierInManoEntity\t0..N\tIf present, match NFV-MANO  services with an instance identifier listed in this attribute.\nThe attributes \"manoServiceIds\" and \"manoServiceNames\" are alternatives  to reference to NFV-MANO services in a filter. They should not be used  together in the same filter instance, but one alternative should be chosen.\n"
                  type: array
                  items:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                manoServiceNames:
                  description: >
                    If present, match NFV-MANO services with an NFV-MANO service
                    name listed  in this attribute.

                    The attributes "manoServiceIds" and "manoServiceNames" are
                    alternatives  to reference to NFV-MANO services in a filter.
                    They should not be used  together in the same filter
                    instance, but one alternative should be chosen.
                  type: array
                  items:
                    type: string
                manoServiceInterfaceIds:
                  description: >
                    If present, match NFV-MANO functional entity produced
                    interfaces with an  instance identifier listed in this
                    attribute.

                    The attributes "manoServiceInterfaceIds" and
                    "manoServiceInterfaceNames"  are alternatives to reference
                    to NFV-MANO functional entity produced  interfaces in a
                    filter. They should not be used both in the same filter 
                    instance, but one alternative should be chosen.
                  type: array
                  items:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                manoServiceInterfaceNames:
                  description: >
                    If present, match NFV-MANO functional entity produced
                    interfaces with an  instance Name listed in this attribute.

                    The attributes "manoServiceInterfaceIds" and
                    "manoServiceInterfaceNames"  are alternatives to reference
                    to NFV-MANO functional entity produced  interfaces in a
                    filter. They should not be used both in the same filter 
                    instance, but one alternative should be chosen.
                  type: array
                  items:
                    type: string
                consumedManoInterfaceIds:
                  description: >
                    If present, match NFV-MANO functional entity consumed
                    interfaces with an  instance identifier listed in this
                    attribute.

                    The attributes "consumedManoInterfaceIds" and
                    "consumedManoInterfaceNames"  are alternatives to reference
                    to NFV-MANO functional entity consumed  interfaces in a
                    filter. They should not be used both in the same filter 
                    instance, but one alternative should be chosen.
                  type: array
                  items:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                consumedManoInterfaceNames:
                  description: >
                    If present, match NFV-MANO functional entity consumed
                    interfaces with an  instance Name listed in this attribute.

                    The attributes "consumedManoInterfaceIds" and
                    "consumedManoInterfaceNames"  are alternatives to reference
                    to NFV-MANO functional entity consumed  interfaces in a
                    filter. They should not be used both in the same filter 
                    instance, but one alternative should be chosen.
                  type: array
                  items:
                    type: string
            notificationTypes:
              description: "Match particular notification types. \nPermitted values:\n  - InformationChangedNotification\n  - ChangeStateNotification\n\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are  spelled exactly as the names of the notification types to facilitate  automated code generation systems.\n"
              type: array
              items:
                type: string
                enum:
                  - InformationChangedNotification
                  - ChangeStateNotification
        callbackUri:
          description: |
            String formatted according to IETF RFC 3986.
          type: string
        _links:
          description: |
            Links to resources related to this resource.
          type: object
          properties:
            self:
              description: |
                This type represents a link to a resource using an absolute URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
          required:
            - self
      required:
        - id
        - callbackUri
        - _links
    ChangeStateRequest:
      description: >
        This type represents request parameters for changing the state of a
        managed entity. 
      type: object
      properties:
        operationalStateChange:
          description: "A change of operational state. Shall be present if the state change request refers to the operational state.  NOTE:\tIn the present document version, a request shall only include an  operational state change (attribute \"operationalStateChange\") or an  administrative state change request (attribute \"administrativeStateChange\"),  but not both.\n"
          type: object
          properties:
            operationalStateAction:
              description: "The enumeration ChangeOperationalStateEnumType defines permitted values  for the change state operation.  The ChangeOperationalStateEnumType shall comply with the provisions:\n  - START\tTo start the managed entity.\n  - STOP\tTo stop the managed entity.\n  - RESTART\tTo stop and start again the managed entity.\n"
              type: string
              enum:
                - START
                - STOP
                - RESTART
            stopType:
              description: "The enumeration ChangeStateOpOccStateEnumType defines permitted values  for the change state operation. It shall comply with the provisions:\n  - GRACEFUL\tTo stop the managed entity immediately after accepting the request.\n  - FORCEFUL\tTo stop the managed entity attempting to gracefully discharge the entity from service.\n"
              type: string
              enum:
                - GRACEFUL
                - FORCEFUL
            gracefulStopTimeout:
              description: "The time internal (in seconds) to wait for the entity to be taken out  of service during graceful stop. \nNOTE:\tThe \"stopType\" shall only be provided when the \"operationalStateAction\"  attribute is equal to \"STOP\" or \"RESTART\".  The \"gracefulStopTimeout\" shall  be absent when the \"stopType\" attribute is equal to \"FORCEFUL\", and may  be provided otherwise.\n"
              type: integer
          required:
            - operationalStateAction
        administrativeStateChange:
          description: "A change of administrative state. Shall be present if the state change request refers to the administrative state. \nNOTE:\tIn the present document version, a request shall only include an  operational state change (attribute \"operationalStateChange\") or an  administrative state change request (attribute \"administrativeStateChange\"),  but not both.\n"
          type: object
          properties:
            administrativeStateAction:
              description: "The enumeration ChangeAdministrativeStateEnumType defines permitted values  for the change of administrative state operation.  The ChangeAdministrativeStateEnumType shall comply with the provisions:\n  - LOCK\tTo lock the managed entity.\n  - UNLOCK\tTo unlock the managed entity.\n"
              type: string
              enum:
                - LOCK
                - UNLOCK
          required:
            - administrativeStateAction
    ChangeStateOpOcc:
      description: |
        This type represents a Change state operation occurrence. 
      type: object
      properties:
        id:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        operationState:
          description: "The enumeration ChangeStateOpOccStateEnumType defines permitted values for the change state operation. It shall comply with the provisions :\n  - PROCESSING\tThe change state operation is currently in execution.\n  - COMPLETED\tThe change state operation has been completed successfully.\n  - FAILED\tThe change state operation has failed.\n"
          type: string
          enum:
            - PROCESSING
            - COMPLETED
            - FAILED
        stateEnteredTime:
          description: >
            Date-time stamp. Representation: String formatted according to IETF
            RFC 3339.
          type: string
          format: date-time
        startTime:
          description: >
            Date-time stamp. Representation: String formatted according to IETF
            RFC 3339.
          type: string
          format: date-time
        managedObjectRef:
          description: >
            This type represents the identifier to reference a managed object of
            a  particular type. 
          type: object
          properties:
            type:
              description: >
                Indicates the type of managed object. Permitted values:
                  - MANO_ENTITY
                  - MANO_SERVICE
                  - MANO_SERVICE_IF
                  - CONSUMED_MANO_IF
                  - MANO_ENTITY_COMPONENT

                The "MANO_ENTITY COMPONENT" is only applicable if attribute
                "manoEntityComponents" in "ManoEntity" is supported by the API
                producer.
              type: string
              enum:
                - MANO_ENTITY
                - MANO_SERVICE
                - MANO_SERVICE_IF
                - CONSUMED_MANO_IF
                - MANO_ENTITY_COMPONENT
            objectId:
              description: |
                An identifier with the intention of being globally unique.
              type: string
            subObjectId:
              description: >
                An identifier that is unique for the respective type within a
                NFV-MANO functional entity, but that need not be globally
                unique. Representation: string of variable length..
              type: string
          required:
            - type
            - objectId
        changeOperationalStateRequest:
          description: "The enumeration ChangeOperationalStateEnumType defines permitted values  for the change state operation.  The ChangeOperationalStateEnumType shall comply with the provisions:\n  - START\tTo start the managed entity.\n  - STOP\tTo stop the managed entity.\n  - RESTART\tTo stop and start again the managed entity.\n"
          type: string
          enum:
            - START
            - STOP
            - RESTART
        changeAdministrativeStateRequest:
          description: "The enumeration ChangeAdministrativeStateEnumType defines permitted values  for the change of administrative state operation.  The ChangeAdministrativeStateEnumType shall comply with the provisions:\n  - LOCK\tTo lock the managed entity.\n  - UNLOCK\tTo unlock the managed entity.\n"
          type: string
          enum:
            - LOCK
            - UNLOCK
        operationParams:
          description: >
            Input parameters of the change state operation. This attribute shall
            be  formatted according to the request data type of the related
            change state  operation. 

            The following mapping between operationType and the data type of
            this  attribute shall apply:
              - CHANGE_STATE: ChangeStateRequest
              
            This attribute shall be present if this data type is returned in a
            response  to reading an individual resource, and may be present
            according to the chosen  attribute selector parameter if this data
            type is returned in a response to  a query of a container resource.
      required:
        - id
        - operationState
        - stateEnteredTime
        - startTime
        - managedObjectRef
    ManoServiceInterface:
      description: >
        This type represents an individual NFV-MANO service interface produced
        by  an NFV-MANO functional entity. 
      type: object
      properties:
        id:
          description: >
            An identifier that is unique for the respective type within a
            NFV-MANO functional entity, but that need not be globally unique.
            Representation: string of variable length..
          type: string
        name:
          description: |
            Human-readable name of the NFV-MANO functional entity interface.
            This attribute can be modified with the PATCH method.
          type: string
        type:
          description: >
            Type of the NFV-MANO service interface produced by the NFV-MANO
            functional  entity. Valid values are defined in clause 5.6.4.3.
          type: string
        standardVersion:
          description: |
            A version.
          type: string
        providerSpecificApiVersion:
          description: |
            A version.
          type: string
        apiVersion:
          description: |
            A version.
          type: string
        apiEndpoint:
          description: |
            Exposed API endpoint of the interface.
          type: object
          properties:
            apiRoot:
              description: |
                String formatted according to IETF RFC 3986.
              type: string
            apiName:
              description: >
                Indicates the interface name in an abbreviated form. Shall be
                present  for ETSI NFV specified RESTful NFV-MANO APIs. The
                {apiName} of each  interface is defined in the standard the
                interface is compliant to  (see also clause 4.1 of ETSI GS
                NFV-SOL 013). May be present otherwise.
              type: string
            apiMajorVersion:
              description: >
                Indicates the current major version of the API. Shall be present
                for  ETSI NFV specified RESTful NFV-MANO APIs. The major version
                is defined  in the standard the interface is compliant to (see
                also clause 4.1 of  ETSI GS NFV-SOL 013). May be present
                otherwise.
              type: string
            apiUri:
              description: |
                String formatted according to IETF RFC 3986.
              type: string
          required:
            - apiUri
        maxConcurrentIntOpNumber:
          description: "Maximum number of concurrent operation requests supported on this interface. \nNOTE:\tIf this attribute is not present, the value of this parameter  is undefined. Overload is handled by the error handling schemes defined  by the applicable API specification.\n"
          type: integer
        supportedOperations:
          description: |
            Information about supported operations of this interface.
          type: array
          items:
            type: object
            properties:
              operationName:
                description: |
                  Name of the operation supported on the interface.
                type: string
              maxConcurrentOpNumber:
                description: "Maximum number of concurrent requests supported by the interface operation. \nNOTE:\tIf this attribute is not present, the value of this parameter  is undefined. Overload is handled by the error handling schemes defined  by the applicable API specification.\n"
                type: integer
            required:
              - operationName
          minItems: 1
        interfaceState:
          description: |
            State of the NFV-MANO service interface.
          properties:
            operationalState:
              description: "The enumeration InterfaceOperationalStateEnumType defines values representing  the operational state of an NFV-MANO service interface type of managed entity.  The InterfaceOperationalStateEnumType shall comply with the provisions :\n   - STARTED\tThe managed entity is operational.\n   - STOPPED\tThe managed entity is not operational.\n   - STOPPING\tThe managed entity is in the transition to stop.\n   - STARTING\tThe managed entity is in the transition to start and become operational.\n"
              type: string
              enum:
                - STARTED
                - STOPPED
                - STOPPING
                - STARTING
            administrativeState:
              description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
              type: string
              enum:
                - LOCKED
                - UNLOCKED
                - LOCKING
            usageState:
              description: "The enumeration UsageStateEnumType defines values representing the usage  state of a managed entity.  The UsageStateEnumType shall comply with the provisions:\n  - IN_USE\tThe managed entity is currently being used.\n  - NOT_IN_USE\tThe managed entity is currently not being used.\n"
              type: string
              enum:
                - IN_USE
                - NOT_IN_USE
          required:
            - operationalState
            - administrativeState
            - usageState
        securityInfo:
          description: >
            This type represents security related information of an NFV-MANO 
            service interface produced by an NFV-MANO functional entity. 
          type: object
          properties:
            authType:
              description: >
                Type of API request authorization to be used by the API
                producer.

                The support of authorization methods for the API producer is
                specified  in clause 8.3.6 of ETSI GS NFV-SOL 013.

                Permitted values:
                  - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                  - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
                  in IETF RFC 6749. 
              type: array
              items:
                type: string
                enum:
                  - TLS_TUNNEL
                  - OAUTH2
              minItems: 1
            oauthServerInfo:
              description: |
                OAuth 2.0 authorization server information and configuration.
              type: object
              properties:
                dynamicDiscovery:
                  description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                  type: object
                  properties:
                    webFingerHost:
                      description: |
                        String formatted according to IETF RFC 3986.
                      type: string
                  required:
                    - webFingerHost
                providedConfiguration:
                  description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                  type: object
                  properties:
                    authServerId:
                      description: |
                        String formatted according to IETF RFC 3986.
                      type: string
                  required:
                    - authServerId
                tlsCipherSuites:
                  description: >
                    List of cipher suites that shall be declared as supported by
                    the  API producer when performing the SSL or TLS negotiation
                    with the  authorization server. Valid values of cipher
                    suites are defined  in IETF RFC 8447.
                  type: array
                  items:
                    type: string
                  minItems: 1
              required:
                - providedConfiguration
                - tlsCipherSuites
            tlsTunnelInfo:
              description: >
                Information and configuration related to the use of TLS tunnel. 
                Shall be present if authType contains "TLS_TUNNEL".
              type: object
              properties:
                tlsTunnelCipherSuites:
                  description: >-
                    List of cipher suites that shall be declared as supported by
                    the API producer when performing the SSL or TLS negotiation
                    with the API client. Valid values of cipher suites are
                    defined in IETF RFC 8447.
                  type: array
                  items:
                    type: string
                  minItems: 1
              required:
                - tlsTunnelCipherSuites
          required:
            - authType
            - oauthServerInfo
        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
      required:
        - id
        - name
        - type
        - standardVersion
        - providerSpecificApiVersion
        - apiVersion
        - apiEndpoint
        - supportedOperations
        - interfaceState
    ManoServiceInterfaceModificationRequest:
      description: >
        This type represents attribute modifications for configuration
        parameters of  an NFV-MANO service interface of the producer NFV-MANO
        functional entity. 
      type: object
      properties:
        name:
          description: "New value of the \"name\" attribute in \"ManoServiceInterface\". \nNOTE:\tChanging the name does not change the corresponding standardized  API name in the resource URI (refer to \"{apiName}\" defined in clause 4.1  of ETSI GS NFV-SOL 013).\n"
          type: string
        apiRoot:
          description: |
            String formatted according to IETF RFC 3986.
          type: string
        apiUri:
          description: |
            String formatted according to IETF RFC 3986.
          type: string
        securityInfo:
          description: >
            This type represents security related information of an NFV-MANO 
            service interface produced by an NFV-MANO functional entity. 
          type: object
          properties:
            authType:
              description: >
                Type of API request authorization to be used by the API
                producer.

                The support of authorization methods for the API producer is
                specified  in clause 8.3.6 of ETSI GS NFV-SOL 013.

                Permitted values:
                  - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                  - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
                  in IETF RFC 6749. 
              type: array
              items:
                type: string
                enum:
                  - TLS_TUNNEL
                  - OAUTH2
              minItems: 1
            oauthServerInfo:
              description: |
                OAuth 2.0 authorization server information and configuration.
              type: object
              properties:
                dynamicDiscovery:
                  description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                  type: object
                  properties:
                    webFingerHost:
                      description: |
                        String formatted according to IETF RFC 3986.
                      type: string
                  required:
                    - webFingerHost
                providedConfiguration:
                  description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                  type: object
                  properties:
                    authServerId:
                      description: |
                        String formatted according to IETF RFC 3986.
                      type: string
                  required:
                    - authServerId
                tlsCipherSuites:
                  description: >
                    List of cipher suites that shall be declared as supported by
                    the  API producer when performing the SSL or TLS negotiation
                    with the  authorization server. Valid values of cipher
                    suites are defined  in IETF RFC 8447.
                  type: array
                  items:
                    type: string
                  minItems: 1
              required:
                - providedConfiguration
                - tlsCipherSuites
            tlsTunnelInfo:
              description: >
                Information and configuration related to the use of TLS tunnel. 
                Shall be present if authType contains "TLS_TUNNEL".
              type: object
              properties:
                tlsTunnelCipherSuites:
                  description: >-
                    List of cipher suites that shall be declared as supported by
                    the API producer when performing the SSL or TLS negotiation
                    with the API client. Valid values of cipher suites are
                    defined in IETF RFC 8447.
                  type: array
                  items:
                    type: string
                  minItems: 1
              required:
                - tlsTunnelCipherSuites
          required:
            - authType
            - oauthServerInfo
        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
    ManoServiceInterfaceModifications:
      description: >
        This type represents attribute modifications that were performed on an 
        Individual NFV-MANO service interface" resource. The attributes that
        can  be included consist of those requested to be modified explicitly in
        the  "ManoServiceInterfaceModificationRequest" data structure. If
        applicable,  additional attributes of the "ManoServiceInterface" data
        structure that  were modified implicitly shall also be provided. 
      type: object
      properties:
        name:
          description: >
            If present, this attribute signals modifications of the "name"
            attribute in  "ManoServiceInterface", as defined in clause 5.6.2.11.
          type: string
        apiRoot:
          description: |
            String formatted according to IETF RFC 3986.
          type: string
        apiUri:
          description: |
            String formatted according to IETF RFC 3986.
          type: string
        securityInfo:
          description: >
            This type represents security related information of an NFV-MANO 
            service interface produced by an NFV-MANO functional entity. 
          type: object
          properties:
            authType:
              description: >
                Type of API request authorization to be used by the API
                producer.

                The support of authorization methods for the API producer is
                specified  in clause 8.3.6 of ETSI GS NFV-SOL 013.

                Permitted values:
                  - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                  - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
                  in IETF RFC 6749. 
              type: array
              items:
                type: string
                enum:
                  - TLS_TUNNEL
                  - OAUTH2
              minItems: 1
            oauthServerInfo:
              description: |
                OAuth 2.0 authorization server information and configuration.
              type: object
              properties:
                dynamicDiscovery:
                  description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                  type: object
                  properties:
                    webFingerHost:
                      description: |
                        String formatted according to IETF RFC 3986.
                      type: string
                  required:
                    - webFingerHost
                providedConfiguration:
                  description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                  type: object
                  properties:
                    authServerId:
                      description: |
                        String formatted according to IETF RFC 3986.
                      type: string
                  required:
                    - authServerId
                tlsCipherSuites:
                  description: >
                    List of cipher suites that shall be declared as supported by
                    the  API producer when performing the SSL or TLS negotiation
                    with the  authorization server. Valid values of cipher
                    suites are defined  in IETF RFC 8447.
                  type: array
                  items:
                    type: string
                  minItems: 1
              required:
                - providedConfiguration
                - tlsCipherSuites
            tlsTunnelInfo:
              description: >
                Information and configuration related to the use of TLS tunnel. 
                Shall be present if authType contains "TLS_TUNNEL".
              type: object
              properties:
                tlsTunnelCipherSuites:
                  description: >-
                    List of cipher suites that shall be declared as supported by
                    the API producer when performing the SSL or TLS negotiation
                    with the API client. Valid values of cipher suites are
                    defined in IETF RFC 8447.
                  type: array
                  items:
                    type: string
                  minItems: 1
              required:
                - tlsTunnelCipherSuites
          required:
            - authType
            - oauthServerInfo
        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
    CreatePeerEntityRequest:
      description: >
        This type represents request parameters for the creation of a new peer
        entity resource. 
      type: object
      properties:
        peerEntityId:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        name:
          description: |
            Human-readable name of the peer functional entity.
          type: string
        type:
          description: "The enumeration PeerEntityEnumType defines the permitted values  to represent peer functional entities. it shall complains with  the provisions :  - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t  The peer functional entity is a VIM. - WIM\t  The peer functional entity is a WIM. - EM\t  The peer functional entity is an EM. - OSS\t  The peer functional entity is an OSS/BSS.\n"
          type: string
          enum:
            - NFVO
            - VNFM
            - VIM
            - WIM
            - EM
            - OSS
        description:
          description: |
            Human-readable description of the peer functional entity.
          type: string
        consumedManoInterfaces:
          description: >
            Initial information of the interface consumed by the NFV-MANO
            functional entity from the peer functional entity.
          type: object
          additionalProperties:
            description: >
              This type represents an interface consumed by the producer NFV
              MANO  functional entity from another peer functional entity. 
            type: object
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              name:
                description: |
                  Human-readable name of the NFV-MANO interface.
                type: string
              type:
                description: >
                  Type of the NFV-MANO service interface consumed by the
                  NFV-MANO  functional entity. Valid values are defined in
                  clause 5.6.4.3.
                type: string
              standardVersion:
                description: |
                  A version.
                type: string
              apiVersion:
                description: |
                  A version.
                type: string
              apiEndpoint:
                description: >
                  Consumable API endpoint of the interface. It provides the
                  information relevant about the protocol, host and port,  and
                  path where the interface API can be accessed.
                type: object
                properties:
                  apiRoot:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                  apiName:
                    description: >
                      Indicates the interface name in an abbreviated form. Shall
                      be present  for ETSI NFV specified RESTful NFV-MANO APIs.
                      The {apiName} of each  interface is defined in the
                      standard the interface is compliant to  (see also clause
                      4.1 of ETSI GS NFV-SOL 013). May be present otherwise.
                    type: string
                  apiMajorVersion:
                    description: >
                      Indicates the current major version of the API. Shall be
                      present for  ETSI NFV specified RESTful NFV-MANO APIs. The
                      major version is defined  in the standard the interface is
                      compliant to (see also clause 4.1  of ETSI GS NFV-SOL
                      013). May be present otherwise.
                    type: string
                  apiUri:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                required:
                  - apiUri
              securityInfo:
                description: >
                  This type represents security related information for
                  accessing an NFV-MANO  service interface produced by an
                  NFV-MANO functional entity.
                type: object
                required:
                  - authType
                  - oauthServerInfo
                properties:
                  authType:
                    description: >
                      Type of API request authorization to be used by the API
                      consumer accessing  the API.

                      The support of authorization methods for the API consumer
                      is specified in  clause 8.3.6 of ETSI GS NFV-SOL 013.

                      Permitted values: - TLS_TUNNEL: Using TLS tunnel, as
                      defined by TLS 1.2 in IETF RFC 5246. - OAUTH2: Using
                      access token, as defined by the OAuth 2.0 specification 
                      in IETF RFC 6749. 
                    type: array
                    items:
                      type: string
                      enum:
                        - TLS_TUNNEL
                        - OAUTH2
                    minItems: 1
                  oauthServerInfo:
                    description: >
                      OAuth 2.0 authorization server information and
                      configuration.
                    type: object
                    properties:
                      dynamicDiscovery:
                        description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                        type: object
                        required:
                          - webFingerHost
                        properties:
                          webFingerHost:
                            description: >
                              Server where the WebFinger service is hosted. When
                              used, the request to  the WebFinger resource shall
                              conform as specified in clause 5.1.3 of  ETSI GS
                              NFV-SEC 022.
                            type: string
                            format: uri
                      providedConfiguration:
                        description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                        type: object
                        required:
                          - authServerId
                        properties:
                          authServerId:
                            description: >
                              Authorization server identifier as defined in ETSI
                              GS NFV-SEC 022.
                            type: string
                            format: uri
                      tlsCipherSuites:
                        description: >
                          List of cipher suites that shall be declared as
                          supported by the API consumer when  performing the SSL
                          or TLS negotiation with the authorization server.
                          Valid values  of cipher suites are defined in IETF RFC
                          8447.
                        type: array
                        items:
                          type: string
                          minItems: 1
                  tlsTunnelInfo:
                    description: >
                      Information and configuration related to the use of TLS
                      tunnel. Shall be  present if authType contains
                      "TLS_TUNNEL".
                    type: object
                    properties:
                      tlsTunnelCipherSuites:
                        description: >
                          List of cipher suites that shall be declared as
                          supported by the API  consumer when performing the SSL
                          or TLS negotiation with the API producer.  Valid
                          values of cipher suites are defined in IETF RFC 8447.
                        type: array
                        items:
                          type: string
                          minItems: 1
            required:
              - id
              - name
              - type
              - standardVersion
              - apiVersion
              - apiEndpoint
        peerEntityState:
          description: |
            Current values of the state of the peer functional entity.
          type: object
          properties:
            operationalState:
              description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
              type: string
              enum:
                - STARTED
                - STOPPED
                - STOPPING
                - STARTING
                - RESTARTING
            administrativeState:
              description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
              type: string
              enum:
                - LOCKED
                - UNLOCKED
                - LOCKING
          required:
            - operationalState
            - administrativeState
      required:
        - peerEntityId
        - name
        - type
    PeerEntity:
      description: |
        This type represents an individual peer entity. 
      type: object
      properties:
        id:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        peerEntityId:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        name:
          description: |
            Human-readable name of the peer functional entity.
            This attribute can be modified with the PATCH method.
          type: string
        type:
          description: "The enumeration PeerEntityEnumType defines the permitted values  to represent peer functional entities. it shall complains with  the provisions :  - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t  The peer functional entity is a VIM. - WIM\t  The peer functional entity is a WIM. - EM\t  The peer functional entity is an EM. - OSS\t  The peer functional entity is an OSS/BSS.\n"
          type: string
          enum:
            - NFVO
            - VNFM
            - VIM
            - WIM
            - EM
            - OSS
        description:
          description: |
            Human-readable description of the peer functional entity.
            This attribute can be modified with the PATCH method.
          type: string
        consumedManoInterfaces:
          description: >
            Information of the interface consumed by the NFV-MANO functional
            entity  from the peer functional entity.

            This attribute can be modified with the PATCH method.

            The keys of the map, each of which identifies information about a
            particular consumed NFV-MANO interface, are managed by the API
            consumer and referenced from other data structures via the
            "consumedManoInterfaceIds" attribute.
          type: object
          additionalProperties:
            description: >
              This type represents an interface consumed by the producer NFV
              MANO  functional entity from another peer functional entity. 
            type: object
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              name:
                description: |
                  Human-readable name of the NFV-MANO interface.
                type: string
              type:
                description: >
                  Type of the NFV-MANO service interface consumed by the
                  NFV-MANO  functional entity. Valid values are defined in
                  clause 5.6.4.3.
                type: string
              standardVersion:
                description: |
                  A version.
                type: string
              apiVersion:
                description: |
                  A version.
                type: string
              apiEndpoint:
                description: >
                  Consumable API endpoint of the interface. It provides the
                  information relevant about the protocol, host and port,  and
                  path where the interface API can be accessed.
                type: object
                properties:
                  apiRoot:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                  apiName:
                    description: >
                      Indicates the interface name in an abbreviated form. Shall
                      be present  for ETSI NFV specified RESTful NFV-MANO APIs.
                      The {apiName} of each  interface is defined in the
                      standard the interface is compliant to  (see also clause
                      4.1 of ETSI GS NFV-SOL 013). May be present otherwise.
                    type: string
                  apiMajorVersion:
                    description: >
                      Indicates the current major version of the API. Shall be
                      present for  ETSI NFV specified RESTful NFV-MANO APIs. The
                      major version is defined  in the standard the interface is
                      compliant to (see also clause 4.1  of ETSI GS NFV-SOL
                      013). May be present otherwise.
                    type: string
                  apiUri:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                required:
                  - apiUri
              securityInfo:
                description: >
                  This type represents security related information for
                  accessing an NFV-MANO  service interface produced by an
                  NFV-MANO functional entity.
                type: object
                required:
                  - authType
                  - oauthServerInfo
                properties:
                  authType:
                    description: >
                      Type of API request authorization to be used by the API
                      consumer accessing  the API.

                      The support of authorization methods for the API consumer
                      is specified in  clause 8.3.6 of ETSI GS NFV-SOL 013.

                      Permitted values: - TLS_TUNNEL: Using TLS tunnel, as
                      defined by TLS 1.2 in IETF RFC 5246. - OAUTH2: Using
                      access token, as defined by the OAuth 2.0 specification 
                      in IETF RFC 6749. 
                    type: array
                    items:
                      type: string
                      enum:
                        - TLS_TUNNEL
                        - OAUTH2
                    minItems: 1
                  oauthServerInfo:
                    description: >
                      OAuth 2.0 authorization server information and
                      configuration.
                    type: object
                    properties:
                      dynamicDiscovery:
                        description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                        type: object
                        required:
                          - webFingerHost
                        properties:
                          webFingerHost:
                            description: >
                              Server where the WebFinger service is hosted. When
                              used, the request to  the WebFinger resource shall
                              conform as specified in clause 5.1.3 of  ETSI GS
                              NFV-SEC 022.
                            type: string
                            format: uri
                      providedConfiguration:
                        description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                        type: object
                        required:
                          - authServerId
                        properties:
                          authServerId:
                            description: >
                              Authorization server identifier as defined in ETSI
                              GS NFV-SEC 022.
                            type: string
                            format: uri
                      tlsCipherSuites:
                        description: >
                          List of cipher suites that shall be declared as
                          supported by the API consumer when  performing the SSL
                          or TLS negotiation with the authorization server.
                          Valid values  of cipher suites are defined in IETF RFC
                          8447.
                        type: array
                        items:
                          type: string
                          minItems: 1
                  tlsTunnelInfo:
                    description: >
                      Information and configuration related to the use of TLS
                      tunnel. Shall be  present if authType contains
                      "TLS_TUNNEL".
                    type: object
                    properties:
                      tlsTunnelCipherSuites:
                        description: >
                          List of cipher suites that shall be declared as
                          supported by the API  consumer when performing the SSL
                          or TLS negotiation with the API producer.  Valid
                          values of cipher suites are defined in IETF RFC 8447.
                        type: array
                        items:
                          type: string
                          minItems: 1
            required:
              - id
              - name
              - type
              - standardVersion
              - apiVersion
              - apiEndpoint
        peerEntityState:
          description: >
            State of the peer functional entity as provided by the API consumer
            when  creating the resource or when updating it with the PATCH
            method.
          type: object
          properties:
            operationalState:
              description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
              type: string
              enum:
                - STARTED
                - STOPPED
                - STOPPING
                - STARTING
                - RESTARTING
            administrativeState:
              description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
              type: string
              enum:
                - LOCKED
                - UNLOCKED
                - LOCKING
          required:
            - operationalState
            - administrativeState
      required:
        - id
        - peerEntityId
        - name
        - type
        - peerEntityState
    PeerEntityConfigModificationRequest:
      description: >
        This type represents attribute modifications for configuration
        parameters  of a peer entity. 
      type: object
      properties:
        name:
          description: |
            New value of the "name" attribute in "PeerEntity".
          type: string
        description:
          description: >
            New value of the "description" attribute in "PeerEntity", or "null"
            to  remove the attribute.
          type: string
        consumedManoInterfaces:
          description: "Modification of the \"consumedManoInterfaces\" attribute in the \"PeerEntity\", as defined below this table.\nIf present, these modifications shall be applied according to the rules of JSON Merge PATCH (see IETF RFC 7396).\nNOTE:\tDue to the security sensitive information contained within the attribute  (refer to \"securityInfo\" within the \"ConsumedManoInterfaceInfo\"), based on  access control policies, the API consumer might have read only, write only,  read/write, or no access at all to the attribute’s value. In case the  API consumer is not allowed to modify the value of the security sensitive  attribute, and the modification request includes new attribute values,  the whole modification request shall be rejected, and proper error information  returned.\n"
          type: object
          additionalProperties:
            description: >
              This type represents an interface consumed by the producer NFV
              MANO  functional entity from another peer functional entity. 
            type: object
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              name:
                description: |
                  Human-readable name of the NFV-MANO interface.
                type: string
              type:
                description: >
                  Type of the NFV-MANO service interface consumed by the
                  NFV-MANO  functional entity. Valid values are defined in
                  clause 5.6.4.3.
                type: string
              standardVersion:
                description: |
                  A version.
                type: string
              apiVersion:
                description: |
                  A version.
                type: string
              apiEndpoint:
                description: >
                  Consumable API endpoint of the interface. It provides the
                  information relevant about the protocol, host and port,  and
                  path where the interface API can be accessed.
                type: object
                properties:
                  apiRoot:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                  apiName:
                    description: >
                      Indicates the interface name in an abbreviated form. Shall
                      be present  for ETSI NFV specified RESTful NFV-MANO APIs.
                      The {apiName} of each  interface is defined in the
                      standard the interface is compliant to  (see also clause
                      4.1 of ETSI GS NFV-SOL 013). May be present otherwise.
                    type: string
                  apiMajorVersion:
                    description: >
                      Indicates the current major version of the API. Shall be
                      present for  ETSI NFV specified RESTful NFV-MANO APIs. The
                      major version is defined  in the standard the interface is
                      compliant to (see also clause 4.1  of ETSI GS NFV-SOL
                      013). May be present otherwise.
                    type: string
                  apiUri:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                required:
                  - apiUri
              securityInfo:
                description: >
                  This type represents security related information for
                  accessing an NFV-MANO  service interface produced by an
                  NFV-MANO functional entity.
                type: object
                required:
                  - authType
                  - oauthServerInfo
                properties:
                  authType:
                    description: >
                      Type of API request authorization to be used by the API
                      consumer accessing  the API.

                      The support of authorization methods for the API consumer
                      is specified in  clause 8.3.6 of ETSI GS NFV-SOL 013.

                      Permitted values: - TLS_TUNNEL: Using TLS tunnel, as
                      defined by TLS 1.2 in IETF RFC 5246. - OAUTH2: Using
                      access token, as defined by the OAuth 2.0 specification 
                      in IETF RFC 6749. 
                    type: array
                    items:
                      type: string
                      enum:
                        - TLS_TUNNEL
                        - OAUTH2
                    minItems: 1
                  oauthServerInfo:
                    description: >
                      OAuth 2.0 authorization server information and
                      configuration.
                    type: object
                    properties:
                      dynamicDiscovery:
                        description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                        type: object
                        required:
                          - webFingerHost
                        properties:
                          webFingerHost:
                            description: >
                              Server where the WebFinger service is hosted. When
                              used, the request to  the WebFinger resource shall
                              conform as specified in clause 5.1.3 of  ETSI GS
                              NFV-SEC 022.
                            type: string
                            format: uri
                      providedConfiguration:
                        description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                        type: object
                        required:
                          - authServerId
                        properties:
                          authServerId:
                            description: >
                              Authorization server identifier as defined in ETSI
                              GS NFV-SEC 022.
                            type: string
                            format: uri
                      tlsCipherSuites:
                        description: >
                          List of cipher suites that shall be declared as
                          supported by the API consumer when  performing the SSL
                          or TLS negotiation with the authorization server.
                          Valid values  of cipher suites are defined in IETF RFC
                          8447.
                        type: array
                        items:
                          type: string
                          minItems: 1
                  tlsTunnelInfo:
                    description: >
                      Information and configuration related to the use of TLS
                      tunnel. Shall be  present if authType contains
                      "TLS_TUNNEL".
                    type: object
                    properties:
                      tlsTunnelCipherSuites:
                        description: >
                          List of cipher suites that shall be declared as
                          supported by the API  consumer when performing the SSL
                          or TLS negotiation with the API producer.  Valid
                          values of cipher suites are defined in IETF RFC 8447.
                        type: array
                        items:
                          type: string
                          minItems: 1
            required:
              - id
              - name
              - type
              - standardVersion
              - apiVersion
              - apiEndpoint
        operationalState:
          description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
          type: string
          enum:
            - STARTED
            - STOPPED
            - STOPPING
            - STARTING
            - RESTARTING
        administrativeState:
          description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
          type: string
          enum:
            - LOCKED
            - UNLOCKED
            - LOCKING
    PeerEntityConfigModifications:
      description: >
        This type represents attribute modifications that were performed on an 
        "Individual peer entity" resource. The attributes that can be included 
        consist of those requested to be modified explicitly in the 
        "PeerEntityConfigModificationRequest" data structure. If applicable, 
        additional attributes of the "PeerEntity" data structure that were 
        modified implicitly shall also be provided.
      type: object
      properties:
        name:
          description: >
            If present, this attribute signals modifications of the "name"
            attribute  in "PeerEntity", as defined in clause 5.6.2.15.
          type: string
        description:
          description: >
            If present, this attribute signals modifications of the
            "description"  attribute in "PeerEntity", as defined in clause
            5.6.2.15.
          type: string
        consumedManoInterfaces:
          description: "If present, this attribute signals modifications of the \"consumedManoInterfaces\" attribute in \"PeerEntity\", as defined in  clause 5.6.2.15. \nNOTE:\tDue to the security sensitive information contained within the  attribute (refer to \"securityInfo\" within the \"ConsumedManoInterfaceInfo\"),  based on access control policies, the API consumer might have read only,  write only, read/write, or no access at all to the attribute’s value.  In case the API consumer is not allowed to read the value of the security  sensitive attribute, the attribute shall be omitted when the information  is to be provided in a response message.\n"
          type: object
          additionalProperties:
            description: >
              This type represents an interface consumed by the producer NFV
              MANO  functional entity from another peer functional entity. 
            type: object
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              name:
                description: |
                  Human-readable name of the NFV-MANO interface.
                type: string
              type:
                description: >
                  Type of the NFV-MANO service interface consumed by the
                  NFV-MANO  functional entity. Valid values are defined in
                  clause 5.6.4.3.
                type: string
              standardVersion:
                description: |
                  A version.
                type: string
              apiVersion:
                description: |
                  A version.
                type: string
              apiEndpoint:
                description: >
                  Consumable API endpoint of the interface. It provides the
                  information relevant about the protocol, host and port,  and
                  path where the interface API can be accessed.
                type: object
                properties:
                  apiRoot:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                  apiName:
                    description: >
                      Indicates the interface name in an abbreviated form. Shall
                      be present  for ETSI NFV specified RESTful NFV-MANO APIs.
                      The {apiName} of each  interface is defined in the
                      standard the interface is compliant to  (see also clause
                      4.1 of ETSI GS NFV-SOL 013). May be present otherwise.
                    type: string
                  apiMajorVersion:
                    description: >
                      Indicates the current major version of the API. Shall be
                      present for  ETSI NFV specified RESTful NFV-MANO APIs. The
                      major version is defined  in the standard the interface is
                      compliant to (see also clause 4.1  of ETSI GS NFV-SOL
                      013). May be present otherwise.
                    type: string
                  apiUri:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                required:
                  - apiUri
              securityInfo:
                description: >
                  This type represents security related information for
                  accessing an NFV-MANO  service interface produced by an
                  NFV-MANO functional entity.
                type: object
                required:
                  - authType
                  - oauthServerInfo
                properties:
                  authType:
                    description: >
                      Type of API request authorization to be used by the API
                      consumer accessing  the API.

                      The support of authorization methods for the API consumer
                      is specified in  clause 8.3.6 of ETSI GS NFV-SOL 013.

                      Permitted values: - TLS_TUNNEL: Using TLS tunnel, as
                      defined by TLS 1.2 in IETF RFC 5246. - OAUTH2: Using
                      access token, as defined by the OAuth 2.0 specification 
                      in IETF RFC 6749. 
                    type: array
                    items:
                      type: string
                      enum:
                        - TLS_TUNNEL
                        - OAUTH2
                    minItems: 1
                  oauthServerInfo:
                    description: >
                      OAuth 2.0 authorization server information and
                      configuration.
                    type: object
                    properties:
                      dynamicDiscovery:
                        description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                        type: object
                        required:
                          - webFingerHost
                        properties:
                          webFingerHost:
                            description: >
                              Server where the WebFinger service is hosted. When
                              used, the request to  the WebFinger resource shall
                              conform as specified in clause 5.1.3 of  ETSI GS
                              NFV-SEC 022.
                            type: string
                            format: uri
                      providedConfiguration:
                        description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                        type: object
                        required:
                          - authServerId
                        properties:
                          authServerId:
                            description: >
                              Authorization server identifier as defined in ETSI
                              GS NFV-SEC 022.
                            type: string
                            format: uri
                      tlsCipherSuites:
                        description: >
                          List of cipher suites that shall be declared as
                          supported by the API consumer when  performing the SSL
                          or TLS negotiation with the authorization server.
                          Valid values  of cipher suites are defined in IETF RFC
                          8447.
                        type: array
                        items:
                          type: string
                          minItems: 1
                  tlsTunnelInfo:
                    description: >
                      Information and configuration related to the use of TLS
                      tunnel. Shall be  present if authType contains
                      "TLS_TUNNEL".
                    type: object
                    properties:
                      tlsTunnelCipherSuites:
                        description: >
                          List of cipher suites that shall be declared as
                          supported by the API  consumer when performing the SSL
                          or TLS negotiation with the API producer.  Valid
                          values of cipher suites are defined in IETF RFC 8447.
                        type: array
                        items:
                          type: string
                          minItems: 1
            required:
              - id
              - name
              - type
              - standardVersion
              - apiVersion
              - apiEndpoint
        operationalState:
          description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
          type: string
          enum:
            - STARTED
            - STOPPED
            - STOPPING
            - STARTING
            - RESTARTING
        administrativeState:
          description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
          type: string
          enum:
            - LOCKED
            - UNLOCKED
            - LOCKING
    ManoConfigurableParams:
      description: |
        # Warning: No definition found in the document ManoConfigurableParams
    ManoEntityComponent:
      description: >
        This type represents information of a deployed component realizing part
        of an  NFV-MANO functional entity. It is optional for the API producer
        to support  this type. 
      type: object
      properties:
        id:
          description: >
            An identifier that is unique for the respective type within a
            NFV-MANO functional entity, but that need not be globally unique.
            Representation: string of variable length..
          type: string
        manoServiceIds:
          description: >
            References to the NFV-MANO services that depend on the NFV-MANO
            functional  entity component. The identifier of the ManoService is
            referred. A service  may depend on multiple components. Multiple
            services may depend on the same  component.
          type: array
          items:
            description: >
              An identifier that is unique for the respective type within a
              NFV-MANO functional entity, but that need not be globally unique.
              Representation: string of variable length..
            type: string
      required:
        - id
    ManoService:
      description: >
        This type represents information about an NFV-MANO service provided by
        the  NFV-MANO functional entity.
      type: object
      properties:
        id:
          description: >
            An identifier that is unique for the respective type within a
            NFV-MANO functional entity, but that need not be globally unique.
            Representation: string of variable length..
          type: string
        name:
          description: |
            Human-readable name of the NFV-MANO service.
            This attribute can be modified with the PATCH method.
          type: string
        description:
          description: |
            Human-readable description of the NFV-MANO service.
            This attribute can be modified with the PATCH method.
          type: string
        manoServiceInterfaceIds:
          description: "Reference to the NFV-MANO interfaces associated to the NFV-MANO service.  If cardinality is greater than one, the type of ManoServiceInterface  (see clause 5.6.3.3) shall be the same. The identifier of the  ManoServiceInterface is referred. \nNOTE:\tA cardinality greater than one supports having different interface  versions or apiEndpoints to be used for accessing the same instance of a  NFV-MANO service.\n"
          type: array
          items:
            description: >
              An identifier that is unique for the respective type within a
              NFV-MANO functional entity, but that need not be globally unique.
              Representation: string of variable length..
            type: string
          minItems: 1
        _links:
          description: |
            Links to resources related to this resource.
          type: object
          properties:
            manoServiceInterfaces:
              description: >
                Link to the "individual NFV-MANO service interface" resources
                with  information about the associated interfaces to the
                NFV-MANO service.
              type: array
              items:
                description: >
                  This type represents a link to a resource using an absolute
                  URI.
                type: object
                required:
                  - href
                properties:
                  href:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
              minItems: 1
          required:
            - manoServiceInterfaces
      required:
        - id
        - name
        - description
        - manoServiceInterfaceIds
        - _links
    NfvoSpecificInfo:
      description: >
        This type represents information attributes specific to an NFVO entity, 
        and that can be relevant to more than one NFV-MANO service offered by
        an  NFVO entity. 
      type: object
      properties:
        maxOnboardedNsdNum:
          description: >
            Maximum number of NSDs that can be on-boarded on the NFVO. 

            NOTE: If this attribute is not present, the value of this parameter 
            is undefined.
          type: integer
        maxOnboardedVnfPkgNum:
          description: >
            Maximum number of VNF Packages that can be on-boarded on the NFVO. 

            NOTE: If this attribute is not present, the value of this parameter 
            is undefined.
          type: integer
        supportedVnfdFormats:
          description: |
            Supported VNFD data formats.
          type: object
          properties:
            vnfdFormat:
              description: |
                Name of the VNFD format.
                Permitted values:
                  - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                  GS NFV-SOL 001 standard.
                  - YANG: The VNFD follows YANG definition according to ETSI 
                  GS NFV-SOL 006 standard.
              type: string
              enum:
                - TOSCA
                - YANG
            standardVersion:
              description: |
                A version.
              type: string
          required:
            - vnfdFormat
            - standardVersion
        supportedNsdFormats:
          description: |
            Supported NSD data formats.
          type: object
          properties:
            nsdFormat:
              description: |
                Name of the NSD format.
                Permitted values:
                  - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                  GS NFV-SOL 001 standard.
                  - YANG: The VNFD follows YANG definition according to ETSI 
                  GS NFV-SOL 006 standard.
              type: string
              enum:
                - TOSCA
                - YANG
            standardVersion:
              description: |
                A version.
              type: string
          required:
            - nsdFormat
            - standardVersion
      required:
        - supportedVnfdFormats
        - supportedNsdFormats
    VnfmSpecificInfo:
      description: >
        This type represents information attributes specific to a VNFM entity, 
        and that can be relevant to more than one NFV-MANO service offered by  a
        VNFM entity.
      type: object
      properties:
        resoruceMgmtModeSupport:
          description: |
            The supported resource management modes of the VNFM.
            Permitted values:
              - DIRECT: The VNFM supports direct mode only.
              - INDIRECT: The VNFM supports indirect mode only.
              - BOTH: The VNFM supports both direct and indirect mode.
          type: string
          enum:
            - DIRECT
            - INDIRECT
            - BOTH
        managedVnfInstanceInfos:
          description: >
            The kinds of VNF instances that can be managed, e.g. to determine
            the  compatibility of a VNF with certain VNFM according to the
            vnfmInfo  attribute in the VNFD (see table 7.1.2.2-1 in ETSI GS
            NFV-IFA 011).
          type: array
          items:
            type: string
          minItems: 1
        supportedVnfdFormats:
          description: |
            Supported VNFD data formats.
          type: array
          items:
            type: object
            properties:
              vnfdFormat:
                description: |
                  Name of the VNFD format.
                  Permitted values:
                    - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                    GS NFV-SOL 001 standard.
                    - YANG: The VNFD follows YANG definition according to ETSI 
                    GS NFV-SOL 006 standard.
                type: string
                enum:
                  - TOSCA
                  - YANG
              standardVersion:
                description: |
                  A version.
                type: string
            required:
              - vnfdFormat
              - standardVersion
          minItems: 1
      required:
        - resoruceMgmtModeSupport
        - managedVnfInstanceInfos
        - supportedVnfdFormats
    VimSpecificInfo:
      description: >
        This type represents information attributes specific to a VIM entity, 
        and that can be relevant to more than one NFV-MANO service offered by  a
        VIM entity.
      type: object
    ManoEntityConfigurableParams:
      description: >
        This type represents list of parameters that can be configured on the 
        NFV MANO functional entity. 
      type: object
      properties:
        clockSyncs:
          description: >-
            Properties of the clock synchronization to be used by the NFV-MANO
            functional entity.
          type: array
          items:
            description: |
              This type represents parameters for connecting to an NTP server. 
            type: object
            properties:
              type:
                description: |
                  Type of clock synchronization.
                  Permitted values:
                    - NTP: For Network Time Protocol (NTP) based clock synchronization.
                    - OTHER: For other types of clock synchronization.
                type: string
                enum:
                  - NTP
                  - OTHER
              ntpServerInfo:
                description: >
                  Information for the NTP based clock synchronization.  Shall be
                  present if type = "NTP".
                type: object
                properties:
                  ipAddress:
                    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
                  hostname:
                    description: "Indicates the hostname of the NTP server. \nNOTE:\tEither ipAddress or hostname shall be set, but not both  at the same time.\n"
                    type: string
              otherClockSyncParams:
                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
            required:
              - type
          minItems: 1
        defaultLogCompileBySizeValue:
          description: |
            Unsigned integer
          type: number
        defaultLogCompileByTimerValue:
          description: |
            Unsigned integer
          type: number
      required:
        - clockSyncs
        - defaultLogCompileBySizeValue
        - defaultLogCompileByTimerValue
    ConsumedManoInterfaceInfo:
      description: >
        This type represents an interface consumed by the producer NFV MANO 
        functional entity from another peer functional entity. 
      type: object
      properties:
        id:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        name:
          description: |
            Human-readable name of the NFV-MANO interface.
          type: string
        type:
          description: >
            Type of the NFV-MANO service interface consumed by the NFV-MANO 
            functional entity. Valid values are defined in clause 5.6.4.3.
          type: string
        standardVersion:
          description: |
            A version.
          type: string
        apiVersion:
          description: |
            A version.
          type: string
        apiEndpoint:
          description: >
            Consumable API endpoint of the interface. It provides the
            information relevant about the protocol, host and port,  and path
            where the interface API can be accessed.
          type: object
          properties:
            apiRoot:
              description: |
                String formatted according to IETF RFC 3986.
              type: string
            apiName:
              description: >
                Indicates the interface name in an abbreviated form. Shall be
                present  for ETSI NFV specified RESTful NFV-MANO APIs. The
                {apiName} of each  interface is defined in the standard the
                interface is compliant to  (see also clause 4.1 of ETSI GS
                NFV-SOL 013). May be present otherwise.
              type: string
            apiMajorVersion:
              description: >
                Indicates the current major version of the API. Shall be present
                for  ETSI NFV specified RESTful NFV-MANO APIs. The major version
                is defined  in the standard the interface is compliant to (see
                also clause 4.1  of ETSI GS NFV-SOL 013). May be present
                otherwise.
              type: string
            apiUri:
              description: |
                String formatted according to IETF RFC 3986.
              type: string
          required:
            - apiUri
        securityInfo:
          description: >
            This type represents security related information for accessing an
            NFV-MANO  service interface produced by an NFV-MANO functional
            entity.
          type: object
          required:
            - authType
            - oauthServerInfo
          properties:
            authType:
              description: >
                Type of API request authorization to be used by the API consumer
                accessing  the API.

                The support of authorization methods for the API consumer is
                specified in  clause 8.3.6 of ETSI GS NFV-SOL 013.

                Permitted values: - TLS_TUNNEL: Using TLS tunnel, as defined by
                TLS 1.2 in IETF RFC 5246. - OAUTH2: Using access token, as
                defined by the OAuth 2.0 specification  in IETF RFC 6749. 
              type: array
              items:
                type: string
                enum:
                  - TLS_TUNNEL
                  - OAUTH2
              minItems: 1
            oauthServerInfo:
              description: |
                OAuth 2.0 authorization server information and configuration.
              type: object
              properties:
                dynamicDiscovery:
                  description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                  type: object
                  required:
                    - webFingerHost
                  properties:
                    webFingerHost:
                      description: >
                        Server where the WebFinger service is hosted. When used,
                        the request to  the WebFinger resource shall conform as
                        specified in clause 5.1.3 of  ETSI GS NFV-SEC 022.
                      type: string
                      format: uri
                providedConfiguration:
                  description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                  type: object
                  required:
                    - authServerId
                  properties:
                    authServerId:
                      description: >
                        Authorization server identifier as defined in ETSI GS
                        NFV-SEC 022.
                      type: string
                      format: uri
                tlsCipherSuites:
                  description: >
                    List of cipher suites that shall be declared as supported by
                    the API consumer when  performing the SSL or TLS negotiation
                    with the authorization server. Valid values  of cipher
                    suites are defined in IETF RFC 8447.
                  type: array
                  items:
                    type: string
                    minItems: 1
            tlsTunnelInfo:
              description: >
                Information and configuration related to the use of TLS tunnel.
                Shall be  present if authType contains "TLS_TUNNEL".
              type: object
              properties:
                tlsTunnelCipherSuites:
                  description: >
                    List of cipher suites that shall be declared as supported by
                    the API  consumer when performing the SSL or TLS negotiation
                    with the API producer.  Valid values of cipher suites are
                    defined in IETF RFC 8447.
                  type: array
                  items:
                    type: string
                    minItems: 1
      required:
        - id
        - name
        - type
        - standardVersion
        - apiVersion
        - apiEndpoint
    CimNotificationsFilter:
      description: >
        This type represents a subscription filter related to notifications 
        about NFV-MANO configuration and information management. 
      type: object
      properties:
        manoEntitySubscriptionFilter:
          description: >
            This type represents subscription filter criteria to match NFV-MANO
            functional  entities and their associated managed objects. 
          type: object
          properties:
            manoEntityId:
              description: |
                An identifier with the intention of being globally unique.
              type: string
            manoServiceIds:
              description: "manoServiceIds\tIdentifierInManoEntity\t0..N\tIf present, match NFV-MANO  services with an instance identifier listed in this attribute.\nThe attributes \"manoServiceIds\" and \"manoServiceNames\" are alternatives  to reference to NFV-MANO services in a filter. They should not be used  together in the same filter instance, but one alternative should be chosen.\n"
              type: array
              items:
                description: >
                  An identifier that is unique for the respective type within a
                  NFV-MANO functional entity, but that need not be globally
                  unique. Representation: string of variable length..
                type: string
            manoServiceNames:
              description: >
                If present, match NFV-MANO services with an NFV-MANO service
                name listed  in this attribute.

                The attributes "manoServiceIds" and "manoServiceNames" are
                alternatives  to reference to NFV-MANO services in a filter.
                They should not be used  together in the same filter instance,
                but one alternative should be chosen.
              type: array
              items:
                type: string
            manoServiceInterfaceIds:
              description: >
                If present, match NFV-MANO functional entity produced interfaces
                with an  instance identifier listed in this attribute.

                The attributes "manoServiceInterfaceIds" and
                "manoServiceInterfaceNames"  are alternatives to reference to
                NFV-MANO functional entity produced  interfaces in a filter.
                They should not be used both in the same filter  instance, but
                one alternative should be chosen.
              type: array
              items:
                description: >
                  An identifier that is unique for the respective type within a
                  NFV-MANO functional entity, but that need not be globally
                  unique. Representation: string of variable length..
                type: string
            manoServiceInterfaceNames:
              description: >
                If present, match NFV-MANO functional entity produced interfaces
                with an  instance Name listed in this attribute.

                The attributes "manoServiceInterfaceIds" and
                "manoServiceInterfaceNames"  are alternatives to reference to
                NFV-MANO functional entity produced  interfaces in a filter.
                They should not be used both in the same filter  instance, but
                one alternative should be chosen.
              type: array
              items:
                type: string
            consumedManoInterfaceIds:
              description: >
                If present, match NFV-MANO functional entity consumed interfaces
                with an  instance identifier listed in this attribute.

                The attributes "consumedManoInterfaceIds" and
                "consumedManoInterfaceNames"  are alternatives to reference to
                NFV-MANO functional entity consumed  interfaces in a filter.
                They should not be used both in the same filter  instance, but
                one alternative should be chosen.
              type: array
              items:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
            consumedManoInterfaceNames:
              description: >
                If present, match NFV-MANO functional entity consumed interfaces
                with an  instance Name listed in this attribute.

                The attributes "consumedManoInterfaceIds" and
                "consumedManoInterfaceNames"  are alternatives to reference to
                NFV-MANO functional entity consumed  interfaces in a filter.
                They should not be used both in the same filter  instance, but
                one alternative should be chosen.
              type: array
              items:
                type: string
        notificationTypes:
          description: "Match particular notification types. \nPermitted values:\n  - InformationChangedNotification\n  - ChangeStateNotification\n\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are  spelled exactly as the names of the notification types to facilitate  automated code generation systems.\n"
          type: array
          items:
            type: string
            enum:
              - InformationChangedNotification
              - ChangeStateNotification
    ClockSyncInfo:
      description: |
        This type represents parameters for connecting to an NTP server. 
      type: object
      properties:
        type:
          description: |
            Type of clock synchronization.
            Permitted values:
              - NTP: For Network Time Protocol (NTP) based clock synchronization.
              - OTHER: For other types of clock synchronization.
          type: string
          enum:
            - NTP
            - OTHER
        ntpServerInfo:
          description: >
            Information for the NTP based clock synchronization.  Shall be
            present if type = "NTP".
          type: object
          properties:
            ipAddress:
              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
            hostname:
              description: "Indicates the hostname of the NTP server. \nNOTE:\tEither ipAddress or hostname shall be set, but not both  at the same time.\n"
              type: string
        otherClockSyncParams:
          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
      required:
        - type
    ServerInterfaceSecurityInfo:
      description: >
        This type represents security related information of an NFV-MANO 
        service interface produced by an NFV-MANO functional entity. 
      type: object
      properties:
        authType:
          description: >
            Type of API request authorization to be used by the API producer.

            The support of authorization methods for the API producer is
            specified  in clause 8.3.6 of ETSI GS NFV-SOL 013.

            Permitted values:
              - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
              - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
              in IETF RFC 6749. 
          type: array
          items:
            type: string
            enum:
              - TLS_TUNNEL
              - OAUTH2
          minItems: 1
        oauthServerInfo:
          description: |
            OAuth 2.0 authorization server information and configuration.
          type: object
          properties:
            dynamicDiscovery:
              description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
              type: object
              properties:
                webFingerHost:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
              required:
                - webFingerHost
            providedConfiguration:
              description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
              type: object
              properties:
                authServerId:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
              required:
                - authServerId
            tlsCipherSuites:
              description: >
                List of cipher suites that shall be declared as supported by
                the  API producer when performing the SSL or TLS negotiation
                with the  authorization server. Valid values of cipher suites
                are defined  in IETF RFC 8447.
              type: array
              items:
                type: string
              minItems: 1
          required:
            - providedConfiguration
            - tlsCipherSuites
        tlsTunnelInfo:
          description: >
            Information and configuration related to the use of TLS tunnel. 
            Shall be present if authType contains "TLS_TUNNEL".
          type: object
          properties:
            tlsTunnelCipherSuites:
              description: >-
                List of cipher suites that shall be declared as supported by the
                API producer when performing the SSL or TLS negotiation with the
                API client. Valid values of cipher suites are defined in IETF
                RFC 8447.
              type: array
              items:
                type: string
              minItems: 1
          required:
            - tlsTunnelCipherSuites
      required:
        - authType
        - oauthServerInfo
    ClientInterfaceSecurityInfo:
      description: >
        This type represents security related information for accessing an
        NFV-MANO  service interface produced by an NFV-MANO functional entity.
      type: object
      required:
        - authType
        - oauthServerInfo
      properties:
        authType:
          description: >
            Type of API request authorization to be used by the API consumer
            accessing  the API.

            The support of authorization methods for the API consumer is
            specified in  clause 8.3.6 of ETSI GS NFV-SOL 013.

            Permitted values: - TLS_TUNNEL: Using TLS tunnel, as defined by TLS
            1.2 in IETF RFC 5246. - OAUTH2: Using access token, as defined by
            the OAuth 2.0 specification  in IETF RFC 6749. 
          type: array
          items:
            type: string
            enum:
              - TLS_TUNNEL
              - OAUTH2
          minItems: 1
        oauthServerInfo:
          description: |
            OAuth 2.0 authorization server information and configuration.
          type: object
          properties:
            dynamicDiscovery:
              description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
              type: object
              required:
                - webFingerHost
              properties:
                webFingerHost:
                  description: >
                    Server where the WebFinger service is hosted. When used, the
                    request to  the WebFinger resource shall conform as
                    specified in clause 5.1.3 of  ETSI GS NFV-SEC 022.
                  type: string
                  format: uri
            providedConfiguration:
              description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
              type: object
              required:
                - authServerId
              properties:
                authServerId:
                  description: >
                    Authorization server identifier as defined in ETSI GS
                    NFV-SEC 022.
                  type: string
                  format: uri
            tlsCipherSuites:
              description: >
                List of cipher suites that shall be declared as supported by the
                API consumer when  performing the SSL or TLS negotiation with
                the authorization server. Valid values  of cipher suites are
                defined in IETF RFC 8447.
              type: array
              items:
                type: string
                minItems: 1
        tlsTunnelInfo:
          description: >
            Information and configuration related to the use of TLS tunnel.
            Shall be  present if authType contains "TLS_TUNNEL".
          type: object
          properties:
            tlsTunnelCipherSuites:
              description: >
                List of cipher suites that shall be declared as supported by the
                API  consumer when performing the SSL or TLS negotiation with
                the API producer.  Valid values of cipher suites are defined in
                IETF RFC 8447.
              type: array
              items:
                type: string
                minItems: 1
    ManoServiceInterfaceTypeShortName:
      description: "For the RESTful NFV-MANO APIs, valid values are all values for \"apiName\" as defined  in ETSI GS NFV-SOL 002, ETSI GS NFV-SOL 003, and ETSI GS NFV-SOL 005.\nFor the NFV-MANO service interfaces for which no API is specified by ETSI NFV, valid  values are defined in table 5.6.4.3-1.\nNOTE:\tThe table is expected to be updated, by removing the corresponding listed entries,  once the interfaces are specified as a RESTful NFV-MANO API. \n"
      type: string
    UsageStateEnumType:
      description: "The enumeration UsageStateEnumType defines values representing the usage  state of a managed entity.  The UsageStateEnumType shall comply with the provisions:\n  - IN_USE\tThe managed entity is currently being used.\n  - NOT_IN_USE\tThe managed entity is currently not being used.\n"
      type: string
      enum:
        - IN_USE
        - NOT_IN_USE
    ChangeOperationalStateEnumType:
      description: "The enumeration ChangeOperationalStateEnumType defines permitted values  for the change state operation.  The ChangeOperationalStateEnumType shall comply with the provisions:\n  - START\tTo start the managed entity.\n  - STOP\tTo stop the managed entity.\n  - RESTART\tTo stop and start again the managed entity.\n"
      type: string
      enum:
        - START
        - STOP
        - RESTART
    ChangeAdministrativeStateEnumType:
      description: "The enumeration ChangeAdministrativeStateEnumType defines permitted values  for the change of administrative state operation.  The ChangeAdministrativeStateEnumType shall comply with the provisions:\n  - LOCK\tTo lock the managed entity.\n  - UNLOCK\tTo unlock the managed entity.\n"
      type: string
      enum:
        - LOCK
        - UNLOCK
    InterfaceOperationalStateEnumType:
      description: "The enumeration InterfaceOperationalStateEnumType defines values representing  the operational state of an NFV-MANO service interface type of managed entity.  The InterfaceOperationalStateEnumType shall comply with the provisions :\n   - STARTED\tThe managed entity is operational.\n   - STOPPED\tThe managed entity is not operational.\n   - STOPPING\tThe managed entity is in the transition to stop.\n   - STARTING\tThe managed entity is in the transition to start and become operational.\n"
      type: string
      enum:
        - STARTED
        - STOPPED
        - STOPPING
        - STARTING
    StopEnumType:
      description: "The enumeration ChangeStateOpOccStateEnumType defines permitted values  for the change state operation. It shall comply with the provisions:\n  - GRACEFUL\tTo stop the managed entity immediately after accepting the request.\n  - FORCEFUL\tTo stop the managed entity attempting to gracefully discharge the entity from service.\n"
      type: string
      enum:
        - GRACEFUL
        - FORCEFUL
    ManoEntityEnumType:
      description: "The enumeration ManoEntityEnumType defines the permitted values to  represent NFV-MANO functional entities. It shall comply with  the provisions :\n  - NFVO\tThe NFV-MANO functional entity is an NFVO.\n  - VNFM\tThe NFV-MANO functional entity is a VNFM.\n  - VIM\tThe NFV-MANO functional entity is a VIM.\n"
      type: string
      enum:
        - NFVO
        - VNFM
        - VIM
    PeerEntityEnumType:
      description: "The enumeration PeerEntityEnumType defines the permitted values  to represent peer functional entities. it shall complains with  the provisions :  - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t  The peer functional entity is a VIM. - WIM\t  The peer functional entity is a WIM. - EM\t  The peer functional entity is an EM. - OSS\t  The peer functional entity is an OSS/BSS.\n"
      type: string
      enum:
        - NFVO
        - VNFM
        - VIM
        - WIM
        - EM
        - OSS
  parameters:
    filter.ManoServiceInterface:
      name: filter
      description: >
        Attribute-based filtering expression according to clause 5.2 of  ETSI GS
        NFV-SOL 013. 

        The NFV-MANO functional entity shall support receiving this parameter 
        as part of the URI query string. The API consumer may supply this 
        parameter. 

        All attribute names that appear in the ManoServiceInterface and in data 
        types referenced from it shall be supported by the NFV-MANO functional 
        entity in the expression. 
      in: query
      required: false
      schema:
        type: string
    filter.CimSubscription:
      name: filter
      description: >
        Attribute-based filtering expression according to clause 5.2 of  ETSI GS
        NFV-SOL 013. 

        The NFV-MANO functional entity shall support receiving this parameter 
        as part of the URI query string. The API consumer may supply this 
        parameter. 

        All attribute names that appear in the CimSubscription and in data 
        types referenced from it shall be supported by the NFV-MANO functional 
        entity in the expression. 
      in: query
      required: false
      schema:
        type: string
    filter.ChangeStateOpOcc:
      name: filter
      description: >
        Attribute-based filtering expression according to clause 5.2 of  ETSI GS
        NFV-SOL 013. 

        The NFV-MANO functional entity shall support receiving this parameter 
        as part of the URI query string. The API consumer may supply this 
        parameter. 

        All attribute names that appear in the ChangeStateOpOcc and in data 
        types referenced from it shall be supported by the NFV-MANO functional 
        entity in the expression. 
      in: query
      required: false
      schema:
        type: string
    filter.PeerEntity:
      name: filter
      description: >
        Attribute-based filtering expression according to clause 5.2 of  ETSI GS
        NFV-SOL 013. 

        The NFV-MANO functional entity shall support receiving this parameter 
        as part of the URI query string. The API consumer may supply this 
        parameter. 

        All attribute names that appear in the PeerEntity and in data  types
        referenced from it shall be supported by the NFV-MANO functional  entity
        in the expression. 
      in: query
      required: false
      schema:
        type: string
    exclude_default.ManoServiceInterface:
      name: exclude_default
      description: >
        Indicates to exclude the following complex attributes from the 
        response. See clause 5.3 of ETSI GS NFV-SOL 013 for details.  The
        NFV-MANO functional entity shall support this parameter.

        The following attributes shall be excluded from the
        ManoServiceInterface  structure in the response body if this parameter
        is provided, or none of  the parameters "all_fields," "fields",
        "exclude_fields", "exclude_default"  are provided: - none
      in: query
      required: false
      schema:
        type: string
    exclude_default.CimSubscription:
      name: exclude_default
      description: >
        Indicates to exclude the following complex attributes from the 
        response. See clause 5.3 of ETSI GS NFV-SOL 013 for details.  The
        NFV-MANO functional entity shall support this parameter.

        The following attributes shall be excluded from the CimSubscription 
        structure in the response body if this parameter is provided, or none
        of  the parameters "all_fields," "fields", "exclude_fields",
        "exclude_default"  are provided: - none
      in: query
      required: false
      schema:
        type: string
    exclude_default.ChangeStateOpOcc:
      name: exclude_default
      description: >
        Indicates to exclude the following complex attributes from the 
        response. See clause 5.3 of ETSI GS NFV-SOL 013 for details.  The
        NFV-MANO functional entity shall support this parameter.

        The following attributes shall be excluded from the ChangeStateOpOcc 
        structure in the response body if this parameter is provided, or none
        of  the parameters "all_fields," "fields", "exclude_fields",
        "exclude_default"  are provided: - none
      in: query
      required: false
      schema:
        type: string
    exclude_default.PeerEntity:
      name: exclude_default
      description: >
        Indicates to exclude the following complex attributes from the 
        response. See clause 5.3 of ETSI GS NFV-SOL 013 for details.  The
        NFV-MANO functional entity shall support this parameter.

        The following attributes shall be excluded from the PeerEntity 
        structure in the response body if this parameter is provided, or none
        of  the parameters "all_fields," "fields", "exclude_fields",
        "exclude_default"  are provided: - none
      in: query
      required: false
      schema:
        type: string
    manoServiceInterfaceId:
      name: manoServiceInterfaceId
      in: path
      description: Identifier of the MANO service interface.
      required: true
      schema:
        description: |
          An identifier with the intention of being globally unique.
        type: string
    subscriptionId:
      name: subscriptionId
      in: path
      description: Identifier of the subscription
      required: true
      schema:
        description: |
          An identifier with the intention of being globally unique.
        type: string
    changeStateOpOccId:
      name: changeStateOpOccId
      in: path
      description: Identifier of the change state operation occurrence
      required: true
      schema:
        description: |
          An identifier with the intention of being globally unique.
        type: string
    peerEntityId:
      name: peerEntityId
      in: path
      description: Identifier of the peer entity
      required: true
      schema:
        description: |
          An identifier with the intention of being globally unique.
        type: string
  requestBodies:
    ModifyManoEntityRequest:
      description: >
        Parameters for the NFV-MANO configuration and information  modification,
        as defined in clause 5.6.2.3. The Content-Type header shall be set to
        "application/merge-patch+json"  according to IETF RFC 7396.
      content:
        application/merge-patch+json:
          schema:
            description: >
              This type represents attribute modifications for configuration
              parameters  of an NFV-MANO functional entity. 
            type: object
            properties:
              name:
                description: |
                  New value of the "name" attribute in "ManoEntity".
                type: string
              description:
                description: |
                  New value of the "description" attribute in "ManoEntity".
                type: string
              clockSyncs:
                description: >
                  Modifications of the "clockSyncs" attribute in the
                  "ManoEntityConfigurableParams". If present, these
                  modifications shall be applied according to the rules of JSON
                  Merge PATCH (see IETF RFC 7396).
                type: object
                additionalProperties:
                  description: >
                    This type represents parameters for connecting to an NTP
                    server. 
                  type: object
                  properties:
                    type:
                      description: |
                        Type of clock synchronization.
                        Permitted values:
                          - NTP: For Network Time Protocol (NTP) based clock synchronization.
                          - OTHER: For other types of clock synchronization.
                      type: string
                      enum:
                        - NTP
                        - OTHER
                    ntpServerInfo:
                      description: >
                        Information for the NTP based clock synchronization. 
                        Shall be present if type = "NTP".
                      type: object
                      properties:
                        ipAddress:
                          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
                        hostname:
                          description: "Indicates the hostname of the NTP server. \nNOTE:\tEither ipAddress or hostname shall be set, but not both  at the same time.\n"
                          type: string
                    otherClockSyncParams:
                      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
                  required:
                    - type
              defaultLogCompileBySizeValue:
                description: |
                  Unsigned integer
                type: number
              defaultLogCompileByTimerValue:
                description: |
                  Unsigned integer
                type: number
              manoServiceModifications:
                description: >
                  New content of certain entries in the "manoServices" attribute
                  array  in the "ManoEntity", as defined below this table.
                type: array
                items:
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier that is unique for the respective type
                        within a NFV-MANO functional entity, but that need not
                        be globally unique. Representation: string of variable
                        length..
                      type: string
                    name:
                      description: "New value for the \"name\" attribute in the \"ManoService\". \nNOTE:\tAt least one of these attributes shall be provided if requesting  a modification of the NFV-MANO service identified by \"id\".\n"
                      type: string
                    description:
                      description: "New value for the \"description\" attribute in the \"ManoService\".\nNOTE:\tAt least one of these attributes shall be provided if requesting  a modification of the NFV-MANO service identified by \"id\".\n"
                      type: string
                  required:
                    - id
      required: true
    ChangeManoEntityStateRequest:
      description: |
        Parameters for the change state operation, as defined in clause 5.6.2.8.
      content:
        application/json:
          schema:
            description: >
              This type represents request parameters for changing the state of
              a managed entity. 
            type: object
            properties:
              operationalStateChange:
                description: "A change of operational state. Shall be present if the state change request refers to the operational state.  NOTE:\tIn the present document version, a request shall only include an  operational state change (attribute \"operationalStateChange\") or an  administrative state change request (attribute \"administrativeStateChange\"),  but not both.\n"
                type: object
                properties:
                  operationalStateAction:
                    description: "The enumeration ChangeOperationalStateEnumType defines permitted values  for the change state operation.  The ChangeOperationalStateEnumType shall comply with the provisions:\n  - START\tTo start the managed entity.\n  - STOP\tTo stop the managed entity.\n  - RESTART\tTo stop and start again the managed entity.\n"
                    type: string
                    enum:
                      - START
                      - STOP
                      - RESTART
                  stopType:
                    description: "The enumeration ChangeStateOpOccStateEnumType defines permitted values  for the change state operation. It shall comply with the provisions:\n  - GRACEFUL\tTo stop the managed entity immediately after accepting the request.\n  - FORCEFUL\tTo stop the managed entity attempting to gracefully discharge the entity from service.\n"
                    type: string
                    enum:
                      - GRACEFUL
                      - FORCEFUL
                  gracefulStopTimeout:
                    description: "The time internal (in seconds) to wait for the entity to be taken out  of service during graceful stop. \nNOTE:\tThe \"stopType\" shall only be provided when the \"operationalStateAction\"  attribute is equal to \"STOP\" or \"RESTART\".  The \"gracefulStopTimeout\" shall  be absent when the \"stopType\" attribute is equal to \"FORCEFUL\", and may  be provided otherwise.\n"
                    type: integer
                required:
                  - operationalStateAction
              administrativeStateChange:
                description: "A change of administrative state. Shall be present if the state change request refers to the administrative state. \nNOTE:\tIn the present document version, a request shall only include an  operational state change (attribute \"operationalStateChange\") or an  administrative state change request (attribute \"administrativeStateChange\"),  but not both.\n"
                type: object
                properties:
                  administrativeStateAction:
                    description: "The enumeration ChangeAdministrativeStateEnumType defines permitted values  for the change of administrative state operation.  The ChangeAdministrativeStateEnumType shall comply with the provisions:\n  - LOCK\tTo lock the managed entity.\n  - UNLOCK\tTo unlock the managed entity.\n"
                    type: string
                    enum:
                      - LOCK
                      - UNLOCK
                required:
                  - administrativeStateAction
      required: true
    ModifyManoEnityInterfaceRequest:
      description: >
        Parameters for the modification of configuration parameters of  the
        NFV-MANO service interface, as defined in clause 5.6.2.12.

        The Content-Type header shall be set to "application/merge-patch+json"
        according to IETF RFC 7396.
      content:
        application/merge-patch+json:
          schema:
            description: >
              This type represents attribute modifications for configuration
              parameters of  an NFV-MANO service interface of the producer
              NFV-MANO functional entity. 
            type: object
            properties:
              name:
                description: "New value of the \"name\" attribute in \"ManoServiceInterface\". \nNOTE:\tChanging the name does not change the corresponding standardized  API name in the resource URI (refer to \"{apiName}\" defined in clause 4.1  of ETSI GS NFV-SOL 013).\n"
                type: string
              apiRoot:
                description: |
                  String formatted according to IETF RFC 3986.
                type: string
              apiUri:
                description: |
                  String formatted according to IETF RFC 3986.
                type: string
              securityInfo:
                description: >
                  This type represents security related information of an
                  NFV-MANO  service interface produced by an NFV-MANO functional
                  entity. 
                type: object
                properties:
                  authType:
                    description: >
                      Type of API request authorization to be used by the API
                      producer.

                      The support of authorization methods for the API producer
                      is specified  in clause 8.3.6 of ETSI GS NFV-SOL 013.

                      Permitted values:
                        - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                        - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
                        in IETF RFC 6749. 
                    type: array
                    items:
                      type: string
                      enum:
                        - TLS_TUNNEL
                        - OAUTH2
                    minItems: 1
                  oauthServerInfo:
                    description: >
                      OAuth 2.0 authorization server information and
                      configuration.
                    type: object
                    properties:
                      dynamicDiscovery:
                        description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                        type: object
                        properties:
                          webFingerHost:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                        required:
                          - webFingerHost
                      providedConfiguration:
                        description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                        type: object
                        properties:
                          authServerId:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                        required:
                          - authServerId
                      tlsCipherSuites:
                        description: >
                          List of cipher suites that shall be declared as
                          supported by the  API producer when performing the SSL
                          or TLS negotiation with the  authorization server.
                          Valid values of cipher suites are defined  in IETF RFC
                          8447.
                        type: array
                        items:
                          type: string
                        minItems: 1
                    required:
                      - providedConfiguration
                      - tlsCipherSuites
                  tlsTunnelInfo:
                    description: >
                      Information and configuration related to the use of TLS
                      tunnel.  Shall be present if authType contains
                      "TLS_TUNNEL".
                    type: object
                    properties:
                      tlsTunnelCipherSuites:
                        description: >-
                          List of cipher suites that shall be declared as
                          supported by the API producer when performing the SSL
                          or TLS negotiation with the API client. Valid values
                          of cipher suites are defined in IETF RFC 8447.
                        type: array
                        items:
                          type: string
                        minItems: 1
                    required:
                      - tlsTunnelCipherSuites
                required:
                  - authType
                  - oauthServerInfo
              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
      required: true
    ChangeManoEntityInterfaceStateRequest:
      description: >
        Parameters for the change state operation, as defined in  clause
        5.6.2.8.
      content:
        application/json:
          schema:
            description: >
              This type represents request parameters for changing the state of
              a managed entity. 
            type: object
            properties:
              operationalStateChange:
                description: "A change of operational state. Shall be present if the state change request refers to the operational state.  NOTE:\tIn the present document version, a request shall only include an  operational state change (attribute \"operationalStateChange\") or an  administrative state change request (attribute \"administrativeStateChange\"),  but not both.\n"
                type: object
                properties:
                  operationalStateAction:
                    description: "The enumeration ChangeOperationalStateEnumType defines permitted values  for the change state operation.  The ChangeOperationalStateEnumType shall comply with the provisions:\n  - START\tTo start the managed entity.\n  - STOP\tTo stop the managed entity.\n  - RESTART\tTo stop and start again the managed entity.\n"
                    type: string
                    enum:
                      - START
                      - STOP
                      - RESTART
                  stopType:
                    description: "The enumeration ChangeStateOpOccStateEnumType defines permitted values  for the change state operation. It shall comply with the provisions:\n  - GRACEFUL\tTo stop the managed entity immediately after accepting the request.\n  - FORCEFUL\tTo stop the managed entity attempting to gracefully discharge the entity from service.\n"
                    type: string
                    enum:
                      - GRACEFUL
                      - FORCEFUL
                  gracefulStopTimeout:
                    description: "The time internal (in seconds) to wait for the entity to be taken out  of service during graceful stop. \nNOTE:\tThe \"stopType\" shall only be provided when the \"operationalStateAction\"  attribute is equal to \"STOP\" or \"RESTART\".  The \"gracefulStopTimeout\" shall  be absent when the \"stopType\" attribute is equal to \"FORCEFUL\", and may  be provided otherwise.\n"
                    type: integer
                required:
                  - operationalStateAction
              administrativeStateChange:
                description: "A change of administrative state. Shall be present if the state change request refers to the administrative state. \nNOTE:\tIn the present document version, a request shall only include an  operational state change (attribute \"operationalStateChange\") or an  administrative state change request (attribute \"administrativeStateChange\"),  but not both.\n"
                type: object
                properties:
                  administrativeStateAction:
                    description: "The enumeration ChangeAdministrativeStateEnumType defines permitted values  for the change of administrative state operation.  The ChangeAdministrativeStateEnumType shall comply with the provisions:\n  - LOCK\tTo lock the managed entity.\n  - UNLOCK\tTo unlock the managed entity.\n"
                    type: string
                    enum:
                      - LOCK
                      - UNLOCK
                required:
                  - administrativeStateAction
      required: true
    CimSubscriptionRequest:
      description: >
        Details of the subscription to be created, as defined in  clause
        5.6.2.5-1.
      content:
        application/json:
          schema:
            description: >
              This type represents a subscription request related to
              notifications  about NFV-MANO configuration and information
              management changes. 
            type: object
            properties:
              filter:
                description: >
                  This type represents a subscription filter related to
                  notifications  about NFV-MANO configuration and information
                  management. 
                type: object
                properties:
                  manoEntitySubscriptionFilter:
                    description: >
                      This type represents subscription filter criteria to match
                      NFV-MANO functional  entities and their associated managed
                      objects. 
                    type: object
                    properties:
                      manoEntityId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      manoServiceIds:
                        description: "manoServiceIds\tIdentifierInManoEntity\t0..N\tIf present, match NFV-MANO  services with an instance identifier listed in this attribute.\nThe attributes \"manoServiceIds\" and \"manoServiceNames\" are alternatives  to reference to NFV-MANO services in a filter. They should not be used  together in the same filter instance, but one alternative should be chosen.\n"
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceNames:
                        description: >
                          If present, match NFV-MANO services with an NFV-MANO
                          service name listed  in this attribute.

                          The attributes "manoServiceIds" and "manoServiceNames"
                          are alternatives  to reference to NFV-MANO services in
                          a filter. They should not be used  together in the
                          same filter instance, but one alternative should be
                          chosen.
                        type: array
                        items:
                          type: string
                      manoServiceInterfaceIds:
                        description: >
                          If present, match NFV-MANO functional entity produced
                          interfaces with an  instance identifier listed in this
                          attribute.

                          The attributes "manoServiceInterfaceIds" and
                          "manoServiceInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity produced 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceInterfaceNames:
                        description: >
                          If present, match NFV-MANO functional entity produced
                          interfaces with an  instance Name listed in this
                          attribute.

                          The attributes "manoServiceInterfaceIds" and
                          "manoServiceInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity produced 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          type: string
                      consumedManoInterfaceIds:
                        description: >
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an  instance identifier listed in this
                          attribute.

                          The attributes "consumedManoInterfaceIds" and
                          "consumedManoInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity consumed 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                      consumedManoInterfaceNames:
                        description: >
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an  instance Name listed in this
                          attribute.

                          The attributes "consumedManoInterfaceIds" and
                          "consumedManoInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity consumed 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          type: string
                  notificationTypes:
                    description: "Match particular notification types. \nPermitted values:\n  - InformationChangedNotification\n  - ChangeStateNotification\n\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are  spelled exactly as the names of the notification types to facilitate  automated code generation systems.\n"
                    type: array
                    items:
                      type: string
                      enum:
                        - InformationChangedNotification
                        - ChangeStateNotification
              callbackUri:
                description: |
                  String formatted according to IETF RFC 3986.
                type: string
              authentication:
                type: object
                required:
                  - authType
                properties:
                  authType:
                    description: >
                      Defines the types of Authentication / Authorization which
                      the API consumer is willing to accept when receiving a
                      notification. Permitted values: * BASIC: In every HTTP
                      request to the notification endpoint, use
                        HTTP Basic authentication with the client credentials.
                      * OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the
                        notification endpoint, use an OAuth 2.0 Bearer token, obtained
                        using the client credentials grant type.
                      * TLS_CERT: Every HTTP request to the notification
                      endpoint is sent
                        over a mutually authenticated TLS session, i.e. not only the
                        server is authenticated, but also the client is authenticated
                        during the TLS tunnel setup.
                    type: array
                    items:
                      type: string
                      enum:
                        - BASIC
                        - OAUTH2_CLIENT_CREDENTIALS
                        - TLS_CERT
                  paramsBasic:
                    description: >
                      Parameters for authentication/authorization using BASIC.
                      Shall be present if authType is "BASIC" and the contained
                      information has not been provisioned out of band. Shall be
                      absent otherwise.
                    type: object
                    properties:
                      userName:
                        description: >
                          Username to be used in HTTP Basic authentication.
                          Shall be present if it has not been provisioned out of
                          band.
                        type: string
                      password:
                        description: >
                          Password to be used in HTTP Basic authentication.
                          Shall be present if it has not been provisioned out of
                          band.
                        type: string
                  paramsOauth2ClientCredentials:
                    description: >
                      Parameters for authentication/authorization using
                      OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is
                      "OAUTH2_CLIENT_CREDENTIALS" and the contained information
                      has not been provisioned out of band. Shall be absent
                      otherwise.
                    type: object
                    properties:
                      clientId:
                        description: >
                          Client identifier to be used in the access token
                          request of the OAuth 2.0 client credentials grant
                          type. Shall be present if it has not been provisioned
                          out of band. The clientId and clientPassword passed in
                          a subscription shall not be the same as the clientId
                          and clientPassword that are used to obtain
                          authorization for API requests. Client credentials may
                          differ between subscriptions. The value of
                          clientPassword should be generated by a random
                          process.
                        type: string
                      clientPassword:
                        description: >
                          Client password to be used in the access token request
                          of the OAuth 2.0 client credentials grant type. Shall
                          be present if it has not been provisioned out of band.
                          The clientId and clientPassword passed in a
                          subscription shall not be the same as the clientId and
                          clientPassword that are used to obtain authorization
                          for API requests. Client credentials may differ
                          between subscriptions. The value of clientPassword
                          should be generated by a random process.
                        type: string
                      tokenEndpoint:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
            required:
              - callbackUri
      required: true
    CreatePeerEntityRequest:
      description: |
        The peer entity creation parameters, as defined in clause 5.6.2.14.
      content:
        application/json:
          schema:
            description: >
              This type represents request parameters for the creation of a new
              peer entity resource. 
            type: object
            properties:
              peerEntityId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              name:
                description: |
                  Human-readable name of the peer functional entity.
                type: string
              type:
                description: "The enumeration PeerEntityEnumType defines the permitted values  to represent peer functional entities. it shall complains with  the provisions :  - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t  The peer functional entity is a VIM. - WIM\t  The peer functional entity is a WIM. - EM\t  The peer functional entity is an EM. - OSS\t  The peer functional entity is an OSS/BSS.\n"
                type: string
                enum:
                  - NFVO
                  - VNFM
                  - VIM
                  - WIM
                  - EM
                  - OSS
              description:
                description: |
                  Human-readable description of the peer functional entity.
                type: string
              consumedManoInterfaces:
                description: >
                  Initial information of the interface consumed by the NFV-MANO
                  functional entity from the peer functional entity.
                type: object
                additionalProperties:
                  description: >
                    This type represents an interface consumed by the producer
                    NFV MANO  functional entity from another peer functional
                    entity. 
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    name:
                      description: |
                        Human-readable name of the NFV-MANO interface.
                      type: string
                    type:
                      description: >
                        Type of the NFV-MANO service interface consumed by the
                        NFV-MANO  functional entity. Valid values are defined in
                        clause 5.6.4.3.
                      type: string
                    standardVersion:
                      description: |
                        A version.
                      type: string
                    apiVersion:
                      description: |
                        A version.
                      type: string
                    apiEndpoint:
                      description: >
                        Consumable API endpoint of the interface. It provides
                        the information relevant about the protocol, host and
                        port,  and path where the interface API can be accessed.
                      type: object
                      properties:
                        apiRoot:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                        apiName:
                          description: >
                            Indicates the interface name in an abbreviated form.
                            Shall be present  for ETSI NFV specified RESTful
                            NFV-MANO APIs. The {apiName} of each  interface is
                            defined in the standard the interface is compliant
                            to  (see also clause 4.1 of ETSI GS NFV-SOL 013).
                            May be present otherwise.
                          type: string
                        apiMajorVersion:
                          description: >
                            Indicates the current major version of the API.
                            Shall be present for  ETSI NFV specified RESTful
                            NFV-MANO APIs. The major version is defined  in the
                            standard the interface is compliant to (see also
                            clause 4.1  of ETSI GS NFV-SOL 013). May be present
                            otherwise.
                          type: string
                        apiUri:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                      required:
                        - apiUri
                    securityInfo:
                      description: >
                        This type represents security related information for
                        accessing an NFV-MANO  service interface produced by an
                        NFV-MANO functional entity.
                      type: object
                      required:
                        - authType
                        - oauthServerInfo
                      properties:
                        authType:
                          description: >
                            Type of API request authorization to be used by the
                            API consumer accessing  the API.

                            The support of authorization methods for the API
                            consumer is specified in  clause 8.3.6 of ETSI GS
                            NFV-SOL 013.

                            Permitted values: - TLS_TUNNEL: Using TLS tunnel, as
                            defined by TLS 1.2 in IETF RFC 5246. - OAUTH2: Using
                            access token, as defined by the OAuth 2.0
                            specification  in IETF RFC 6749. 
                          type: array
                          items:
                            type: string
                            enum:
                              - TLS_TUNNEL
                              - OAUTH2
                          minItems: 1
                        oauthServerInfo:
                          description: >
                            OAuth 2.0 authorization server information and
                            configuration.
                          type: object
                          properties:
                            dynamicDiscovery:
                              description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                              type: object
                              required:
                                - webFingerHost
                              properties:
                                webFingerHost:
                                  description: >
                                    Server where the WebFinger service is
                                    hosted. When used, the request to  the
                                    WebFinger resource shall conform as
                                    specified in clause 5.1.3 of  ETSI GS
                                    NFV-SEC 022.
                                  type: string
                                  format: uri
                            providedConfiguration:
                              description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                              type: object
                              required:
                                - authServerId
                              properties:
                                authServerId:
                                  description: >
                                    Authorization server identifier as defined
                                    in ETSI GS NFV-SEC 022.
                                  type: string
                                  format: uri
                            tlsCipherSuites:
                              description: >
                                List of cipher suites that shall be declared as
                                supported by the API consumer when  performing
                                the SSL or TLS negotiation with the
                                authorization server. Valid values  of cipher
                                suites are defined in IETF RFC 8447.
                              type: array
                              items:
                                type: string
                                minItems: 1
                        tlsTunnelInfo:
                          description: >
                            Information and configuration related to the use of
                            TLS tunnel. Shall be  present if authType contains
                            "TLS_TUNNEL".
                          type: object
                          properties:
                            tlsTunnelCipherSuites:
                              description: >
                                List of cipher suites that shall be declared as
                                supported by the API  consumer when performing
                                the SSL or TLS negotiation with the API
                                producer.  Valid values of cipher suites are
                                defined in IETF RFC 8447.
                              type: array
                              items:
                                type: string
                                minItems: 1
                  required:
                    - id
                    - name
                    - type
                    - standardVersion
                    - apiVersion
                    - apiEndpoint
              peerEntityState:
                description: |
                  Current values of the state of the peer functional entity.
                type: object
                properties:
                  operationalState:
                    description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                    type: string
                    enum:
                      - STARTED
                      - STOPPED
                      - STOPPING
                      - STARTING
                      - RESTARTING
                  administrativeState:
                    description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                    type: string
                    enum:
                      - LOCKED
                      - UNLOCKED
                      - LOCKING
                required:
                  - operationalState
                  - administrativeState
            required:
              - peerEntityId
              - name
              - type
      required: true
    ModifyPeerEntityRequest:
      description: >
        Parameters for the modification of configuration parameters of  the peer
        functional entity, as defined in clause 5.6.2.16

        The Content-Type header shall be set to "application/merge-patch+json" 
        according to IETF RFC 7396.
      content:
        application/merge-patch+json:
          schema:
            description: >
              This type represents attribute modifications for configuration
              parameters  of a peer entity. 
            type: object
            properties:
              name:
                description: |
                  New value of the "name" attribute in "PeerEntity".
                type: string
              description:
                description: >
                  New value of the "description" attribute in "PeerEntity", or
                  "null" to  remove the attribute.
                type: string
              consumedManoInterfaces:
                description: "Modification of the \"consumedManoInterfaces\" attribute in the \"PeerEntity\", as defined below this table.\nIf present, these modifications shall be applied according to the rules of JSON Merge PATCH (see IETF RFC 7396).\nNOTE:\tDue to the security sensitive information contained within the attribute  (refer to \"securityInfo\" within the \"ConsumedManoInterfaceInfo\"), based on  access control policies, the API consumer might have read only, write only,  read/write, or no access at all to the attribute’s value. In case the  API consumer is not allowed to modify the value of the security sensitive  attribute, and the modification request includes new attribute values,  the whole modification request shall be rejected, and proper error information  returned.\n"
                type: object
                additionalProperties:
                  description: >
                    This type represents an interface consumed by the producer
                    NFV MANO  functional entity from another peer functional
                    entity. 
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    name:
                      description: |
                        Human-readable name of the NFV-MANO interface.
                      type: string
                    type:
                      description: >
                        Type of the NFV-MANO service interface consumed by the
                        NFV-MANO  functional entity. Valid values are defined in
                        clause 5.6.4.3.
                      type: string
                    standardVersion:
                      description: |
                        A version.
                      type: string
                    apiVersion:
                      description: |
                        A version.
                      type: string
                    apiEndpoint:
                      description: >
                        Consumable API endpoint of the interface. It provides
                        the information relevant about the protocol, host and
                        port,  and path where the interface API can be accessed.
                      type: object
                      properties:
                        apiRoot:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                        apiName:
                          description: >
                            Indicates the interface name in an abbreviated form.
                            Shall be present  for ETSI NFV specified RESTful
                            NFV-MANO APIs. The {apiName} of each  interface is
                            defined in the standard the interface is compliant
                            to  (see also clause 4.1 of ETSI GS NFV-SOL 013).
                            May be present otherwise.
                          type: string
                        apiMajorVersion:
                          description: >
                            Indicates the current major version of the API.
                            Shall be present for  ETSI NFV specified RESTful
                            NFV-MANO APIs. The major version is defined  in the
                            standard the interface is compliant to (see also
                            clause 4.1  of ETSI GS NFV-SOL 013). May be present
                            otherwise.
                          type: string
                        apiUri:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                      required:
                        - apiUri
                    securityInfo:
                      description: >
                        This type represents security related information for
                        accessing an NFV-MANO  service interface produced by an
                        NFV-MANO functional entity.
                      type: object
                      required:
                        - authType
                        - oauthServerInfo
                      properties:
                        authType:
                          description: >
                            Type of API request authorization to be used by the
                            API consumer accessing  the API.

                            The support of authorization methods for the API
                            consumer is specified in  clause 8.3.6 of ETSI GS
                            NFV-SOL 013.

                            Permitted values: - TLS_TUNNEL: Using TLS tunnel, as
                            defined by TLS 1.2 in IETF RFC 5246. - OAUTH2: Using
                            access token, as defined by the OAuth 2.0
                            specification  in IETF RFC 6749. 
                          type: array
                          items:
                            type: string
                            enum:
                              - TLS_TUNNEL
                              - OAUTH2
                          minItems: 1
                        oauthServerInfo:
                          description: >
                            OAuth 2.0 authorization server information and
                            configuration.
                          type: object
                          properties:
                            dynamicDiscovery:
                              description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                              type: object
                              required:
                                - webFingerHost
                              properties:
                                webFingerHost:
                                  description: >
                                    Server where the WebFinger service is
                                    hosted. When used, the request to  the
                                    WebFinger resource shall conform as
                                    specified in clause 5.1.3 of  ETSI GS
                                    NFV-SEC 022.
                                  type: string
                                  format: uri
                            providedConfiguration:
                              description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                              type: object
                              required:
                                - authServerId
                              properties:
                                authServerId:
                                  description: >
                                    Authorization server identifier as defined
                                    in ETSI GS NFV-SEC 022.
                                  type: string
                                  format: uri
                            tlsCipherSuites:
                              description: >
                                List of cipher suites that shall be declared as
                                supported by the API consumer when  performing
                                the SSL or TLS negotiation with the
                                authorization server. Valid values  of cipher
                                suites are defined in IETF RFC 8447.
                              type: array
                              items:
                                type: string
                                minItems: 1
                        tlsTunnelInfo:
                          description: >
                            Information and configuration related to the use of
                            TLS tunnel. Shall be  present if authType contains
                            "TLS_TUNNEL".
                          type: object
                          properties:
                            tlsTunnelCipherSuites:
                              description: >
                                List of cipher suites that shall be declared as
                                supported by the API  consumer when performing
                                the SSL or TLS negotiation with the API
                                producer.  Valid values of cipher suites are
                                defined in IETF RFC 8447.
                              type: array
                              items:
                                type: string
                                minItems: 1
                  required:
                    - id
                    - name
                    - type
                    - standardVersion
                    - apiVersion
                    - apiEndpoint
              operationalState:
                description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                type: string
                enum:
                  - STARTED
                  - STOPPED
                  - STOPPING
                  - STARTING
                  - RESTARTING
              administrativeState:
                description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                type: string
                enum:
                  - LOCKED
                  - UNLOCKED
                  - LOCKING
      required: true
  responses:
    mano_entity.get.200:
      description: >
        200 OK

        Shall be returned when configuration and information about  the NFV-MANO
        functional entity has been read successfully. The response body shall
        contain a representation of the NFV-MANO functional entity, as defined
        in clause 5.6.2.2.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: |
              This type represents an NFV-MANO functional entity.
            type: object
            required:
              - id
              - type
              - name
              - description
              - provider
              - softwareVersion
              - manoConfigurableParams
              - manoApplicationState
              - _links
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              type:
                description: "The enumeration ManoEntityEnumType defines the permitted values to  represent NFV-MANO functional entities. It shall comply with  the provisions :\n  - NFVO\tThe NFV-MANO functional entity is an NFVO.\n  - VNFM\tThe NFV-MANO functional entity is a VNFM.\n  - VIM\tThe NFV-MANO functional entity is a VIM.\n"
                type: string
                enum:
                  - NFVO
                  - VNFM
                  - VIM
              name:
                description: |
                  Human-readable name of the NFV-MANO functional entity.
                  This attribute can be modified with the PATCH method.
                type: string
              description:
                description: |
                  Human-readable description of the NFV-MANO functional entity.
                  This attribute can be modified with the PATCH method.
                type: string
              provider:
                description: >
                  Information about the provider of the NFV-MANO functional
                  entity.  It typically includes the name of the provider.
                type: string
              softwareVersion:
                description: >
                  The version of the software of the NFV-MANO functional entity.
                  $ref:
                  "../components/SOL009_schemas.yaml#/components/schemas/Version"
              manoEntityComponents:
                description: "The deployed NFV-MANO functional entity components which realize the  NFV-MANO functional entity. \nNOTE:\tIt is optional for the API producer to support the \"manoEntityComponents\"  attribute.\n"
                type: array
                items:
                  description: >
                    This type represents information of a deployed component
                    realizing part of an  NFV-MANO functional entity. It is
                    optional for the API producer to support  this type. 
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier that is unique for the respective type
                        within a NFV-MANO functional entity, but that need not
                        be globally unique. Representation: string of variable
                        length..
                      type: string
                    manoServiceIds:
                      description: >
                        References to the NFV-MANO services that depend on the
                        NFV-MANO functional  entity component. The identifier of
                        the ManoService is referred. A service  may depend on
                        multiple components. Multiple services may depend on the
                        same  component.
                      type: array
                      items:
                        description: >
                          An identifier that is unique for the respective type
                          within a NFV-MANO functional entity, but that need not
                          be globally unique. Representation: string of variable
                          length..
                        type: string
                  required:
                    - id
              manoServices:
                description: >
                  Information about the NFV-MANO services provided by the
                  NFV-MANO  functional entity.
                type: array
                items:
                  description: >
                    This type represents information about an NFV-MANO service
                    provided by the  NFV-MANO functional entity.
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier that is unique for the respective type
                        within a NFV-MANO functional entity, but that need not
                        be globally unique. Representation: string of variable
                        length..
                      type: string
                    name:
                      description: |
                        Human-readable name of the NFV-MANO service.
                        This attribute can be modified with the PATCH method.
                      type: string
                    description:
                      description: |
                        Human-readable description of the NFV-MANO service.
                        This attribute can be modified with the PATCH method.
                      type: string
                    manoServiceInterfaceIds:
                      description: "Reference to the NFV-MANO interfaces associated to the NFV-MANO service.  If cardinality is greater than one, the type of ManoServiceInterface  (see clause 5.6.3.3) shall be the same. The identifier of the  ManoServiceInterface is referred. \nNOTE:\tA cardinality greater than one supports having different interface  versions or apiEndpoints to be used for accessing the same instance of a  NFV-MANO service.\n"
                      type: array
                      items:
                        description: >
                          An identifier that is unique for the respective type
                          within a NFV-MANO functional entity, but that need not
                          be globally unique. Representation: string of variable
                          length..
                        type: string
                      minItems: 1
                    _links:
                      description: |
                        Links to resources related to this resource.
                      type: object
                      properties:
                        manoServiceInterfaces:
                          description: >
                            Link to the "individual NFV-MANO service interface"
                            resources with  information about the associated
                            interfaces to the NFV-MANO service.
                          type: array
                          items:
                            description: >
                              This type represents a link to a resource using an
                              absolute URI.
                            type: object
                            required:
                              - href
                            properties:
                              href:
                                description: |
                                  String formatted according to IETF RFC 3986.
                                type: string
                          minItems: 1
                      required:
                        - manoServiceInterfaces
                  required:
                    - id
                    - name
                    - description
                    - manoServiceInterfaceIds
                    - _links
              manoConfigurableParams:
                description: >
                  # Warning: No definition found in the document
                  ManoConfigurableParams
              manoApplicationState:
                description: >
                  Information and current values of the NFV-MANO functional
                  entity’s application state. 
                type: object
                required:
                  - operationalState
                  - administrativeState
                  - usageState
                properties:
                  operationalState:
                    description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                    type: string
                    enum:
                      - STARTED
                      - STOPPED
                      - STOPPING
                      - STARTING
                      - RESTARTING
                  administrativeState:
                    description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                    type: string
                    enum:
                      - LOCKED
                      - UNLOCKED
                      - LOCKING
                  usageState:
                    description: "The enumeration UsageStateEnumType defines values representing the usage  state of a managed entity.  The UsageStateEnumType shall comply with the provisions:\n  - IN_USE\tThe managed entity is currently being used.\n  - NOT_IN_USE\tThe managed entity is currently not being used.\n"
                    type: string
                    enum:
                      - IN_USE
                      - NOT_IN_USE
              nfvoSpecificInfo:
                description: >
                  This type represents information attributes specific to an
                  NFVO entity,  and that can be relevant to more than one
                  NFV-MANO service offered by an  NFVO entity. 
                type: object
                properties:
                  maxOnboardedNsdNum:
                    description: >
                      Maximum number of NSDs that can be on-boarded on the
                      NFVO. 

                      NOTE: If this attribute is not present, the value of this
                      parameter  is undefined.
                    type: integer
                  maxOnboardedVnfPkgNum:
                    description: >
                      Maximum number of VNF Packages that can be on-boarded on
                      the NFVO. 

                      NOTE: If this attribute is not present, the value of this
                      parameter  is undefined.
                    type: integer
                  supportedVnfdFormats:
                    description: |
                      Supported VNFD data formats.
                    type: object
                    properties:
                      vnfdFormat:
                        description: |
                          Name of the VNFD format.
                          Permitted values:
                            - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                            GS NFV-SOL 001 standard.
                            - YANG: The VNFD follows YANG definition according to ETSI 
                            GS NFV-SOL 006 standard.
                        type: string
                        enum:
                          - TOSCA
                          - YANG
                      standardVersion:
                        description: |
                          A version.
                        type: string
                    required:
                      - vnfdFormat
                      - standardVersion
                  supportedNsdFormats:
                    description: |
                      Supported NSD data formats.
                    type: object
                    properties:
                      nsdFormat:
                        description: |
                          Name of the NSD format.
                          Permitted values:
                            - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                            GS NFV-SOL 001 standard.
                            - YANG: The VNFD follows YANG definition according to ETSI 
                            GS NFV-SOL 006 standard.
                        type: string
                        enum:
                          - TOSCA
                          - YANG
                      standardVersion:
                        description: |
                          A version.
                        type: string
                    required:
                      - nsdFormat
                      - standardVersion
                required:
                  - supportedVnfdFormats
                  - supportedNsdFormats
              vnfmSpecificInfo:
                description: >
                  This type represents information attributes specific to a VNFM
                  entity,  and that can be relevant to more than one NFV-MANO
                  service offered by  a VNFM entity.
                type: object
                properties:
                  resoruceMgmtModeSupport:
                    description: |
                      The supported resource management modes of the VNFM.
                      Permitted values:
                        - DIRECT: The VNFM supports direct mode only.
                        - INDIRECT: The VNFM supports indirect mode only.
                        - BOTH: The VNFM supports both direct and indirect mode.
                    type: string
                    enum:
                      - DIRECT
                      - INDIRECT
                      - BOTH
                  managedVnfInstanceInfos:
                    description: >
                      The kinds of VNF instances that can be managed, e.g. to
                      determine the  compatibility of a VNF with certain VNFM
                      according to the vnfmInfo  attribute in the VNFD (see
                      table 7.1.2.2-1 in ETSI GS NFV-IFA 011).
                    type: array
                    items:
                      type: string
                    minItems: 1
                  supportedVnfdFormats:
                    description: |
                      Supported VNFD data formats.
                    type: array
                    items:
                      type: object
                      properties:
                        vnfdFormat:
                          description: |
                            Name of the VNFD format.
                            Permitted values:
                              - TOSCA: The VNFD follows TOSCA definition, according to ETSI 
                              GS NFV-SOL 001 standard.
                              - YANG: The VNFD follows YANG definition according to ETSI 
                              GS NFV-SOL 006 standard.
                          type: string
                          enum:
                            - TOSCA
                            - YANG
                        standardVersion:
                          description: |
                            A version.
                          type: string
                      required:
                        - vnfdFormat
                        - standardVersion
                    minItems: 1
                required:
                  - resoruceMgmtModeSupport
                  - managedVnfInstanceInfos
                  - supportedVnfdFormats
              vimSpecificInfo:
                description: >
                  This type represents information attributes specific to a VIM
                  entity,  and that can be relevant to more than one NFV-MANO
                  service offered by  a VIM entity.
                type: object
              _links:
                description: |
                  Links to resources related to this resource.
                type: object
                required:
                  - self
                  - manoServiceInterfaces
                  - peerEntities
                  - changeState
                  - changeStateOpOccs
                properties:
                  self:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  manoServiceInterfaces:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  peerEntities:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  changeState:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  changeStateOpOccs:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
    mano_entity.patch.200:
      description: >
        200 OK

        Shall be returned when the modification of configuration on the 
        NFV-MANO functional entity has been accepted and completed.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              This type represents attribute modifications that were performed
              on the  "NFV-MANO entity" resource of the producer NFV-MANO
              functional entity.  The attributes that can be included consist of
              those requested to be  modified explicitly in the
              "ManoConfigModificationRequest" data structure. 
            type: object
            properties:
              name:
                description: >
                  If present, this attribute signals modifications of the
                  "name"  attribute in "ManoEntity", as defined in clause
                  5.6.2.3
                type: string
              description:
                description: >
                  If present, this attribute signals modifications of the
                  "description"  attribute in "ManoEntity", as defined in clause
                  5.6.2.3.
                type: string
              clockSyncs:
                description: >
                  If present, this attribute signals modifications of the
                  "clockSyncs" attribute in "ManoEntityConfigurableParams", as
                  defined in clause 5.6.2.3.
                type: object
                additionalProperties:
                  description: >
                    This type represents parameters for connecting to an NTP
                    server. 
                  type: object
                  properties:
                    type:
                      description: |
                        Type of clock synchronization.
                        Permitted values:
                          - NTP: For Network Time Protocol (NTP) based clock synchronization.
                          - OTHER: For other types of clock synchronization.
                      type: string
                      enum:
                        - NTP
                        - OTHER
                    ntpServerInfo:
                      description: >
                        Information for the NTP based clock synchronization. 
                        Shall be present if type = "NTP".
                      type: object
                      properties:
                        ipAddress:
                          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
                        hostname:
                          description: "Indicates the hostname of the NTP server. \nNOTE:\tEither ipAddress or hostname shall be set, but not both  at the same time.\n"
                          type: string
                    otherClockSyncParams:
                      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
                  required:
                    - type
              defaultLogCompileBySizeValue:
                description: |
                  Unsigned integer
                type: number
              defaultLogCompileByTimerValue:
                description: |
                  Unsigned integer
                type: number
              manoServiceModifications:
                description: >
                  If present, this attribute signals modifications of the
                  "manoServices"  attribute array in the "ManoEntity", as
                  defined in clause 5.6.2.3.
                type: array
                items:
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier that is unique for the respective type
                        within a NFV-MANO functional entity, but that need not
                        be globally unique. Representation: string of variable
                        length..
                      type: string
                    name:
                      description: >
                        If present, this attribute signals modification of the
                        "name"  attribute in the "ManoService".
                      type: string
                    description:
                      description: >
                        If present, this attribute signals modification of the 
                        "description" attribute in the "ManoService".
                      type: string
                  required:
                    - id
    mano_entity.patch.409:
      description: >
        409 CONFLICT

        Shall be returned upon the following error: The operation cannot  be
        executed currently, due to a conflict with the state of the  "NFV-MANO
        entity" resource.

        Typically, this is due to the fact that another configuration and 
        information modification is ongoing.

        The response body shall contain a ProblemDetails structure, in which 
        the "detail" attribute should convey more information about the error.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    mano_entity.patch.412:
      description: >
        412 PRECONDITION FAILED

        Shall be returned upon the following error: A precondition given in  an
        HTTP request header is not fulfilled.

        Typically, this is due to an ETag mismatch, indicating that the
        resource  was modified by another entity.

        The response body should contain a ProblemDetails structure, in which 
        the "detail" attribute should convey more information about the error
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    mano_entity-change_state.post.202:
      description: >
        202 ACCEPTED

        Shall be returned when the request has been accepted for processing.

        The response body shall be empty.

        The HTTP response shall include a "Location" HTTP header that contains 
        the URI of the newly-created "Individual change state operation
        occurrence" resource corresponding to the operation.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Location:
          description: >
            The resource URI of the created "Individual change state operation
            occurence" resource.
          schema:
            type: string
            format: url
            minimum: 1
            maximum: 1
    mano_entity-change_state.post.409:
      description: >
        409 CONFLICT

        Shall be returned upon the following error: The operation cannot be 
        executed currently, due to a conflict with the state of the resource.

        Typically, this is due to the fact that the resource is in an
        incompatible  state, or that another change state operation is ongoing.

        The response body shall contain a ProblemDetails structure, in which
        the  "detail" attribute shall convey more information about the error.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    mano_entity-mano_interfaces.get.200:
      description: >
        200 OK

        Shall be returned when information about zero or more NFV-MANO  service
        interfaces has been queried successfully.

        The response body shall contain in an array the representations  of zero
        or more NFV-MANO service interfaces, as defined in  clause 5.6.2.11.

        If the “filter" URI parameter or one of the "all_fields", "fields"  (if
        supported), "exclude_fields" (if supported) or "exclude_default"  URI
        parameters was supplied in the request, the data in the response  body
        shall have been transformed according to the rules specified in  clauses
        5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013, respectively.

        If the NFV-MANO functional entity supports alternative N°2 (paging) 
        according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
        inclusion of the Link HTTP header in this response shall follow the 
        provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
      headers:
        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
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Link:
          description: >
            Reference to other resources. Link HTTP header in this response 
            shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL
            013.
          schema:
            type: string
            minimum: 0
            maximum: 1
      content:
        application/json:
          schema:
            type: array
            items:
              description: >
                This type represents an individual NFV-MANO service interface
                produced by  an NFV-MANO functional entity. 
              type: object
              properties:
                id:
                  description: >
                    An identifier that is unique for the respective type within
                    a NFV-MANO functional entity, but that need not be globally
                    unique. Representation: string of variable length..
                  type: string
                name:
                  description: >
                    Human-readable name of the NFV-MANO functional entity
                    interface.

                    This attribute can be modified with the PATCH method.
                  type: string
                type:
                  description: >
                    Type of the NFV-MANO service interface produced by the
                    NFV-MANO functional  entity. Valid values are defined in
                    clause 5.6.4.3.
                  type: string
                standardVersion:
                  description: |
                    A version.
                  type: string
                providerSpecificApiVersion:
                  description: |
                    A version.
                  type: string
                apiVersion:
                  description: |
                    A version.
                  type: string
                apiEndpoint:
                  description: |
                    Exposed API endpoint of the interface.
                  type: object
                  properties:
                    apiRoot:
                      description: |
                        String formatted according to IETF RFC 3986.
                      type: string
                    apiName:
                      description: >
                        Indicates the interface name in an abbreviated form.
                        Shall be present  for ETSI NFV specified RESTful
                        NFV-MANO APIs. The {apiName} of each  interface is
                        defined in the standard the interface is compliant to 
                        (see also clause 4.1 of ETSI GS NFV-SOL 013). May be
                        present otherwise.
                      type: string
                    apiMajorVersion:
                      description: >
                        Indicates the current major version of the API. Shall be
                        present for  ETSI NFV specified RESTful NFV-MANO APIs.
                        The major version is defined  in the standard the
                        interface is compliant to (see also clause 4.1 of  ETSI
                        GS NFV-SOL 013). May be present otherwise.
                      type: string
                    apiUri:
                      description: |
                        String formatted according to IETF RFC 3986.
                      type: string
                  required:
                    - apiUri
                maxConcurrentIntOpNumber:
                  description: "Maximum number of concurrent operation requests supported on this interface. \nNOTE:\tIf this attribute is not present, the value of this parameter  is undefined. Overload is handled by the error handling schemes defined  by the applicable API specification.\n"
                  type: integer
                supportedOperations:
                  description: |
                    Information about supported operations of this interface.
                  type: array
                  items:
                    type: object
                    properties:
                      operationName:
                        description: |
                          Name of the operation supported on the interface.
                        type: string
                      maxConcurrentOpNumber:
                        description: "Maximum number of concurrent requests supported by the interface operation. \nNOTE:\tIf this attribute is not present, the value of this parameter  is undefined. Overload is handled by the error handling schemes defined  by the applicable API specification.\n"
                        type: integer
                    required:
                      - operationName
                  minItems: 1
                interfaceState:
                  description: |
                    State of the NFV-MANO service interface.
                  properties:
                    operationalState:
                      description: "The enumeration InterfaceOperationalStateEnumType defines values representing  the operational state of an NFV-MANO service interface type of managed entity.  The InterfaceOperationalStateEnumType shall comply with the provisions :\n   - STARTED\tThe managed entity is operational.\n   - STOPPED\tThe managed entity is not operational.\n   - STOPPING\tThe managed entity is in the transition to stop.\n   - STARTING\tThe managed entity is in the transition to start and become operational.\n"
                      type: string
                      enum:
                        - STARTED
                        - STOPPED
                        - STOPPING
                        - STARTING
                    administrativeState:
                      description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                      type: string
                      enum:
                        - LOCKED
                        - UNLOCKED
                        - LOCKING
                    usageState:
                      description: "The enumeration UsageStateEnumType defines values representing the usage  state of a managed entity.  The UsageStateEnumType shall comply with the provisions:\n  - IN_USE\tThe managed entity is currently being used.\n  - NOT_IN_USE\tThe managed entity is currently not being used.\n"
                      type: string
                      enum:
                        - IN_USE
                        - NOT_IN_USE
                  required:
                    - operationalState
                    - administrativeState
                    - usageState
                securityInfo:
                  description: >
                    This type represents security related information of an
                    NFV-MANO  service interface produced by an NFV-MANO
                    functional entity. 
                  type: object
                  properties:
                    authType:
                      description: >
                        Type of API request authorization to be used by the API
                        producer.

                        The support of authorization methods for the API
                        producer is specified  in clause 8.3.6 of ETSI GS
                        NFV-SOL 013.

                        Permitted values:
                          - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                          - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
                          in IETF RFC 6749. 
                      type: array
                      items:
                        type: string
                        enum:
                          - TLS_TUNNEL
                          - OAUTH2
                      minItems: 1
                    oauthServerInfo:
                      description: >
                        OAuth 2.0 authorization server information and
                        configuration.
                      type: object
                      properties:
                        dynamicDiscovery:
                          description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                          type: object
                          properties:
                            webFingerHost:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                          required:
                            - webFingerHost
                        providedConfiguration:
                          description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                          type: object
                          properties:
                            authServerId:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                          required:
                            - authServerId
                        tlsCipherSuites:
                          description: >
                            List of cipher suites that shall be declared as
                            supported by the  API producer when performing the
                            SSL or TLS negotiation with the  authorization
                            server. Valid values of cipher suites are defined 
                            in IETF RFC 8447.
                          type: array
                          items:
                            type: string
                          minItems: 1
                      required:
                        - providedConfiguration
                        - tlsCipherSuites
                    tlsTunnelInfo:
                      description: >
                        Information and configuration related to the use of TLS
                        tunnel.  Shall be present if authType contains
                        "TLS_TUNNEL".
                      type: object
                      properties:
                        tlsTunnelCipherSuites:
                          description: >-
                            List of cipher suites that shall be declared as
                            supported by the API producer when performing the
                            SSL or TLS negotiation with the API client. Valid
                            values of cipher suites are defined in IETF RFC
                            8447.
                          type: array
                          items:
                            type: string
                          minItems: 1
                      required:
                        - tlsTunnelCipherSuites
                  required:
                    - authType
                    - oauthServerInfo
                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
              required:
                - id
                - name
                - type
                - standardVersion
                - providerSpecificApiVersion
                - apiVersion
                - apiEndpoint
                - supportedOperations
                - interfaceState
    mano_entity-mano_interfaces.get.400:
      description: |
        400 BAD REQUEST
        Shall be returned upon the following errors: 
          - Invalid attribute-based filtering expression.
            The response body shall contain a ProblemDetails structure, in which 
            the "detail" attribute should convey more information about the error.
          - Invalid attribute selector.
            The response body shall contain a ProblemDetails structure, in which 
            the "detail" attribute should convey more information about the error.
          - Response too big.
            If the NFV-MANO functional entity supports alternative N°1 (error) 
            according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
            this error response shall follow the provisions in clause 5.4.2.2 of 
            ETSI GS NFV-SOL 013.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    mano_entity-mano_interface.get.200:
      description: >
        200 OK

        Shall be returned when information about an individual NFV-MANO  service
        interface has been read successfully.

        The response body shall contain a representation of the NFV-MANO 
        service interface, as defined in clause 5.6.2.11.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              This type represents an individual NFV-MANO service interface
              produced by  an NFV-MANO functional entity. 
            type: object
            properties:
              id:
                description: >
                  An identifier that is unique for the respective type within a
                  NFV-MANO functional entity, but that need not be globally
                  unique. Representation: string of variable length..
                type: string
              name:
                description: >
                  Human-readable name of the NFV-MANO functional entity
                  interface.

                  This attribute can be modified with the PATCH method.
                type: string
              type:
                description: >
                  Type of the NFV-MANO service interface produced by the
                  NFV-MANO functional  entity. Valid values are defined in
                  clause 5.6.4.3.
                type: string
              standardVersion:
                description: |
                  A version.
                type: string
              providerSpecificApiVersion:
                description: |
                  A version.
                type: string
              apiVersion:
                description: |
                  A version.
                type: string
              apiEndpoint:
                description: |
                  Exposed API endpoint of the interface.
                type: object
                properties:
                  apiRoot:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                  apiName:
                    description: >
                      Indicates the interface name in an abbreviated form. Shall
                      be present  for ETSI NFV specified RESTful NFV-MANO APIs.
                      The {apiName} of each  interface is defined in the
                      standard the interface is compliant to  (see also clause
                      4.1 of ETSI GS NFV-SOL 013). May be present otherwise.
                    type: string
                  apiMajorVersion:
                    description: >
                      Indicates the current major version of the API. Shall be
                      present for  ETSI NFV specified RESTful NFV-MANO APIs. The
                      major version is defined  in the standard the interface is
                      compliant to (see also clause 4.1 of  ETSI GS NFV-SOL
                      013). May be present otherwise.
                    type: string
                  apiUri:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                required:
                  - apiUri
              maxConcurrentIntOpNumber:
                description: "Maximum number of concurrent operation requests supported on this interface. \nNOTE:\tIf this attribute is not present, the value of this parameter  is undefined. Overload is handled by the error handling schemes defined  by the applicable API specification.\n"
                type: integer
              supportedOperations:
                description: |
                  Information about supported operations of this interface.
                type: array
                items:
                  type: object
                  properties:
                    operationName:
                      description: |
                        Name of the operation supported on the interface.
                      type: string
                    maxConcurrentOpNumber:
                      description: "Maximum number of concurrent requests supported by the interface operation. \nNOTE:\tIf this attribute is not present, the value of this parameter  is undefined. Overload is handled by the error handling schemes defined  by the applicable API specification.\n"
                      type: integer
                  required:
                    - operationName
                minItems: 1
              interfaceState:
                description: |
                  State of the NFV-MANO service interface.
                properties:
                  operationalState:
                    description: "The enumeration InterfaceOperationalStateEnumType defines values representing  the operational state of an NFV-MANO service interface type of managed entity.  The InterfaceOperationalStateEnumType shall comply with the provisions :\n   - STARTED\tThe managed entity is operational.\n   - STOPPED\tThe managed entity is not operational.\n   - STOPPING\tThe managed entity is in the transition to stop.\n   - STARTING\tThe managed entity is in the transition to start and become operational.\n"
                    type: string
                    enum:
                      - STARTED
                      - STOPPED
                      - STOPPING
                      - STARTING
                  administrativeState:
                    description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                    type: string
                    enum:
                      - LOCKED
                      - UNLOCKED
                      - LOCKING
                  usageState:
                    description: "The enumeration UsageStateEnumType defines values representing the usage  state of a managed entity.  The UsageStateEnumType shall comply with the provisions:\n  - IN_USE\tThe managed entity is currently being used.\n  - NOT_IN_USE\tThe managed entity is currently not being used.\n"
                    type: string
                    enum:
                      - IN_USE
                      - NOT_IN_USE
                required:
                  - operationalState
                  - administrativeState
                  - usageState
              securityInfo:
                description: >
                  This type represents security related information of an
                  NFV-MANO  service interface produced by an NFV-MANO functional
                  entity. 
                type: object
                properties:
                  authType:
                    description: >
                      Type of API request authorization to be used by the API
                      producer.

                      The support of authorization methods for the API producer
                      is specified  in clause 8.3.6 of ETSI GS NFV-SOL 013.

                      Permitted values:
                        - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                        - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
                        in IETF RFC 6749. 
                    type: array
                    items:
                      type: string
                      enum:
                        - TLS_TUNNEL
                        - OAUTH2
                    minItems: 1
                  oauthServerInfo:
                    description: >
                      OAuth 2.0 authorization server information and
                      configuration.
                    type: object
                    properties:
                      dynamicDiscovery:
                        description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                        type: object
                        properties:
                          webFingerHost:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                        required:
                          - webFingerHost
                      providedConfiguration:
                        description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                        type: object
                        properties:
                          authServerId:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                        required:
                          - authServerId
                      tlsCipherSuites:
                        description: >
                          List of cipher suites that shall be declared as
                          supported by the  API producer when performing the SSL
                          or TLS negotiation with the  authorization server.
                          Valid values of cipher suites are defined  in IETF RFC
                          8447.
                        type: array
                        items:
                          type: string
                        minItems: 1
                    required:
                      - providedConfiguration
                      - tlsCipherSuites
                  tlsTunnelInfo:
                    description: >
                      Information and configuration related to the use of TLS
                      tunnel.  Shall be present if authType contains
                      "TLS_TUNNEL".
                    type: object
                    properties:
                      tlsTunnelCipherSuites:
                        description: >-
                          List of cipher suites that shall be declared as
                          supported by the API producer when performing the SSL
                          or TLS negotiation with the API client. Valid values
                          of cipher suites are defined in IETF RFC 8447.
                        type: array
                        items:
                          type: string
                        minItems: 1
                    required:
                      - tlsTunnelCipherSuites
                required:
                  - authType
                  - oauthServerInfo
              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
            required:
              - id
              - name
              - type
              - standardVersion
              - providerSpecificApiVersion
              - apiVersion
              - apiEndpoint
              - supportedOperations
              - interfaceState
    mano_entity-mano_interface.patch.200:
      description: >
        200 OK

        Shall be returned when the request has been accepted and completed.

        The response body shall contain a representation of the attribute 
        modifications for the "Individual NFV-MANO service interface" resource,
        as defined in clause 5.6.2.13.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              This type represents attribute modifications that were performed
              on an  Individual NFV-MANO service interface" resource. The
              attributes that can  be included consist of those requested to be
              modified explicitly in the 
              "ManoServiceInterfaceModificationRequest" data structure. If
              applicable,  additional attributes of the "ManoServiceInterface"
              data structure that  were modified implicitly shall also be
              provided. 
            type: object
            properties:
              name:
                description: >
                  If present, this attribute signals modifications of the "name"
                  attribute in  "ManoServiceInterface", as defined in clause
                  5.6.2.11.
                type: string
              apiRoot:
                description: |
                  String formatted according to IETF RFC 3986.
                type: string
              apiUri:
                description: |
                  String formatted according to IETF RFC 3986.
                type: string
              securityInfo:
                description: >
                  This type represents security related information of an
                  NFV-MANO  service interface produced by an NFV-MANO functional
                  entity. 
                type: object
                properties:
                  authType:
                    description: >
                      Type of API request authorization to be used by the API
                      producer.

                      The support of authorization methods for the API producer
                      is specified  in clause 8.3.6 of ETSI GS NFV-SOL 013.

                      Permitted values:
                        - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
                        - OAUTH2: Using access token, as defined by the OAuth 2.0 specification 
                        in IETF RFC 6749. 
                    type: array
                    items:
                      type: string
                      enum:
                        - TLS_TUNNEL
                        - OAUTH2
                    minItems: 1
                  oauthServerInfo:
                    description: >
                      OAuth 2.0 authorization server information and
                      configuration.
                    type: object
                    properties:
                      dynamicDiscovery:
                        description: "Configuration data used when performing dynamic discovery of  the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                        type: object
                        properties:
                          webFingerHost:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                        required:
                          - webFingerHost
                      providedConfiguration:
                        description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization  server information and configuration shall be supported, and  dynamic configuration may be supported.\n"
                        type: object
                        properties:
                          authServerId:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                        required:
                          - authServerId
                      tlsCipherSuites:
                        description: >
                          List of cipher suites that shall be declared as
                          supported by the  API producer when performing the SSL
                          or TLS negotiation with the  authorization server.
                          Valid values of cipher suites are defined  in IETF RFC
                          8447.
                        type: array
                        items:
                          type: string
                        minItems: 1
                    required:
                      - providedConfiguration
                      - tlsCipherSuites
                  tlsTunnelInfo:
                    description: >
                      Information and configuration related to the use of TLS
                      tunnel.  Shall be present if authType contains
                      "TLS_TUNNEL".
                    type: object
                    properties:
                      tlsTunnelCipherSuites:
                        description: >-
                          List of cipher suites that shall be declared as
                          supported by the API producer when performing the SSL
                          or TLS negotiation with the API client. Valid values
                          of cipher suites are defined in IETF RFC 8447.
                        type: array
                        items:
                          type: string
                        minItems: 1
                    required:
                      - tlsTunnelCipherSuites
                required:
                  - authType
                  - oauthServerInfo
              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
    mano_entity-mano_interface.patch.409:
      description: >
        409 CONFLICT

        Shall be returned upon the following error: The operation cannot  be
        executed currently, due to a conflict with the state of the  "Individual
        NFV-MANO service interface" resource.

        Typically, this is due to the fact that another operation is  ongoing.

        The response body shall contain a ProblemDetails structure,  in which
        the "detail" attribute should convey more information  about the error.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    mano_entity-mano_interface.patch.412:
      description: >
        412 PRECONDITION FAILED

        Shall be returned upon the following error: A precondition given  in an
        HTTP request header is not fulfilled.

        Typically, this is due to an ETag mismatch, indicating that the 
        resource was modified by another entity.

        The response body should contain a ProblemDetails structure,  in which
        the "detail" attribute should convey more information  about the error.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    mano_entity-mano_interface-change_state.post.202:
      description: >
        202 ACCEPTED

        Shall be returned when the request has been accepted for  processing.

        The response body shall be empty.

        The HTTP response shall include a “Location” HTTP header that  contains
        the URI of the newly-created "Individual change state  operation
        occurrence" resource corresponding to the operation.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Location:
          description: >
            The resource URI of the created "Individual change state  operation
            occurence" resource.
          schema:
            type: string
            format: url
            minimum: 1
            maximum: 1
    mano_entity-mano_interface-change_state.post.409:
      description: >
        409 CONFLICT

        Shall be returned upon the following error: The operation cannot be 
        executed currently, due to a conflict with the state of the resource.

        Typically, this is due to the fact that the resource is in an
        incompatible  state, or that another change state operation is ongoing.

        The response body shall contain a ProblemDetails structure, in which
        the  "detail" attribute shall convey more information about the error.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    subscriptions.post.201:
      description: >
        201 CREATED

        Shall be returned when the subscription has been created  successfully.

        The response body shall contain a representation of the  created
        "Individual subscription" resource.

        The HTTP response shall include a "Location" HTTP header  that points to
        the created "Individual subscription" resource.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Location:
          description: |
            The resource URI of the created "Individual subscription" resource.
          schema:
            type: string
            format: url
            minimum: 1
            maximum: 1
      content:
        application/json:
          schema:
            description: >
              This type represents a subscription related to notifications
              about  NFV-MANO configuration and information management changes
            type: object
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              filter:
                description: >
                  This type represents a subscription filter related to
                  notifications  about NFV-MANO configuration and information
                  management. 
                type: object
                properties:
                  manoEntitySubscriptionFilter:
                    description: >
                      This type represents subscription filter criteria to match
                      NFV-MANO functional  entities and their associated managed
                      objects. 
                    type: object
                    properties:
                      manoEntityId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      manoServiceIds:
                        description: "manoServiceIds\tIdentifierInManoEntity\t0..N\tIf present, match NFV-MANO  services with an instance identifier listed in this attribute.\nThe attributes \"manoServiceIds\" and \"manoServiceNames\" are alternatives  to reference to NFV-MANO services in a filter. They should not be used  together in the same filter instance, but one alternative should be chosen.\n"
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceNames:
                        description: >
                          If present, match NFV-MANO services with an NFV-MANO
                          service name listed  in this attribute.

                          The attributes "manoServiceIds" and "manoServiceNames"
                          are alternatives  to reference to NFV-MANO services in
                          a filter. They should not be used  together in the
                          same filter instance, but one alternative should be
                          chosen.
                        type: array
                        items:
                          type: string
                      manoServiceInterfaceIds:
                        description: >
                          If present, match NFV-MANO functional entity produced
                          interfaces with an  instance identifier listed in this
                          attribute.

                          The attributes "manoServiceInterfaceIds" and
                          "manoServiceInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity produced 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceInterfaceNames:
                        description: >
                          If present, match NFV-MANO functional entity produced
                          interfaces with an  instance Name listed in this
                          attribute.

                          The attributes "manoServiceInterfaceIds" and
                          "manoServiceInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity produced 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          type: string
                      consumedManoInterfaceIds:
                        description: >
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an  instance identifier listed in this
                          attribute.

                          The attributes "consumedManoInterfaceIds" and
                          "consumedManoInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity consumed 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                      consumedManoInterfaceNames:
                        description: >
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an  instance Name listed in this
                          attribute.

                          The attributes "consumedManoInterfaceIds" and
                          "consumedManoInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity consumed 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          type: string
                  notificationTypes:
                    description: "Match particular notification types. \nPermitted values:\n  - InformationChangedNotification\n  - ChangeStateNotification\n\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are  spelled exactly as the names of the notification types to facilitate  automated code generation systems.\n"
                    type: array
                    items:
                      type: string
                      enum:
                        - InformationChangedNotification
                        - ChangeStateNotification
              callbackUri:
                description: |
                  String formatted according to IETF RFC 3986.
                type: string
              _links:
                description: |
                  Links to resources related to this resource.
                type: object
                properties:
                  self:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                required:
                  - self
            required:
              - id
              - callbackUri
              - _links
    subscriptions.post.303:
      description: >
        303 SEE OTHER

        SShall be returned when a subscription with the same  callbackURI and
        the same filter already exists and the  policy of NFV-MANO functional
        entity is to not create  redundant subscriptions.

        The HTTP response shall include a "Location" HTTP header  that contains
        the resource URI of the existing "Individual  subscription" resource.

        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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Location:
          description: |
            The resource URI of the created "Individual subscription" resource.
          schema:
            type: string
            format: url
            minimum: 1
            maximum: 1
    subscriptions.post.422:
      description: >
        422 Unprocessable Entity

        Shall be returned upon the following error: The content type of the
        payload body is supported and the payload body of a request contains
        syntactically correct data but the data cannot be processed.

        The general cause for this error and its handling is specified in clause
        6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the
        response body.

        Specifically in case of this resource, the response code 422 shall also
        be returned if the API producer has tested the Notification endpoint as
        described in clause 5.5.6.3.2 and the test has failed.

        In this case, the "detail" attribute in the "ProblemDetails" structure
        shall convey more information about the error.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    subscriptions.get.200:
      description: >
        200 OK

        Shall be returned when the list of subscriptions has been queried 
        successfully.

        The response body shall contain in an array the representations of  all
        active subscriptions of the functional block that invokes the  method,
        i.e., zero or more representations of NFV-MANO configuration  and
        information management subscriptions as defined in clause 5.6.2.6.

        If the "filter" URI parameter was supplied in the request, the data in 
        the response body shall have been transformed according to the rules 
        specified in clause 5.2.2 of ETSI GS NFV-SOL 013.

        If the NFV-MANO functional entity supports alternative N°2 (paging) 
        according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
        inclusion of the Link HTTP header in this response shall follow the 
        provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
      headers:
        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
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Link:
          description: >
            Reference to other resources. Link HTTP header in this response 
            shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL
            013.
          schema:
            type: string
            minimum: 0
            maximum: 1
      content:
        application/json:
          schema:
            type: array
            items:
              description: >
                This type represents a subscription related to notifications
                about  NFV-MANO configuration and information management changes
              type: object
              properties:
                id:
                  description: |
                    An identifier with the intention of being globally unique.
                  type: string
                filter:
                  description: >
                    This type represents a subscription filter related to
                    notifications  about NFV-MANO configuration and information
                    management. 
                  type: object
                  properties:
                    manoEntitySubscriptionFilter:
                      description: >
                        This type represents subscription filter criteria to
                        match NFV-MANO functional  entities and their associated
                        managed objects. 
                      type: object
                      properties:
                        manoEntityId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        manoServiceIds:
                          description: "manoServiceIds\tIdentifierInManoEntity\t0..N\tIf present, match NFV-MANO  services with an instance identifier listed in this attribute.\nThe attributes \"manoServiceIds\" and \"manoServiceNames\" are alternatives  to reference to NFV-MANO services in a filter. They should not be used  together in the same filter instance, but one alternative should be chosen.\n"
                          type: array
                          items:
                            description: >
                              An identifier that is unique for the respective
                              type within a NFV-MANO functional entity, but that
                              need not be globally unique. Representation:
                              string of variable length..
                            type: string
                        manoServiceNames:
                          description: >
                            If present, match NFV-MANO services with an NFV-MANO
                            service name listed  in this attribute.

                            The attributes "manoServiceIds" and
                            "manoServiceNames" are alternatives  to reference to
                            NFV-MANO services in a filter. They should not be
                            used  together in the same filter instance, but one
                            alternative should be chosen.
                          type: array
                          items:
                            type: string
                        manoServiceInterfaceIds:
                          description: >
                            If present, match NFV-MANO functional entity
                            produced interfaces with an  instance identifier
                            listed in this attribute.

                            The attributes "manoServiceInterfaceIds" and
                            "manoServiceInterfaceNames"  are alternatives to
                            reference to NFV-MANO functional entity produced 
                            interfaces in a filter. They should not be used both
                            in the same filter  instance, but one alternative
                            should be chosen.
                          type: array
                          items:
                            description: >
                              An identifier that is unique for the respective
                              type within a NFV-MANO functional entity, but that
                              need not be globally unique. Representation:
                              string of variable length..
                            type: string
                        manoServiceInterfaceNames:
                          description: >
                            If present, match NFV-MANO functional entity
                            produced interfaces with an  instance Name listed in
                            this attribute.

                            The attributes "manoServiceInterfaceIds" and
                            "manoServiceInterfaceNames"  are alternatives to
                            reference to NFV-MANO functional entity produced 
                            interfaces in a filter. They should not be used both
                            in the same filter  instance, but one alternative
                            should be chosen.
                          type: array
                          items:
                            type: string
                        consumedManoInterfaceIds:
                          description: >
                            If present, match NFV-MANO functional entity
                            consumed interfaces with an  instance identifier
                            listed in this attribute.

                            The attributes "consumedManoInterfaceIds" and
                            "consumedManoInterfaceNames"  are alternatives to
                            reference to NFV-MANO functional entity consumed 
                            interfaces in a filter. They should not be used both
                            in the same filter  instance, but one alternative
                            should be chosen.
                          type: array
                          items:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                        consumedManoInterfaceNames:
                          description: >
                            If present, match NFV-MANO functional entity
                            consumed interfaces with an  instance Name listed in
                            this attribute.

                            The attributes "consumedManoInterfaceIds" and
                            "consumedManoInterfaceNames"  are alternatives to
                            reference to NFV-MANO functional entity consumed 
                            interfaces in a filter. They should not be used both
                            in the same filter  instance, but one alternative
                            should be chosen.
                          type: array
                          items:
                            type: string
                    notificationTypes:
                      description: "Match particular notification types. \nPermitted values:\n  - InformationChangedNotification\n  - ChangeStateNotification\n\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are  spelled exactly as the names of the notification types to facilitate  automated code generation systems.\n"
                      type: array
                      items:
                        type: string
                        enum:
                          - InformationChangedNotification
                          - ChangeStateNotification
                callbackUri:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
                _links:
                  description: |
                    Links to resources related to this resource.
                  type: object
                  properties:
                    self:
                      description: >
                        This type represents a link to a resource using an
                        absolute URI.
                      type: object
                      required:
                        - href
                      properties:
                        href:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                  required:
                    - self
              required:
                - id
                - callbackUri
                - _links
    subscriptions.get.400:
      description: |
        400 BAD REQUEST
        Shall be returned upon the following errors: 
          - Invalid attribute-based filtering expression.
            The response body shall contain a ProblemDetails structure, in which 
            the "detail" attribute should convey more information about the error.
          - Response too big.
            If the NFV-MANO functional entity supports alternative N°1 (error) 
            according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
            this error response shall follow the provisions in clause 5.4.2.2 of 
            ETSI GS NFV-SOL 013.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    subscription.get.200:
      description: >
        200 OK

        Shall be returned when information about an individual subscription  has
        been read successfully.

        The response body shall contain a representation of the "Individual 
        subscription" resource.
            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.
          schema:
            type: string
        Version:
          description: >
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              This type represents a subscription related to notifications
              about  NFV-MANO configuration and information management changes
            type: object
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              filter:
                description: >
                  This type represents a subscription filter related to
                  notifications  about NFV-MANO configuration and information
                  management. 
                type: object
                properties:
                  manoEntitySubscriptionFilter:
                    description: >
                      This type represents subscription filter criteria to match
                      NFV-MANO functional  entities and their associated managed
                      objects. 
                    type: object
                    properties:
                      manoEntityId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      manoServiceIds:
                        description: "manoServiceIds\tIdentifierInManoEntity\t0..N\tIf present, match NFV-MANO  services with an instance identifier listed in this attribute.\nThe attributes \"manoServiceIds\" and \"manoServiceNames\" are alternatives  to reference to NFV-MANO services in a filter. They should not be used  together in the same filter instance, but one alternative should be chosen.\n"
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceNames:
                        description: >
                          If present, match NFV-MANO services with an NFV-MANO
                          service name listed  in this attribute.

                          The attributes "manoServiceIds" and "manoServiceNames"
                          are alternatives  to reference to NFV-MANO services in
                          a filter. They should not be used  together in the
                          same filter instance, but one alternative should be
                          chosen.
                        type: array
                        items:
                          type: string
                      manoServiceInterfaceIds:
                        description: >
                          If present, match NFV-MANO functional entity produced
                          interfaces with an  instance identifier listed in this
                          attribute.

                          The attributes "manoServiceInterfaceIds" and
                          "manoServiceInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity produced 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceInterfaceNames:
                        description: >
                          If present, match NFV-MANO functional entity produced
                          interfaces with an  instance Name listed in this
                          attribute.

                          The attributes "manoServiceInterfaceIds" and
                          "manoServiceInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity produced 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          type: string
                      consumedManoInterfaceIds:
                        description: >
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an  instance identifier listed in this
                          attribute.

                          The attributes "consumedManoInterfaceIds" and
                          "consumedManoInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity consumed 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                      consumedManoInterfaceNames:
                        description: >
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an  instance Name listed in this
                          attribute.

                          The attributes "consumedManoInterfaceIds" and
                          "consumedManoInterfaceNames"  are alternatives to
                          reference to NFV-MANO functional entity consumed 
                          interfaces in a filter. They should not be used both
                          in the same filter  instance, but one alternative
                          should be chosen.
                        type: array
                        items:
                          type: string
                  notificationTypes:
                    description: "Match particular notification types. \nPermitted values:\n  - InformationChangedNotification\n  - ChangeStateNotification\n\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are  spelled exactly as the names of the notification types to facilitate  automated code generation systems.\n"
                    type: array
                    items:
                      type: string
                      enum:
                        - InformationChangedNotification
                        - ChangeStateNotification
              callbackUri:
                description: |
                  String formatted according to IETF RFC 3986.
                type: string
              _links:
                description: |
                  Links to resources related to this resource.
                type: object
                properties:
                  self:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                required:
                  - self
            required:
              - id
              - callbackUri
              - _links
    subscription.delete.204:
      description: >
        204 NO CONTENT

        Shall be returned when the "Individual subscription" resource  has been
        deleted successfully.

        The response body shall be empty.
      headers:
        WWW-Authenticate:
          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
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
    change_state_ops.get.200:
      description: >
        200 OK

        Shall be returned when status information for zero or more  "change
        state operation occurrences" has been queried successfully.

        The response body shall contain in an array the status information 
        about zero or more "Individual change state operation occurrences",  as
        defined in clause 5.6.2.9.

        If the “filter" URI parameter or one of the "all_fields", "fields"  (if
        supported), "exclude_fields" (if supported) or "exclude_default"  URI
        parameters was supplied in the request, the data in the response  body
        shall have been transformed according to the rules specified in  clauses
        5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013, respectively.

        If the NFV-MANO functional entity supports alternative N°2 (paging) 
        according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
        inclusion of the Link HTTP header in this response shall follow the 
        provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
      headers:
        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
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Link:
          description: >
            Reference to other resources. Link HTTP header in this response 
            shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL
            013.
          schema:
            type: string
            minimum: 0
            maximum: 1
      content:
        application/json:
          schema:
            type: array
            items:
              description: |
                This type represents a Change state operation occurrence. 
              type: object
              properties:
                id:
                  description: |
                    An identifier with the intention of being globally unique.
                  type: string
                operationState:
                  description: "The enumeration ChangeStateOpOccStateEnumType defines permitted values for the change state operation. It shall comply with the provisions :\n  - PROCESSING\tThe change state operation is currently in execution.\n  - COMPLETED\tThe change state operation has been completed successfully.\n  - FAILED\tThe change state operation has failed.\n"
                  type: string
                  enum:
                    - PROCESSING
                    - COMPLETED
                    - FAILED
                stateEnteredTime:
                  description: >
                    Date-time stamp. Representation: String formatted according
                    to IETF RFC 3339.
                  type: string
                  format: date-time
                startTime:
                  description: >
                    Date-time stamp. Representation: String formatted according
                    to IETF RFC 3339.
                  type: string
                  format: date-time
                managedObjectRef:
                  description: >
                    This type represents the identifier to reference a managed
                    object of a  particular type. 
                  type: object
                  properties:
                    type:
                      description: >
                        Indicates the type of managed object. Permitted values:
                          - MANO_ENTITY
                          - MANO_SERVICE
                          - MANO_SERVICE_IF
                          - CONSUMED_MANO_IF
                          - MANO_ENTITY_COMPONENT

                        The "MANO_ENTITY COMPONENT" is only applicable if
                        attribute "manoEntityComponents" in "ManoEntity" is
                        supported by the API producer.
                      type: string
                      enum:
                        - MANO_ENTITY
                        - MANO_SERVICE
                        - MANO_SERVICE_IF
                        - CONSUMED_MANO_IF
                        - MANO_ENTITY_COMPONENT
                    objectId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    subObjectId:
                      description: >
                        An identifier that is unique for the respective type
                        within a NFV-MANO functional entity, but that need not
                        be globally unique. Representation: string of variable
                        length..
                      type: string
                  required:
                    - type
                    - objectId
                changeOperationalStateRequest:
                  description: "The enumeration ChangeOperationalStateEnumType defines permitted values  for the change state operation.  The ChangeOperationalStateEnumType shall comply with the provisions:\n  - START\tTo start the managed entity.\n  - STOP\tTo stop the managed entity.\n  - RESTART\tTo stop and start again the managed entity.\n"
                  type: string
                  enum:
                    - START
                    - STOP
                    - RESTART
                changeAdministrativeStateRequest:
                  description: "The enumeration ChangeAdministrativeStateEnumType defines permitted values  for the change of administrative state operation.  The ChangeAdministrativeStateEnumType shall comply with the provisions:\n  - LOCK\tTo lock the managed entity.\n  - UNLOCK\tTo unlock the managed entity.\n"
                  type: string
                  enum:
                    - LOCK
                    - UNLOCK
                operationParams:
                  description: >
                    Input parameters of the change state operation. This
                    attribute shall be  formatted according to the request data
                    type of the related change state  operation. 

                    The following mapping between operationType and the data
                    type of this  attribute shall apply:
                      - CHANGE_STATE: ChangeStateRequest
                      
                    This attribute shall be present if this data type is
                    returned in a response  to reading an individual resource,
                    and may be present according to the chosen  attribute
                    selector parameter if this data type is returned in a
                    response to  a query of a container resource.
              required:
                - id
                - operationState
                - stateEnteredTime
                - startTime
                - managedObjectRef
    change_state_ops.get.400:
      description: |
        400 BAD REQUEST
        Shall be returned upon the following errors: 
          - Invalid attribute-based filtering expression.
            The response body shall contain a ProblemDetails structure, in which 
            the "detail" attribute should convey more information about the error.
          - Invalid attribute selector.
            The response body shall contain a ProblemDetails structure, in which 
            the "detail" attribute should convey more information about the error.
          - Response too big.
            If the NFV-MANO functional entity supports alternative N°1 (error) 
            according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
            this error response shall follow the provisions in clause 5.4.2.2 of 
            ETSI GS NFV-SOL 013.
            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.
          schema:
            type: string
        Version:
          description: >
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    change_state_op.get.200:
      description: >
        200 OK

        Shall be returned when information about an "Individual change  state
        operation occurrence" resource has been read successfully.

        The response body shall contain status information about a change  state
        operation occurrence, as defined in clause 5.6.2.9.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: |
              This type represents a Change state operation occurrence. 
            type: object
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              operationState:
                description: "The enumeration ChangeStateOpOccStateEnumType defines permitted values for the change state operation. It shall comply with the provisions :\n  - PROCESSING\tThe change state operation is currently in execution.\n  - COMPLETED\tThe change state operation has been completed successfully.\n  - FAILED\tThe change state operation has failed.\n"
                type: string
                enum:
                  - PROCESSING
                  - COMPLETED
                  - FAILED
              stateEnteredTime:
                description: >
                  Date-time stamp. Representation: String formatted according to
                  IETF RFC 3339.
                type: string
                format: date-time
              startTime:
                description: >
                  Date-time stamp. Representation: String formatted according to
                  IETF RFC 3339.
                type: string
                format: date-time
              managedObjectRef:
                description: >
                  This type represents the identifier to reference a managed
                  object of a  particular type. 
                type: object
                properties:
                  type:
                    description: >
                      Indicates the type of managed object. Permitted values:
                        - MANO_ENTITY
                        - MANO_SERVICE
                        - MANO_SERVICE_IF
                        - CONSUMED_MANO_IF
                        - MANO_ENTITY_COMPONENT

                      The "MANO_ENTITY COMPONENT" is only applicable if
                      attribute "manoEntityComponents" in "ManoEntity" is
                      supported by the API producer.
                    type: string
                    enum:
                      - MANO_ENTITY
                      - MANO_SERVICE
                      - MANO_SERVICE_IF
                      - CONSUMED_MANO_IF
                      - MANO_ENTITY_COMPONENT
                  objectId:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  subObjectId:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                required:
                  - type
                  - objectId
              changeOperationalStateRequest:
                description: "The enumeration ChangeOperationalStateEnumType defines permitted values  for the change state operation.  The ChangeOperationalStateEnumType shall comply with the provisions:\n  - START\tTo start the managed entity.\n  - STOP\tTo stop the managed entity.\n  - RESTART\tTo stop and start again the managed entity.\n"
                type: string
                enum:
                  - START
                  - STOP
                  - RESTART
              changeAdministrativeStateRequest:
                description: "The enumeration ChangeAdministrativeStateEnumType defines permitted values  for the change of administrative state operation.  The ChangeAdministrativeStateEnumType shall comply with the provisions:\n  - LOCK\tTo lock the managed entity.\n  - UNLOCK\tTo unlock the managed entity.\n"
                type: string
                enum:
                  - LOCK
                  - UNLOCK
              operationParams:
                description: >
                  Input parameters of the change state operation. This attribute
                  shall be  formatted according to the request data type of the
                  related change state  operation. 

                  The following mapping between operationType and the data type
                  of this  attribute shall apply:
                    - CHANGE_STATE: ChangeStateRequest
                    
                  This attribute shall be present if this data type is returned
                  in a response  to reading an individual resource, and may be
                  present according to the chosen  attribute selector parameter
                  if this data type is returned in a response to  a query of a
                  container resource.
            required:
              - id
              - operationState
              - stateEnteredTime
              - startTime
              - managedObjectRef
    peer_entities.post.201:
      description: >
        201 CREATED

        Shall be returned when a new "Individual peer entity" resource  has been
        created successfully.

        The response body shall contain a representation of the created 
        resource with regards to a peer entity, as defined in  clause 5.6.2.15.

        The HTTP response shall include a “Location” HTTP header that  points to
        the created "Individual peer entity" resource.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Location:
          description: |
            The resource URI of the created "Individual peer entity" resource.
          schema:
            type: string
            format: url
            minimum: 1
            maximum: 1
      content:
        application/json:
          schema:
            description: |
              This type represents an individual peer entity. 
            type: object
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              peerEntityId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              name:
                description: |
                  Human-readable name of the peer functional entity.
                  This attribute can be modified with the PATCH method.
                type: string
              type:
                description: "The enumeration PeerEntityEnumType defines the permitted values  to represent peer functional entities. it shall complains with  the provisions :  - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t  The peer functional entity is a VIM. - WIM\t  The peer functional entity is a WIM. - EM\t  The peer functional entity is an EM. - OSS\t  The peer functional entity is an OSS/BSS.\n"
                type: string
                enum:
                  - NFVO
                  - VNFM
                  - VIM
                  - WIM
                  - EM
                  - OSS
              description:
                description: |
                  Human-readable description of the peer functional entity.
                  This attribute can be modified with the PATCH method.
                type: string
              consumedManoInterfaces:
                description: >
                  Information of the interface consumed by the NFV-MANO
                  functional entity  from the peer functional entity.

                  This attribute can be modified with the PATCH method.

                  The keys of the map, each of which identifies information
                  about a particular consumed NFV-MANO interface, are managed by
                  the API consumer and referenced from other data structures via
                  the "consumedManoInterfaceIds" attribute.
                type: object
                additionalProperties:
                  description: >
                    This type represents an interface consumed by the producer
                    NFV MANO  functional entity from another peer functional
                    entity. 
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    name:
                      description: |
                        Human-readable name of the NFV-MANO interface.
                      type: string
                    type:
                      description: >
                        Type of the NFV-MANO service interface consumed by the
                        NFV-MANO  functional entity. Valid values are defined in
                        clause 5.6.4.3.
                      type: string
                    standardVersion:
                      description: |
                        A version.
                      type: string
                    apiVersion:
                      description: |
                        A version.
                      type: string
                    apiEndpoint:
                      description: >
                        Consumable API endpoint of the interface. It provides
                        the information relevant about the protocol, host and
                        port,  and path where the interface API can be accessed.
                      type: object
                      properties:
                        apiRoot:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                        apiName:
                          description: >
                            Indicates the interface name in an abbreviated form.
                            Shall be present  for ETSI NFV specified RESTful
                            NFV-MANO APIs. The {apiName} of each  interface is
                            defined in the standard the interface is compliant
                            to  (see also clause 4.1 of ETSI GS NFV-SOL 013).
                            May be present otherwise.
                          type: string
                        apiMajorVersion:
                          description: >
                            Indicates the current major version of the API.
                            Shall be present for  ETSI NFV specified RESTful
                            NFV-MANO APIs. The major version is defined  in the
                            standard the interface is compliant to (see also
                            clause 4.1  of ETSI GS NFV-SOL 013). May be present
                            otherwise.
                          type: string
                        apiUri:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                      required:
                        - apiUri
                    securityInfo:
                      description: >
                        This type represents security related information for
                        accessing an NFV-MANO  service interface produced by an
                        NFV-MANO functional entity.
                      type: object
                      required:
                        - authType
                        - oauthServerInfo
                      properties:
                        authType:
                          description: >
                            Type of API request authorization to be used by the
                            API consumer accessing  the API.

                            The support of authorization methods for the API
                            consumer is specified in  clause 8.3.6 of ETSI GS
                            NFV-SOL 013.

                            Permitted values: - TLS_TUNNEL: Using TLS tunnel, as
                            defined by TLS 1.2 in IETF RFC 5246. - OAUTH2: Using
                            access token, as defined by the OAuth 2.0
                            specification  in IETF RFC 6749. 
                          type: array
                          items:
                            type: string
                            enum:
                              - TLS_TUNNEL
                              - OAUTH2
                          minItems: 1
                        oauthServerInfo:
                          description: >
                            OAuth 2.0 authorization server information and
                            configuration.
                          type: object
                          properties:
                            dynamicDiscovery:
                              description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                              type: object
                              required:
                                - webFingerHost
                              properties:
                                webFingerHost:
                                  description: >
                                    Server where the WebFinger service is
                                    hosted. When used, the request to  the
                                    WebFinger resource shall conform as
                                    specified in clause 5.1.3 of  ETSI GS
                                    NFV-SEC 022.
                                  type: string
                                  format: uri
                            providedConfiguration:
                              description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                              type: object
                              required:
                                - authServerId
                              properties:
                                authServerId:
                                  description: >
                                    Authorization server identifier as defined
                                    in ETSI GS NFV-SEC 022.
                                  type: string
                                  format: uri
                            tlsCipherSuites:
                              description: >
                                List of cipher suites that shall be declared as
                                supported by the API consumer when  performing
                                the SSL or TLS negotiation with the
                                authorization server. Valid values  of cipher
                                suites are defined in IETF RFC 8447.
                              type: array
                              items:
                                type: string
                                minItems: 1
                        tlsTunnelInfo:
                          description: >
                            Information and configuration related to the use of
                            TLS tunnel. Shall be  present if authType contains
                            "TLS_TUNNEL".
                          type: object
                          properties:
                            tlsTunnelCipherSuites:
                              description: >
                                List of cipher suites that shall be declared as
                                supported by the API  consumer when performing
                                the SSL or TLS negotiation with the API
                                producer.  Valid values of cipher suites are
                                defined in IETF RFC 8447.
                              type: array
                              items:
                                type: string
                                minItems: 1
                  required:
                    - id
                    - name
                    - type
                    - standardVersion
                    - apiVersion
                    - apiEndpoint
              peerEntityState:
                description: >
                  State of the peer functional entity as provided by the API
                  consumer when  creating the resource or when updating it with
                  the PATCH method.
                type: object
                properties:
                  operationalState:
                    description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                    type: string
                    enum:
                      - STARTED
                      - STOPPED
                      - STOPPING
                      - STARTING
                      - RESTARTING
                  administrativeState:
                    description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                    type: string
                    enum:
                      - LOCKED
                      - UNLOCKED
                      - LOCKING
                required:
                  - operationalState
                  - administrativeState
            required:
              - id
              - peerEntityId
              - name
              - type
              - peerEntityState
    peer_entities.get.200:
      description: >
        200 OK

        Shall be returned when information about zero or more peer  entities has
        been queried successfully.

        The response body shall contain in an array the resource 
        representations of zero or more peer entities, as defined  in clause
        5.6.2.15.

        If the “filter" URI parameter or one of the "all_fields", "fields"  (if
        supported), "exclude_fields" (if supported) or "exclude_default"  URI
        parameters was supplied in the request, the data in the response  body
        shall have been transformed according to the rules specified in  clauses
        5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013, respectively.

        If the NFV-MANO functional entity supports alternative N°2 (paging) 
        according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
        inclusion of the Link HTTP header in this response shall follow the 
        provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
      headers:
        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
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Link:
          description: >
            Reference to other resources. Link HTTP header in this response 
            shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL
            013.
          schema:
            type: string
            minimum: 0
            maximum: 1
      content:
        application/json:
          schema:
            type: array
            items:
              description: |
                This type represents an individual peer entity. 
              type: object
              properties:
                id:
                  description: |
                    An identifier with the intention of being globally unique.
                  type: string
                peerEntityId:
                  description: |
                    An identifier with the intention of being globally unique.
                  type: string
                name:
                  description: |
                    Human-readable name of the peer functional entity.
                    This attribute can be modified with the PATCH method.
                  type: string
                type:
                  description: "The enumeration PeerEntityEnumType defines the permitted values  to represent peer functional entities. it shall complains with  the provisions :  - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t  The peer functional entity is a VIM. - WIM\t  The peer functional entity is a WIM. - EM\t  The peer functional entity is an EM. - OSS\t  The peer functional entity is an OSS/BSS.\n"
                  type: string
                  enum:
                    - NFVO
                    - VNFM
                    - VIM
                    - WIM
                    - EM
                    - OSS
                description:
                  description: |
                    Human-readable description of the peer functional entity.
                    This attribute can be modified with the PATCH method.
                  type: string
                consumedManoInterfaces:
                  description: >
                    Information of the interface consumed by the NFV-MANO
                    functional entity  from the peer functional entity.

                    This attribute can be modified with the PATCH method.

                    The keys of the map, each of which identifies information
                    about a particular consumed NFV-MANO interface, are managed
                    by the API consumer and referenced from other data
                    structures via the "consumedManoInterfaceIds" attribute.
                  type: object
                  additionalProperties:
                    description: >
                      This type represents an interface consumed by the producer
                      NFV MANO  functional entity from another peer functional
                      entity. 
                    type: object
                    properties:
                      id:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      name:
                        description: |
                          Human-readable name of the NFV-MANO interface.
                        type: string
                      type:
                        description: >
                          Type of the NFV-MANO service interface consumed by the
                          NFV-MANO  functional entity. Valid values are defined
                          in clause 5.6.4.3.
                        type: string
                      standardVersion:
                        description: |
                          A version.
                        type: string
                      apiVersion:
                        description: |
                          A version.
                        type: string
                      apiEndpoint:
                        description: >
                          Consumable API endpoint of the interface. It provides
                          the information relevant about the protocol, host and
                          port,  and path where the interface API can be
                          accessed.
                        type: object
                        properties:
                          apiRoot:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                          apiName:
                            description: >
                              Indicates the interface name in an abbreviated
                              form. Shall be present  for ETSI NFV specified
                              RESTful NFV-MANO APIs. The {apiName} of each 
                              interface is defined in the standard the interface
                              is compliant to  (see also clause 4.1 of ETSI GS
                              NFV-SOL 013). May be present otherwise.
                            type: string
                          apiMajorVersion:
                            description: >
                              Indicates the current major version of the API.
                              Shall be present for  ETSI NFV specified RESTful
                              NFV-MANO APIs. The major version is defined  in
                              the standard the interface is compliant to (see
                              also clause 4.1  of ETSI GS NFV-SOL 013). May be
                              present otherwise.
                            type: string
                          apiUri:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                        required:
                          - apiUri
                      securityInfo:
                        description: >
                          This type represents security related information for
                          accessing an NFV-MANO  service interface produced by
                          an NFV-MANO functional entity.
                        type: object
                        required:
                          - authType
                          - oauthServerInfo
                        properties:
                          authType:
                            description: >
                              Type of API request authorization to be used by
                              the API consumer accessing  the API.

                              The support of authorization methods for the API
                              consumer is specified in  clause 8.3.6 of ETSI GS
                              NFV-SOL 013.

                              Permitted values: - TLS_TUNNEL: Using TLS tunnel,
                              as defined by TLS 1.2 in IETF RFC 5246. - OAUTH2:
                              Using access token, as defined by the OAuth 2.0
                              specification  in IETF RFC 6749. 
                            type: array
                            items:
                              type: string
                              enum:
                                - TLS_TUNNEL
                                - OAUTH2
                            minItems: 1
                          oauthServerInfo:
                            description: >
                              OAuth 2.0 authorization server information and
                              configuration.
                            type: object
                            properties:
                              dynamicDiscovery:
                                description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                type: object
                                required:
                                  - webFingerHost
                                properties:
                                  webFingerHost:
                                    description: >
                                      Server where the WebFinger service is
                                      hosted. When used, the request to  the
                                      WebFinger resource shall conform as
                                      specified in clause 5.1.3 of  ETSI GS
                                      NFV-SEC 022.
                                    type: string
                                    format: uri
                              providedConfiguration:
                                description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                                type: object
                                required:
                                  - authServerId
                                properties:
                                  authServerId:
                                    description: >
                                      Authorization server identifier as defined
                                      in ETSI GS NFV-SEC 022.
                                    type: string
                                    format: uri
                              tlsCipherSuites:
                                description: >
                                  List of cipher suites that shall be declared
                                  as supported by the API consumer when 
                                  performing the SSL or TLS negotiation with the
                                  authorization server. Valid values  of cipher
                                  suites are defined in IETF RFC 8447.
                                type: array
                                items:
                                  type: string
                                  minItems: 1
                          tlsTunnelInfo:
                            description: >
                              Information and configuration related to the use
                              of TLS tunnel. Shall be  present if authType
                              contains "TLS_TUNNEL".
                            type: object
                            properties:
                              tlsTunnelCipherSuites:
                                description: >
                                  List of cipher suites that shall be declared
                                  as supported by the API  consumer when
                                  performing the SSL or TLS negotiation with the
                                  API producer.  Valid values of cipher suites
                                  are defined in IETF RFC 8447.
                                type: array
                                items:
                                  type: string
                                  minItems: 1
                    required:
                      - id
                      - name
                      - type
                      - standardVersion
                      - apiVersion
                      - apiEndpoint
                peerEntityState:
                  description: >
                    State of the peer functional entity as provided by the API
                    consumer when  creating the resource or when updating it
                    with the PATCH method.
                  type: object
                  properties:
                    operationalState:
                      description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                      type: string
                      enum:
                        - STARTED
                        - STOPPED
                        - STOPPING
                        - STARTING
                        - RESTARTING
                    administrativeState:
                      description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                      type: string
                      enum:
                        - LOCKED
                        - UNLOCKED
                        - LOCKING
                  required:
                    - operationalState
                    - administrativeState
              required:
                - id
                - peerEntityId
                - name
                - type
                - peerEntityState
    peer_entities.get.400:
      description: |
        400 BAD REQUEST
        Shall be returned upon the following errors: 
          - Invalid attribute-based filtering expression.
            The response body shall contain a ProblemDetails structure, in which 
            the "detail" attribute should convey more information about the error.
          - Invalid attribute selector.
            The response body shall contain a ProblemDetails structure, in which 
            the "detail" attribute should convey more information about the error.
          - Response too big.
            If the NFV-MANO functional entity supports alternative N°1 (error) 
            according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, 
            this error response shall follow the provisions in clause 5.4.2.2 of 
            ETSI GS NFV-SOL 013.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    peer_entitie.get.200:
      description: >
        200 OK

        Shall be returned when information about an individual peer  functional
        entity has been read successfully.

        The response body shall contain a resource representation of  the peer
        functional entity, as defined in clause 5.6.2.15.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: |
              This type represents an individual peer entity. 
            type: object
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              peerEntityId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              name:
                description: |
                  Human-readable name of the peer functional entity.
                  This attribute can be modified with the PATCH method.
                type: string
              type:
                description: "The enumeration PeerEntityEnumType defines the permitted values  to represent peer functional entities. it shall complains with  the provisions :  - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t  The peer functional entity is a VIM. - WIM\t  The peer functional entity is a WIM. - EM\t  The peer functional entity is an EM. - OSS\t  The peer functional entity is an OSS/BSS.\n"
                type: string
                enum:
                  - NFVO
                  - VNFM
                  - VIM
                  - WIM
                  - EM
                  - OSS
              description:
                description: |
                  Human-readable description of the peer functional entity.
                  This attribute can be modified with the PATCH method.
                type: string
              consumedManoInterfaces:
                description: >
                  Information of the interface consumed by the NFV-MANO
                  functional entity  from the peer functional entity.

                  This attribute can be modified with the PATCH method.

                  The keys of the map, each of which identifies information
                  about a particular consumed NFV-MANO interface, are managed by
                  the API consumer and referenced from other data structures via
                  the "consumedManoInterfaceIds" attribute.
                type: object
                additionalProperties:
                  description: >
                    This type represents an interface consumed by the producer
                    NFV MANO  functional entity from another peer functional
                    entity. 
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    name:
                      description: |
                        Human-readable name of the NFV-MANO interface.
                      type: string
                    type:
                      description: >
                        Type of the NFV-MANO service interface consumed by the
                        NFV-MANO  functional entity. Valid values are defined in
                        clause 5.6.4.3.
                      type: string
                    standardVersion:
                      description: |
                        A version.
                      type: string
                    apiVersion:
                      description: |
                        A version.
                      type: string
                    apiEndpoint:
                      description: >
                        Consumable API endpoint of the interface. It provides
                        the information relevant about the protocol, host and
                        port,  and path where the interface API can be accessed.
                      type: object
                      properties:
                        apiRoot:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                        apiName:
                          description: >
                            Indicates the interface name in an abbreviated form.
                            Shall be present  for ETSI NFV specified RESTful
                            NFV-MANO APIs. The {apiName} of each  interface is
                            defined in the standard the interface is compliant
                            to  (see also clause 4.1 of ETSI GS NFV-SOL 013).
                            May be present otherwise.
                          type: string
                        apiMajorVersion:
                          description: >
                            Indicates the current major version of the API.
                            Shall be present for  ETSI NFV specified RESTful
                            NFV-MANO APIs. The major version is defined  in the
                            standard the interface is compliant to (see also
                            clause 4.1  of ETSI GS NFV-SOL 013). May be present
                            otherwise.
                          type: string
                        apiUri:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                      required:
                        - apiUri
                    securityInfo:
                      description: >
                        This type represents security related information for
                        accessing an NFV-MANO  service interface produced by an
                        NFV-MANO functional entity.
                      type: object
                      required:
                        - authType
                        - oauthServerInfo
                      properties:
                        authType:
                          description: >
                            Type of API request authorization to be used by the
                            API consumer accessing  the API.

                            The support of authorization methods for the API
                            consumer is specified in  clause 8.3.6 of ETSI GS
                            NFV-SOL 013.

                            Permitted values: - TLS_TUNNEL: Using TLS tunnel, as
                            defined by TLS 1.2 in IETF RFC 5246. - OAUTH2: Using
                            access token, as defined by the OAuth 2.0
                            specification  in IETF RFC 6749. 
                          type: array
                          items:
                            type: string
                            enum:
                              - TLS_TUNNEL
                              - OAUTH2
                          minItems: 1
                        oauthServerInfo:
                          description: >
                            OAuth 2.0 authorization server information and
                            configuration.
                          type: object
                          properties:
                            dynamicDiscovery:
                              description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                              type: object
                              required:
                                - webFingerHost
                              properties:
                                webFingerHost:
                                  description: >
                                    Server where the WebFinger service is
                                    hosted. When used, the request to  the
                                    WebFinger resource shall conform as
                                    specified in clause 5.1.3 of  ETSI GS
                                    NFV-SEC 022.
                                  type: string
                                  format: uri
                            providedConfiguration:
                              description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                              type: object
                              required:
                                - authServerId
                              properties:
                                authServerId:
                                  description: >
                                    Authorization server identifier as defined
                                    in ETSI GS NFV-SEC 022.
                                  type: string
                                  format: uri
                            tlsCipherSuites:
                              description: >
                                List of cipher suites that shall be declared as
                                supported by the API consumer when  performing
                                the SSL or TLS negotiation with the
                                authorization server. Valid values  of cipher
                                suites are defined in IETF RFC 8447.
                              type: array
                              items:
                                type: string
                                minItems: 1
                        tlsTunnelInfo:
                          description: >
                            Information and configuration related to the use of
                            TLS tunnel. Shall be  present if authType contains
                            "TLS_TUNNEL".
                          type: object
                          properties:
                            tlsTunnelCipherSuites:
                              description: >
                                List of cipher suites that shall be declared as
                                supported by the API  consumer when performing
                                the SSL or TLS negotiation with the API
                                producer.  Valid values of cipher suites are
                                defined in IETF RFC 8447.
                              type: array
                              items:
                                type: string
                                minItems: 1
                  required:
                    - id
                    - name
                    - type
                    - standardVersion
                    - apiVersion
                    - apiEndpoint
              peerEntityState:
                description: >
                  State of the peer functional entity as provided by the API
                  consumer when  creating the resource or when updating it with
                  the PATCH method.
                type: object
                properties:
                  operationalState:
                    description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                    type: string
                    enum:
                      - STARTED
                      - STOPPED
                      - STOPPING
                      - STARTING
                      - RESTARTING
                  administrativeState:
                    description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                    type: string
                    enum:
                      - LOCKED
                      - UNLOCKED
                      - LOCKING
                required:
                  - operationalState
                  - administrativeState
            required:
              - id
              - peerEntityId
              - name
              - type
              - peerEntityState
    peer_entitie.patch.200:
      description: >
        200 OK

        Shall be returned when the request has been accepted and completed.

        The response body shall contain a representation of the attribute 
        modifications for the "Individual peer entity" resource, as defined  in
        clause 5.6.2.17.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              This type represents attribute modifications that were performed
              on an  "Individual peer entity" resource. The attributes that can
              be included  consist of those requested to be modified explicitly
              in the  "PeerEntityConfigModificationRequest" data structure. If
              applicable,  additional attributes of the "PeerEntity" data
              structure that were  modified implicitly shall also be provided.
            type: object
            properties:
              name:
                description: >
                  If present, this attribute signals modifications of the "name"
                  attribute  in "PeerEntity", as defined in clause 5.6.2.15.
                type: string
              description:
                description: >
                  If present, this attribute signals modifications of the
                  "description"  attribute in "PeerEntity", as defined in clause
                  5.6.2.15.
                type: string
              consumedManoInterfaces:
                description: "If present, this attribute signals modifications of the \"consumedManoInterfaces\" attribute in \"PeerEntity\", as defined in  clause 5.6.2.15. \nNOTE:\tDue to the security sensitive information contained within the  attribute (refer to \"securityInfo\" within the \"ConsumedManoInterfaceInfo\"),  based on access control policies, the API consumer might have read only,  write only, read/write, or no access at all to the attribute’s value.  In case the API consumer is not allowed to read the value of the security  sensitive attribute, the attribute shall be omitted when the information  is to be provided in a response message.\n"
                type: object
                additionalProperties:
                  description: >
                    This type represents an interface consumed by the producer
                    NFV MANO  functional entity from another peer functional
                    entity. 
                  type: object
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    name:
                      description: |
                        Human-readable name of the NFV-MANO interface.
                      type: string
                    type:
                      description: >
                        Type of the NFV-MANO service interface consumed by the
                        NFV-MANO  functional entity. Valid values are defined in
                        clause 5.6.4.3.
                      type: string
                    standardVersion:
                      description: |
                        A version.
                      type: string
                    apiVersion:
                      description: |
                        A version.
                      type: string
                    apiEndpoint:
                      description: >
                        Consumable API endpoint of the interface. It provides
                        the information relevant about the protocol, host and
                        port,  and path where the interface API can be accessed.
                      type: object
                      properties:
                        apiRoot:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                        apiName:
                          description: >
                            Indicates the interface name in an abbreviated form.
                            Shall be present  for ETSI NFV specified RESTful
                            NFV-MANO APIs. The {apiName} of each  interface is
                            defined in the standard the interface is compliant
                            to  (see also clause 4.1 of ETSI GS NFV-SOL 013).
                            May be present otherwise.
                          type: string
                        apiMajorVersion:
                          description: >
                            Indicates the current major version of the API.
                            Shall be present for  ETSI NFV specified RESTful
                            NFV-MANO APIs. The major version is defined  in the
                            standard the interface is compliant to (see also
                            clause 4.1  of ETSI GS NFV-SOL 013). May be present
                            otherwise.
                          type: string
                        apiUri:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                      required:
                        - apiUri
                    securityInfo:
                      description: >
                        This type represents security related information for
                        accessing an NFV-MANO  service interface produced by an
                        NFV-MANO functional entity.
                      type: object
                      required:
                        - authType
                        - oauthServerInfo
                      properties:
                        authType:
                          description: >
                            Type of API request authorization to be used by the
                            API consumer accessing  the API.

                            The support of authorization methods for the API
                            consumer is specified in  clause 8.3.6 of ETSI GS
                            NFV-SOL 013.

                            Permitted values: - TLS_TUNNEL: Using TLS tunnel, as
                            defined by TLS 1.2 in IETF RFC 5246. - OAUTH2: Using
                            access token, as defined by the OAuth 2.0
                            specification  in IETF RFC 6749. 
                          type: array
                          items:
                            type: string
                            enum:
                              - TLS_TUNNEL
                              - OAUTH2
                          minItems: 1
                        oauthServerInfo:
                          description: >
                            OAuth 2.0 authorization server information and
                            configuration.
                          type: object
                          properties:
                            dynamicDiscovery:
                              description: "Configuration data used when performing dynamic discovery of the authorization  server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                              type: object
                              required:
                                - webFingerHost
                              properties:
                                webFingerHost:
                                  description: >
                                    Server where the WebFinger service is
                                    hosted. When used, the request to  the
                                    WebFinger resource shall conform as
                                    specified in clause 5.1.3 of  ETSI GS
                                    NFV-SEC 022.
                                  type: string
                                  format: uri
                            providedConfiguration:
                              description: "Configuration data used to setup the authorization server identifier. \nNOTE:\tProvided configuration of the OAuth 2.0 authorization server information  and configuration shall be supported, and dynamic configuration may be supported.\n"
                              type: object
                              required:
                                - authServerId
                              properties:
                                authServerId:
                                  description: >
                                    Authorization server identifier as defined
                                    in ETSI GS NFV-SEC 022.
                                  type: string
                                  format: uri
                            tlsCipherSuites:
                              description: >
                                List of cipher suites that shall be declared as
                                supported by the API consumer when  performing
                                the SSL or TLS negotiation with the
                                authorization server. Valid values  of cipher
                                suites are defined in IETF RFC 8447.
                              type: array
                              items:
                                type: string
                                minItems: 1
                        tlsTunnelInfo:
                          description: >
                            Information and configuration related to the use of
                            TLS tunnel. Shall be  present if authType contains
                            "TLS_TUNNEL".
                          type: object
                          properties:
                            tlsTunnelCipherSuites:
                              description: >
                                List of cipher suites that shall be declared as
                                supported by the API  consumer when performing
                                the SSL or TLS negotiation with the API
                                producer.  Valid values of cipher suites are
                                defined in IETF RFC 8447.
                              type: array
                              items:
                                type: string
                                minItems: 1
                  required:
                    - id
                    - name
                    - type
                    - standardVersion
                    - apiVersion
                    - apiEndpoint
              operationalState:
                description: "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n  - STARTED\tThe managed entity is operational.\n  - STOPPED\tThe managed entity is not operational.\n  - STOPPING\tThe managed entity is in the transition to stop.\n  - STARTING\tThe managed entity is in the transition to start and become operational.\n  - RESTARTING\tThe managed entity is in the transition to stop and start again.\n"
                type: string
                enum:
                  - STARTED
                  - STOPPED
                  - STOPPING
                  - STARTING
                  - RESTARTING
              administrativeState:
                description: "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n  - LOCKED\tThe managed entity is administratively prohibited to be used.\n  - UNLOCKED\tThe managed entity is administratively allowed to be used.\n  - LOCKING\tThe managed entity is in the transition to be locked.\n"
                type: string
                enum:
                  - LOCKED
                  - UNLOCKED
                  - LOCKING
    peer_entitie.patch.409:
      description: >
        409 CONFLICT.

        Shall be returned upon the following error: The operation cannot be 
        executed currently, due to a conflict with the state of the  "Individual
        peer entity" resource.

        Typically, this is due to the fact that another operation is ongoing.

        The response body shall contain a ProblemDetails structure, in which 
        the "detail" attribute should convey more information about the error.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    peer_entitie.patch.412:
      description: >
        412 PRECONDITION FAILED

        Shall be returned upon the following error: A precondition given in  an
        HTTP request header is not fulfilled.

        Typically, this is due to an ETag mismatch, indicating that the 
        resource was modified by another entity.

        The response body should contain a ProblemDetails structure, in which 
        the "detail" attribute should convey more information about the error.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    peer_entitie.delete.204:
      description: >
        204 NO CONTENT

        Shall be returned when the "Individual peer entity" resource  has been
        deleted 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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
    peer_entitie.delete.409:
      description: >
        409 CONFLICT.

        Shall be returned upon the following error: The operation cannot be 
        executed currently, due to a conflict with the state of the  "Individual
        peer entity" resource.

        Typically, this is due to the fact that another operation is ongoing.

        The response body shall contain a ProblemDetails structure, in which 
        the "detail" attribute should convey more information about the error.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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
    peer_entitie.delete.412:
      description: >
        412 PRECONDITION FAILED

        Shall be returned upon the following error: A precondition given in  an
        HTTP request header is not fulfilled.

        Typically, this is due to an ETag mismatch, indicating that the 
        resource was modified by another entity.

        The response body should contain a ProblemDetails structure, in which 
        the "detail" attribute should convey more information about the error.
      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.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], 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 [19] 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 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] 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

