Hi Warren I'm happy with this approach and YES it is a catch all as well as a matter which has a high degree of both interest and concern for the ICANN and wider community... See inter-spaced <font class="Apple-style-span" color="#330099"><CLO> </font>a few points bellow (above and below your original Signature line)<div>
<br></div><div>Now to the matter of creating the template documents for Saturday => I'm going to have to ask Louie as Co-Chair to focus on this refinement by Warren to be utilized into what needs to be done with the rest of you on the WG#3 team for the next 24-48 hrs I am somewhat involved in 'family matters' as I received a message in the transit lounge at Singapore on the way home from our meeting that my youngest son (24) had been in a car accident that happened about the same time as we took off from Beijing, and so I must excuse myself from all but the 'just keeping up with things' part of the work flow for a short while.<br>
<div><br></div><div><br clear="all">Cheryl Langdon-Orr<br>(CLO)<br><br>
<br><br><div class="gmail_quote">On 2 September 2010 06:55, <span dir="ltr"><<a href="mailto:wadelman@godaddy.com">wadelman@godaddy.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><span style="font-family:Verdana;color:#000000;font-size:10pt"><div><span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Times;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="font-family:Arial;font-size:13px;text-align:left"></span></span></div>
<div>Cheryl/Louie</div><div><br></div><div>I wanted to share some thoughts (below the signature) on what WG#3's task would look like if we hit the proverbial "reset button." I started with the AoC 9.1 (c) through (e), and moved through the documents presented by both of you in Beijing.<font class="Apple-style-span" color="#330099"> <CLO> I wish you had had time to do this before our meeting it would have been of great assistance as I do appreciate and like this specific direction.></font></div>
<div><br></div><div>I can see why WG#3 is off track, <font class="Apple-style-span" color="#330099"><CLO> I'd have used terms like too broadly focussed rather than off target as that implies there was more to focus on and hit but I DO know EXACTLY what you mean ;-) ></font> IMO, because the other WGs have very specific targets (Board selection, Board appeals, GAC). In other words, WG#3 appears to be a catch-all for ICANN interactions with its stakeholders. <font class="Apple-style-span" color="#330099"><CLO> exactly!></font></div>
<div><br></div><div>Perhaps the outline below is over-simplified <font class="Apple-style-span" color="#330099"><CLO> it needed to be simplified and given the very limiting (limited) time constraints I see this narrower focus as essential.></font> and leaves too many issues/topics on the table, but I see no choice at this juncture in the timeline. <font class="Apple-style-span" color="#330099"><CLO> Yep!> </font> Many of the topics WG#3 would like to explore simply cannot be covered if the ATRT expects to produce quality output by the deadline. So, I would recommend WG#3 truncate its focus on the entire ICANN structure (SO/ACs) and focus on the Board & Staff. (SO/ACs have their own review process and GNSO is in midst of one presently). <font class="Apple-style-span" color="#330099"><CLO> though I believe we need to reference mention them and their status in our part of the report so it is clear that this RT was aware of them and noting why we were limited in this case how future RT's on A&T need to use the current 'improvements processes' as a baseline and to see if mechanisms proposed have been implemented and to what effect. particular cross reference here is do parts d0 & e) of AoC 9.1 and step 3 below...></font></div>
<div><span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Times;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium;clear:both"><span style="font-family:verdana, geneva;font-size:13px"><br>
</span></span></div><div><span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Times;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium;clear:both"><span style="font-family:verdana, geneva;font-size:13px">Olivier/Erik-as WG#3 team members do you share these concerns on this WG?</span></span></div>
<div><span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Times;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium;clear:both"><span style="font-family:verdana, geneva;font-size:13px"><br>
</span></span></div><div><span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Times;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium;clear:both"><span style="font-family:verdana, geneva;font-size:13px">All input from the ATRT welcome.</span></span></div>
<div><br style="clear:both">Warren</div><div></div><div><br>Warren Adelman<br>President & COO<br><a href="http://GoDaddy.com" target="_blank">GoDaddy.com</a><br><a href="mailto:warren@godaddy.com" target="_blank">warren@godaddy.com</a><br>
twitter: <a href="http://twitter.com/asocialcontract" target="_blank">http://twitter.com/asocialcontract</a></div><div><a href="http://www.godaddy.com" target="_blank">http://www.godaddy.com</a></div><div><br></div><div>=============================================================</div>
<div><br></div><div></div><div><span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div> <div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div>
<div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-family:'Times New Roman';font-size:16px"><b><span style="font-size:14.0pt;font-family:Calibri;color:black">AoC Baseline:</span></b></span></div>
<div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div> <div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman">
<span style="font-size:14.0pt;font-family:Calibri;color:black">Sec 9.1</span></div> <div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div>
<div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black">(c) [Assess] and [improve] the processes by which ICANN receives public input, including adequate explanation of decisions taken and the rationale thereof;</span></div>
<div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black">(d) [Assess] the extent to which ICANN's decisions are embraced, supported, and accepted by the Internet community; and</span></div>
<div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black">(e) [Assess] the policy development process to facilitate enhanced cross-community deliberations, and effective and timely policy development.</span></div>
<div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div> <div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman">
<span style="font-family:'Times New Roman';font-size:16px"><b><span style="font-size:14.0pt;font-family:Calibri;color:black">Team 3 Remit:</span></b></span></div> <div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman">
<span style="font-size:14.0pt;font-family:Calibri"><span> </span></span></div> <div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black">Team # 3: Community/Stakeholder engagement, including effectiveness and quality of ICANN support for the policy development process, the quality of PDP output and the extent to which the ICANN PDP develops consensus, including across stakeholder groups, the level and quality of public input into the ICANN process, and the extent to which such input is reflected in ICANN decision-making</span><span style="font-size:14.0pt;font-family:Calibri;color:black">.</span></div>
<div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div> <div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman">
<span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div> <div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-family:'Times New Roman';font-size:16px"><b><span style="font-size:14.0pt;font-family:Calibri;color:black">Which became:</span></b></span></div>
<div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:TimesNewRomanPSMT;color:black"><a href="http://icann.org/en/reviews/affirmation/wg3-framework-30aug10-en.pdf" target="_blank"><span style="font-family:Calibri">http://icann.org/en/reviews/affirmation/wg3-framework-30aug10-en.pdf</span></a></span><span style="font-size:14.0pt;font-family:Calibri;color:black"></span></div>
<div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div> <div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman">
<span style="font-size:14.0pt;font-family:Calibri;color:black">Of the four ATRT Working Groups, this team has the broadest and least defined task.</span></div> <div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman">
<span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div> <div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black">Recommend going back to the AoC Sec. 9.1 and breaking this in to three steps:</span></div>
<div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div> <ol style="padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px" start="1">
<li style="margin-top:0in;margin-right:0in;margin-bottom:0px;font-size:16px;font-family:'Times New Roman';list-style-type:decimal;margin-left:0.5in;padding-left:0.22in"><span style="font-size:14.0pt;font-family:Calibri;color:black">Review existing public input and participation mechanisms, as described in the ICANN bylaws, and how these factor in to the PDP and Board decisions. It is not necessary to <span style="text-decoration:underline">recursively</span> expand this to the public input / participation mechanisms described in the bylaws of all the SO/ACs (e.g. GNSO), but rather keep the focus on ICANN Board and Staff.</span><span style="font-size: 14pt; font-family: Calibri; "><font class="Apple-style-span" color="#330099"> <CLO> but it *must* include the current work / progress of the Public Participation Committee and I would also suggest implementation of any recommendations from reviews of the AC's and SO's already accepted in reports to the Board (which does tie also to 3. below. NOTE this is stuff we can ask for as update from staff responsible as a set of status report></font></span></li>
</ol><div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div> <ol style="padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px" start="2">
<li style="margin-top:0in;margin-right:0in;margin-bottom:0px;font-size:16px;font-family:'Times New Roman';list-style-type:decimal;margin-left:0.5in;padding-left:0.22in"><span style="font-size:14.0pt;font-family:Calibri;color:black">Review a sample of ICANN Board (non-PDP?) decisions over a given period (post-JPA or post-AoC) and test their acceptance by the community.<span> </span>Are there any that stand out (via comments / feedback in Brussels) that were not "accepted, supported, embraced"?<span> </span>Basically, invert the hypotheses or this group will be chasing an endlessly moving target. </span><span style="font-size: 14pt; font-family: Calibri; "><font class="Apple-style-span" color="#330099"><CLO> Good More than Happy to do this></font></span></li>
</ol><div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size:14.0pt;font-family:Calibri;color:black"> </span></div> <ol style="padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px" start="3">
<li style="margin-top:0in;margin-right:0in;margin-bottom:0px;font-size:16px;font-family:'Times New Roman';list-style-type:decimal;margin-left:0.5in;padding-left:0.22in"><span style="font-size:14.0pt;font-family:Calibri;color:black">WG3 has correctly identified that this is nearly identical to the PPSC-PDP effort.<span> </span>But that is limited to the GNSO.<span> </span>Who is examining the PDP for the other SO/ACs?<span> </span>(specifically, the ccNSO).<span> </span>To simplify, recommend that WG3 review the PPSC-PDP and PPSC-WG efforts and produce a "right track / wrong track" finding.<span> </span>Wrong Track = any recommendations to course correct.</span><span style="font-size: 14pt; font-family: Calibri; "><font class="Apple-style-span" color="#330099"> <CLO> as part of the ALAC input into that effort I know those teams are in a position to also give some responses to any specific questions we might wish to pose here as well as note the specifics of the Draft guidelines (just coming back from 1st review) that has been done for the GNSO Review Implementation effort have been very particularly designed with a view to becoming a set of ICANN WG standards and therefore have also been adopted (even in their draft form) by the current Joint GNSO - ALAC WG's and Cross Community WG's running at the moment so again we can ask for feedback here.> </font></span></li>
</ol><div style="margin:0in;margin-bottom:0px;font-size:16px;font-family:Times New Roman"><span style="font-size: 14pt; font-family: Calibri; "><font class="Apple-style-span" color="#330099"> </font></span></div> <div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0px;font-size:16px;font-family:'Times New Roman';clear:both">
<font class="Apple-style-span" face="Calibri" size="6"><span class="Apple-style-span" style="font-size: 19px;"><br></span></font></div><div></div><div><br><br></div><blockquote style="border-left:2px solid blue;margin-left:8px;padding-left:8px;font-size:10pt;color:black;font-family:verdana">
<div> -------- Original Message --------<br> Subject: [AT-Review] ATRT WG-3 Framework Adaption<br> From: Louie Lee <<a href="mailto:louienet@gmail.com" target="_blank">louienet@gmail.com</a>><br> Date: Mon, August 30, 2010 4:33 pm<br>
To: A&T Review Team <<a href="mailto:at-review@icann.org" target="_blank">at-review@icann.org</a>><br> <br> <br> On Aug 29, 2010, at 6:26 PM, Alice Jansen wrote:<br> <br> > Following up on Cheryl's request, please find attached the WG3's discussion document for presentation.<br>
<br> RT,<br> <br> Please find attached the ATRT WG-3 Framework Adaption using Larry's template.<br> <br> Louie<br> <br> <hr>_______________________________________________<br> AT-Review mailing list<br> <a href="mailto:AT-Review@icann.org" target="_blank">AT-Review@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/at-review" target="_blank">https://mm.icann.org/mailman/listinfo/at-review</a><br> </div> </blockquote></span></div>
</blockquote></div><br></div></div>