Reset Action param "ResetType" is optional; how to handle?

Yes, from the normative "LongDescription" (see DSP0268 - Redfish Schema Supplement - for the "guide" version that has all the normative language), the system should perform a reset, with the "type" left to the implementation. We don't want the service to reject the command, because the user obviously wants the reset to occur...

This was done in an attempt to improve interoperability - because early implementations had a mix of ResetType support - and there were cases where there was no overlap of support between vendors. So providing the user the means to say "just reset, I don't care how you do it, just do it..." was our way of addressing the user intent and removing the need to learn from each service what types of reset were supported beforehand.


We should probably choose a different example for the specification since ResetType is the only (and optional) parameter on that Action. But yes, an implementation can make an optional-by-specification parameter a required-by-my-implementation. However, for Reset, we would not recommend that unless it truly is critical for the implementation.

And to be clear - yes, an implementation should accept the Reset action without a ResetType specified, and perform an appropriate reset.

Jeff