mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-09-01 22:45:18 +00:00
Code Issues Releases Wiki Activity

[#1745] document vivso options

Browse Source
This commit is contained in:
Andrei Pavel
2021-10-08 16:59:30 +03:00
parent f31ef484fd
commit 03c86b0096
3 changed files with 50 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
doc/sphinx/arm/dhcp4-srv.rst
View File

@@ -2432,12 +2432,24 @@ Alternatively, the option can be specified using its code.
Another popular option that is often somewhat imprecisely called the "vendor Another popular option that is often somewhat imprecisely called the "vendor
option" is option 125. Its proper name is the "vendor-independent option" is option 125. Its proper name is the "vendor-independent
vendor-specific information option" or "vivso". The idea behind vivso vendor-specific information option" or "vivso". The idea behind vivso options
options is that each vendor has its own unique set of options with their is that each vendor has its own unique set of options with their own custom
own custom formats. The vendor is identified by a 32-bit unsigned integer formats. The vendor is identified by a 32-bit unsigned integer called
called `enterprise-id` or `vendor-id`. For example, vivso with vendor-id `enterprise-number` or `vendor-id`.
4491 represents DOCSIS options, and they are often seen
when dealing with cable modems.
The standard spaces defined in Kea and their options are:
- ``vendor-4491``: Cable Television Laboratories, Inc. for DOCSIS3 options:
+-------------+--------------+------------------------------------------------------------------------+
| option code | option name | option description |
+=============+==============+========================================================================+
| 1 | oro | ORO (or Option Request Option) is used by clients to request a list of |
| | | options they are interested in. |
+-------------+--------------+------------------------------------------------------------------------+
| 2 | tftp-servers | a list of IPv4 addresses of TFTP servers to be used by the cable modem |
+-------------+--------------+------------------------------------------------------------------------+
In Kea each vendor is represented by its own vendor space. Since there In Kea each vendor is represented by its own vendor space. Since there
are hundreds of vendors and sometimes they use different option are hundreds of vendors and sometimes they use different option

32
doc/sphinx/arm/dhcp6-srv.rst
View File

@@ -1975,7 +1975,37 @@ DHCPv6 Vendor-Specific Options
------------------------------ ------------------------------
Vendor options in DHCPv6 are carried in the Vendor-Specific Vendor options in DHCPv6 are carried in the Vendor-Specific
Information option (code 17). The following examples show how to Information option (code 17). The idea behind option 17
is that each vendor has its own unique set of options with their own custom
formats. The vendor is identified by a 32-bit unsigned integer called
`enterprise-number` or `vendor-id`.
The standard spaces defined in Kea and their options are:
- ``vendor-2495``: Internet Systems Consortium, Inc. for 4o6 options:
+-------------+--------------------+------------------------------------------------------------------------+
| option code | option name | option description |
+=============+====================+========================================================================+
| 60000 | 4o6-interface | the name of the 4o6 server's client-facing interface |
+-------------+--------------------+------------------------------------------------------------------------+
| 60001 | 4o6-source-address | the address that the 4o6 server uses to send packets to the client |
+-------------+--------------------+------------------------------------------------------------------------+
| 60002 | 4o6-source-port | the port that the 4o6 server opens to send packets to the client |
+-------------+--------------------+------------------------------------------------------------------------+
- ``vendor-4491``: Cable Television Laboratories, Inc. for DOCSIS3 options:
+-------------+--------------------+------------------------------------------------------------------------+
| option code | option name | option description |
+=============+====================+========================================================================+
| 1 | oro | ORO (or Option Request Option) is used by clients to request a list of |
| | | options they are interested in. |
+-------------+--------------------+------------------------------------------------------------------------+
| 2 | tftp-servers | a list of IPv4 addresses of TFTP servers to be used by the cable modem |
+-------------+--------------------+------------------------------------------------------------------------+
The following examples show how to
define an option "foo" with code 1 that consists of an IPv6 address, define an option "foo" with code 1 that consists of an IPv6 address,
an unsigned 16-bit integer, and a string. The "foo" option is an unsigned 16-bit integer, and a string. The "foo" option is
conveyed in a Vendor-Specific Information option, which comprises a conveyed in a Vendor-Specific Information option, which comprises a

2
src/lib/dhcp/dhcp6.h
View File

@@ -263,7 +263,7 @@ static const uint16_t HWTYPE_INFINIBAND = 0x0020;
#define SHA_512 2 #define SHA_512 2
#define RSASSA_PKCS1v1_5 1 #define RSASSA_PKCS1v1_5 1
// Taken from http://www.iana.org/assignments/enterprise-numbers // Taken from https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers
static const uint32_t ENTERPRISE_ID_ISC = 2495; static const uint32_t ENTERPRISE_ID_ISC = 2495;
/* DHCPv4-over-DHCPv6 (RFC 7341) inter-process communication. These are option /* DHCPv4-over-DHCPv6 (RFC 7341) inter-process communication. These are option