ICANN ICANN Email List Archives

[gnso-impl-irtpc-rt]


<<< Chronological Index >>>    <<< Thread Index >>>

[gnso-impl-irtpc-rt] IRTP C Clarification

  • To: "gnso-impl-irtpc-rt@xxxxxxxxx" <gnso-impl-irtpc-rt@xxxxxxxxx>
  • Subject: [gnso-impl-irtpc-rt] IRTP C Clarification
  • From: Caitlin Tubergen <caitlin.tubergen@xxxxxxxxx>
  • Date: Tue, 10 Dec 2013 14:52:09 -0800

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




Attachment: transcript-irtp-d-20nov13-en[2][2][1].pdf
Description: Adobe PDF document

Attachment: smime.p7s
Description: S/MIME cryptographic signature



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy