|
@@ -1214,14 +1214,6 @@ temporarily override a list of interface names and listen on all interfaces.
|
|
|
<row><entry>client-linklayer-addr</entry><entry>79</entry><entry>binary</entry><entry>false</entry></row>
|
|
|
<!-- <row><entry>dhcpv4-message</entry><entry>87</entry><entry>binary</entry><entry>false</entry></row> -->
|
|
|
<row><entry>dhcp4o6-server-addr</entry><entry>88</entry><entry>ipv6-address</entry><entry>true</entry></row>
|
|
|
-<row><entry>s46-rule</entry><entry>89</entry><entry>record (uint8, uint8, uint8, ipv4-address, ipv6-prefix)</entry><entry>false</entry></row>
|
|
|
-<row><entry>s46-br</entry><entry>90</entry><entry>ipv6-address</entry><entry>false</entry></row>
|
|
|
-<row><entry>s46-dmr</entry><entry>91</entry><entry>ipv6-prefix</entry><entry>false</entry></row>
|
|
|
-<row><entry>s46-v4v6bind</entry><entry>92</entry><entry>record (ipv4-address, ipv6-prefix)</entry><entry>false</entry></row>
|
|
|
-<row><entry>s46-portparams</entry><entry>93</entry><entry>record(uint8, psid)</entry><entry>false</entry></row>
|
|
|
-<row><entry>s46-cont-mape</entry><entry>94</entry><entry>empty</entry><entry>false</entry></row>
|
|
|
-<row><entry>s46-cont-mapt</entry><entry>95</entry><entry>empty</entry><entry>false</entry></row>
|
|
|
-<row><entry>s46-cont-lw</entry><entry>96</entry><entry>empty</entry><entry>false</entry></row>
|
|
|
</tbody>
|
|
|
</tgroup>
|
|
|
</table>
|
|
@@ -1249,187 +1241,6 @@ temporarily override a list of interface names and listen on all interfaces.
|
|
|
</para>
|
|
|
</section>
|
|
|
|
|
|
- <section id="s46-options">
|
|
|
- <title>Common Softwire46 Options</title>
|
|
|
- <para>
|
|
|
- Softwire46 options are involved in IPv4 over IPv6 provisioning by
|
|
|
- means of tunneling or translation as specified in the
|
|
|
- <ulink url="http://tools.ietf.org/html/rfc7598">RFC 7598</ulink>.
|
|
|
- The following sections provide configuration examples of these
|
|
|
- options.
|
|
|
- </para>
|
|
|
-
|
|
|
- <section id="s46-containers">
|
|
|
- <title>Softwire46 Container Options</title>
|
|
|
- <para>
|
|
|
- S46 container options group rules and optional port parameters
|
|
|
- for a specified domain. There are three container options specified
|
|
|
- in the "dhcp6" (top level) option space: MAP-E Container option,
|
|
|
- MAP-T Container option and S46 Lightweight 4over6 Container option.
|
|
|
- These options only contain encapsulated options specified below.
|
|
|
- They do not include any data fields.
|
|
|
- </para>
|
|
|
-
|
|
|
- <para>
|
|
|
- In order to configure the server to send specific container option
|
|
|
- along with all encapsulated options, the container option must be
|
|
|
- included in the server configuration as shown below:
|
|
|
-<screen>
|
|
|
-"Dhcp6": {
|
|
|
- ...
|
|
|
- "option-data": [
|
|
|
- {
|
|
|
- "name": "s46-cont-mape"
|
|
|
- } ],
|
|
|
- ...
|
|
|
-}
|
|
|
-</screen>
|
|
|
-
|
|
|
- This configuration will cause the server to include MAP-E Container
|
|
|
- option to the client. Use "s46-cont-mapt" or "s46-cont-lw" for the
|
|
|
- MAP-T Container and S46 Lightweight 4over6 Container options
|
|
|
- respectively.
|
|
|
- </para>
|
|
|
-
|
|
|
- <para>
|
|
|
- All remaining softwire options described below are included in one
|
|
|
- of the container options. Thus, they have to be included in appropriate
|
|
|
- option spaces by selecting a "space" name, which specifies in which
|
|
|
- option they are supposed to be included.
|
|
|
- </para>
|
|
|
- </section>
|
|
|
-
|
|
|
- <section>
|
|
|
- <title>S46 Rule Option</title>
|
|
|
- <para>
|
|
|
- The S46 Rule option is used for conveying the Basic Mapping Rule (BMR)
|
|
|
- and Forwarding Mapping Rule (FMR).
|
|
|
-<screen>
|
|
|
-{
|
|
|
- "space": "s46-cont-mape-options",
|
|
|
- "name": "s46-rule",
|
|
|
- "data": "128, 0, 24, 192.0.2.0, 2001:db8:1::/64"
|
|
|
-}
|
|
|
-</screen>
|
|
|
- Other possible "space" value is "s46-cont-mapt-options".
|
|
|
- </para>
|
|
|
-
|
|
|
- <para>
|
|
|
- The S46 Rule option conveys a number of parameters:
|
|
|
-
|
|
|
- <itemizedlist>
|
|
|
- <listitem>
|
|
|
- <simpara><command>flags</command>, an unsigned 8 bits integer, with
|
|
|
- currently only the most significant bit specified. It denotes whether
|
|
|
- the rule can be used for forwarding (128) or not (0).
|
|
|
- </simpara>
|
|
|
- </listitem>
|
|
|
-
|
|
|
- <listitem>
|
|
|
- <simpara><command>ea-len</command>, an 8 bits long Embedded Address length. Allowed values
|
|
|
- range from 0 to 48.</simpara>
|
|
|
- </listitem>
|
|
|
-
|
|
|
- <listitem>
|
|
|
- <simpara><command>IPv4 prefix length</command>, 8 bits long; expresses the prefix length of the
|
|
|
- Rule IPv4 prefix specified in the ipv4-prefix field. Allowed
|
|
|
- values range from 0 to 32.</simpara>
|
|
|
- </listitem>
|
|
|
-
|
|
|
- <listitem>
|
|
|
- <simpara><command>IPv4 prefix</command>, a fixed-length 32-bit field that specifies the IPv4
|
|
|
- prefix for the S46 rule. The bits in the prefix after prefix4-len
|
|
|
- number of bits are reserved and MUST be initialized to zero by the
|
|
|
- sender and ignored by the receiver.</simpara>
|
|
|
- </listitem>
|
|
|
-
|
|
|
- <listitem>
|
|
|
- <simpara><command>IPv6 prefix</command> in prefix/length notation that specifies the IPv6 domain
|
|
|
- prefix for the S46 rule. The field is padded on the right with zero
|
|
|
- bits up to the nearest octet boundary when prefix6-len is not evenly
|
|
|
- divisible by 8.</simpara>
|
|
|
- </listitem>
|
|
|
-
|
|
|
- </itemizedlist>
|
|
|
- </para>
|
|
|
- </section>
|
|
|
- <section>
|
|
|
- <title>S46 BR Option</title>
|
|
|
- <para>
|
|
|
- The S46 BR option is used to convey the IPv6 address of the
|
|
|
- Border Relay. This option is mandatory in the MAP-E
|
|
|
- Container option and not permitted in the MAP-T and
|
|
|
- S46 Lightweight 4over6 Container options.
|
|
|
-<screen>
|
|
|
-{
|
|
|
- "space": "s46-cont-mape-options",
|
|
|
- "name": "s46-br",
|
|
|
- "data": "2001:db8:cafe::1",
|
|
|
-}
|
|
|
-</screen>
|
|
|
- Other possible "space" value is "s46-cont-lw-options".
|
|
|
- </para>
|
|
|
- </section>
|
|
|
-
|
|
|
- <section>
|
|
|
- <title>S46 DMR Option</title>
|
|
|
- <para>
|
|
|
- The S46 DMR option is used to convey values for the Default
|
|
|
- Mapping Rule (DMR). This option is mandatory in the MAP-T
|
|
|
- container option and not permitted in the MAP-E and S46
|
|
|
- Lightweight 4over6 Container options.
|
|
|
-<screen>
|
|
|
-{
|
|
|
- "space": "s46-cont-mapt-options",
|
|
|
- "name": "s46-dmr",
|
|
|
- "data": "2001:db8:cafe::/64",
|
|
|
-}
|
|
|
-</screen>
|
|
|
- This option must not be included in other containers.
|
|
|
- </para>
|
|
|
- </section>
|
|
|
-
|
|
|
- <section>
|
|
|
- <title>S46 IPv4/IPv6 Address Binding option.</title>
|
|
|
- <para>
|
|
|
- The S46 IPv4/IPv6 Address Binding option may be used to specify
|
|
|
- the full or shared IPv4 address of the Customer Edge (CE).
|
|
|
- The IPv6 prefix field is used by the CE to identify the
|
|
|
- correct prefix to use for the tunnel source.
|
|
|
-<screen>
|
|
|
-{
|
|
|
- "space": "s46-cont-lw",
|
|
|
- "name": "s46-v4v6bind",
|
|
|
- "data": "192.0.2.3, 2001:db8:1:cafe::/64"
|
|
|
-}
|
|
|
-</screen>
|
|
|
- This option must not be included in other containers.
|
|
|
- </para>
|
|
|
- </section>
|
|
|
- <section>
|
|
|
- <title>S46 Port Parameters</title>
|
|
|
- <para>
|
|
|
- The S46 Port Parameters option specifies optional port set
|
|
|
- information that MAY be provided to CEs
|
|
|
-<screen>
|
|
|
-{
|
|
|
- "space": "s46-rule-options",
|
|
|
- "name": "s46-portparams",
|
|
|
- "data": "2, 3/4",
|
|
|
-}
|
|
|
-</screen>
|
|
|
- Other possible "space" value is "s46-v4v6bind" to include
|
|
|
- this option in the S46 IPv4/IPv6 Address Binding option.
|
|
|
- </para>
|
|
|
- <para>
|
|
|
- Note that the second value in the example above specifies the
|
|
|
- PSID and PSID length fields in the format of PSID/PSID length.
|
|
|
- This is equivalent to the values of PSID-len=4 and
|
|
|
- PSID=12288 conveyed in the S46 Port Parameters option.
|
|
|
- </para>
|
|
|
- </section>
|
|
|
- </section>
|
|
|
-
|
|
|
<section id="dhcp6-custom-options">
|
|
|
<title>Custom DHCPv6 Options</title>
|
|
|
<para>It is possible to define options in addition to the standard ones.
|
|
@@ -4166,20 +3977,18 @@ If not specified, the default value is:
|
|
|
different for each pool.
|
|
|
</para>
|
|
|
<para>
|
|
|
- Let's consider a lightweight 4over6 deployment as an example. It is an
|
|
|
- IPv6 transition technology that allows mapping IPv6 prefix into full
|
|
|
- or parts of IPv4 addresses. In DHCP context, these are certain
|
|
|
- parameters that are supposed to be delivered to clients in form of
|
|
|
- additional options. Values of those options are correlated to
|
|
|
- delegated prefixes, so it is reasonable to keep those parameters
|
|
|
- together with the PD pool. On the other hand, lightweight 4over6 is
|
|
|
- not a commonly used feature, so it is not a part of the base Kea
|
|
|
- code. The solution to this problem is to use user context. For each PD
|
|
|
- pool that is expected to be used for lightweight 4over6, user context
|
|
|
- with extra parameters is defined. Those extra parameters will be used
|
|
|
- by hook library that would be loaded only when dynamic calculation of
|
|
|
- the lightweight 4over6 option is actually needed. An example
|
|
|
- configuration looks as follows:
|
|
|
+ Let's consider an example where certain parameters are supposed
|
|
|
+ to be delivered to clients in form of additional options,
|
|
|
+ and the values of those options are correlated to delegated
|
|
|
+ prefixes. It seems reasonable to keep those parameters with
|
|
|
+ the the definition of the PD pool. On the other hand, this
|
|
|
+ functionality is is not part of the base Kea code so Kea will
|
|
|
+ not understand any hook-specific keywords in that definition.
|
|
|
+ The solution to this problem is to use user context. For
|
|
|
+ each PD pool that is expected to be used with this feature,
|
|
|
+ a "user context" is defined. This is a structure that holds the
|
|
|
+ parameters used by the hook library when it is loaded.
|
|
|
+ An example configuration could look as follows:
|
|
|
<screen>
|
|
|
"Dhcp4": {
|
|
|
"subnet6": [ {
|
|
@@ -4189,10 +3998,10 @@ If not specified, the default value is:
|
|
|
"prefix-len": 56,
|
|
|
"delegated-len": 64,
|
|
|
<userinput>"user-context": {
|
|
|
- "lw4over6-sharing-ratio": 64,
|
|
|
- "lw4over6-v4-pool": "192.0.2.0/24",
|
|
|
- "lw4over6-sysports-exclude": true,
|
|
|
- "lw4over6-bind-prefix-len": 56
|
|
|
+ "sharing-ratio": 64,
|
|
|
+ "v4-pool": "192.0.2.0/24",
|
|
|
+ "sysports-exclude": true,
|
|
|
+ "bind-prefix-len": 56
|
|
|
}</userinput>
|
|
|
} ],
|
|
|
"subnet": "2001:db8::/32"
|
|
@@ -4202,8 +4011,8 @@ If not specified, the default value is:
|
|
|
</para>
|
|
|
|
|
|
<para>
|
|
|
- It should be noted that Kea will not use any information in the user
|
|
|
- context, but will simply store and make it available to the hook
|
|
|
+ Kea does not interpret or use the information in the user context:
|
|
|
+ it just stores it makes it available to the hook
|
|
|
libraries. It is up to the hook library to extract that information
|
|
|
and make use of it.
|
|
|
</para>
|
|
@@ -4285,13 +4094,6 @@ If not specified, the default value is:
|
|
|
7550</ulink>: All recommendations related to the DHCPv6 server
|
|
|
operation are supported.</simpara>
|
|
|
</listitem>
|
|
|
- <listitem>
|
|
|
- <simpara><emphasis>DHCPv6 Options for Configuration of Softwire
|
|
|
- Address and Port-Mapped Clients</emphasis>,
|
|
|
- <ulink url="http://tools.ietf.org/html/rfc7598">RFC
|
|
|
- 7598</ulink>: All options specified in this specification are
|
|
|
- supported by the DHCPv6 server.</simpara>
|
|
|
- </listitem>
|
|
|
</itemizedlist>
|
|
|
</section>
|
|
|
|