[DTC CSC] CSC role in disputes between IANA and registry operator

[Kim Davies]

Hi Donna, Hi all,

I don’t think we have good figures on it, but precisely because they are extremely rare. The number of escalations according to the procedure I think can be counted on one hand in the 8 or 9 years the procedure has been in existence. I will go back to my colleague who works on our continuous improvement and see if she has statistics that may be more specific.

In practice, I think I would say the disputes or negative feedback we see are typically fall into a few categories:

(a) disputes between two parties, in country, in the context of ccTLDs. In such cases we direct them, per RFC 1591 et.al, to talk it out locally and come to consensus, although some parties want ICANN to step in and resolve such conflicts;
(b) disagreement with the general procedure for root zone management pertaining to a specific request, such as “why does IANA do this technical test?”, “why can’t IANA proceed with this change request without confirmation from the admin or technical contact?”
(c) disagreement with the procedure in the abstract, such as “why doesn’t IANA perform public consultations on pending redelegation requests?”, “why isn’t the root zone fully automated?". This kind of feedback usually comes in industry meetings etc.
(d) timeliness questions, usually because there has been a complication relating to the issues in (b).

I don’t recall any case where there is a issue with IANA’s performance pertaining to a specific request that couldn’t be solved or adequately explained to the customer within the IANA department without going through further escalation. That said, there are cases where an issue is escalated “beyond” IANA, i.e. to the ICANN Ombudsman, ICANN CEO or NTIA. This is because the party has generally gone to them first before seeking remediation by the IANA department. From time to time, for example, for Governments to go to the NTIA or the ICANN CEO first with a request, not to IANA. These parties know to refer such issues to IANA to allow us to act.

kim 

> On Apr 13, 2015, at 10:12 AM, Donna Austin <Donna.Austin at ariservices.com> wrote:
> 
> Hi Kim
>  
> Our Design Team is getting some serious push-back to take on some role in disputes between IANA and a registry operators.
>  
> Do you have information about the type of complaints you receive, how often, how they are resolved, are they often escalated beyond the IANA team, to your knowledge has NTIA ever been asked to intervene.
>  
> If we have some background, perhaps we can be more informed in making our decisions.
>  
> Team: I still would prefer that the CSC not become involved, but we may need to reconsider. Jonathan suggested rather than the CSC becoming involved in the dispute that they manage the process for resolution; perhaps to this end the CSC could direct complaints to a mediator. If it came to that, I don’t see why IANA could not also offer the same service of a mediator.
>  
> Thanks,
>  
> Donna
>  
> <image002.png>DONNA AUSTIN
> Policy and Industry Affairs Manager
>  
> ARI REGISTRY SERVICES
> Melbourne | Los Angeles 
> P  +1 310 890 9655
> P  +61 3 9866 3710
> E  donna.austin at ariservices.com <mailto:donna.austin at ariservices.com>
> W  www.ariservices.com <http://www.ariservices.com/>
>  
> Follow us on Twitter <https://twitter.com/ARIservices>
>  
> The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/dt3/attachments/20150414/3b5bbb8a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3863 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/dt3/attachments/20150414/3b5bbb8a/smime.p7s>