Re: [dnssd] The DNSSD WG has placed draft-sctl-service-registration in state "Call For Adoption By WG Issued"

[Ted Lemon <[e-mail]>]

Yes, this requires separate registrations for IPv4 and IPv6.   I think
that's okay.   What's a bit chancy is that it also means that if you have a
ULA and a GUA, you have to pick one, or do two updates.   As for NAT, I
think we have to assume that the network is not double-natted.   If it's a
homenet, that will be true.   If it's a campus network, that will be true.
 If it's a bunch of crappy routers plugged together, it's unlikely that
service registration will be available anyway, so we don't care.   Do you
buy that?   :)

On Thu, Jul 12, 2018 at 5:27 PM, Toke Høiland-Jørgensen <[e-mail]>
wrote:

> Ted Lemon <[e-mail]> writes:
>
> > The only reason I think it would be a serious problem for a service to
> > register an IP address other than its own is that it could be used as
> > a way to wedge in an attack.
>
> Right. But if we want to protect against that we'd need to only allow
> registrations for the IP we are talking to; which means separate
> registrations for IPv4 and IPv6. And for v4 it would probably mean a
> requirement for on-link presence, since anything that is not on-link is
> likely to have at least one layer of NAT in-between...
>
> > The real sticky wicket is that you can't update two zones in the same
> > update, but that's not really what you were talking about.
>
> Ah, right, then it makes sense. I may have been ignoring this part of
> the spec in my implementation ;)
>
> -Toke
>