SOL005_31 to SOL005_46 (5b86f348) · Commits · NFV - Network Functions Virtualisation / SOL005

src/SOL005/NSDManagement/NSDManagement.yaml

+25 −18

Original line number	Original line	Diff line number	Diff line
	@@ -1070,6 +1070,10 @@ components:
	in: path		in: path
	description: \|		description: \|
	Identifier of the individual NS descriptor resource.		Identifier of the individual NS descriptor resource.

			This identifier can be retrieved from the resource referenced by the "Location" HTTP header in
			the response to a POST request creating a new NS descriptor resource. It can also be retrieved
			from the "id" attribute in the message content of that response.
	required: true		required: true
	style: simple		style: simple
	explode: false		explode: false
	@@ -1081,6 +1085,9 @@ components:
	in: path		in: path
	description: \|		description: \|
	Identifier of the individual PNF descriptor resource.		Identifier of the individual PNF descriptor resource.
			This identifier can be retrieved from the resource referenced by the "Location" HTTP header in
			the response to a POST request creating a new PNF descriptor resource. It can also be retrieved
			from the "id" attribute in the message content of that response.
	required: true		required: true
	style: simple		style: simple
	explode: false		explode: false
	@@ -1147,7 +1154,7 @@ components:
	Identifier of this subscription.		Identifier of this subscription.
	This identifier can be retrieved from the resource referenced by the "Location" HTTP header in		This identifier can be retrieved from the resource referenced by the "Location" HTTP header in
	the response to a POST request creating a new subscription resource. It can also be retrieved		the response to a POST request creating a new subscription resource. It can also be retrieved
	from the "id" attribute in the payload body of that response.		from the "id" attribute in the message content of that response.
	required: true		required: true
	style: simple		style: simple
	explode: false		explode: false
	@@ -1836,12 +1843,12 @@ components:

	If the "include_signatures" URI query parameter was absent in the request, or if the		If the "include_signatures" URI query parameter was absent in the request, or if the
	manifest file has all security-related information embedded (i.e. there is no separate		manifest file has all security-related information embedded (i.e. there is no separate
	certificate file), the payload body shall contain a copy of the manifest file of the		certificate file), the message content shall contain a copy of the manifest file of the
	NSD archive, and the "Content-Type" HTTP header shall be set to "text/plain".		NSD archive, and the "Content-Type" HTTP header shall be set to "text/plain".
	If the "include_signatures" URI query parameter was present in the related request and		If the "include_signatures" URI query parameter was present in the related request and
	the manifest file does not have all the security-related information embedded (i.e. there		the manifest file does not have all the security-related information embedded (i.e. there
	is a separate certificate file), the "Content-Type" HTTP header shall be set to "application/zip"		is a separate certificate file), the "Content-Type" HTTP header shall be set to "application/zip"
	and the payload body shall contain a ZIP archive which includes:		and the message content shall contain a ZIP archive which includes:
	- a copy of the manifest file of the NSD archive;		- a copy of the manifest file of the NSD archive;
	- a copy of the related individual certificate file.		- a copy of the related individual certificate file.
	headers:		headers:
	@@ -1912,7 +1919,7 @@ components:
	Shall be returned when the content of the artifact file has been read successfully.		Shall be returned when the content of the artifact file has been read successfully.

	If the "include_signatures" request URI parameter was not provided in the related request,		If the "include_signatures" request URI parameter was not provided in the related request,
	the payload body shall contain a copy of the artifact file from the NSD archive, as defined		the message content shall contain a copy of the artifact file from the NSD archive, as defined
	by ETSI GS NFV-SOL 007, and the "Content-Type" HTTP header shall be set according to the		by ETSI GS NFV-SOL 007, and the "Content-Type" HTTP header shall be set according to the
	content type of the artifact file. If the artifact is encrypted, the header shall be set to		content type of the artifact file. If the artifact is encrypted, the header shall be set to
	the value "application/cms" (IETF RFC 7193).		the value "application/cms" (IETF RFC 7193).
	@@ -1920,7 +1927,7 @@ components:
	If the content type cannot be determined, the header shall be set to the value		If the content type cannot be determined, the header shall be set to the value
	"application/octet-stream". If the "include_signatures" request URI parameter was provided		"application/octet-stream". If the "include_signatures" request URI parameter was provided
	in the related request, the "Content-Type" HTTP header shall be set to "application/zip"		in the related request, the "Content-Type" HTTP header shall be set to "application/zip"
	and the payload body shall contain a ZIP archive which includes:		and the message content shall contain a ZIP archive which includes:
	- a copy of the artifact file from the VNF package, as defined by ETSI GS NFVSOL 007		- a copy of the artifact file from the VNF package, as defined by ETSI GS NFVSOL 007
	- the related security information (individual signature file and optional related individual		- the related security information (individual signature file and optional related individual
	certificate file).		certificate file).
	@@ -1964,7 +1971,7 @@ components:
	If the content type cannot be determined, the header shall be set to the value		If the content type cannot be determined, the header shall be set to the value
	"application/octet-stream".		"application/octet-stream".

	The "Content-Range" HTTP header shall be provided according to IETF RFC 7233.		The "Content-Range" HTTP header shall be provided according to IETF RFC 9110.
	headers:		headers:
	Content-Type:		Content-Type:
	description: \|		description: \|
	@@ -2303,7 +2310,7 @@ components:

	Shall be returned when the content of the PNFD archive has		Shall be returned when the content of the PNFD archive has
	been read successfully.		been read successfully.
	The payload body shall contain a copy of the PNFD archive		The message content shall contain a copy of the PNFD archive
	The "Content-Type" HTTP header shall be set to "application/zip".		The "Content-Type" HTTP header shall be set to "application/zip".
	headers:		headers:
	Content-Type:		Content-Type:
	@@ -2337,7 +2344,7 @@ components:
	when a single consecutive byte range from the content of the PNFD archive		when a single consecutive byte range from the content of the PNFD archive
	has been read successfully according to the request.		has been read successfully according to the request.
	The response body shall contain the requested part of the PNFD archive.		The response body shall contain the requested part of the PNFD archive.
	The "Content-Range" HTTP header shall be provided according to IETF RFC 7233.		The "Content-Range" HTTP header shall be provided according to IETF RFC 9110.
	The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response.		The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response.
	headers:		headers:
	Content-Type:		Content-Type:
	@@ -2526,7 +2533,7 @@ components:
	200 OK		200 OK

	Shall be returned when the content of the PNFD has been read successfully.		Shall be returned when the content of the PNFD has been read successfully.
	The payload body shall contain a copy of the file representing the PNFD		The message content shall contain a copy of the file representing the PNFD
	or a ZIP file that contains the file or multiple files representing the		or a ZIP file that contains the file or multiple files representing the
	PNFD, as specified above.		PNFD, as specified above.
	The "Content-Type" HTTP header shall be set according to the format of		The "Content-Type" HTTP header shall be set according to the format of
	@@ -2625,14 +2632,14 @@ components:
	read successfully.		read successfully.
	If the "include_signatures" URI query parameter was absent in the		If the "include_signatures" URI query parameter was absent in the
	request, or if the manifest file has all security-related information		request, or if the manifest file has all security-related information
	embedded (i.e. there is no separate certificate file), the payload		embedded (i.e. there is no separate certificate file), the message
	body shall contain a copy of the manifest file of the PNFD archive,		content shall contain a copy of the manifest file of the PNFD archive,
	and the "Content-Type" HTTP header shall be set to "text/plain".		and the "Content-Type" HTTP header shall be set to "text/plain".
	If the "include_signatures" URI query parameter was present in the		If the "include_signatures" URI query parameter was present in the
	related request and the manifest file does not have all the		related request and the manifest file does not have all the
	security-related information embedded (i.e. there is a separate certificate file),		security-related information embedded (i.e. there is a separate certificate file),
	the "Content-Type" HTTP header shall be set to "application/zip" and		the "Content-Type" HTTP header shall be set to "application/zip" and
	the payload body shall contain a ZIP archive which includes:		the message content shall contain a ZIP archive which includes:
	- a copy of the manifest file of the PNFD archive;		- a copy of the manifest file of the PNFD archive;
	- a copy of the related individual certificate file.		- a copy of the related individual certificate file.
	headers:		headers:
	@@ -2709,7 +2716,7 @@ components:
	Shall be returned when the content of the artifact file has been read successfully.		Shall be returned when the content of the artifact file has been read successfully.

	If the "include_signatures" request URI parameter was not provided in the related request,		If the "include_signatures" request URI parameter was not provided in the related request,
	the payload body shall contain a copy of the artifact file from the PNFD archive, as defined		the message content shall contain a copy of the artifact file from the PNFD archive, as defined
	by ETSI GS NFV-SOL 004, and the "Content-Type" HTTP header shall be set according to the		by ETSI GS NFV-SOL 004, and the "Content-Type" HTTP header shall be set according to the
	content type of the artifact file. If the artifact is encrypted, the header shall be set to		content type of the artifact file. If the artifact is encrypted, the header shall be set to
	the value "application/cms" (IETF RFC 7193).		the value "application/cms" (IETF RFC 7193).
	@@ -2717,14 +2724,14 @@ components:
	If the content type cannot be determined, the header shall be set to the value		If the content type cannot be determined, the header shall be set to the value
	"application/octetstream". If the "include_signatures" request URI parameter was provided		"application/octetstream". If the "include_signatures" request URI parameter was provided
	in the related request, the "Content-Type" HTTP header shall be set to "application/zip"		in the related request, the "Content-Type" HTTP header shall be set to "application/zip"
	and the payload body shall contain a ZIP archive which includes:		and the message content shall contain a ZIP archive which includes:
	- a copy of the artifact file from the VNF package, as defined by ETSI GS NFVSOL 004		- a copy of the artifact file from the VNF package, as defined by ETSI GS NFVSOL 004
	- the related security information (individual signature file and optional related individual		- the related security information (individual signature file and optional related individual
	certificate file).		certificate file).
	headers:		headers:
	Content-Type:		Content-Type:
	description: \|		description: \|
	The MIME type of the body of the request. Reference: IETF RFC 7231		The MIME type of the body of the request. Reference: IETF RFC 9110
	style: simple		style: simple
	explode: false		explode: false
	schema:		schema:
	@@ -2970,10 +2977,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 of the payload body is supported and the payload		Shall be returned upon the following error: The content type of the message content is supported and the message content
	body of a request contains syntactically correct data but the data cannot be processed.		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 [16],		The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [16],
	including rules for the presence of the response body.		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 NFVO has tested		Specifically in case of this resource, the response code 422 shall also be returned if the NFVO has tested

Admin message