From eb18195205b6c733142f833998923224eae4c9c9 Mon Sep 17 00:00:00 2001 From: Marcin Siodelski Date: Fri, 27 Apr 2018 13:38:32 +0200 Subject: [PATCH] [5458] Updated leases6_committed doc to include Rapid Commit case. --- src/bin/dhcp6/dhcp6_hooks.dox | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/bin/dhcp6/dhcp6_hooks.dox b/src/bin/dhcp6/dhcp6_hooks.dox index 80ab98d496..8b76fd5a04 100644 --- 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 -- 2.47.2