NFVSOL(26)000088_SOL026_Review_Contribution_Update_to_latest_DMTF_protocol_specification

<span id="_ref_1"></span><a name="_ref_1">[1]</a>    ETSI GS NFV-IFA 053: \"Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Requirements and interface specification for Physical Infrastructure Management\".

<span id="_ref_2"></span><a name="_ref_2">[2]</a>    [DMTF&reg; DSP0266](DMTF&reg; DSP0266): \"Redfish Specification\", v1.22.0.

<span id="_ref_2"></span><a name="_ref_2">[2]</a>    [DMTF&reg; DSP0266](https://www.dmtf.org/sites/default/files/standards/documents/DSP0266_1.23.1.pdf): \"Redfish Specification\", v1.23.1.

<span id="_ref_3"></span><a name="_ref_3">[3]</a>     [DMTF&reg; DSP0268](DMTF&reg; DSP0268): \"Redfish Data Model Specification\", v2025.1.

- /redfish/v1/EventService/Subscriptions

- /redfish/v1/TaskService/TaskMonitors

<mark>Editor's Note:    Creation of composed physical system via composition service needs further study. Appropriate endpoints for creating a composed system via composition service URI can be added later if required. Although, clause 15 of Redfish interface specification [\[2\]](#_ref_2) suggests that the same /redfish/v1/Systems endpoint may be used even for creating composed systems. The CompositionService is used for creating a composed system. Once composed that system would appears in the same Systems collection resource.</mark>

## 6.3 Resource structure and HTTP methods

Figures 6.3-1, 6.3-2 and 6.3-3 show resource structures of the Redfish® API [\[2\]](#_ref_2) resources that are applicable for the physical resource provisioning and lifecycle management service interface.