The general advice I give when dealing with corner cases like this is:
"Don't crash"
It doesn't really matter what the responder does. There's no "correct" response. But it's important that the responder doesn't crash so that it can keep operating when/if a controller generates this condition by mistake.
IMO route 1 and 2 are both good approaches. I'd be wary of #3 because I hesitate to generate a break on the line during the time when other equipment on the wire might be expecting a discovery response.
I do a lot of tests like this when I'm evaluating a responder. Discover to Unicast, Discovery to Vendorcast, discover to sub-devices, etc. These tests help find corner cases in the software. But if the responder stays online (doesn't crash) and is ready for the next packet, the I consider if to have passes the test.
|