[dhcwg] dhcpv6-24: vendor-specific issues

>    Servers can interpret the meanings of multiple class specifications
>    in an implementation dependent or configuration dependent manner, and
>    so the use of multiple classes by a DHCP client should be based on
>    the specific server implementation and configuration which will be
>    used to process that User class option.

This sure reads badly in the sense that it smells like
interoperability will not result. But I'm not sure what the intent of
the wording is here... Could someone clarify?

> 22.18. Vendor-specific Information option
>
>    This option is used by clients and servers to exchange
>    vendor-specific information.  The definition of this information is
>    vendor specific.  The vendor is indicated in the enterprise-number
>    field.  Clients that do not receive desired vendor-specific
>    information SHOULD make an attempt to operate without it, although
>    they may do so (and announce they are doing so) in a degraded mode.

This also reads badly and against interoperabilty. DHC clients should
never depend on vendor-specific options in order to function
correctly.

Thomas

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg