<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">hi Mike,<div><br></div><div>i think "how we fit" is in our remit, because we will have a unique perspective on dependencies. but i agree that creating the larger structure that we fit *into* isn't. do a search on "program management" for tips on how to put together and manage a portfolio of inter-connected projects. i think we be a project, within a larger program. </div><div><br></div><div>mikey</div><div><br></div><div><br><div><div>On Jun 6, 2013, at 8:56 AM, James M. Bladel <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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>Right. And this IRT must be aware of all these new changes, particularly those that could affect its own items.</div>
<div><br>
</div>
<div>For example, the new 2013 RAA will have validation/verification requirements. The IRT must consider how this (not yet adopted) verification process will affect the Change of Registrant procedure. There are probably a bunch of unknown dependencies like
that….</div>
<div><br>
</div>
<div>J.</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family: Calibri; font-size: 11pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223); ">
<span style="font-weight:bold">From: </span>Mike Zupke <<a href="mailto:Mike.Zupke@icann.org">Mike.Zupke@icann.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, June 6, 2013 08:50<br>
<span style="font-weight:bold">To: </span>James Bladel <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>>, "<a href="mailto:gnso-impl-irtpc-rt@icann.org">gnso-impl-irtpc-rt@icann.org</a>" <<a href="mailto:gnso-impl-irtpc-rt@icann.org">gnso-impl-irtpc-rt@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>RE: [gnso-impl-irtpc-rt] IRTP WG C IRT Kick-off<br>
</div>
<div><br>
</div>
<div xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1"><p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Thanks, James.
<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">The schedule/project plan is indeed topic #1. But I think the bigger question - how does this fit into all of the rest of the work underway? - is
probably outside this group’s remit. My team (on staff) is currently mapping out all of the implementation items we see on the horizon and trying to figure out a way to manage those in a responsible way. I think, ultimately, it might require a discussion
with the GNSO council, but that’s as far as my thinking has progressed to date... Happy to discuss on the call if you and others like.<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Best,<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></font></p>
<div><p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Mike Zupke<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Director, Registrar Programs<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Internet Corporation for Assigned Names and Numbers<o:p></o:p></span></font></p>
</div><p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></font></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><font size="2" face="Tahoma"><span style="font-size: 10pt; font-family: Tahoma, sans-serif; font-weight: bold; ">From:</span></font></b><font size="2" face="Tahoma"><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "> James
M. Bladel [<a href="mailto:jbladel@godaddy.com">mailto:jbladel@godaddy.com</a>] <br>
<b><span style="font-weight:bold">Sent:</span></b> Wednesday, June 05, 2013 6:01 PM<br>
<b><span style="font-weight:bold">To:</span></b> Mike Zupke; <a href="mailto:gnso-impl-irtpc-rt@icann.org">
gnso-impl-irtpc-rt@icann.org</a><br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [gnso-impl-irtpc-rt] IRTP WG C IRT Kick-off<o:p></o:p></span></font></p>
</div>
</div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 10.5pt; ">Mike and Team:<o:p></o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 10.5pt; "><o:p> </o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 10.5pt; ">What is ICANN's plan w.r.t. scheduling this implementation? We are still working on Rec 9 of IRTP-B, ERRP, TMCH, and soon New gTLDs and the 2013 RAA. I'm
concerned that these changes are starting to work against each other, and are definitely contending for the same development resources. <o:p></o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 10.5pt; "><o:p> </o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 10.5pt; ">Recommend we make this Agenda Topic #1 during our first call.<o:p></o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 10.5pt; "><o:p> </o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 10.5pt; ">Thanks--<o:p></o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 10.5pt; "><o:p> </o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 10.5pt; ">J.<o:p></o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 10.5pt; "><o:p> </o:p></span></font></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><font size="2" face="Calibri"><span style="font-size: 11pt; font-weight: bold; ">From:
</span></font></b><font><span style="">Mike Zupke <<a href="mailto:Mike.Zupke@icann.org">Mike.Zupke@icann.org</a>><br>
<b><span style="font-weight:bold">Date: </span></b>Wednesday, June 5, 2013 16:39<br>
<b><span style="font-weight:bold">To: </span></b>"<a href="mailto:gnso-impl-irtpc-rt@icann.org">gnso-impl-irtpc-rt@icann.org</a>" <<a href="mailto:gnso-impl-irtpc-rt@icann.org">gnso-impl-irtpc-rt@icann.org</a>><br>
<b><span style="font-weight:bold">Subject: </span></b>[gnso-impl-irtpc-rt] IRTP WG C IRT Kick-off<o:p></o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 10.5pt; "><o:p> </o:p></span></font></p>
</div>
<div>
<div><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">Greetings!<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">Welcome to the Transfer Policy Working Group C Implementation Review Team (“IRTPWGCIRT”). I will be leading ICANN’s implementation of the GNSO’s IRTP
C recommendations, and it is my pleasure to have the opportunity to work with you on this effort.<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; "> <o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">As a refresher, the GNSO made 3 recommendations that were adopted by the ICANN Board:<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">1. Modify the IRTP / Create a consensus policy that would apply to inter-registrant transfers.<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">2. Revise the existing Inter-Registrar Transfer Policy related to the expiration of the Form of Authorization used by registrars during transfers.<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">3. Require registries to include registrars’ GURIDs (aka IANA IDs) in Whois output.
<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; "> <o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">Recommendation 3 is currently being implemented by Staff, so that leaves recs 1 & 2 for us. There is quite a bit of work to be done on these, so I’ve
created a project plan that I’d like to share with you for feedback on a kick-off call. If you’re interested in attending, would you kindly enter your availability in this doodle poll?:
<a href="http://doodle.com/7uq5vaiyu7n8fpu8">http://doodle.com/7uq5vaiyu7n8fpu8</a>
<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; "> <o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">Thanks in advance. I look forward to working with you.
<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; "> <o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">Sincerely,<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; "> <o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">Mike Zupke<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">Director, Registrar Programs<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; ">Internet Corporation for Assigned Names and Numbers<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size: 11pt; "> <o:p></o:p></span></font></p>
</div>
</div>
</div>
</div>
</div>
</span>
</div>
</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>