Changes between Version 6 and Version 7 of KeaToDo


Ignore:
Timestamp:
Jul 14, 2015, 9:06:27 AM (2 years ago)
Author:
tomek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • KeaToDo

    v6 v7  
    1010(3) Storing static host reservations in the SQL database (MySQL, later also Postgres). This feature was planned for 0.9.1 release but later deferred to post 1.0 due to time constraints.
    1111
    12 (4) Command Control Interface which would support sending commands to the DHCP server to trigger certain actions. The design is expected to be done prior to 1.0 release.
     12~~(4) Command Control Interface which would support sending commands to the DHCP server to trigger certain actions. The design is expected to be done prior to 1.0 release. (implemented in 0.9.2-beta)~~
    1313
    1414(5) Use of client identifier vs MAC address to identify the client. The RFC 2131 seems to say that client id is a primary identifier, but some real deployments prefer MAC addresses because client id get randomized frequently or is otherwise broken (e.g. non-unique). We should revise our use of client identifier and possibly come up with some configuration switches to control whether client id or MAC address is a primary identifier to be used by the server.
    1515
    16 (6) Update the DHCPv6 server to support https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/. This fixes a number of problems with the combined use of IA_NA and IA_PD in a single DHCP session.
     16(6) Update the DHCPv6 server to support RFC7550. This fixes a number of problems with the combined use of IA_NA and IA_PD in a single DHCP session.
    1717
    1818(7) Rip-off any remaining BIND10 code which we don't use in Kea.
     
    2020(8) Implement support for assigning multiple IPv6 addresses in a single IA_NA, to facilitate the graceful renumbering. The new lease is assigned while the old lease lifetime is being decreased during renewals and eventually expires.
    2121
    22 (9) Implement lease expiration with the ability to remove DDNS records and execute the hooks for each lease.
     22(9) Implement lease expiration with the ability to remove DDNS records and execute the hooks for each lease: planned for 1.0.
    2323
    2424(10) Implement database connection failure recovery.