Commit fa9c65b7 authored by Francis Dupont's avatar Francis Dupont
Browse files

[5351] Updated the doc

parent 4f5be570
...@@ -101,12 +101,12 @@ ...@@ -101,12 +101,12 @@
"match-client-id": true, "match-client-id": true,
// The following list defines subnets. Each subnet consists of at // The following list defines subnets. Each subnet consists of at
// least subnet and pool entries. One extra feature that requires some // least subnet and pool entries. One extra feature that requires
// explanation is user-context. This is a structure that you can define // some explanation is user-context. This is a structure that you can
// in subnets and pools. It is parsed by Kea, but not used directly. // define in subnets, pools and others. It is parsed by Kea, but not
// It is intended to keep anything you may want to put there - comments, // used directly. It is intended to keep anything you may want to
// extra designations, floor or department names etc. These structures // put there - comments, extra designations, floor or department
// will be made available to Kea hooks. // names etc. These structures will be made available to Kea hooks.
// You can define multiple user-contexts in the same scope without // You can define multiple user-contexts in the same scope without
// the last one replacing previous values. A comment entry is // the last one replacing previous values. A comment entry is
// translated into a user-context with a "comment" property so // translated into a user-context with a "comment" property so
......
...@@ -4636,8 +4636,11 @@ autogenerated IDs are not stable across configuration changes.</para> ...@@ -4636,8 +4636,11 @@ autogenerated IDs are not stable across configuration changes.</para>
</para> </para>
<para> <para>
User contexts can be specified on either subnet or pool level. One User contexts can be specified on either global scope,
other useful usage is the ability to store comments or descriptions. shared network, subnet, pool, client class, option data or
definition level but not yet for a host reservation. One
other useful usage is the ability to store comments or
descriptions.
</para> </para>
<para> <para>
......
...@@ -4597,8 +4597,11 @@ autogenerated IDs are not stable across configuration changes. ...@@ -4597,8 +4597,11 @@ autogenerated IDs are not stable across configuration changes.
</para> </para>
<para> <para>
User contexts can be specified on either subnet or pool level. One User contexts can be specified on either global scope,
other useful usage is the ability to store comments or descriptions. shared network, subnet, pool, client class, option data or
definition level but not yet for a host reservation. One
other useful usage is the ability to store comments or
descriptions.
</para> </para>
<para> <para>
......
...@@ -2566,10 +2566,13 @@ both the command and the response. ...@@ -2566,10 +2566,13 @@ both the command and the response.
common usage. common usage.
</para> </para>
<para> <para>
As of Kea 1.3, the structures that allow user contexts are pools of all As of Kea 1.3, the structures that allow user contexts are
types (addresses and prefixes) and subnets. These are supported in both pools of all types (addresses and prefixes) and subnets. Kea
DHCPv4 and DHCPv6. It is expected that other structures will be extended 1.4 extended to the global scope, shared-networks, client
in the future to provide the user context capability. classes, and option data and definitions. These are supported
in both DHCPv4 and DHCPv6. It is expected that host
reservations and other structures will be extended in the
future to provide the user context capability.
</para> </para>
</section> </section>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment