ISO/IEC DIS 30115-2-2025 PDF
Information technology-Redfish scalable platforms management API specification-Part 2: Redfish data model specification
- AA-The Aluminum Association
- AAMI-Association for the Advancement of Medical Instrumentation
- AASHTO-American Association of State Highway and Transportation Officials
- AATCC-American Association of Textile Chemists and Colorists
- ACI-American Concrete Institute
- ANSI-American National Standards Institute
- API-American Petroleum Institute
- AS-Standards Australia
- ASABE-American Society of Agricultural and Biological Engineers (Formerly ASAE)
- ASCE-American Society of Civil Engineers
- ASHRAE-American Society of Heating, Refrigerating, and Air Conditioning Engineers
- ASME-ASME International
- ASTM-ASTM International
- AWS-American Welding Society
- AWWA-American Water Works Association
- BS-BSI Group
- ISO-International Organization for Standardization
- IEC-International Electrotechnical Commission
- IEEE-Institute of Electrical and Electronics Engineers
Your shopping cart is empty!
Product Description
Information technology — Redfish scalable platforms management API specification — Part 2: Redfish data model specification
Introduction: Redfish is a standard that uses RESTful interface semantics to access a schema-based data model to conduct management operations. It is suitable for a wide range of devices, from stand-alone servers to composable infrastructures and large-scale cloud environments. The initial Redfish scope targeted servers. DMTF and its alliance partners expanded that scope to cover most data center IT equipment and other solutions, and both in- and out-of-band access methods. Additionally, DMTF and other organizations that use Redfish as part of their industry standard or solution have added educational material. This document defines the RESTful interface protocol and the various concepts and services necessary to implement a Redfish interface. The definition of the schema based data model and standard messages for the Redfish interface are covered separately in the following documents: DMTF DSP8010, Redfish Schema Bundle, https://www.dmtf.org/dsp/DSP8010 contains the individual schema definition files in multiple schema description languages. DMTF DSP0268, Redfish Data Model Specification, https://www.dmtf.org/dsp/DSP0268 contains the normative descriptions and example payloads for all standard Redfish schema in a single reference guide. DMTF DSP8011, Redfish Standard Registries Bundle, https://www.dmtf.org/dsp/DSP8011 contains the message registries used for error reporting and event messages. DSP0266 Redfish Specification Version 1.20.0 Published ISO/IEC DIS 30115-2:2025(en) © ISO/IEC 20
Scope: This specification defines the required protocols, data model, behaviors, and other architectural components for an interoperable, multivendor, remote, and out-of-band capable interface. This interface meets the cloud-based and web-based IT professionals’ expectations for scalable platform management. While large and hyperscale environments are the primary focus, clients can use the specification for individual system management. The specification defines the required elements for all Redfish implementations, and the optional elements that system vendors and manufacturers can choose. This specification also defines at which points an implementation can provide OEM-specific extensions. The specification sets normative requirements for Redfish services and associated materials, such as Redfish schema files. In general, the specification does not set requirements for Redfish clients but indicates how a client can successfully and effectively access and use a Redfish service. The specification does not require that implementations of the Redfish interfaces and functions require particular hardware or firmware. Redfish Specification DSP0266 Published Version 1.20.0 ISO/IEC DIS 30115-2:2025(en) © ISO/IEC 2025 – All rights reserved 2 Normative references The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. DMTF DSP0270, Redfish Host Interface Specification, https://www.dmtf.org/sites/default/files/standards/ documents/DSP0270_1.0.0.pdf Redfish Schema: RedfishExtensions v1.0.0, https://redfish.dmtf.org/schemas/v1/RedfishExtensions_v1.xml Transport Layer Security (TLS) Parameters, https://www.iana.org/assignments/tls-parameters/tls- parameters.xhtml JSON Schema: A Media Type for Describing JSON Documents draft-handrews-json-schema-01, https://tools.ietf.org/html/draft-handrews-json-schema-01 JSON Schema Validation: A Vocabulary for Structural Validation of JSON draft-handrews-json-schema- validation-01, https://tools.ietf.org
Contents:
- 1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
- 2 Normative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
- 3 Terms, definitions, symbols, and abbreviated terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
- 3.1 Hardware terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
- 3.1.1 baseboard management controller (BMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
- 3.1.2 IPMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
- 3.1.3 KVM-IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
- 3.1.4 NIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- 3.1.5 PCI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- 3.1.6 PCIe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- 3.2 Web development terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- 3.2.1 CORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- 3.2.2 CRUD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- 3.2.3 CSRF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- 3.2.4 event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- 3.2.5 excerpt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- 3.2.6 HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- 3.2.7 HTTPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- 3.2.8 hypermedia API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
- 3.2.9 IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
- 3.2.10 JSON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
- 3.2.11 member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
- 3.2.12 message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
- 3.2.13 OData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
- 3.2.14 OData service document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
- 3.2.15 operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
- 3.2.16 parent resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
- 3.2.17 property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
- 3.2.18 request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
- 3.2.19 response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20



