Well not entirely true either. There are ccTLDs, to which ICANN can make just recommendations. But, our world have gTLDs, where ICANN can set the rules for the zones bellow. :) It's not just black or white. :) Dusan -----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Yuriy Kargapolov Sent: Sunday, April 23, 2017 11:33 PM To: Jaap Akkerhuis <jaap@NLnetLabs.nl>; ua-discuss@icann.org Subject: Re: [UA-discuss] Fw: Re: IDN Implementation Guidelines [RE: Re : And now about phishing...] Monday, April 24, 2017, 12:16:54 AM, you wrote:
Andrew Sullivan writes:
And that, of course, is where they will stop. ICANN is capable of >> making rules about the root zone, but it cannot set policies for the >> zones below -- that's up to the operators of those zones.
not simply - ICANN is capable of making rules about the root zone - ICANN is capable of making at last the unified rules on the root zone and in absolutely ICANN cannot set policies for the zones below -- that's up to the Administrators of Registries of those zones. In paradigm split-off the roles of Administrator (setting and establishment of policies) and Technical Operator (technical support and maintenance) of the Registry
And maybe the contractual arrangments they have with these operators? Jaap, soory, what kinds of operators?
jaap
-- Yuri mailto:yvk@uanic.net --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus