[5458] Updated leases6_committed doc to include Rapid Commit case.

diff --git a/src/bin/dhcp6/dhcp6_hooks.dox b/src/bin/dhcp6/dhcp6_hooks.dox
index 80ab98d496d8499a773fa43d7b98b950752f0e16..8b76fd5a0478fb4bc6412ef6bef0b96bc9e7f4f6 100644 (file)
--- a/src/bin/dhcp6/dhcp6_hooks.dox
+++ b/src/bin/dhcp6/dhcp6_hooks.dox
@@ -298,9 +298,10 @@ to the end of this list.
    processing. This includes writing new lease into the database,
    releasing an old lease for this client or declining a lease. This
    callout is executed only for the DHCP client messages which may
-   cause lease changes, i.e. REQUEST, RENEW, REBIND, RELEASE and
-   DECLINE. This callout is not executed for SOLICIT, CONFIRM and
-   INFORMATION REQUEST.  If the callouts are executed as a result of
+   cause lease changes, i.e. SOLICIT with Rapid Commit option included
+   and when Rapid Commit is enabled, REQUEST, RENEW, REBIND, RELEASE and
+   DECLINE. This callout is not executed for SOLICIT without Rapid Commit,
+   CONFIRM and INFORMATION REQUEST.  If the callouts are executed as a result of
    REQUEST or RENEW message, it is possible that both leases
    collections hold leases to be handled. This is the case when the
    new lease allocation replaces an existing lease for the client. The