If there is no auth NS there is no whois. Acceptable limitation. 

In short term, no incentives. My hope is to get consensus, make it an RFC, then 
start encouraging auditors and the like to flag on it. But yes, it needs some 
critical mass of adoption or its just another idea on paper. 

Reputation and contact-ability intersect in this use case in my mind. 

—
John Bambenek

On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license 
which means commercial use will require a license. Contact 
sa...@bambenekconsulting.com for details

On Jul 8, 2019, at 17:14, Patrick Mevzek <mev...@uniregistry.com> wrote:

> On 2019-07-08 17:05 -0500, John Bambenek <j...@bambenekconsulting.com> 
> wrote:> For domains with no NS records? Who cares, they aren’t in actual use. 
> (Or if they are something is broken or more likely malicious so block it).
> 
> They could be (in use), at some point. See past "fast flux" cases.
> 
> WHOIS was invented to be able to contact "someone" for any kind of problems, 
> technical or administrative. A domain not having NS records may be a 
> technical problem, or not, but if it is a problem who to contact if that 
> information lives in the DNS itself?
> 
>> Yes, the onus is on domain owners (and that requires consensus and adoption 
>> which are not given but why its being brought up here).
> 
> So you are expecting registrants to abide by this, and then all DNS providers 
> to update their web interface so that people will be able to enter those 
> records? What incentives will they all have to do that?
> 
> I am probably less optimist than you.
> 
> But my understanding is that it seems you are trying to publish some data to 
> derive some "reputation" based on it, instead of really data to be able to 
> contact people. They are different goals probably.
> -- 
> Patrick Mevzek
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to