Hal Murray <hmur...@megapathdsl.net>:
> Are you trying to say that we can drop the interface tracking if we switch to
> listening on a single wildcard socket? (If so, I'd missed that in any
> previous discussions.)
Yes. I did say that before - it's the main reason I think SINGLESOCK
needs to be done early, in order to enable later complexity
reductions.
> I can't think of why we actually need it. I would have to scan the code to
> look.
If you have the bandwidth, please do check that premise.
> One example is the don't synchronize with self case. That could be fixed
> with a few lines of code in the path of processing a response.
I don't quite grasp why we need to do anything special. The broadcast-client
and anycast-client support are gone, so how does an instance sync to itself
unless an admin writes a bad server directive?
> A potential case where we might want to do something is a laptop with WiFi
> that goes to sleep and wakes up in a different location.
How does location matter?
> If you move but keep your laptop active, interesting things happen when you
> change from one access point to another.
Can you be more specific?
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
