From 24ab3fd327e01a155e93c3d911ce2c56d9173a96 Mon Sep 17 00:00:00 2001 From: Marcin Siodelski Date: Wed, 25 Apr 2018 19:46:42 +0200 Subject: [PATCH] [5458] Corrections in the descriptions of new DHCPv6 server callouts. --- src/bin/dhcp6/dhcp6_hooks.dox | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/bin/dhcp6/dhcp6_hooks.dox b/src/bin/dhcp6/dhcp6_hooks.dox index ec54ed20c1..80ab98d496 100644 --- a/src/bin/dhcp6/dhcp6_hooks.dox +++ b/src/bin/dhcp6/dhcp6_hooks.dox @@ -301,16 +301,16 @@ to the end of this list. 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 - PREQUEST or RENEW message, it is possible that both leases + 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 "deleted_leases6" object will hold a previous lease instance and the "leases6" object will hold the new lease for this client. The callouts should be prepared to handle such situation. When the callout is executed as a result RELEASE or DECLINE, the callout - will typically receive only one lease (being released) in the - "deleted_leases6" object. Both leases collections are always - provided to the callouts, even though they may sometimes be empty. + will typically receive one or more leases in the "deleted_leases6" + object. Both leases collections are always provided to the callouts, + even though they may sometimes be empty. - Next step status: If any callout installed on the "leases6_committed" sets the next step action to DROP the server will drop the processed query. -- 2.47.2