> Il 9 luglio 2019 00:01 John Bambenek 
> <jcb=40bambenekconsulting....@dmarc.ietf.org> ha scritto:
> 
> 
> Like I said, I’m ok with someone lying to me. Its easy to detect
> and easy to deal with. For instance, in DNS a mailserver could 
> query these records, see phone number is set to 0000000000 and 
> then just reject email from said domain. With existing whois that 
> was never possible, due to rate limiting.

At first sight, your proposal looked ok - if someone wants to publish their 
information voluntarily, why not? But then I read this and now I am seriously 
concerned: it looks like this is explicitly being designed to penalize 
registrants that care about their privacy and choose not to publish information 
about themselves (or publish fake information, which used to be the only 
practical way in the old mandatory Whois times).

> The domain registrant system issue was easy to solve. Make 
> private domain registrations free for everyone who wanted it.
> That solution was rejected out of hand be registries and 
> registrars at ICANN. Likely because they want the system to die 
> entirely. Differentiated access sounds nice, but those who govern
> such things have made clear it will the differentiation is “do 
> you have a court order”. I’ve been party to those discussions and
> my view is that the multi-stakeholder model isn’t going to work.

Your frustrations are understandable, and personally I hope that ICANN manages 
to set up a usable differentiated access system soon and I even contributed 
some ideas to it. However, basically what you are saying is that you are not 
happy with the result of the policy development process in the proper place 
(i.e. ICANN), so you are now trying to use the IETF to bypass that consensus. 
Is this really the right thing to do for the IETF?

> The fundamental issue is voluntary interconnection. If you want
> to connect to me, I should have a programmatic way to get 
> something about you to make that decision. You can publish 
> nothing if you want, or publish fake info. And I can do what I
> want with it.

I understand this viewpoint, I'm not saying it does not make sense, but this 
looks too much like the email authentication stuff that has made it 
increasingly difficult to run independent mail servers and still get your 
messages accepted by the big platforms. If between "you" and "the entity that 
wants to connect to you" there is a fundamental difference in size and power, 
this becomes a way for you to force the other party into whatever you want - it 
is not a peer relationship any more. So, before proceeding with this (if ever), 
some thoughts should be given to potential centralizing effects and how to deal 
with them.

--
Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bert...@open-xchange.com
Office @ Via Treviso 12, 10144 Torino, Italy

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

Reply via email to