Merge branch 'NFVSOL(26)000098_SOL026_Editorial_adjustments_for_clauses_6-11' into 'main' (ca7a8160) · Commits · NFV - Network Functions Virtualisation / Specifications / GS NFV-SOL 026

GS_NFV-SOL_026.md

+9 −9

Original line number	Diff line number	Diff line
		@@ -445,7 +445,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 6.3-
		\| \| \| \| \|This resource endpoint shall be supported if \|
		\| \| \| \| \|the API producer supports asynchronous operations. \|
		+---------------------------------+-----------------------------------------+---------------------+-----------------+---------------------------------------------------------------------+
		\|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI is used by \|
		\|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI is used by \|
		\|the API producer to send notifications to the API consumer. This resource is not produced by the API producer.\ \|
		\|NOTE 2: The URI of the task monitor is provided in the Location header of the HTTP response to the API consumer \|
		\|when the API producer returns a \"202 Accepted\" response. \|
		@@ -844,8 +844,8 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 7.3-
		\| \| \| \| \|if the API producer supports asynchronous operations. \|
		+-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+
		\|NOTE 1: See clause 5.3.4 for the resource URIs of each inventory object collection. \|
		\|NOTE 2: The resource URI of an indivdual object can be acquired from the corresponding object collection in its \"Members\" property. \|
		\|NOTE 3: Notification endpoint resource and the corresponding NotficiationTargetURI \|
		\|NOTE 2: The resource URI of an individual object can be acquired from the corresponding object collection in its \"Members\" property. \|
		\|NOTE 3: Notification endpoint resource and the corresponding NotificationTargetURI \|
		\|is used by the API producer to send notifications to the API consumer. \|
		\|This resource is not produced by the API producer. \ \|
		\|NOTE 4: The URI of the task monitor is provided in the Location header \|
		@@ -1168,7 +1168,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 8.3-
		\| \| \| \| \|This resource endpoint shall be supported \|
		\| \| \| \| \|if the API producer supports asynchronous operations. \|
		+-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+
		\|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI \|
		\|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI \|
		\|is used by the API producer to send notifications to the API consumer. \|
		\|This resource is not produced by the API producer.\ \|
		\|NOTE 2: The URI of the task monitor is provided in the Location header \|
		@@ -1594,7 +1594,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 9.3-
		\| \| \| \| \|This resource endpoint shall be supported \|
		\| \| \| \| \|if the API producer supports asynchronous operations. \|
		+-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+
		\|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI \|
		\|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI \|
		\|is used by the API producer to send notifications to the API consumer. \|
		\|This resource is not produced by the API producer. \|
		\|NOTE 2: See clause 9.4.8 for the flow related to the API consumers receiving \|
		@@ -1745,7 +1745,7 @@ The querying of information about one or more performance reports, as illustrate

		### 9.4.8 Receiving performance reports asynchronously

		This clause describes the sequence for receiving performance reports asynchrnously as notifications.
		This clause describes the sequence for receiving performance reports asynchronously as notifications.

		![Figure 9.4.8-1: Flow of receiving performance reports as notifications](media/image31.png)

		@@ -2053,7 +2053,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 10.3
		\| \| \| \| \|This resource endpoint shall be supported \|
		\| \| \| \| \|if the API producer supports asynchronous operations. \|
		+-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+
		\|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI \|
		\|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI \|
		\|is used by the API producer to send notifications to the API consumer. \|
		\|This resource is not produced by the API producer. \ \|
		\|NOTE 2: The URI of the task monitor is provided in the Location header \|
		@@ -2249,7 +2249,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 11.3
		+-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+
		\|NOTE 1: Possible URI paths for the LogService and LogEntry resources are specified \|
		\|in the Redfish® data model specification [\[3\]](#_ref_3). \ \|
		\|NOTE 2: Notification endpoint resource and the corresponding NotficiationTargetURI \|
		\|NOTE 2: Notification endpoint resource and the corresponding NotificationTargetURI \|
		\|is used by the API producer to send notifications to the API consumer. \|
		\|This resource is not produced by the API producer. \ \|
		\|NOTE 3: The URI of the task monitor is provided in the Location header \|
		@@ -2530,7 +2530,7 @@ The URI query parameters, request and response bodies, and response codes of the

		### 11.5.6 Resource: Subscriptions

		This resource represents subscriptions related to log management of physical resources and can be used to retrieve a collection of already created subscription resources as well as to create a new individual subscription resource. This resource can be used to create a subscription to receive a notification once the Redfish service has successfully collected logs (diagnostics data) in the respectiv message registry.
		This resource represents subscriptions related to log management of physical resources and can be used to retrieve a collection of already created subscription resources as well as to create a new individual subscription resource. This resource can be used to create a subscription to receive a notification once the Redfish® service has successfully collected logs (diagnostics data) in the respectiv message registry.

		Table 11.5.6-1 specifies the supported HTTP methods for this resource and maps them against the PIM service interface requirements as specified in ETSI GS NFV-IFA 053 [\[1\]](#_ref_1).

Original line number	Diff line number	Diff line
		@@ -445,7 +445,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 6.3-
		\| \| \| \| \|This resource endpoint shall be supported if \|
		\| \| \| \| \|the API producer supports asynchronous operations. \|
		+---------------------------------+-----------------------------------------+---------------------+-----------------+---------------------------------------------------------------------+
		\|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI is used by \|
		\|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI is used by \|
		\|the API producer to send notifications to the API consumer. This resource is not produced by the API producer.\ \|
		\|NOTE 2: The URI of the task monitor is provided in the Location header of the HTTP response to the API consumer \|
		\|when the API producer returns a \"202 Accepted\" response. \|
		@@ -844,8 +844,8 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 7.3-
		\| \| \| \| \|if the API producer supports asynchronous operations. \|
		+-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+
		\|NOTE 1: See clause 5.3.4 for the resource URIs of each inventory object collection. \|
		\|NOTE 2: The resource URI of an indivdual object can be acquired from the corresponding object collection in its \"Members\" property. \|
		\|NOTE 3: Notification endpoint resource and the corresponding NotficiationTargetURI \|
		\|NOTE 2: The resource URI of an individual object can be acquired from the corresponding object collection in its \"Members\" property. \|
		\|NOTE 3: Notification endpoint resource and the corresponding NotificationTargetURI \|
		\|is used by the API producer to send notifications to the API consumer. \|
		\|This resource is not produced by the API producer. \ \|
		\|NOTE 4: The URI of the task monitor is provided in the Location header \|
		@@ -1168,7 +1168,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 8.3-
		\| \| \| \| \|This resource endpoint shall be supported \|
		\| \| \| \| \|if the API producer supports asynchronous operations. \|
		+-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+
		\|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI \|
		\|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI \|
		\|is used by the API producer to send notifications to the API consumer. \|
		\|This resource is not produced by the API producer.\ \|
		\|NOTE 2: The URI of the task monitor is provided in the Location header \|
		@@ -1594,7 +1594,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 9.3-
		\| \| \| \| \|This resource endpoint shall be supported \|
		\| \| \| \| \|if the API producer supports asynchronous operations. \|
		+-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+
		\|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI \|
		\|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI \|
		\|is used by the API producer to send notifications to the API consumer. \|
		\|This resource is not produced by the API producer. \|
		\|NOTE 2: See clause 9.4.8 for the flow related to the API consumers receiving \|
		@@ -1745,7 +1745,7 @@ The querying of information about one or more performance reports, as illustrate

		### 9.4.8 Receiving performance reports asynchronously

		This clause describes the sequence for receiving performance reports asynchrnously as notifications.
		This clause describes the sequence for receiving performance reports asynchronously as notifications.

		![Figure 9.4.8-1: Flow of receiving performance reports as notifications](media/image31.png)

		@@ -2053,7 +2053,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 10.3
		\| \| \| \| \|This resource endpoint shall be supported \|
		\| \| \| \| \|if the API producer supports asynchronous operations. \|
		+-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+
		\|NOTE 1: Notification endpoint resource and the corresponding NotficiationTargetURI \|
		\|NOTE 1: Notification endpoint resource and the corresponding NotificationTargetURI \|
		\|is used by the API producer to send notifications to the API consumer. \|
		\|This resource is not produced by the API producer. \ \|
		\|NOTE 2: The URI of the task monitor is provided in the Location header \|
		@@ -2249,7 +2249,7 @@ The HTTP methods marked as \"M\" (mandatory) in the \"Cat\" column of table 11.3
		+-------------------------+---------------------------------+-----------------+----------+----------------------------------------------------------+
		\|NOTE 1: Possible URI paths for the LogService and LogEntry resources are specified \|
		\|in the Redfish® data model specification [\[3\]](#_ref_3). \ \|
		\|NOTE 2: Notification endpoint resource and the corresponding NotficiationTargetURI \|
		\|NOTE 2: Notification endpoint resource and the corresponding NotificationTargetURI \|
		\|is used by the API producer to send notifications to the API consumer. \|
		\|This resource is not produced by the API producer. \ \|
		\|NOTE 3: The URI of the task monitor is provided in the Location header \|
		@@ -2530,7 +2530,7 @@ The URI query parameters, request and response bodies, and response codes of the

		### 11.5.6 Resource: Subscriptions

		This resource represents subscriptions related to log management of physical resources and can be used to retrieve a collection of already created subscription resources as well as to create a new individual subscription resource. This resource can be used to create a subscription to receive a notification once the Redfish service has successfully collected logs (diagnostics data) in the respectiv message registry.
		This resource represents subscriptions related to log management of physical resources and can be used to retrieve a collection of already created subscription resources as well as to create a new individual subscription resource. This resource can be used to create a subscription to receive a notification once the Redfish® service has successfully collected logs (diagnostics data) in the respectiv message registry.

		Table 11.5.6-1 specifies the supported HTTP methods for this resource and maps them against the PIM service interface requirements as specified in ETSI GS NFV-IFA 053 [\[1\]](#_ref_1).