dhcp6-srv.xml 115 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY mdash  "&#x2014;" >
]>

  <chapter id="dhcp6">
    <title>The DHCPv6 Server</title>

    <section id="dhcp6-start-stop">
      <title>Starting and Stopping the DHCPv6 Server</title>

      <para>
14
      It is recommended that the Kea DHCPv6 server be started and stopped
Jeremy C. Reed's avatar
Jeremy C. Reed committed
15
      using <command>keactrl</command> (described in <xref linkend="keactrl"/>).
16 17
      However, it is also possible to run the server directly: it accepts
      the following command-line switches:
18 19
      </para>

20 21
      <itemizedlist>
          <listitem>
22 23 24 25
            <simpara>
            <command>-c <replaceable>file</replaceable></command> -
            specifies the configuration file. This is the only mandatory
            switch.</simpara>
26 27
          </listitem>
          <listitem>
28
            <simpara>
29
            <command>-d</command> - specifies whether the server
30
            logging should be switched to verbose mode. In verbose mode,
31
            the logging severity and debuglevel specified in the configuration
32 33 34 35
            file are ignored and "debug" severity and the maximum debuglevel
            (99) are assumed. The flag is convenient, for temporarily
            switching the server into maximum verbosity, e.g. when
            debugging.</simpara>
36 37
          </listitem>
          <listitem>
38 39
            <simpara>
            <command>-p <replaceable>port</replaceable></command> -
40 41
            specifies UDP port on which the server will listen. This is only
            useful during testing, as a DHCPv6 server listening on
42 43
            ports other than default DHCPv6 ports will not be able to
            handle regular DHCPv6 queries.</simpara>
44
          </listitem>
Tomek Mrugalski's avatar
Tomek Mrugalski committed
45 46
          <listitem>
            <simpara>
Tomek Mrugalski's avatar
Tomek Mrugalski committed
47
              <command>-v</command> - prints out Kea version and exits.
Tomek Mrugalski's avatar
Tomek Mrugalski committed
48 49 50 51 52
            </simpara>
          </listitem>
          <listitem>
            <simpara>
              <command>-V</command> - prints out Kea extended version with
Tomek Mrugalski's avatar
Tomek Mrugalski committed
53
              additional parameters and exits.
Tomek Mrugalski's avatar
Tomek Mrugalski committed
54 55
            </simpara>
          </listitem>
56 57 58 59 60 61
          <listitem>
            <simpara>
              <command>-W</command> - prints out Kea configuration report
              and exits.
            </simpara>
          </listitem>
62 63
      </itemizedlist>

64 65 66 67 68 69 70
      <para>
            The <command>-V</command> returns the versions of the
            external libraries dynamically linked, at the opposite
            the <command>-W</command> describes the environment used
            to build Kea.
      </para>

71
      <para>
72 73
            All of the executable binaries in Kea contain an embedded
            copy of the <filename>config.report</filename>
74 75 76
            file produced by <userinput>./configure</userinput>
            and displayed by the <command>-W</command> command,
            but is accessible in some other ways when needed.
77
            The following command may be used to extract this information.
78
            The binary <userinput>path</userinput> may be found in the
79 80 81 82
            install directory or in the <filename>.libs</filename>
            subdirectory in the source treee. For example
            <filename>kea/src/bin/dhcp6/.libs/kea-dhcp6</filename>.

83 84 85 86 87 88
<screen>
strings <userinput>path</userinput>/kea-dhcp6 | sed -n 's/;;;; //p'
</screen>
      </para>

      <para>
89 90 91
	    When running in a console, the server can be shut down by
	    pressing ctrl-c. It detects the key combination and shuts
	    down gracefully.
92 93 94
      </para>

      <para>
95
        On start-up, the server will detect available network interfaces
96 97
        and will attempt to open UDP sockets on all interfaces
        mentioned in the configuration file.
98 99 100
      </para>

      <para>
101 102
        Since the DHCPv6 server opens privileged ports, it requires root
        access. Make sure you run this daemon as root.
103 104 105 106 107 108
      </para>

    </section>

    <section id="dhcp6-configuration">
      <title>DHCPv6 Server Configuration</title>
109 110 111 112


<section>
  <title>Introduction</title>
113
      <para>
114
        This section explains how to configure the DHCPv6 server using the
115 116
        Kea configuration backend. (Kea configuration using any other
        backends is outside of scope of this document.) Before DHCPv6
117 118
        is started, its configuration file has to be created. The
        basic configuration looks as follows:
119
<screen>
120
{
121
# DHCPv6 configuration starts on the next line
122 123 124 125 126 127 128 129
"Dhcp6": {

# First we set up global values
    "renew-timer": 1000,
    "rebind-timer": 2000,
    "preferred-lifetime": 3000,
    "valid-lifetime": 4000,

130 131 132 133 134 135
# Next we setup the interfaces to be used by the server.
    "interfaces-config": {
        "interfaces": [ "eth0" ]
    },

# And we specify the type of a lease database
136 137
    "lease-database": {
        "type": "memfile",
138
        "persist": true,
139 140 141 142 143 144 145 146 147 148 149 150 151 152
        "name": "/var/kea/dhcp6.leases"
    },

# Finally, we list the subnets from which we will be leasing addresses.
    "subnet6": [
        {
            "subnet": "2001:db8:1::/64",
            "pools": [
                 {
                     "pool": "2001:db8:1::1-2001:db8:1::ffff"
                 }
             ]
        }
    ]
153
# DHCPv6 configuration ends with the next line
154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173
}

} </screen>
</para>

<para>The following paragraphs provide a brief overview of the parameters in
the above example and
their format. Subsequent sections of this chapter go into much greater detail
for these and other parameters.</para>

