From 164aa812b34fcadc0f772cee7c243a3a971b961f Mon Sep 17 00:00:00 2001 From: Francis Dupont Date: Sat, 12 Oct 2019 22:10:10 +0200 Subject: [PATCH] [950-dhcp-option-43-pad-end] Updated doc --- doc/sphinx/arm/dhcp4-srv.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst index d193859a57..48efaa0975 100644 --- a/doc/sphinx/arm/dhcp4-srv.rst +++ b/doc/sphinx/arm/dhcp4-srv.rst @@ -2150,6 +2150,16 @@ The definition used to decode a VSI option is: matching these cases and an option definition for the VSI option with a binary type and no encapsulation. +.. note:: + + In the Vendor-Specific Information option (code 43) sub-option code 0 + and 255 mean PAD and END respectively according to + `RFC 2132 `_. Kea allows to + configured sub-options with codes from 0 to 255: when an VSI option + is parsed in an incoming query and the sub-option 0 is configured + sub-option code 0 is no longer parsed as a PAD. Same for sub-option 255 + and END. + .. note:: Option definitions in client classes are allowed only for this -- 2.47.2