Caitlin / Tim

One of the things that a couple of people have suggested is to rollout updates / changes that have an operational impact at fixed periods throughout the year ..

Regards

Michele

Mr Michele Neylon

Blacknight Solutions

Hosting & Colocation, Domains

http://www.blacknight.co/

http://blog.blacknight.com/

http://www.technology.ie

Intl. +353 (0) 59 9183072

Locall: 1850 929 929

Direct Dial: +353 (0)59 9183090

Fax. +353 (0) 1 4811 763

Twitter: http://twitter.com/mneylon

-------------------------------

Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty

Road,Graiguecullen,Carlow,Ireland Company No.: 370845

From: owner-gnso-impl-irtpc-rt@icann.org [mailto:owner-gnso-impl-irtpc-rt@icann.org] On Behalf Of Caitlin Tubergen
Sent: Tuesday, December 10, 2013 10:52 PM
To: gnso-impl-irtpc-rt@icann.org
Cc: Tim Cole
Subject: [gnso-impl-irtpc-rt] IRTP C Clarification

Hello Mikey, James, and IRTP C IRT,

I attended the IRTP D session at ICANN48 remotely. As it was pretty early Los Angeles time, I wanted to touch base with you to make sure I understood the effect of various comments made during the session. I have attached the transcript for ease of reference.

On page 31 of the transcript, James asked if we could pause implementation efforts for IRTP C due to something that was uncovered in IRTP D discussions. I wanted to confirm what was meant by "pause implementation efforts". During our last IRTP C call, there was a discussion of a face-to-face meeting to finely tune the implementation plan on a whiteboard. I am happy to arrange that meeting; I just want to confirm that I should still move forward in light of the IRTP D discussions in Buenos Aires.

Additionally, in light of requested delays, Tim Cole asked how we should allay the community concern of repeated implementation delays, and Mikey asked if we could prepare some messaging regarding delays. I have included a few points below to consider:

Members of the registrar community expressed some concern about all of the new contractual and policy implementation efforts that were coming down the pipeline including but not limited to:

the 2013 RAA;

the Expired Registration Recovery Policy (PEDNR/ERRP);

IRTP Part B Recommendations 8 and 9; and

IRTP Part C Recommendations 1, 2 and 3

To that end, ICANN plans to work with the registrar community on an implementation roll-out plan, designed to make policy implementation cycles more predictable and thereby more manageable for registrars to incorporate into their business models.

Some of the recommendations of IRTP D appear to conflict with recommendations of IRTP C, and until those conflicts are resolved, the team is recommending that implementation efforts for IRTP C be paused. It may also be beneficial to acknowledge that the members of the IRTP C Implementation Review Team have extensive overlap with the IRTP D Working Group.

Feel free to edit the above messaging as you see appropriate. Also, please let me know if you would like me to schedule an in-person meeting for January or February, depending on availability. I want to keep the ball rolling; I just want to be sure I correctly understood the instructions of the group.

Kind regards,

Caitlin Tubergen

Registrar Relations and Contracts Manager

ICANN