Open Boot and Management Framework (CLA)
The Open Boot and Management Framework (OBMF) Workstream is a semi-private (CLA) workstream under the OCP Hardware Management Project. It is producing a specification that prescribes the DC-SCM interface, or recommended physical interfaces, and a standardized protocol for boot, configuration, and runtime communication between the Host Processor Module and the Baseboard Management Controller on the DC-SCM module. The protocol is designed to be CPU-vendor and physical-interface agnostic, reusable for devices such as PCIe and CXL cards, extensible through vendor extensions, and aligned with OCP, DMTF, and SPDM standards. Published documents include the OBMF-ICP Specification v0.7.1 and OBMF-ICP over USB v1.0.
About This Workstream
The Open Boot and Management Framework (OBMF) Workstream is a Semi-Private (CLA) Workstream under the OCP Hardware Management Project.
The workstream is producing a specification to prescribe the DC-SCM interface (or a list of recommended physical interfaces) and a standardized protocol for use in boot, configuration, and runtime communication between the Host Processor or other devices on the Host Processor Module (HPM) and the Baseboard Management Controller (BMC) on the DC-SCM Module.
Requirements
- Host Processor (CPU) vendor agnostic
- Applicable to non-DC-SCM use cases
- Reusable for other devices, e.g. PCIe cards, CXL cards, etc.
- Physical-interface-agnostic protocol (e.g., MCTP/PLDM)
- Recommended physical interface choices for DC-SCM use cases
- Supporting an adoption model for vendor-specific features (vendor extensions)
- Leveraging OCP standards and DMTF standards
- Aligned to existing security standards and requirements (e.g., SPDM)
Published Documents
- OBMF-ICP Specification v0.7.1 (October 2025)
- OBMF-ICP over USB v1.0 (April 2026)
- DMTF DSP0295 — OBMF-ICP over MCTP v0.8 WIP (March 2026)
Scope
The OBMF Workstream’s scope covers:
- Protocol Definition : use cases and applicability; definition of initiator and target; protocol states and state-transition flows; API definition; message formats and encoding
- Security : security requirements aligned to existing standards such as SPDM
- Standards Reuse : alignment with and reuse of existing communication standards defined by DMTF (MCTP, PLDM)
- Firmware & Interoperability : firmware requirements and interoperability design documents
- Related Requirements : requirements pertaining to MHS, DC-SCM, and Streaming Boot
