Re: [dnssd] Adoption call for draft-sctl-advertising-proxy

[Ted Lemon <[e-mail]>]

On August 13, 2021 at 6:24:51 PM, Jonathan Hui ([e-mail]) wrote:

Another thing to be aware of is that because of the way mDNS works, if you
> are using mDNS for discovery, a name conflict when names aren't being
> defended will sit around in the cache for a few minutes. If names are
> defended, this doesn't happen; one alternative is to just defend names and
> count on SRP to deal with conflicts, but the downside of this is that now
> there is a delay before the new information appears.
>
> This delay could potentially be minimized by retrying to register as soon
> as the SRP replication update has been acknowledged by all SRP replication
> peers—right now my code (when name defense is enabled) just waits two
> minutes before re-attempting, which is a lot longer than should be
> necessary.
>
Sounds like a good idea to explore. My initial concern is that waiting for
positive confirmation from all peers can lead to other failure modes
resulting from poor implementation or connectivity. At the same time, those
same assumptions are what would lead us back to needing other mitigations.

The problem with anything that's ad-hoc and not integrated into the
infrastructure is that there's no model that guarantees success. It's
always going to be best effort. The goal has to be to make "best" as good
as possible, but have a backup strategy for when it's not quite good enough.