Flex option hook should support unspecified number of encapsulation levels (just like the core code does). - Follow-up from "Draft: Resolve "[ISC-support #20152] Support for custom spaces in flex_option hook""
Flex option hook should support unspecified number of encapsulation levels (just like the core code does).
Core supported spaces and options:
#define ISC_V6_OPTION_SPACE "4o6"
#define MAPE_V6_OPTION_SPACE "s46-cont-mape-options"
#define MAPT_V6_OPTION_SPACE "s46-cont-mapt-options"
#define LW_V6_OPTION_SPACE "s46-cont-lw-options"
#define V4V6_RULE_OPTION_SPACE "s46-rule-options"
#define V4V6_BIND_OPTION_SPACE "s46-v4v6bind-options"
D6O_DHCPV4_MSG = 87, /* RFC7341 */
D6O_DHCPV4_O_DHCPV6_SERVER = 88, /* RFC7341 */
D6O_S46_RULE = 89, /* RFC7598 */
D6O_S46_BR = 90, /* RFC7598 */
D6O_S46_DMR = 91, /* RFC7598 */
D6O_S46_V4V6BIND = 92, /* RFC7598 */
D6O_S46_PORTPARAMS = 93, /* RFC7598 */
D6O_S46_CONT_MAPE = 94, /* RFC7598 */
D6O_S46_CONT_MAPT = 95, /* RFC7598 */
D6O_S46_CONT_LW = 96, /* RFC7598 */
The following discussion from !1600 (merged) should be addressed:
-
@razvan started a discussion: (+2 comments) we can have "sub-options" here also and we will effectively have unlimited encapsulation levels (of course limited by user definitions and configuration text), and we can call parseSubOptions in parseSubOptions recursively.
Edited by Razvan Becheriu