Should this error logline be info instead?

Summary

After upgrade from 9.16.16 to 9.16.27 we are seeing a new kind of error in the logs when doing a xfer-out. The transfer finishes at the same micro-second and we have no evidence that shows the transfer went wrong. We suspect this error message maybe should have been an info message instead.

BIND version used

We are running 9.16.27 (because of an advisory still under NDA)

Steps to reproduce

What we did: Download source as directed in the advisory. Build from source and package as rpm. install and run 9.16.27 over 9.16.16. observe the logging of outgoing transfers.

What is the current bug behavior?

14-Mar-2022 13:31:04.924 xfer-out: info: client @0x7f5cc4024eb0 <ip address>#37444/key <key name> (politie): transfer of 'politie/IN': IXFR started: TSIG <key name> (serial 2022031426 -> 2022031427)
14-Mar-2022 13:31:04.925 xfer-out: error: client @0x7f5cc4024eb0 <ip address>#37444/key <key name> (politie): transfer of 'politie/IN': starting maxtime timer 7200000 ms
14-Mar-2022 13:31:04.925 xfer-out: info: client @0x7f5cc4024eb0 <ip address>#37444/key <key name> (politie): transfer of 'politie/IN': IXFR ended: 1 messages, 6 records, 624 bytes, 0.001 secs (624000 bytes/sec) (serial 2022031427)

Possibly:

... xfer-out: info: client @0x7f5cc4024eb0 ... starting maxtime timer 7200000 ms