[Design] how to identify the request between BIOS and OOB user

tianocore / edk2-redfish-client

Utilizes the EFI protocols provided by EDK2 Redfish Foundation to communicate with the Redfish service for creating, consuming, and updating the Redfish properties which are managed by firmware.

Other

7 stars 5 forks source link

[Design] how to identify the request between BIOS and OOB user #26

Open nicklela opened 1 year ago

nicklela commented 1 year ago

Idea: Bootstrap credential + ComputerSystem.BootProgress

only host FW can get bootstrap credential. credential is generated on each request and it gets deleted on system reset.
OS or option rom can also get bootstrap credential. So, BMC can identify it is BIOS by checking the boot progress code. (OpenBMC has boot progress code implemented)
Boot progress support is a requirement from ARM SBMR specification:

nicklela commented 1 year ago

Two ideas

bootstrap credential is only used by BIOS not OS. OS should have their own way to get credential. vs.
OS can also use bootstrap credential to communicate with BMC

nicklela commented 1 year ago

There is a grey area so we like to send email to author of bootstrap credential. (Jeff Bobzin)