<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">hi Caitlin.<div><br></div><div>what?? you don't follow what we're saying? humph. *I* don't follow what we're saying half the time. ;-)</div><div><br></div><div>it would probably do us all some good to quickly schedule an IRTP C IRT call to work through the implications of all this.</div><div><br></div><div>-- the IRTP-D conversations have been inconsistent about the scope of the delay to IRTP-C implementation. sometimes we say "all of it" sometimes we say "some of it" and when we say "some" we change which bits we're talking about. i'm glad to see that you're grabbing us by the scruff of the neck and saying "wait. what??" </div><div><br></div><div>-- i'm not sure whether we need to pause *all* of C or just parts of it. that requires more thought -- maybe drag Marika into that thought process?</div><div><br></div><div>-- we *have* uncovered a problem with the IRTP-C recommendation during IRTP-D. in C, we created this whole new kind of transfer category -- the inter REGISTRANT transfer. we wrote a lot about that process, but then punted on the dispute-resolution part of that and said "sure, TDRP can handle that." turns out that's more complicated than we thought and we're just wading through that discussion right now in D. it would be good to coordinate what we do in D with what's being done in the implementation of C.</div><div><br></div><div>-- i'm starting to rethink the face to face meeting idea. i'd like to ponder than some more -- but the ICANN level of activity just went off the scale with all this Brazil stuff (on top of all the other stuff). we might want to schedule a few *long* teleconference meetings rather than face-to-face meetings and see where that takes us. a lot cheaper and a lot less disruptive of schedules and lives.</div><div><br></div><div>just a few random thoughts. i don't see how you people with day jobs get through all this ICANN stuff. it's pretty heavy-duty right now.</div><div><br></div><div>thanks for your note. let's bat this around a little more and see where we land.</div><div><br></div><div>mikey</div><div><br></div><div><br><div><div>On Dec 10, 2013, at 4:52 PM, Caitlin Tubergen <<a href="mailto:caitlin.tubergen@icann.org">caitlin.tubergen@icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; "><div>Hello Mikey, James, and IRTP C IRT,</div><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; "><div><br></div><div>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.</div><div><br></div><div>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. </div><div><br></div><div>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:</div><div><span style="font-family: Calibri; "><br></span></div><div>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: </div></div></span><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; "><ul><li>the 2013 RAA;</li></ul></div></span><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; "><ul><li>the Expired Registration Recovery Policy (PEDNR/ERRP);</li></ul></div></span><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; "><ul><li>IRTP Part B Recommendations 8 and 9; and </li></ul></div></span><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; "><ul><li>IRTP Part C Recommendations 1, 2 and 3 </li></ul></div></span><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; ">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. </div></span><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; "><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Kind regards,</div><div><br></div><div><span style="font-family: Calibri; ">Caitlin Tubergen</span></div><div><div><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri">Registrar Relations and Contracts Manager</font></font></div><div>ICANN</div><div><br></div><div><div style="font-family: Consolas; font-size: medium; "><br></div></div></div></div></span></div>
<span><transcript-irtp-d-20nov13-en[2][2][1].pdf></span></blockquote></div><br><div apple-content-edited="true">
<br class="Apple-interchange-newline"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">PHONE: 651-647-6109, FAX: 866-280-2356, WEB: <a href="http://www.haven2.com">www.haven2.com</a>, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)</span>
</div>
<br></div></body></html>