[kea-dev] DHCPv4 vendor-encapsulated-options (43) option (problem)

[Francis Dupont]

Currently the option is defined as empty with encapsulated space
set to vendor-encapsulated-options-space.
Even it is not very sexy it works in at least 90% of cases but
the specs (RFC 2132) say:
   If a vendor potentially encodes more than one item of information in
   this option, then the vendor SHOULD encode the option using
   "Encapsulated vendor-specific options" as described below:
	 
so with one encoded item the option is not filled by suboptions
but with a raw value, i.e., the correct definition is binary
(or no definition at all as it is the default).

It can raise a bug during decoding (unpack) and drop correct but
wrongly unparsable received messages. This is why #5073 was created
for Kea 1.2.

Regards

Francis Dupont <fdupont at isc.org>