-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello everyone,
Jim Reid <[email protected]> wrote: > > BTW, whois was originally intended to provide a way to publish > out-of-band contact data so the domain holder could be > contacted whenever their DNS or email was broken. Putting this > info in the DNS would defeat that. Implementation details aside, I think having a technical specification like this would be quite interesting from the point of view of automatically updates to existing Whois databases, without requiring the registrant directly (or indirectly) interact with complex APIs or provider-specific web interfaces. Much like CDS for DS records, and CSYNC for NS records, having a well defined vocabulary for this data in DNS could be a useful step towards such automation. Assuming a cautious implementation, this need not make whois any less reliable. So, that's a potential use-case which I haven't seen mentioned here yet. That said, I agree it cannot solve GDPR or other policy concerns. Also, I really don't see this data as meaningfully useful in fighting abuse, if only because it's very unlikely to see wide adoption in the near future, and because it will be incredibly easy to just create plausible looking (or maliciously Joe-jobbing) fake records. This will largely boil down to 2 bits of information: "did someone in the domain's chain of tools & admins decide to implement this standard?" and "did anybody decide to fill out the relevant forms?" - neither of which are meaningful when combating abuse. I am extremely skeptical of any claims that there's more information to be extracted here. The fact that it will be easier to programmatically look up this information seems to me unlikely to actually make things better, I see it mostly adding complexity and more GI for the GO. Just my opinion, obviously. But I remain vaguely excited about the potential for automation! Cheers, - Bjarni - -- Sent using Mailpile, Free Software from www.mailpile.is -----BEGIN PGP SIGNATURE----- iQGzBAEBCgAdFiEELPAMGTG3kMo305suWQtbDAPCJoUFAl0koYMACgkQWQtbDAPC JoWELQv/TfNARJISejOLP+17xUyMKBHo6gCSOodY+v6PE5fwElbRTjBynQCs2/yM E7qyt96cDKzDuU6iak82znm0cKE+bDN/sLq5Ww/0qO5HT18ZEz78BAS8yWZsiLiY oxsPdtCxYPlzJqKA8DeZ6/dJ+ljTyZk5Jr8nw86Ji9vQdE+R1EY02FO6+9EpOjcA 0cnCHD1My4AvY34e7LwRy/4zlJlfvkblu2d7s+XlUTz151ipnTfkAKJNi1zDfcaw Anae5N7Dnq+CArI+wkZNX+Hq1YK10R6RQk7OM2ZjD9s+9eSnpPG0+NbkSaHVIqkT udcVeo50zuXoEYtK2OGi4ojnFQbB+rPMegTHOaR0o+UxfHsoMv7kfHe9sA2u+jAn b/+Xiz7kJtYD0pFalJBPOMXwt+jK1bFqoFrZ5+D431p8os2LVc2QYiFckmgwnpGF sn3Lj4EOp9T1qLjQwy/Mm5BRq0Z7IFf6Cn/BGctv/m6JEF+bg0ljXahbHA0Uzn0K L6p2KZAN =plYr -----END PGP SIGNATURE-----
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
