Skip to content

[v5.2.1] Additional implementation of common error code 416 in the SOL003 OpenAPI VNFLCM operations without information in the SOL003/SOL013 specification

[Actual Status] Situation with SOL003 416 Response code:

  • Is it in the SOL003 Word document? ×
  • Is it in the SOL013 Word document? ×
  • Is the content of SOL003 Word document in OpenAPI? - ※ It's not applicable as it doesn't exist in the Word document
  • Is the content of SOL013 Word document in OpenAPI? - ※ It's not applicable as it doesn't exist in the Word document
  • Other: Is the content of the 416 response in OpenAPI? 〇

[SOL003/SOL013 specification document]

In v5.2.1, the SOL013 specification document does not include a description for the common error code 416, as referenced in the SOL003 operations detailed in sections 5.4.2.3.2, 5.4.3.3.2, and 5.4.4.3.1.

Example: 5.4.2.3.2 https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/05.02.01_60/gs_NFV-SOL003v050201p.pdf

image

[OpenAPI]

On the other hand, there is a description for common error codes 416 in the SOL003 OpenAPI VNFLCM operations for

Inconsistencies with SOL documentation.

[Problem]

The issue is that the content of the 416 response exists in OpenAPI.

[Conclusion]

Reference of common error code 416 should be removed from SOL003 VNFLCM OpenAPI operation "VNFLifecycleManagement.yaml" file below operation.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information