Commit 144afcd2 authored by Giacomo Bernini's avatar Giacomo Bernini
Browse files

addressed comments from SOL WG review

parent 4daa16fd
Pipeline #13389 passed with stage
in 0 seconds
...@@ -735,6 +735,8 @@ components: ...@@ -735,6 +735,8 @@ components:
PeerEntity: PeerEntity:
description: > description: >
This type represents an individual peer entity. This type represents an individual peer entity.
* NOTE: ETSI GS NFV-IFA 031 defines an additional attribute named "apiDiscoveryEndpoint" in the
PeerManoEntity. The modelling of this attribute is not specified in the present document version.
* NOTE 1: The value of the "peerEntityId" attribute is the same as the value of the "id" attribute in the * NOTE 1: The value of the "peerEntityId" attribute is the same as the value of the "id" attribute in the
"ManoEntity" of the corresponding NFV-MANO functional entity that acts as peer entity, and shall "ManoEntity" of the corresponding NFV-MANO functional entity that acts as peer entity, and shall
follow the uniqueness requirements set out in clause 5.6.2.2 for the "id" attribute. follow the uniqueness requirements set out in clause 5.6.2.2 for the "id" attribute.
...@@ -1567,6 +1569,7 @@ components: ...@@ -1567,6 +1569,7 @@ components:
Permitted values: Permitted values:
- TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246. - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.
- TLS_TUNNEL_13: Using TLS tunnel, as defined by TLS 1.3 in IETF RFC 8446.
- OAUTH2: Using access token, as defined by the OAuth 2.0 specification - OAUTH2: Using access token, as defined by the OAuth 2.0 specification
in IETF RFC 6749. in IETF RFC 6749.
type: array type: array
......
...@@ -20,7 +20,7 @@ info: ...@@ -20,7 +20,7 @@ info:
externalDocs: externalDocs:
description: ETSI GS NFV-SOL 009 V3.7.1 description: ETSI GS NFV-SOL 009 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.07.01_60/gs_NFV-SOL009v0307601p.pdf url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.07.01_60/gs_NFV-SOL009v030701p.pdf
servers: servers:
- url: http://127.0.0.1/nfvmanofm/v1 - url: http://127.0.0.1/nfvmanofm/v1
......
...@@ -20,7 +20,7 @@ info: ...@@ -20,7 +20,7 @@ info:
externalDocs: externalDocs:
description: ETSI GS NFV-SOL 009 V3.7.1 description: ETSI GS NFV-SOL 009 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.07.01_60/gs_NFV-SOL009v0307601p.pdf url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.07.01_60/gs_NFV-SOL009v030701p.pdf
servers: servers:
- url: http://127.0.0.1/callback/v1 - url: http://127.0.0.1/callback/v1
......
...@@ -688,10 +688,10 @@ components: ...@@ -688,10 +688,10 @@ components:
Subscriptions.Post.422: Subscriptions.Post.422:
description: > description: >
422 UNPROCESSABLE ENTITY 422 UNPROCESSABLE CONTENT
Shall be returned upon the following error: The content type Shall be returned upon the following error: The content type
of the payload body is supported and the payload body of a request of the message content is supported and the message content of a request
contains syntactically correct data but the data cannot be processed. contains syntactically correct data but the data cannot be processed.
The general cause for this error and its handling is specified in The general cause for this error and its handling is specified in
......
...@@ -20,8 +20,8 @@ info: ...@@ -20,8 +20,8 @@ info:
version: 2.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1 version: 2.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1
externalDocs: externalDocs:
description: ETSI GS NFV-SOL 009 V3.6.1 description: ETSI GS NFV-SOL 009 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.06.01_60/gs_NFV-SOL009v030601p.pdf url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.07.01_60/gs_NFV-SOL009v030701p.pdf
servers: servers:
- url: http://127.0.0.1/nfvmanopm/v2 - url: http://127.0.0.1/nfvmanopm/v2
...@@ -434,10 +434,10 @@ components: ...@@ -434,10 +434,10 @@ components:
$ref: "./components/NFVManoPerformanceManagement_def.yaml#/components/schemas/PmJob" $ref: "./components/NFVManoPerformanceManagement_def.yaml#/components/schemas/PmJob"
pm_jobs.Post.422: pm_jobs.Post.422:
description: > description: >
422 Unprocessable Entity 422 Unprocessable Content
Shall be returned upon the following error: The content type Shall be returned upon the following error: The content type
of the payload body is supported and the payload body of a request of the message content is supported and the message content of a request
contains syntactically correct data but the data cannot be processed. contains syntactically correct data but the data cannot be processed.
The general cause for this error and its handling is specified in The general cause for this error and its handling is specified in
......
...@@ -74,7 +74,7 @@ components: ...@@ -74,7 +74,7 @@ components:
"ProblemDetails" structure to be returned. "ProblemDetails" structure to be returned.
If the request is malformed or syntactically incorrect (e.g. if the request URI contains incorrect 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), query parameters or the message content contains a syntactically incorrect data structure),
the API producer shall respond with this response code. The "ProblemDetails" structure shall be provided, 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. and should include in the "detail" attribute more information about the source of the problem.
...@@ -206,7 +206,7 @@ components: ...@@ -206,7 +206,7 @@ components:
This response code is not appropriate in case the resource addressed by the URI is a container resource 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 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 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. contains a 200 OK response code and a message content with an empty array.
headers: headers:
Content-Type: Content-Type:
description: The MIME type of the body of the response. description: The MIME type of the body of the response.
...@@ -375,7 +375,7 @@ components: ...@@ -375,7 +375,7 @@ components:
description: > description: >
413 PAYLOAD TOO LARGE 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, If the message content 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 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. of the "Retry-After" HTTP header and for closing the connection. The "ProblemDetails" structure may be omitted.
headers: headers:
...@@ -474,9 +474,9 @@ components: ...@@ -474,9 +474,9 @@ components:
422: 422:
description: > description: >
422 UNPROCESSABLE ENTITY 422 UNPROCESSABLE CONTENT
If the payload body of a request contains syntactically correct data (e.g. well-formed JSON) but the data If the message content 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 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" 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. attribute more information about the source of the problem.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment