Documentation clarification about unsigned/signed integer

[Alex Duzsardi]

Thank you, i wasn't aware of that.
So basically the server just decodes bytes in whatever format they might be
provided be it integer, hex, text and it expects the decoded data to make
sense for the type of the option set, integer in the case of option code 93
Is this behavior the same for other option types
(string,ip-address,text,flag) ?

Guessing providing an integer for a string type option doesn't really make
sense , will the server ignore the option in this case or just crash or log
an error ?  (i'll test it on a lab server later)

Thank you for the clarification Simon!

On Wed, 13 Apr 2022 22:04:48 +0100, Simon Hobson <dhcp1 at thehobsons.co.uk>
> wrote:
>
> The server really doesn't care - those examples are equivalent. It really
> comes down to what makes the most sense to the humans involved.
>
> For something that's "just a number" then the decimal version makes sense.
> If it's something more readable in hex then use one of the hex formats.
>
> You could also use a string. E.g. "AA" is (if I remember my codes after a
> long day) the same as 0x4141, or 41:41, or 16705.
>
> Simon
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20220414/a1d03142/attachment.htm>