<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi,</div><div><br></div><div><br></div><div><div>On Jan 27, 2010, at 10:23 PM, Milton L Mueller wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>I think I have hit on a solution that all of us will find agreeable. <br><br>I am suggesting that our Councilors vote FOR "motion 2" before the Council, which is available here. <br><a href="https://st.icann.org/gnso-council/index.cgi?28_january_2010_motions">https://st.icann.org/gnso-council/index.cgi?28_january_2010_motions</a> <br>We can I think reach consensus on voting for it as long as it does NOT include the recently proposed amendments by Mike Rodenbaugh. <br><br>Motion 2 resolves to:<br>1. initiate a PDP<br>2. evaluation which policy recommendations, if any, should be developed on the topic of vertical integration between Registries and Registrars affecting both new gTLDs and existing ones<br>3. convenes a drafting team to propose a drasft charter for the PDP working group<br><br>How does this solve our conflict? <br>First, we all agree that there should be a PDP. The debate is about what it is about and how long it will take. <br>This motion allows us to draft a charter for the PDP - later. The charter can establish a definition of "Joint marketing and cross ownership" (JM/CO) as different from "vertical integration" and thus NOT part of the PDP. A charter that does that may or may not pass - our own Council reps may not even vote the same on that issue. But it is much better to defer that issue to later. In the meantime, we will get our PDP (as long as CSG supports #2), we don't need to go to the trouble and risk of trying to amend it at the last minute. </div></blockquote><br></div><div>Ok, so Milton has accepted the principle that we should pass a PDP motion and then try to address his concerns about JM/CO in the charter process. I think this is a good procedural solution that for now square the circle between the different positions and allows us to proceed with an effort to begin putting in place a coherent policy framework as an alternative to staff discretion. Very happy to we got here.</div><div><br></div><div>So the the question is which version of 2. Per previous, subsequent to the NCSG-CSG conference call, Mike R. of CSG offered amendments he thought took on board some of the issues we discussed. Milton saw these as a step backward to the extent that they could be read to focus on the short-term DAG treatment of JM/CO, others were more favorably incline. Mary then took Mike's language and scrubbed it further in an effort to make it palatable to all and preserve an output of the NCSG-CSG collaboration, i.e. intra-house team building. IPC and BC have responded favorably, meaning if we all agree there is a very solid block vote for this PDF language.</div><div><br></div><div>The operative provisions of the two approaches on the table are:</div><div><br></div><div><div><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 18px; ">Margie's original motion 2:</span></font></div><div><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 18px; "><br></span></font></div><div><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 18px; ">RESOLVED, that the GNSO Council has reviewed the recommendations contained in the Issues Report, and nonetheless approves the initiation of a PDP on the topic of Vertical Integration between Registries and Registrars;<br><br>FURTHER RESOLVED, that the PDP shall evaluate which policy recommendations, if any, should be developed on the topic of vertical integration between registrars and registries affecting both new gTLDs and existing gTLDs, as may be possible under existing contracts and as allowed under the ICANN Bylaws;<br><br>FURTHER RESOLVED, recognizing that this PDP may not conclude its work in time to affect the initial round of New gTLD applications, the GNSO Council recommends that any Stakeholder Group or Constituency affected by this issue actively participate in the implementation activities conducted by ICANN for the New gTLD program;<br><br>FURTHER RESOLVED, that the GNSO Council shall convene a drafting team to propose a draft charter for a working group to be created to fulfill the requirements of the PDP, which draft charter to be delivered approximately thirty (30) days from the date of this resolution.</span></font></div><div><br></div></div><div><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal; "><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 18px; ">Mary/Mike's revised motion 2: </span></font></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal; "><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 18px; ">RESOLVED, that the GNSO Council has reviewed the recommendations contained in the Issues Report, and nonetheless approves the initiation of a PDP on the topic of vertical integration between registries and registrars;</span></font></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal; "><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 18px; ">FURTHER RESOLVED, that the PDP shall evaluate which policy recommendations, if any, should be developed on the topic of vertical integration between registrars and registries affecting both new gTLDs and existing gTLDs, as may be possible under existing contracts and as allowed under the ICANN Bylaws;</span></font></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal; "><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 18px; ">FURTHER RESOLVED, that the GNSO Council shall convene a Working Group to fulfill the requirements of the PDP, including a review of ICANN Staff’s prior work with respect to vertical integration, and develop recommendations accordingly; and</span></font></p><p class="MsoNormal" style="margin-bottom: 5pt; line-height: normal; "><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 18px; "> FURTHER RESOLVED, that the Working Group shall deliver its Final Report to the GNSO Council no later than ninety (90) days from the date of this resolution.</span></font></p><div><br></div><div>The latter drops the "<span class="Apple-style-span" style="font-size: 18px; ">may not conclude its work in time to affect the initial round of New gTLD applications," which could lead to asymmetric treatment (of concern to registries) and other sources of possible confusion. That seems desirable, given all the concerns expressed on our calls about timing. It convenes a WG but not a DT to charter the WG; I may be missing something, but isn't this problematic if we wanted to take the charter opportunity to specify the scope more carefully? It also adds that the WG should review staff work (I'm sure that'll be welcome...), which I'm ok with, and sets a very short time line for the WG to deliver a final report (seems a bit overly ambitious to me...I'd have given it a half year).</span></div><div><br></div><div>My reading of late night mail exchanges indicates that some councilors are fully prepared to support the <span class="Apple-style-span" style="font-size: 18px; ">Mary/Mike revision. I doubt anyone in the US is awake at this hour, but if someone could clarify for me the thinking behind a) WG but not a DT to charter the WG and b) WG report in 90 days rather than something more realistic, I'd appreciate it. Not sure at present which to vote for, both have problems.</span></div><div><br></div><div>Thanks,</div><div><br></div><div>Bill</div><div><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 18px; "><br></span></font></div><div><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 18px;"><br></span></font></div></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Arial; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">***********************************************************<br>William J. Drake<br>Senior Associate<br>Centre for International Governance<br>Graduate Institute of International and<br> Development Studies<br>Geneva, Switzerland<br><a href="mailto:william.drake@graduateinstitute.ch">william.drake@graduateinstitute.ch</a><br>www.graduateinstitute.ch/cig/drake.html<br>***********************************************************<br><br></span>
</div>
<br></body></html>