<para>The lines starting with a hash (#) are comments and are ignored by
the server; they do not impact its
operation in any way.</para>

<para>The configuration starts in the first line with the initial
opening curly bracket (or brace). Each configuration consists of
one or more objects. In this specific example, we have only one
object called Dhcp6. This is a simplified configuration, as usually
there will be additional objects, like <command>Logging</command> or
<command>DhcpDns</command>, but we omit them now for clarity. The Dhcp6
174
configuration starts with the <command>"Dhcp6": {</command> line
175 176 177 178
and ends with the corresponding closing brace (in the above example,
the brace after the last comment).  Everything defined between those
lines is considered to be the Dhcp6 configuration.</para>

179
<para>In the general case, the order in which those parameters appear does not
180
matter. There are two caveats here though. The first one is to remember that
181 182 183
the configuration file must be well formed JSON. That means that parameters
for any given scope must be separated by a comma and there must not be a comma
after the last parameter. When reordering a configuration file, keep in mind that
184
moving a parameter to or from the last position in a given scope may require
185 186
moving the comma as well. The second caveat is that it is uncommon &mdash; although
legal JSON &mdash; to
187 188 189 190 191 192
repeat the same parameter multiple times. If that happens, the last occurrence of a
given parameter in a given scope is used while all previous instances are
ignored. This is unlikely to cause any confusion as there are no real life
reasons to keep multiple copies of the same parameter in your configuration
file.</para>

193 194
<para>Moving onto the DHCPv6 configuration elements, the very first few elements
define some global parameters. <command>valid-lifetime</command>
195
defines for how long the addresses (leases) given out by the server are valid. If
196
nothing changes, a client that got an address is allowed to use it for 4000
197 198 199 200 201
seconds. (Note that integer numbers are specified as is, without any quotes
around them.) The address will become deprecated in 3000 seconds (clients are
allowed to keep old connections, but can't use this address for creating new
connections). <command>renew-timer</command> and <command>
rebind-timer</command> are values that define T1 and T2 timers that govern when
202
the client will begin the renewal and rebind procedures.</para>
203

204 205 206 207 208 209 210 211 212 213 214 215 216 217
<para>The <command>interfaces-config</command> map specifies the server
configuration concerning the network interfaces, on which the server should
listen to the DHCP messages. The <command>interfaces</command> parameter
specifies a list of network interfaces on which the server should listen.
Lists are opened and closed with square brackets, with elements separated
by commas. Had we wanted to listen on two interfaces, the
<command>interfaces-config</command> would look like this:
<screen>
"interfaces-config": {
    "interfaces": [ "eth0", "eth1" ]
},
</screen>
</para>

218
<para>The next couple of lines define the lease database, the place where the server
219 220
stores its lease information. This particular example tells the server to use
<command>memfile</command>, which is the simplest (and fastest) database
221
backend. It uses an in-memory database and stores leases on disk in a CSV
222 223 224 225 226 227 228 229 230 231 232
file. This is a very simple configuration. Usually, lease database configuration
is more extensive and contains additional parameters.  Note that
<command>lease-database</command>
is an object and opens up a new scope, using an opening brace.
Its parameters (just one in this example -- <command>type</command>)
follow. Had there been more than one, they would be separated by commas. This
scope is closed with a closing brace. As more parameters follow, a trailing
comma is present.</para>

<para>Finally, we need to define a list of IPv6 subnets. This is the
most important DHCPv6 configuration structure as the server uses that
233 234
information to process clients' requests. It defines all subnets from
which the server is expected to receive DHCP requests. The subnets are
235 236
specified with the <command>subnet6</command> parameter.  It is a list,
so it starts and ends with square brackets.  Each subnet definition in
237
the list has several attributes associated with it, so it is a structure
238 239 240 241 242 243 244 245 246 247
and is opened and closed with braces. At minimum, a subnet definition
has to have at least two parameters: <command>subnet</command> (that
defines the whole subnet) and <command>pool</command> (which is a list of
dynamically allocated pools that are governed by the DHCP server).</para>

<para>The example contains a single subnet. Had more than one been defined,
additional elements
in the <command>subnet6</command> parameter would be specified and
separated by commas. For example, to define two subnets, the following
syntax would be used:
248
<screen>
249 250 251 252 253 254 255 256 257 258
"subnet6": [
    {
        "pools": [
        {
            "pool": "2001:db8:1::/112"
        }
        ],
        "subnet": "2001:db8:1::/64"
    },
    {
259 260
        "pools": [ { "pool": "2001:db8:2::1-2001:db8:2::ffff" } ],
        "subnet": "2001:db8:2::/64",
261 262 263
        "interface": "eth0"
    }
]
264
</screen>
265 266
Note that indentation is optional and is used for aesthetic purposes only.
In some cases in may be preferable to use more compact notation.
267
</para>
268

269

270 271
<para>After all parameters are specified, we have two contexts open:
global and Dhcp6, hence we need two closing curly brackets to close them.
272 273
In a real life configuration file there most likely would be additional
components defined such as Logging or DhcpDdns, so the closing brace would
274 275 276 277 278 279 280 281 282 283
be followed by a comma and another object definition.</para>

</section>

<section>
  <title>Lease Storage</title>
  <para>All leases issued by the server are stored in the lease database.
  Currently there are three database backends available:
  memfile (which is the default backend), MySQL and PostgreSQL.</para>
<section>
284
  <title>Memfile, Basic Storage for Leases</title>
285 286 287

  <para>The server is able to store lease data in different repositories. Larger
  deployments may elect to store leases in a database. <xref
288
  linkend="database-configuration6"/> describes this option. In typical
289 290 291 292 293 294
  smaller deployments though, the server will use a CSV file rather than a database to
  store lease information. As well as requiring less administration, an
  advantage of using a file for storage is that it
  eliminates a dependency on third-party database software.</para>

  <para>The configuration of the file backend (Memfile) is controlled through
295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338
  the Dhcp6/lease-database parameters. The <command>type</command> parameter
  is mandatory and it specifies which storage for leases the server should use.
  The value of <userinput>"memfile"</userinput> indicates that the file should
  be used as the storage. The following list presents the remaining, not mandatory
  parameters, which can be used to configure the Memfile backend.

  <itemizedlist>
    <listitem>
      <simpara><command>persist</command>: controls whether the new leases and
      updates to existing leases are written to the file. It is strongly
      recommended that the value of this parameter is set to
      <userinput>true</userinput> at all times, during the server's normal
      operation. Not writing leases to disk will mean that if a server is restarted
      (e.g. after a power failure), it will not know what addresses have been
      assigned.  As a result, it may hand out addresses to new clients that are
      already in use. The value of <userinput>false</userinput> is mostly useful
      for performance testing purposes. The default value of the
      <command>persist</command> parameter is <userinput>true</userinput>,
      which enables writing lease updates
      to the lease file.
      </simpara>
    </listitem>

    <listitem>
      <simpara><command>name</command>: specifies an absolute location of the lease
      file in which new leases and lease updates will be recorded. The default value
      for this parameter is <userinput>"[kea-install-dir]/var/kea/kea-leases6.csv"
      </userinput>.</simpara>
    </listitem>

    <listitem>
      <simpara><command>lfc-interval</command>: specifies the interval in seconds, at
      which the server (Memfile backend) will perform a lease file cleanup (LFC),
      which removes the redundant (historical) information from the lease file
      and effectively reduces the lease file size. The cleanup process is described
      in more detailed fashion further in this section. The default value of the
      <command>lfc-interval</command> is <userinput>0</userinput>, which disables
      the LFC.</simpara>
    </listitem>

  </itemizedlist>
  </para>

  <para>The example configuration of the Memfile backend is presented below:
Jeremy C. Reed's avatar
Jeremy C. Reed committed
339

340
<screen>
341
"Dhcp6": {
342 343
    "lease-database": {
        <userinput>"type": "memfile"</userinput>,
344
        <userinput>"persist": true</userinput>,
345 346
        <userinput>"name": "/tmp/kea-leases6.csv"</userinput>,
        <userinput>"lfc-interval": 1800</userinput>
347 348 349 350 351
    }
}
</screen>
  </para>

352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395
  <para>It is important to know how the lease file contents are organized
  to understand why the periodic lease file cleanup is needed. Every time when
  the server updates a lease or creates a new lease for the client, the new
  lease information must be recorded in the lease file. For performance reasons,
  the server does not supersede the existing client's lease, as it would require
  the lookup of the specific lease entry, but simply appends the new lease
  information at the end of the lease file. The previous lease entries for the
  client are not removed. When the server loads leases from the lease file, e.g.
  at the server startup, it assumes that the latest lease entry for the client
  is the valid one. The previous entries are discarded. This means that the
  server can re-construct the accurate information about the leases even though
  there may be many lease entries for each client. However, storing many entries
  for each client results in bloated lease file and impairs the performance of
  the server's startup and reconfiguration, as it needs to process larger number
  of lease entries.
  </para>

  <para>The lease file cleanup removes all previous entries for each client and
  leaves only the latest ones. The interval at which the cleanup is performed
  is configurable, and it should be selected according to the frequency of lease
  renewals initiated by the clients. The more frequent renewals are, the lesser
  value of the <command>lfc-interval</command> should be. Note however, that the
  LFC takes time and thus it is possible (although unlikely) that new cleanup
  is started while the previous cleanup instance is still running, if the
  <command>lfc-interval</command> is too short. The server would recover from
  this by skipping the new cleanup when it detects that the previous cleanup
  is still in progress. But, this implies that the actual cleanups will be
  triggered more rarely than configured. Moreover, triggering a new cleanup
  adds an overhead to the server, which will not be able to respond to new
  requests for a short period of time when the new cleanup process is spawned.
  Therefore, it is recommended that the <command>lfc-interval</command> value
  is selected in a way that would allow for completing the cleanup before the
  new cleanup is triggered.
  </para>

  <para>The LFC is performed by a separate process (in background) to avoid
  performance impact on the server process. In order to avoid the conflicts
  between the two processes both using the same lease files, the LFC process
  operates on the copy of the original lease file, rather than on the lease
  file used by the server to record lease updates. There are also other files
  being created as a side effect of the lease file cleanup. The detailed
  description of the LFC is located on the Kea wiki:
  <ulink url="http://kea.isc.org/wiki/LFCDesign"/>.
  </para>
396 397 398 399 400 401 402 403 404 405 406 407 408 409 410
</section>

<section id="database-configuration6">
  <title>Database Configuration</title>

  <note>
    <para>Database access information must be configured for the DHCPv6 server,
    even if it has already been configured for the DHCPv4 server.  The servers
    store their information independently, so each server can use a separate
    database or both servers can use the same database.</para>
  </note>

  <para>Database configuration is controlled through the Dhcp6/lease-database
  parameters. The type of the database must be set to "mysql" or "postgresql",
  e.g.
411
<screen>
412
"Dhcp6": { "lease-database": { <userinput>"type": "mysql"</userinput>, ... }, ... }
413
</screen>
414
  Next, the name of the database is to hold the leases must be set: this is the
415 416
  name used when the lease database was created (see <xref linkend="mysql-database-create"/>
  or <xref linkend="pgsql-database-create"/>).
417
<screen>
418
"Dhcp6": { "lease-database": { <userinput>"name": "<replaceable>database-name</replaceable>" </userinput>, ... }, ... }
419
</screen>
420 421 422
  If the database is located on a different system than the DHCPv6 server, the
  database host name must also be specified (although it should be noted that this
  configuration may have a severe impact on server performance):
423
<screen>
424
"Dhcp6": { "lease-database": { <userinput>"host": <replaceable>remote-host-name</replaceable></userinput>, ... }, ... }
425
</screen>
426 427
  The usual state of affairs will be to have the database on the same machine as
  the DHCPv6 server.  In this case, set the value to the empty string:
428
<screen>
429
"Dhcp6": { "lease-database": { <userinput>"host" : ""</userinput>, ... }, ... }
430
</screen>
431 432 433
  </para>
  <para>Finally, the credentials of the account under which the server will
  access the database should be set:
434
<screen>
435
"Dhcp6": { "lease-database": { <userinput>"user": "<replaceable>user-name</replaceable>"</userinput>,
436
                               <userinput>"password": "<replaceable>password</replaceable>"</userinput>,
437 438
                              ... },
           ... }
439
</screen>
440 441 442 443
  If there is no password to the account, set the password to the empty string
  "". (This is also the default.)</para>
</section>
</section>
444

445 446 447
<section id="dhcp6-interface-selection">
  <title>Interface selection</title>
  <para>The DHCPv6 server has to be configured to listen on specific network
448
  interfaces.  The simplest network interface configuration instructs the server to
449 450
  listen on all available interfaces:
  <screen>
451 452 453 454 455 456 457
"Dhcp6": {
    "interfaces-config": {
        "interfaces": [ <userinput>"*"</userinput> ]
    }
    ...
}
</screen>
458 459 460
  The asterisk plays the role of a wildcard and means "listen on all interfaces".
  However, it is usually a good idea to explicitly specify interface names:
  <screen>
461 462 463 464 465 466 467 468
"Dhcp6": {
    "interfaces-config": {
        "interfaces": [ <userinput>"eth1", "eth3"</userinput> ]
    },
    ...
}
  </screen>
</para>
469
  <para>It is possible to use wildcard interface name (asterisk) concurrently
470
  with the actual interface names:
471
  <screen>
472 473 474 475 476 477 478
"Dhcp6": {
    "interfaces-config": {
        "interfaces": [ <userinput>"eth1", "eth3", "*"</userinput> ]
    },
    ...
}
  </screen>
479 480 481 482
It is anticipated that this will form of usage only be used where it is desired to
temporarily override a list of interface names and listen on all interfaces.
  </para>
</section>
483 484 485 486

    <section id="ipv6-subnet-id">
      <title>IPv6 Subnet Identifier</title>
      <para>
487
        The subnet identifier is a unique number associated with a particular subnet.
488
        In principle, it is used to associate clients' leases with respective subnets.
489
        When the subnet identifier is not specified for a subnet being configured, it will
490 491 492 493 494 495 496
        be automatically assigned by the configuration mechanism. The identifiers
        are assigned from 1 and are monotonically increased for each subsequent
        subnet: 1, 2, 3 ....
      </para>
      <para>
       If there are multiple subnets configured with auto-generated identifiers and
       one of them is removed, the subnet identifiers may be renumbered. For example:
497 498 499
       if there are four subnets and the third is removed the last subnet will be assigned
       the identifier that the third subnet had before removal. As a result, the leases
       stored in the lease database for subnet 3 are now associated with
500
       subnet 4, which may have unexpected consequences. In the future it is planned
501
       to implement a mechanism to preserve auto-generated subnet ids upon removal
502
       of one of the subnets. Currently, the only remedy for this issue is to
503
       manually specify a unique subnet identifier for each subnet.
504
      </para>
505

506
      <para>
507
	The following configuration will assign the specified subnet
508 509
	identifier to the newly configured subnet:

510 511 512
	<screen>
"Dhcp6": {
    "subnet6": [
513 514 515 516 517
        {
            "subnet": "2001:db8:1::/64",
            <userinput>"id": 1024</userinput>,
            ...
        }
518 519 520 521 522 523
    ]
}
</screen>
	This identifier will not change for this subnet unless the "id" parameter is
	removed or set to 0. The value of 0 forces auto-generation of the subnet
	identifier.
524
      </para>
525 526
      <!-- @todo: describe whether database needs to be updated after changing
      id -->
527 528 529 530 531
    </section>

    <section id="dhcp6-unicast">
      <title>Unicast traffic support</title>
      <para>
532
        When the DHCPv6 server starts, by default it listens to the DHCP traffic
533 534 535 536 537
        sent to multicast address ff02::1:2 on each interface that it is
        configured to listen on (see <xref linkend="dhcp6-interface-selection"/>).
        In some cases it is useful to configure a server to handle incoming
        traffic sent to the global unicast addresses as well. The most common
        reason for that is to have relays send their traffic to the server
538 539 540 541
        directly. To configure the server to listen on a specific unicast address, the
        notation to specify interfaces has been extended.  An interface name can be
        optionally followed by a slash, followed by the global unicast address on which
        the server should listen. This will be done in addition to normal
542 543
        link-local binding + listening on ff02::1:2 address. The sample configuration
        below shows how to listen on 2001:db8::1 (a global address)
544 545 546
        configured on the eth1 interface.
      </para>
      <para>
547 548
 <screen>
"Dhcp6": {
549 550 551
    "interfaces-config": {
        "interfaces": [ <userinput>"eth1/2001:db8::1"</userinput> ]
    },
552
    ...
553 554
}
 </screen>
555

556
        This configuration will cause the server to listen on
557 558 559 560
        eth1 on link-local address, multicast group (ff02::1:2) and 2001:db8::1.
      </para>
      <para>
        It is possible to mix interface names, wildcards and interface name/addresses
561
        on the list of interfaces. It is not possible to specify more than one
562 563 564 565 566
        unicast address on a given interface.
      </para>
      <para>
        Care should be taken to specify proper unicast addresses. The server will
        attempt to bind to those addresses specified, without any additional checks.
567 568
        This approach is selected on purpose, so the software can be used to
        communicate over uncommon addresses if the administrator so desires.
569 570 571 572 573 574 575 576 577 578 579 580 581 582
      </para>
    </section>

    <section id="dhcp6-address-config">
      <title>Subnet and Address Pool</title>
      <para>
        The essential role of a DHCPv6 server is address assignment. For this,
        the server has to be configured with at least one subnet and one pool of dynamic
        addresses to be managed. For example, assume that the server
        is connected to a network segment that uses the 2001:db8:1::/64
        prefix. The Administrator of that network has decided that addresses from range
        2001:db8:1::1 to 2001:db8:1::ffff are going to be managed by the Dhcp6
        server. Such a configuration can be achieved in the following way:
        <screen>
583 584 585 586 587 588
"Dhcp6": {
    <userinput>"subnet6": [
       {
           "subnet": "2001:db8:1::/64",
           "pools": [
               {
589
                   "pool": "2001:db8:1::1-2001:db8:1::ffff"
590 591 592 593 594 595 596
               }
           ],
           ...
       }
    ]</userinput>
}</screen>

597 598 599 600
        Note that subnet is defined as a simple string, but the pool parameter
        is actually a list of pools: for this reason, the pool definition is
        enclosed in square brackets, even though only one range of addresses
        is specified.</para>
601 602

        <para>Each <command>pool</command> is a structure that contains the
603
        parameters that describe a single pool. Currently there is only one
604 605 606 607
        parameter, <command>pool</command>, which gives the range of addresses
        in the pool. Additional parameters will be added in future releases of
        Kea.</para>

608 609
        <para>It is possible to define more than one pool in a
        subnet: continuing the previous example, further assume that
610
        2001:db8:1:0:5::/80 should also be managed by the server. It could be written as
611 612 613 614 615
        2001:db8:1:0:5:: to 2001:db8:1::5:ffff:ffff:ffff, but typing so many 'f's
        is cumbersome. It can be expressed more simply as 2001:db8:1:0:5::/80. Both
        formats are supported by Dhcp6 and can be mixed in the pool list.
        For example, one could define the following pools:
        <screen>
616 617 618 619 620
"Dhcp6": {
    <userinput>"subnet6": [
    {
        "subnet": "2001:db8:1::/64",
        "pools": [
621 622
            { "pool": "2001:db8:1::1-2001:db8:1::ffff" },
            { "pool": "2001:db8:1:05::/80" }
623 624 625 626 627
        ]</userinput>,
        ...
    }
    ]
}</screen>
628 629 630 631 632 633 634
        The number of pools is not limited, but for performance reasons it is recommended to
        use as few as possible.
      </para>
      <para>
         The server may be configured to serve more than one subnet. To add a second subnet,
         use a command similar to the following:
        <screen>
635 636 637 638 639
"Dhcp6": {
    <userinput>"subnet6": [
    {
        "subnet": "2001:db8:1::/64",
        "pools": [
640
            { "pool": "2001:db8:1::1-2001:db8:1::ffff" }
641 642 643 644 645
        ]
    },
    {
        "subnet": "2001:db8:2::/64",
        "pools": [
646
            { "pool": "2001:db8:2::/64" }
647 648 649 650 651 652
        ]
    },
</userinput>
        ...
    ]
}</screen>
653
        In this example, we allow the server to
654
        dynamically assign all addresses available in the whole subnet. Although
655
        rather wasteful, it is certainly a valid configuration to dedicate the
656
        whole /64 subnet for that purpose. Note that the Kea server does not preallocate
657
        the leases, so there is no danger in using gigantic address pools.
658 659 660
      </para>
      <para>
        When configuring a DHCPv6 server using prefix/length notation, please pay
661 662
        attention to the boundary values. When specifying that the server can use
        a given pool, it will also be able to allocate the first (typically network
663 664 665
        address) address from that pool. For example for pool 2001:db8:2::/64 the
        2001:db8:2:: address may be assigned as well. If you want to avoid this,
        use the "min-max" notation.
666 667 668 669 670 671 672
      </para>
    </section>

    <section>
<!-- @todo: add real meat to the prefix delegation config this is just place holder stuff -->
      <title>Subnet and Prefix Delegation Pools</title>
      <para>
673
        Subnets may also be configured to delegate prefixes, as defined in
674
	    <ulink url="http://tools.ietf.org/html/rfc3633">RFC 3633</ulink>.
675 676
        A subnet may have one or more prefix delegation pools.  Each pool has
        a prefixed address, which is specified as a prefix and a prefix length,
677
        as well as a delegated prefix length. <command>delegated-len</command>
678 679 680 681
	    must not be shorter (that is it must be numerically greater or equal)
	    than <command>prefix-len</command>.
	    If both <command>delegated-len</command>
	    and <command>prefix-len</command> are equal, the server will be able to
682 683
	    delegate only one prefix. The delegated <command>prefix</command> does
        not have to match the <command>subnet</command> prefix.
684 685 686
      </para>
      <para> Below is a sample subnet configuration which enables prefix
      delegation for the subnet:
687
      <screen>
688 689 690 691 692 693
"Dhcp6": {
    "subnet6": [
        {
            "subnet": "2001:d8b:1::/64",
            <userinput>"pd-pools": [
                {
694
                    "prefix": "3000:1::",
695 696 697 698 699 700 701 702
                    "prefix-len": 64,
                    "delegated-len": 96
                }
            ]</userinput>
        }
    ],
    ...
}</screen>
703 704 705 706 707 708
      </para>
    </section>

    <section id="dhcp6-std-options">
      <title>Standard DHCPv6 options</title>
      <para>
709 710
        One of the major features of a DHCPv6 server is to provide configuration
        options to clients.  Although there are several options that require
711
        special behavior, most options are sent by the server only if the client
712
        explicitly requests them.  The following example shows how to
713
        configure DNS servers, which is one of the most frequently used
714 715
        options.  Numbers in the first column are added for easier reference and
        will not appear on screen.  Options specified in this way are considered
716 717 718
        global and apply to all configured subnets.

        <screen>
719
"Dhcp6": {
720 721 722 723 724
    "option-data": [
        {
           <userinput>"name": "dns-servers",
           "code": 23,
           "space": "dhcp6",
725
           "csv-format": true,
726 727 728 729 730
           "data": "2001:db8::cafe, 2001:db8::babe"</userinput>
        },
        ...
    ]
}
731 732
</screen>
      </para>
733

734
    <para>
735 736
      The <command>option-data></command> line creates a new entry in
      the option-data table.  This table contains
737
      information on all global options that the server is supposed to configure
738
      in all subnets.  The <command>name</command> line specifies the option name.
739
      (For a complete list
740
      of currently supported names, see <xref
741
      linkend="dhcp6-std-options-list"/>.)  The next line specifies the option code,
742 743 744
      which must match one of the values from that list. The line beginning with
      <command>space</command> specifies the option space, which must always be set
      to "dhcp6" as these are standard DHCPv6 options.  For other name spaces,
745
      including custom option spaces, see <xref
746
      linkend="dhcp6-option-spaces"/>. The next line specifies the format in
747
      which the data will be entered: use of CSV (comma separated values) is
748 749
      recommended. The <command>data</command> line gives the actual value to be sent to
      clients.  Data is specified as normal text, with values separated by
750
      commas if more than one value is allowed.
751 752 753
    </para>

    <para>
754
      Options can also be configured as hexadecimal values.  If "csv-format" is
755
      set to false, the option data must be specified as a string of hexadecimal
756
      numbers.  The
757 758 759
      following commands configure the DNS-SERVERS option for all
      subnets with the following addresses: 2001:db8:1::cafe and
      2001:db8:1::babe.
760
        <screen>
761
"Dhcp6": {
762 763 764 765 766
    "option-data": [
        {
           <userinput>"name": "dns-servers",
           "code": 23,
           "space": "dhcp6",
767
           "csv-format": false,
768 769 770 771 772 773 774 775 776 777
           "data": "2001 0DB8 0001 0000 0000 0000 0000 CAFE
                    2001 0DB8 0001 0000 0000 0000 0000 BABE"</userinput>
        },
        ...
    ]
}
</screen>

       The value for the setting of the "data" element is split across two
       lines in this document for clarity: when entering the command, the
778
       whole string should be entered on the same line.  Care should be taken
779 780
       to use proper encoding when using hexadecimal format as Kea's ability
       to validate data correctness in hexadecimal is limited.
781 782
      </para>

783 784 785 786 787 788 789
      <para>
        Most of the parameters in the "option-data" structure are optional and
        can be omitted in some circumstances as discussed in the
        <xref linkend="dhcp6-option-data-defaults"/>.
      </para>


790 791 792 793 794 795 796 797 798 799 800 801 802 803
    <para>
      It is possible to override options on a per-subnet basis.  If
      clients connected to most of your subnets are expected to get the
      same values of a given option, you should use global options: you
      can then override specific values for a small number of subnets.
      On the other hand, if you use different values in each subnet,
      it does not make sense to specify global option values
      (Dhcp6/option-data), rather you should set only subnet-specific values
      (Dhcp6/subnet[X]/option-data[Y]).
     </para>
     <para>
      The following commands override the global
      DNS servers option for a particular subnet, setting a single DNS
      server with address 2001:db8:1::3.
804 805 806 807 808 809 810 811
<screen>
"Dhcp6": {
    "subnet6": [
        {
            <userinput>"option-data": [
                {
                    "name": "dns-servers",
                    "code": 23,
Jeremy C. Reed's avatar
Jeremy C. Reed committed
812
                    "space": "dhcp6",
813
                    "csv-format": true,
814 815 816 817 818 819 820 821 822 823 824
                    "data": "2001:db8:1::3"
                },
                ...
            ]</userinput>,
            ...
        },
        ...
    ],
    ...
}
</screen>
825 826 827 828 829 830 831 832 833 834 835 836 837
    </para>

    <para>
      The currently supported standard DHCPv6 options are
      listed in <xref linkend="dhcp6-std-options-list"/>.
      The "Name" and "Code"
      are the values that should be used as a name in the option-data
      structures. "Type" designates the format of the data: the meanings of
      the various types is given in <xref linkend="dhcp-types"/>.
    </para>
    <para>
      Some options are designated as arrays, which means that more than one
      value is allowed in such an option. For example the option dns-servers
838
      allows the specification of more than one IPv6 address, allowing
839
      clients to obtain the addresses of multiple DNS servers.
840 841 842 843 844 845 846 847 848 849 850 851 852 853
    </para>

<!-- @todo: describe record types -->

      <para>
        The <xref linkend="dhcp6-custom-options"/> describes the configuration
        syntax to create custom option definitions (formats). It is generally not
        allowed to create custom definitions for standard options, even if the
        definition being created matches the actual option format defined in the
        RFCs. There is an exception from this rule for standard options for which
        Kea does not provide a definition yet. In order to use such options,
        a server administrator must create a definition as described in
        <xref linkend="dhcp6-custom-options"/> in the 'dhcp6' option space. This
        definition should match the option format described in the relevant
854 855
        RFC but the configuration mechanism would allow any option format as it has
        no means to validate the format at the moment.
856 857 858 859 860 861 862 863
      </para>


    <para>
      <table frame="all" id="dhcp6-std-options-list">
        <title>List of standard DHCPv6 options</title>
        <tgroup cols='4'>
        <colspec colname='name'/>
864 865 866
        <colspec colname='code' align='center'/>
        <colspec colname='type' align='center'/>
        <colspec colname='array' align='center'/>
867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919
        <thead>
          <row><entry>Name</entry><entry>Code</entry><entry>Type</entry><entry>Array?</entry></row>
        </thead>
        <tbody>
<!-- Our engine uses those options on its own, admin must not configure them on his own
<row><entry>clientid</entry><entry>1</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>serverid</entry><entry>2</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>ia-na</entry><entry>3</entry><entry>record</entry><entry>false</entry></row>
<row><entry>ia-ta</entry><entry>4</entry><entry>uint32</entry><entry>false</entry></row>
<row><entry>iaaddr</entry><entry>5</entry><entry>record</entry><entry>false</entry></row>
<row><entry>oro</entry><entry>6</entry><entry>uint16</entry><entry>true</entry></row> -->
<row><entry>preference</entry><entry>7</entry><entry>uint8</entry><entry>false</entry></row>

<!-- Our engine uses those options on its own, admin must not configure them on his own
<row><entry>elapsed-time</entry><entry>8</entry><entry>uint16</entry><entry>false</entry></row>
<row><entry>relay-msg</entry><entry>9</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>auth</entry><entry>11</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>unicast</entry><entry>12</entry><entry>ipv6-address</entry><entry>false</entry></row>
<row><entry>status-code</entry><entry>13</entry><entry>record</entry><entry>false</entry></row>
<row><entry>rapid-commit</entry><entry>14</entry><entry>empty</entry><entry>false</entry></row>
<row><entry>user-class</entry><entry>15</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>vendor-class</entry><entry>16</entry><entry>record</entry><entry>false</entry></row>
<row><entry>vendor-opts</entry><entry>17</entry><entry>uint32</entry><entry>false</entry></row>
<row><entry>interface-id</entry><entry>18</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>reconf-msg</entry><entry>19</entry><entry>uint8</entry><entry>false</entry></row>
<row><entry>reconf-accept</entry><entry>20</entry><entry>empty</entry><entry>false</entry></row> -->
<row><entry>sip-server-dns</entry><entry>21</entry><entry>fqdn</entry><entry>true</entry></row>
<row><entry>sip-server-addr</entry><entry>22</entry><entry>ipv6-address</entry><entry>true</entry></row>
<row><entry>dns-servers</entry><entry>23</entry><entry>ipv6-address</entry><entry>true</entry></row>
<row><entry>domain-search</entry><entry>24</entry><entry>fqdn</entry><entry>true</entry></row>
<!-- <row><entry>ia-pd</entry><entry>25</entry><entry>record</entry><entry>false</entry></row> -->
<!-- <row><entry>iaprefix</entry><entry>26</entry><entry>record</entry><entry>false</entry></row> -->
<row><entry>nis-servers</entry><entry>27</entry><entry>ipv6-address</entry><entry>true</entry></row>
<row><entry>nisp-servers</entry><entry>28</entry><entry>ipv6-address</entry><entry>true</entry></row>
<row><entry>nis-domain-name</entry><entry>29</entry><entry>fqdn</entry><entry>true</entry></row>
<row><entry>nisp-domain-name</entry><entry>30</entry><entry>fqdn</entry><entry>true</entry></row>
<row><entry>sntp-servers</entry><entry>31</entry><entry>ipv6-address</entry><entry>true</entry></row>
<row><entry>information-refresh-time</entry><entry>32</entry><entry>uint32</entry><entry>false</entry></row>
<row><entry>bcmcs-server-dns</entry><entry>33</entry><entry>fqdn</entry><entry>true</entry></row>
<row><entry>bcmcs-server-addr</entry><entry>34</entry><entry>ipv6-address</entry><entry>true</entry></row>
<row><entry>geoconf-civic</entry><entry>36</entry><entry>record</entry><entry>false</entry></row>
<row><entry>remote-id</entry><entry>37</entry><entry>record</entry><entry>false</entry></row>
<row><entry>subscriber-id</entry><entry>38</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>client-fqdn</entry><entry>39</entry><entry>record</entry><entry>false</entry></row>
<row><entry>pana-agent</entry><entry>40</entry><entry>ipv6-address</entry><entry>true</entry></row>
<row><entry>new-posix-timezone</entry><entry>41</entry><entry>string</entry><entry>false</entry></row>
<row><entry>new-tzdb-timezone</entry><entry>42</entry><entry>string</entry><entry>false</entry></row>
<row><entry>ero</entry><entry>43</entry><entry>uint16</entry><entry>true</entry></row>
<row><entry>lq-query</entry><entry>44</entry><entry>record</entry><entry>false</entry></row>
<row><entry>client-data</entry><entry>45</entry><entry>empty</entry><entry>false</entry></row>
<row><entry>clt-time</entry><entry>46</entry><entry>uint32</entry><entry>false</entry></row>
<row><entry>lq-relay-data</entry><entry>47</entry><entry>record</entry><entry>false</entry></row>
<row><entry>lq-client-link</entry><entry>48</entry><entry>ipv6-address</entry><entry>true</entry></row>
920 921 922
<row><entry>erp-local-domain-name</entry><entry>65</entry><entry>fqdn</entry><entry>false</entry></row>
<row><entry>rsoo</entry><entry>66</entry><entry>empty</entry><entry>false</entry></row>
<row><entry>client-linklayer-addr</entry><entry>79</entry><entry>binary</entry><entry>false</entry></row>
923 924 925 926 927 928 929 930 931 932 933 934
        </tbody>
        </tgroup>
      </table>
    </para>
    </section>

    <section id="dhcp6-custom-options">
      <title>Custom DHCPv6 options</title>
      <para>It is also possible to define options other than the standard ones.
      Assume that we want to define a new DHCPv6 option called "foo" which will have
      code 100 and will convey a single unsigned 32 bit integer value. We can define
      such an option by using the following commands:
935 936 937 938 939 940 941
<screen>
"Dhcp6": {
    "option-def": [
        {
            <userinput>"name": "foo",
            "code": 100,
            "type": "uint32",
942
            "array": false,
943 944 945 946 947 948 949 950 951 952 953
            "record-types": "",
            "space": "dhcp6",
            "encapsulate": ""</userinput>
        }, ...
    ],
    ...
}
</screen>
      The "false" value of the "array" parameter determines that the option does
      NOT comprise an array of "uint32" values but rather a single value.  Two
      other parameters have been left blank: "record-types" and "encapsulate".
954 955 956 957 958
      The former specifies the comma separated list of option data fields if the
      option comprises a record of data fields. The "record-fields" value should
      be non-empty if the "type" is set to "record". Otherwise it must be left
      blank. The latter parameter specifies the name of the option space being
      encapsulated by the particular option. If the particular option does not
959 960 961
      encapsulate any option space it should be left blank.  Note that the above
      set of comments define the format of the new option and do not set its
      values.
962 963 964 965
      </para>
      <para>Once the new option format is defined, its value is set
      in the same way as for a standard option. For example the following
      commands set a global value that applies to all subnets.
966 967 968 969
<screen>
"Dhcp6": {
    "option-data": [
        {
970
            <userinput>"name": "foo",
971 972
            "code": 100,
            "space": "dhcp6",
973
            "csv-format": true,
974 975 976 977 978 979
            "data": "12345"</userinput>
        }, ...
    ],
    ...
}
</screen>
980 981 982 983 984 985 986 987 988 989 990 991
      </para>

      <para>New options can take more complex forms than simple use of
      primitives (uint8, string, ipv6-address etc): it is possible to
      define an option comprising a number of existing primitives.
      </para>
      <para>
      Assume we want to define a new option that will consist of an IPv6
      address, followed by an unsigned 16 bit integer, followed by a
      boolean value, followed by a text string. Such an option could
      be defined in the following way:
<screen>
992 993 994 995 996 997 998
"Dhcp6": {
    "option-def": [
        {
            <userinput>"name": "bar",
            "code": 101,
            "space": "dhcp6",
            "type": "record",
999
            "array": false,
1000 1001 1002 1003 1004 1005
            "record-types": "ipv4-address, uint16, boolean, string",
            "encapsulate": ""</userinput>
        }, ...
    ],
    ...
}
1006 1007 1008 1009 1010 1011 1012 1013
</screen>
      The "type" is set to "record" to indicate that the option contains
      multiple values of different types.  These types are given as a comma-separated
      list in the "record-types" field and should be those listed in <xref linkend="dhcp-types"/>.
      </para>
      <para>
      The values of the option are set as follows:
<screen>
1014 1015 1016 1017 1018 1019
"Dhcp6": {
    "option-data": [
        {
            <userinput>"name": "bar",
            "space": "dhcp6",
            "code": 101,
1020
            "csv-format": true,
1021 1022 1023 1024 1025
            "data": "2001:db8:1::10, 123, false, Hello World"</userinput>
        }
    ],
    ...
}</screen>
1026 1027 1028 1029

      <command>csv-format</command> is set <command>true</command> to indicate
      that the <command>data</command> field comprises a command-separated list
      of values.  The values in the "data" must correspond to the types set in
1030 1031
      the "record-types" field of the option definition.
      </para>
1032

1033
      <note>
1034
       <para>In the general case, boolean values are specified as <command>true</command> or
1035 1036 1037 1038 1039
       <command>false</command>, without quotes. Some specific boolean parameters may
       accept also <command>"true"</command>, <command>"false"</command>,
       <command>0</command>, <command>1</command>, <command>"0"</command> and
       <command>"1"</command>. Future Kea versions will accept all those values
       for all boolean parameters.</para>
1040
      </note>
1041

1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057
    </section>

    <section id="dhcp6-vendor-opts">
      <title>DHCPv6 vendor specific options</title>
      <para>
      Currently there are three option spaces defined: dhcp4 (to be used
      in DHCPv4 daemon) and dhcp6 (for the DHCPv6 daemon); there is also
      vendor-opts-space, which is empty by default, but options can be
      defined in it. Those options are called vendor-specific information
      options. The following examples show how to 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 conveyed in a vendor specific
      information option. This option comprises a single uint32 value
      that is set to "12345". The sub-option "foo" follows the data
      field holding this value.
      <screen>
1058 1059 1060 1061 1062 1063 1064
"Dhcp6": {
    "option-def": [
        {
            <userinput>"name": "foo",
            "code": 1,
            "space": "vendor-encapsulated-options-space",
            "type": "record",
1065
            "array": false,
1066 1067 1068 1069 1070 1071 1072
            "record-types": "ipv6-address, uint16, string",
            "encapsulates": ""</userinput>
        }
    ],
    ...
}</screen>
     (Note that the option space is set to <command>vendor-opts-space</command>.)
1073 1074
     Once the option format is defined, the next step is to define actual values
     for that option:
1075 1076 1077 1078
<screen>
"Dhcp6": {
    "option-data": [
        {
1079
            <userinput>"name": "foo",
1080 1081
            "space": "vendor-encapsulated-options-space",
            "code": 1,
1082
            "csv-format": true,
1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095
            "data": "2001:db8:1::10, 123, Hello World"</userinput>
        },
        ...
    ],
    ...
}</screen>
    We should also define values for the vendor-opts, that will convey our
    option foo.
<screen>
"Dhcp6": {
    "option-data": [
        ...,
        {
1096
            <userinput>"name": "vendor-encapsulated-options",
1097 1098
            "space": "dhcp6",
            "code": 17,
1099
            "csv-format": true,
1100
            "data": "12345"</userinput>
1101 1102 1103 1104
        }
    ],
    ...
}</screen>
1105 1106 1107 1108 1109 1110 1111
      </para>
    </section>

    <section id="dhcp6-option-spaces">
      <title>Nested DHCPv6 options (custom option spaces)</title>
      <para>It is sometimes useful to define completely new option
      spaces.  This is useful if the user wants his new option to
1112
      convey sub-options that use a separate numbering scheme, for
1113 1114 1115 1116
      example sub-options with codes 1 and 2. Those option codes
      conflict with standard DHCPv6 options, so a separate option
      space must be defined.
      </para>
1117 1118 1119
      <para>Note that it is not required to create a new option space when
      defining sub-options for a standard option because it is
      created by default if the standard option is meant to convey
1120 1121 1122 1123 1124 1125 1126
      any sub-options (see <xref linkend="dhcp6-vendor-opts"/>).
      </para>
      <para>
      Assume that we want to have a DHCPv6 option called "container"
      with code 102 that conveys two sub-options with codes 1 and 2.
      First we need to define the new sub-options:
<screen>
1127 1128 1129 1130 1131 1132
"Dhcp6": {
    "option-def": [
        {
            <userinput>"name": "subopt1",
            "code": 1,
            "space": "isc",
1133
            "type": "ipv6-address",
1134
            "record-types": "",
1135
            "array": false,
1136
            "encapsulate": ""</userinput>
1137 1138
        },
        {
1139
            <userinput>"name": "subopt2",
1140 1141 1142 1143
            "code": 2,
            "space": "isc",
            "type": "string",
            "record-types": "",
1144
            "array": false
1145 1146 1147 1148 1149
            "encapsulate": ""</userinput>
        }
    ],
    ...
}</screen>
1150 1151 1152 1153 1154 1155 1156
    Note that we have defined the options to belong to a new option space
    (in this case, "isc").
    </para>
    <para>
The next step is to define a regular DHCPv6 option and specify that it
should include options from the isc option space:
<screen>
1157
"Dhcp6": {
1158 1159 1160 1161 1162 1163 1164
    "option-def": [
        ...,
        {
            <userinput>"name": "container",
            "code": 102,
            "space": "dhcp6",
            "type": "empty",
1165
            "array": false,
1166 1167 1168 1169 1170 1171 1172 1173 1174
            "record-types": "",
            "encapsulate": "isc"</userinput>
        }
    ],
    ...
}</screen>

    The name of the option space in which the sub-options are defined is set in
    the <command>encapsulate</command> field. The <command>type</command> field
1175 1176
    is set to <command>empty</command> which limits this option to only carrying
    data in sub-options.
1177 1178 1179 1180
    </para>
    <para>
    Finally, we can set values for the new options:
<screen>
1181 1182 1183 1184 1185 1186
"Dhcp6": {
    "option-data": [
        {
            <userinput>"name": "subopt1",
            "space": "isc",
            "code": 1,
1187
            "csv-format": true,
1188 1189 1190 1191 1192 1193
            "data": "2001:db8::abcd"</userinput>
        },
        }
            <userinput>"name": "subopt2",
            "space": "isc",
            "code": 2,
1194
            "csv-format": true,
1195 1196 1197 1198 1199 1200
            "data": "Hello world"</userinput>
        },
        {
            <userinput>"name": "container",
            "space": "dhcp6",
            "code": 102,
1201
            "csv-format": true,
1202 1203 1204 1205 1206
            "data": ""</userinput>
        }
    ],
    ...
}