<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (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:12.0pt;
font-family:"Times New Roman","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;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Please note the following email from Cheryl Langdon-Orr, ALAC
Chair, that was sent to me along with Heather Dryden and Frank March of the GAC.
Noting that the references to the GNSO Council meeting should be corrected to 7
October (not 8 October as stated in Cheryl’s message), under agenda ‘</span>Item
7: New gTLD Board Resolutions from Board Retreat<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>’ I would like to
request direction from the GNSO Council regarding how I should respond.
In particular, please note the following excerpts from Cheryl’s message:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>“</span>My proposal to GNSO and GAC is that with the
knowledge of how our AC is planning to proceed and brief outline on some of the
matters we wish to address, would GNSO and/or GAC like to
collaborate and proceed in these inquiries and analysis as a
joint activity? It is our belief
that particularly where we were jointly operating as Chartering
Organisations or in Cross Community mode this would be
quite advantageous and if GNSO and/or GAC do wish to do so the
ALAC and I look forward to the opportunity to continue to build better and more
robust models for multi-stakeholderism and bottom up consensus built
policy processes in ICANN.<span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>”<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>“. . . </span>ALAC will be writing to the Board
and Senior staff involved, to requesting some information and
materials that we trust will help us (as well as the WG participants
and wider ICANN Community) the rational to the resolutions of the
Board regarding the Reports provided, as well as some information as to depth and
time taken in deliberation of the recommendations from the community
(specifically the Consensus ones, but also those with Strong Support) by the
Board and for any information and/or explanation we can be given to assist our
understanding in the decisions outlined in those resolutions, we will also be
requesting access to and prompt delivery of the Board briefing
materials and staff briefings on these substantial reports, (the Board
Books) under the previously announced intentions and guidelines for
these publications, (since Brussels) noting that at this stage the
community has not had access to the Aug meetings materials and if a
similar delay was seen with this retreat / meeting we would still be requesting
information, explanation and assistance towards our understanding as we go
into the Catagena meeting. We have also been requested to write to the
ATRT with these concerns and with copy of the requests we make.<span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>”<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Please forward this request to your respective SGs and
constituencies as soon as possible and be prepared to discuss this on 7
October.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks, Chuck<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Cheryl Langdon-Orr
[mailto:langdonorr@gmail.com] <br>
<b>Sent:</b> Thursday, September 30, 2010 3:15 AM<br>
<b>To:</b> Gomes, Chuck; Heather.Dryden@ic.gc.ca; Frank March<br>
<b>Cc:</b> alac-excom@atlarge-lists.icann.org<br>
<b>Subject:</b> Action item on me from our teleconf yesterday regarding the
recent Board Resolutions from Trondheim, reflecting on reports from various
WG's including JAS and Rec6 CWG...<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif"'>As discussed
in our brief chat yesterday, the ALAC at its meeting on the
28th discussed several matters and concerns to our
community and the At-Large participants in several of the recent WG
activities (particularly the WG focussed on VI, JAS and Rec6CWG) arising out of
the resolutions published recently from the Board Retreat at Trondheim,
Norway see </span><a
href="http://www.icann.org/en/minutes/resolutions-25sep10-en.htm"
target="_blank"><span style='font-family:"Arial","sans-serif"'>http://www.icann.org/en/minutes/resolutions-25sep10-en.htm</span></a><span
style='font-family:"Arial","sans-serif"'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>The ALAC meeting was joined by Regional (RALO)
leadership, At-Large Liaisons to ICANN SO's and other AC's and participants to
the aforementioned WG's which as you know range from the
'traditional SO / GNSO Chartered WG (VI) through the Joint
Chartering Organisation of JAS-WG between GNSO and <span style='font-family:
"Arial","sans-serif"'>ALAC to the tripartite or multi SOAC Cross Community WG
for Rec6 that was jointly managed under Terms of Reference from GNSO, GAC and
ALAC; the ALAC had formally appointed a Liaison from us as a joint
CO to both the JAS and Rec6CWG (operating under
role definitions and mechanisms from the current near final draft
GNSO WG guidelines <span class=apple-style-span><span
style='color:black'>Section 2.2 page 11 of</span></span></span><span
class=apple-style-span><span style='color:#330099'><a
href="http://goog_673367091/" target="_blank"><span style='font-family:"Arial","sans-serif";
color:#0658B5'> </span></a></span></span><span class=apple-style-span><span
style='font-family:"Arial","sans-serif";color:#330099'> </span><span
style='color:#333333'><a
href="https://docs.google.com/viewer?url=https%3A%2F%2Fst.icann.org%2Fdata%2Fworkspaces%2Ficann-ppsc%2Fattachments%2Fworking_group_team%3A20100520152255-0-26262%2Foriginal%2FGNSO%252520Working%252520Group%252520Guidelines%252520-%252520clean%252520-%252520updated%25252020%252520May%2525202010.doc"
target="_blank"><span style='font-family:"Arial","sans-serif";color:#0658B5'>GNSO
Working Group Guidelines - clean - updated 20 May 2010.doc</span></a></span></span><span
style='font-family:"Arial","sans-serif"'> ) and both these Liaisons
addressed serious concerns raised by their respective WG's since the
Board resolutions have been published and the ALAC agreed that<b> <i>"Cheryl
and ExCom to follow up on possibility of executive of two chartering
organizations (GNSO and ALAC) speaking to Chuck about concerns re Board's
reaction to JAS WG. Similar concerns regarding the response to the report from
the Rec6CWG, will be raised by Cheryl in a teleconference between the CO's and
Co-Chairs of that WG and again follow through on this will be actioned either
by the ALAC or in any joint reaction from GNSO, GAC and ALAC that
might occur (this will be followed though on either jointly with
other issues or separately)."</i></b> from AI's from ALAC meeting of 28
Sept. </span><a
href="https://st.icann.org/alac/index.cgi?action_items_28_september_2010_en">https://st.icann.org/alac/index.cgi?action_items_28_september_2010_en</a> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I am writing to you with this information and the
following proposal so that the GAC and GNSO can consider what next steps
they might wish to take jointly or severally with that which the ALAC intends
to do. As I also mentioned in our call the GNSO Liaison to the Joint
JAS-WG is expected to bring this matter forward at the GNSO meeting of the 8th
of October and knowledge of ALAC deliberations and AI's on this matter may be
of some interest or use to the GNSO Councils deliberations on this JAS specific
matter as well as whatever might be raised regarding Rec6CWG.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>On behalf of the At-Large Community involved
and/or interested in these WG activities conducted since Nairobi and
deadlined to feed into the Board Retreat where they were
considering the new
gTLD program Application Guidelines etc., ALAC will
be writing to the Board and Senior staff involved, to requesting some
information and materials that we trust will help us (as well as the WG
participants and wider ICANN Community) the rational to the
resolutions of the Board regarding the Reports provided, as well as some
information as to depth and time taken in deliberation of the recommendations
from the community (specifically the Consensus ones, but also those with
Strong Support) by the Board and for any information and/or explanation we can
be given to assist our understanding in the decisions outlined in those
resolutions, we will also be requesting access to
and prompt delivery of the Board briefing materials and staff
briefings on these substantial reports, (the Board Books) under the
previously announced intentions and guidelines for these
publications, (since Brussels) noting that at this stage the
community has not had access to the Aug meetings materials and if a
similar delay was seen with this retreat / meeting we would still be requesting
information, explanation and assistance towards our understanding as we go
into the Catagena meeting. We have also been requested to write to the
ATRT with these concerns and with copy of the requests we make.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>There is concern in our community that the briefings and
staff advice given to the Board may not have done justice to the degree of
information and the specifics of the various recommendations in
these reports, nor that sufficient time or debate was allocated
to them and we will be seeking assurances and information to disprove or otherwise
these fears.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>My proposal to GNSO and GAC is that with the knowledge
of how our AC is planning to proceed and brief outline on some of the matters
we wish to address, would GNSO and/or GAC like to collaborate and
proceed in these inquiries and analysis as a joint activity?
It is our belief that particularly where we were jointly
operating as Chartering Organisations or in Cross Community mode this
would be quite advantageous and if GNSO and/or GAC do wish to
do so the ALAC and I look forward to the opportunity to continue to build
better and more robust models for multi-stakeholderism and bottom up
consensus built policy processes in ICANN.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Chuck I trust this missive is timely enough for it
to be of some use to the GNSO Council meeting on the 8th and
Heather recognizing that the GAC does not have
an intersession model that matches the frequency of ALAC and GNSO
Council meeting do let me know if there is anything I can do to assist any
discussion and deliberations your AC is making on these matters and note also
that as ALAC works with all of At-Large and at-large, we would value
any individual or partial/subset interactions and interventions
from your Members and Constituencies, if you as SO and AC are unable to
join us in cross community collaboration on this...<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I look forward to your Council and AC reactions to this
proposals and towards ALAC and A-Large working with you in any way deemed most
suitable and effective on this issue in the near future. Please note that
by our mid month ExCom meeting (held in the week of Oct 11 TBC)
where we next review our AI's I would like to have your feedback,
guidance and suggestions on how you wish to proceed. Naturally as leadership
and key representation in the ICANN Community we can I believe work more effectively and successfully in
concert and collaboration rather than by divided effort on this
and many other matters, and I hope your structures might see it that was as
well.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Kindest regards,<o:p></o:p></p>
</div>
<p class=MsoNormal><br clear=all>
Cheryl Langdon-Orr (CLO)<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Chair of ALAC 2007- 2010<o:p></o:p></p>
</div>
</div>
</body>
</html>