On Aug 16, 2011, at 10:53 AM, Fred Baker wrote: Seems reasonable. It has the same authenticity issues as DDNS; the fact that a system with an address announces a name doesn't make it so.
Yup. Historically this hasn't been an issue: names are offered on a first-come, first-served basis, much like mdns. Names that don't have DUID records can't be updated, so even if you update a common zone, there's no way for a client to get ftp.example.com<http://ftp.example.com>, for instance. Typically names are deleted once the lifetime of the address has expired without renewal, so the system automatically cleans up stale name registrations.
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
