There are four ways a Serial Number is supported (by DRIP):
As itself as a clear-text string with additional information
As itself as a clear-text string mapped to a DET "post"
generation by the manufacturer (for use in authentication) and
additional information
As itself as a clear-text string mapped to a DET "post"
generation by the user (for use in authentication) and additional
information
As an encoding of an HI and associated DET by the manufacturer
(for use in authentication) with additional information
these could be both tightened up and be more clear if written as something like
the following track backing and forth between the explanitory notes or the
cases should end up being 4 sub headings e.g. 6.1.1 2/3/4 and not simply a list.
The proposed example has been removed here for conciseness.
From the opsdir review:
The proposed example has been removed here for conciseness.