RFC Compliance in Kea DHCP
  • Updated on 23 May 2019
  • 1 minute to read
  • Contributors
  • Print
  • Share
  • Dark
    Light

RFC Compliance in Kea DHCP

  • Print
  • Share
  • Dark
    Light

The following is a partial list of IETF RFCs that Kea is compliant with:

  • RFC 2131 (Dynamic Host Configuration Protocol)
  • RFC 2132 (DHCP Options and BOOTP Vendor Extensions)
  • RFC 3046 (DHCP Relay Agent Information Option)
    Kea can parse RAI and use its suboptions to do various tasks, including but not limited to: select a host reservation (which allows assigning a specific address and extra options), assign a client to a specific subnet, assign a client to a specific pool, or reject clients with specific RAI sub-option values.
  • RFC 3315 (Dynamic Host Configuration Protocol for IPv6)
  • RFC 3319 (Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers)
  • RFC 3633 (IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6)
    Kea can perform dynamic allocations and reserve specific prefixes for each host.
  • RFC 3646 (DNS Configuration Options for DHCPv6)
  • RFC 3736 (Stateless DHCP Service for IPv6)
    Kea can handle information-request messages that provide only options, without assigning addresses or prefixes.
  • RFC 3925 (Vendor-Identifying Vendor Options for DHCPv4)
  • RFC 4242 Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6))
  • RFC 4649 (DHCPv6 Relay Agent Remote-ID Option)
  • RFC 6221 (Lightweight DHCPv6 Relay Agent)
    The major difference is that a lightweight relay agent does not have an IPv6 address. Kea can use different criteria (options) to select a subnet.
  • RFC 6644 (Rebind Capability in DHCPv6 Reconfigure Messages)
  • RFC 6939 (Client Link-Layer Address Option in DHCPv6)
  • RFC 7550 (Issues and Recommendations with Multiple Stateful DHCPv6 Options) (An ISC engineer is a co-author of this standard.)
  • RFC 8415 Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

Note that a number of the RFCs above have recently been replaced with the comprehensive RFC 8415 Dynamic Host Configuration Protocol for IPv6 (DHCPv6).

We are considering compliance with the following standards in future releases of Kea, depending on customer demand:

  • RFC 3203 (DHCP Reconfigure Extension)
  • RFC 4388 (DHCP Leasequery)
  • RFC 6704 (Forcerenew Nonce Authentication)
Was this article helpful?