1 of 9

2 of 9

SERVER

OCP NIC Community Update�May 2026

�����Sub-group Project Wiki: https://www.opencompute.org/wiki/Server/NIC�

Mailing List: https://ocp-all.groups.io/g/OCP-NIC

NIC3.0

3 of 9

Agenda

​

  • Thermal Test Fixture update
  • Thermal workstream update
  • OCP Academy

​

​

​

4 of 9

OCP NIC TTF contribution

Dell is contributing the latest OCP TTF

Update: Seeking OCP SC approval May 13th

​

5 of 9

Thermal Workstream Update - LC TSFF

​

  • Liquid cooling feasibility study complete
    • 3 mechanical design concepts
    • Updated thermal model results for each concept
  • Need feedback from NIC community
  • Next steps
    • Share in system level workstream (MHS?) for feedback

​

6 of 9

OCP Academy

​

  • OCP foundation initiative
  • Content is being developed
  • Have to go thru workstream leads review & feedback for accuracy

​

7 of 9

​

Thank You

​

​

​

​

​

8 of 9

Board Info Area Format Mfg Date/Time Rollover

  • Defined by the IPMI FRU Storage Information Specification. Last updated March 2015.
    • Board Info Area Format has a 3-byte Mfg Date/Time field.
    • Defined as the number of minutes from 0:00 hrs 1/1/1996.
    • Rolls over Nov 24th, 2027.

​

Option 1: OCP NIC leaves the Mfg Date/Time field as-is and allows the value to roll over with a start year ambiguity (1996, 2027, 2058, etc). Possibly following the OpenBMC format: https://gerrit.openbmc.org/c/openbmc/entity-manager/+/87782

Option 2: OCP NIC cards may start using the value of 00_00_00h (“unspecified”) going forward and is required to use 00_00_00h after Nov 24th, 2027.

Option 3: OCP NIC amends the 0xC0 Base OEM Record with a four byte manufacturing date field that starts from 0:00 hrs Jan 1st, 1996.

Option 4: OCP NIC amends the 0xC0 Base OEM Record with a four byte manufacturing date field that starts from 0:00 hrs Nov 24th, 2027.

E-mail reflector thread: https://ocp-all.groups.io/g/OCP-NIC/message/324

​

​

Company Input (thus far):

​

Option

Company Preference

1

Meta

2

Dell, Intel, Lenovo

3

​

4

Broadcom

5

Intel, Lenovo

Add DMTF option 5 → Next slide

9 of 9

Board Info Area Format Mfg Date/Time Rollover

Option 5: Implement a DMTF FRU (DSP0220) format in “hybrid” mode. Enables a gradual transition to the DMTF FRU. Backwards compatible.

​

High Level Changes:

  • Add a new DMTF OEM Record (0xC0, IANA 0xB41A00) containing a four-byte offset to the new DMTF General FRU Record File position.
    • BMCs that don’t understand the DMTF OEM Record will skip/ignore the new data.
  • Option 2 would also be implemented (zero out the mfg date/time field) and, at minimum, includes a new structure with a 13-byte Manufacture Date Field.
    • Card vendors may populate additional field types (such as the Manufacturer, Part Number, Serial Number) as defined in DSP0257.
    • Field Types with IPMI equivalents shall have the same data replicated in the DMTF FRU section.

​

Pros:

  • Maintains backwards compatibility with existing FRU format.
  • Minimal effort for NIC vendors.
    • Existing OCP NIC 3.0 IPMI OEM Records continue to be used as-is
    • Can co-exist with the IPMI FRU format and I2C EEPROMs.
  • Baseboard vendors may already support DSP0220 FRU formats.

​

Cons:

  • DMTF needs tools/validators/minor specification clarifications.
  • Misbehaved BMCs need to be examined.

​

Common Header

Board Info Area

Product Info Area