Re: [dnssd] Strategy of advertising proxy for hostname conflicts during key lease period? (draft-ietf-dnssd-advertising-proxy-00)

You are correct. Fortunately, we always have a KEY record that we can
publish on the owner name. This is what the advertising proxy should do to
defend the name. If some non-SRP service tries to register the name, it
will get a hostname conflict.

On Wed, Jun 8, 2022 at 9:36 AM Esko Dijk <esko.dijk@iotconsultancy.nl>
wrote:

> Hi all,
>
>
>
> Something that could be added to draft-ietf-dnssd-advertising-proxy-00 is
> the handling of hostname conflicts; and how an advertising proxy would
> “defend” an SRP registration on the mDNS link side. (There was a previous
> thread on this too.)
>
>
>
> In particular, what if a host registration has already expired but the
> key-lease is still active? In SRP, then no-one else can claim this
> hostname. But in mDNS, we don’t seem to have such mechanism i.e. the
> advertising proxy doesn’t “defend” the hostname registration on the mDNS
> link. Or does it?
>
> So it could happen that this hostname is claimed on the mDNS side by an
> mDNS native device, even though a particular SRP client still has the
> key-lease on this name.
>
>
>
> The original name owner (SRP client) could later come back online and it
> may need to claim the name again – conflicting with the mDNS link.
>
>
>
> Best regards
>
> Esko
>
>
>
> *IoTconsultancy.nl*  |  Email/Teams: esko.dijk@iotconsultancy.nl    |
> +31 6 2385 8339
>
>
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd
>