/// @todo The timeout value could be set to 0 to trigger timeout
/// instantly. However, it may lead to situations that the message sent
/// in one test will not be dropped by the kernel by the time, the next
- /// test starts. This will lead to intermittent unit test errors as
- /// described in the ticket http://oldkea.isc.org/ticket/3265.
+ /// test starts. This will lead to intermittent unit test errors.
/// Increasing the timeout to a non-zero value mitigates this problem.
/// The proper way to solve this problem is to receive the packet
/// on our own and drop it. Such a fix will need to be applied not only