Opened 9 months ago

Last modified 3 months ago

#5497 new defect

VIVSO configuration is not clearly documented

Reported by: jasonguy Owned by:
Priority: low Milestone: Outstanding Tasks
Component: documentation Version: git
Keywords: vivso Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Low
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

The documentation around using VIVSO is a bit ambiguous. This ticket is primarily meant to address adding some additional detail around the mandatory option space string used, must be defined specifically as "vendor-<enterprise-id>".

Looking at this a little more broadly, there are only a couple fragments of documentation addressing VIVSO:

  • One is found in the Host Reservation section. This section has an example of setting VIVSO data in a host reservation. The option space is set properly in the example, but it is not explained and not obvious that the string used for the option space must be vendor-<enterprise-id>.

I have not found anywhere in the documentation indicating if a VIVSO option must be defined under option-defs configuration in order to use it, similar to the custom options section. Apparently to use VIVSO options in a client class, the VIVSO schema does not need to be defined. This is because the client classification parses unknown options as binary, so apparently the structure of the VIVSO options do not need to be defined. Though it helps to define the VIVSO option and suboptions, in order to organize your thoughts.

Subtickets

Change History (3)

comment:1 Changed 8 months ago by tomek

  • Milestone changed from Kea-proposed to Kea1.4-final

comment:2 Changed 4 months ago by tomek

  • Priority changed from very low to low

comment:3 Changed 3 months ago by tomek

  • Milestone changed from Kea1.4-final to Outstanding Tasks

As discussed on 2018-06-20 call.

Note: See TracTickets for help on using tickets.