ICANN ICANN Email List Archives


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

Re: [gnso-impl-irtpc-rt] IRTP Part C Update

  • To: "James M. Bladel" <jbladel@xxxxxxxxxxx>, "gnso-impl-irtpc-rt@xxxxxxxxx" <gnso-impl-irtpc-rt@xxxxxxxxx>
  • Subject: Re: [gnso-impl-irtpc-rt] IRTP Part C Update
  • From: Caitlin Tubergen <caitlin.tubergen@xxxxxxxxx>
  • Date: Wed, 16 Oct 2013 15:24:18 -0700

Hi James,

Thank you for your message.  Any descriptions/flowcharts that you are able
to share with the group would be great and very much appreciated.

Thank you for the initiative.

Kind regards,

Caitlin Tubergen
Registrar Relations and Contracts Manager

From:  "James M. Bladel" <jbladel@xxxxxxxxxxx>
Date:  Wednesday, October 16, 2013 1:43 PM
To:  Caitlin Tubergen <caitlin.tubergen@xxxxxxxxx>,
"gnso-impl-irtpc-rt@xxxxxxxx" <gnso-impl-irtpc-rt@xxxxxxxx>,
"gnso-impl-irtpc-rt@xxxxxxxxx" <gnso-impl-irtpc-rt@xxxxxxxxx>
Subject:  Re: [gnso-impl-irtpc-rt] IRTP Part C Update

Hi Catilin.  Thanks for the update.  Agree that Registrars have (more than)
enough on their plates at the moment.  Even large organizations are
struggling to keep up, and we are very wary of the potential confusion for

If there is one major change resulting from IRTP-C, it was the change of
Registrant (COR) process.  Like many registrars, Go Daddy already offers
this service internally.  But I can ask if we have any descriptions or
flowcharts that are shareable with the group that might help guide our work
on this recommendation.  I'll try to post this in the next few weeks.



From: Caitlin Tubergen <caitlin.tubergen@xxxxxxxxx>
Date: Wednesday, October 16, 2013 3:12 PM
To: "gnso-impl-irtpc-rt@xxxxxxxx" <gnso-impl-irtpc-rt@xxxxxxxx>,
"gnso-impl-irtpc-rt@xxxxxxxxx" <gnso-impl-irtpc-rt@xxxxxxxxx>
Subject: [gnso-impl-irtpc-rt] IRTP Part C Update

Dear Colleagues,

Thank you for volunteering to participate in the IRTP Part C IRT.  I wanted
to give you a quick update on where things stand.

The IRT met once on 3 July to go over the project plan drafted by Mike
Zupke.  Thank you again to all who participated in the call.  ICANN 47 in
Durban took place shortly after this call, and 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, we plan 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.

In addition to putting together a more predictable policy implementation
cycle, the Registrar Services Team is in the process of interviewing
candidates for a new position within the team.  This new ICANN staff member
will be responsible for liaising with the ICANN Policy Team, Working Groups,
and Implementation Review Teams on issues that involve the registrar

The board approval of the 2013 RAA and related outreach and education
efforts as well as resource limitations in the Registrar Services Team has
caused delays in the IRTP Part C IRT meeting planning.  While we appreciate
that members of the community were hoping for an earlier implementation
plan, I wanted to provide you with an explanation of what has been going on
during this period.  We are also aware that there may be concerns about
keeping fresh the WG discussions and original intent. In short, we have not
forgotten about the work of this team, and we are confident that adding
another staff member and having a thought-out policy implementation cycle
will mitigate these types of delays in the future.  If the group believes
that some work could be done in the interim, please let us know so we can
provide the resources for the IRT to discuss on a call.

Mike Zupke, who was previously responsible for leading this group, is on an
extended leave until early November.  Accordingly, if you have any questions
or concerns, please feel free to reach out to me directly.

Kind regards,

Caitlin Tubergen
Registrar Relations and Contracts Manager

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

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

Privacy Policy | Terms of Service | Cookies Policy