<html>
<body>
Overall type of projects to be funded will be decided by the CCWG (if it
indeed makes any such restrictions). Adherence to the ICANN Mission and
Goals will be a pre-requisite. Detailed funding decisions will be the job
of the process/infrastructure recommended by the CCWG and approved by the
Board. Your specific suggestion will surely be up to the latter body.
Conflict of interest guidelines will explicitly preclude CCWG members
advocating specific projects that they may later be submitting.<br><br>
I cannot imagine the ALAC doing anything other than to have one CCWG
Member per region, chosen according to our normal processes which will
include a wide-spread call for Expressions of Interest.This is what we
have always done before and regional balance is the reason that the
process allows five Members per AC/SO.<br><br>
Alan<br><br>
At 30/09/2016 01:06 PM, Judith Hellerstein wrote:<br><br>
<blockquote type=cite class=cite cite="">HI Allan,<br><br>
Thanks for passing this on to us for comments. I think it is fine
and wide enough in the community benefits for some of the projects we
would like to accomplish. One thought I had would be to expand the
fellowship to disadvantaged communities in North America and Europe
and other developed countries which are not able to obtain funding to
attend ICANN meetings. Also to do more outreach to these communities and
create special programs for these and others who have been left out,
including the urban poor, rural and remote rural, people with
disabilities and specific needs, indigenous communities/ We could
target more of these communities and work to increase engagement. I see
this in line with ICANN's mission<br>
<br>
I do note that once this charter is approved than the CCWG will be open
to others to join. Will there be a call out for people to be
appointed like we had for the BCEC and BPMPC?<br><br>
Participation in the CCWG, and its sub-teams (should these be created),
is open to Chartering Organization appointed Members, participants and
observers. Members are appointed by the Chartering Organizations in
accordance with their own rules and procedures. Each Chartering
Organization shall appoint a minimum of 2 and a maximum of 5 Members. I
suggest we use all five and have one from each RALO appointed. Others can
then join in as participants as it says below<br><br>
I note the following: Chartering Organizations are encouraged to use open
and inclusive processes when selecting their members for a CCWG and this
should include reasonable efforts to ensure that each of ICANN’s five
regions is represented.<br><br>
In addition, the CCWG will be open to any interested person as a
Participant. Participants may be from a Chartering Organization, from a
stakeholder group not represented in the CCWG, or may be self-appointed
and derive from within the ICANN or broader community. Participants will
be able to actively participate in and attend all CCWG meetings, work
groups and sub-work groups. However, should there be a need for a
consensus call or decision, such consensus call or decision will be
limited to CCWG members appointed by the Chartering Organizations who may
consult as appropriate with their respective Chartering
Organization.<br><br>
Best,<br><br>
Judith<br><br>
<pre>
_________________________________________________________________________
Judith Hellerstein, Founder & CEO
Hellerstein & Associates
3001 Veazey Terrace NW, Washington DC 20008
Phone: (202) 362-5139 Skype ID: judithhellerstein
E-mail:
<a href="mailto:Judith@jhellerstein.com">Judith@jhellerstein.com</a>
Website:
<a href="http://www.jhellerstein.com">www.jhellerstein.com</a>
Linked In:
<a href="http://www.linkedin.com/in/jhellerstein/">
www.linkedin.com/in/jhellerstein/</a>
Opening Telecom & Technology Opportunities Worldwide
</pre>On 9/30/2016 11:39 AM, Alan Greenberg wrote:<br>
<blockquote type=cite class=cite cite="">Please note that we need any
concerns raised with utmost haste.<br><br>
Alan<br><br>
At 27/09/2016 12:31 AM, Alan Greenberg wrote:<br><br>
<blockquote type=cite class=cite cite="">Somehow this got lost and never
went to the ALAC. We will clearly not meet the deadline, but I have said
we would reply as soon as possible.<br><br>
A bit of background. As the draft Charter says, the work of the CCWG will
not be to allocate funds, but to develop a process for doing this. A lot
of work has gone into the draft charter, and I believe that it is close
to ready. There are many constraints on what the funds can be used for
based on the ICANN Bylaws, and given the amount of money (currently
$235,000,000 if the .web auction stands) conflict of interest is a very
serious matter.<br><br>
Please get any comments to me by the end of Monday at the very
latest.<br><br>
Of crucial importance are matters of substance which would stop the ALAC
from ratifying the charter. If you find typos and such, please let me
know but that is not the focus. <br><br>
Alan<br><br>
<br>
<blockquote type=cite class=cite cite="">Subject: For your review -
proposed charter new gTLD Auction Proceeds CCWG<br>
Date: Tue, 13 Sep 2016 16:41:28 +0000<br><br>
<br>
Sending on behalf of Jonathan Robinson, new gTLD Auction Proceeds
Drafting Team Chair & Alan Greenberg, DT Vice-Chair:<br>
<br>
Dear SO/AC Chairs,<br>
<br>
On behalf of the new gTLD Auction Proceeds Drafting Team (DT), we are
delighted to submit to you and your respective SO/ACs, the proposed
charter for a Cross-Community Working Group on new gTLD Auction Proceeds.
As you may recall, representatives of all ICANN SO/ACs, apart from the
ccNSO (which decided not to take part in the DT effort), participated in
the DT deliberations (see
<a href="https://community.icann.org/x/AR_AAw">
https://community.icann.org/x/AR_AAw</a> for DT members).<br>
<br>
This proposed charter is the result of extensive input and deliberations,
including careful review of input that was received as part of the
cross-community session at ICANN 56 in Helsinki (see
<a href="https://community.icann.org/x/fgmbAw%29">
https://community.icann.org/x/fgmbAw)</a> and we believe it now
represents a careful balance between the different viewpoints and
perspectives, including from both the DT Members and the ICANN Board
liaisons to the DT. As such, the DT would like to request you review the
proposed charter with this careful balance in mind and only flag to the
DT any pertinent issues that would prevent your respective SO/AC from
adopting this charter. We would like to request you highlight such
pertinent issues <b><u>by 30 September 2016 at the latest</u></b>,
including an indication of when you anticipate your respective SO/AC to
be in a position to consider the charter for adoption following 30
September, provided that no pertinent issues have been identified by any
of the ICANN SO/ACs.<br>
<br>
Of course, should you have any clarifying questions, please do not
hesitate to respond to this message. The DT looks forward to receiving
your feedback.<br>
<br>
Best wishes,<br>
<br>
Jonathan Robinson, DT Chair & Alan Greenberg, DT
Vice-Chair</blockquote>Content-Type: application/msword;<br>
<x-tab> </x-tab>
name="CCWG Auction Proceeds - clean - FINAL Charter - 9 September
2016.doc";<br>
<x-tab> </x-tab>
x-mac-type=42494E41; x-mac-creator=4D535744<br>
Content-Disposition: attachment;<br>
<x-tab> </x-tab>
filename="CCWG Auction Proceeds - clean - FINAL Charter - 9
September"<br>
2016.doc"<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;DM5PR03MB2714;9:1gmqnEhp7gkCouELrLqnZyNOqReRcVRm6NYT5thEWR36TD1tnCgjJL/PlgcB0SdatHpmKhDmZUbEzBvB6AoEKNqG9VjIUmW9DThrIu0Ejx92/6ruy0N4kEDXc395WldzfI+EmEZ/j5DSERwf9MzBb6FpVQCUVJAwJoqLlFub9ytahPHLevWmvt5o86/ZV60BYHI0UPGqpLgrMu/0Cv25xQ==<br>
<br>
Content-Type: application/pdf;<br>
<x-tab> </x-tab>
name="CCWG Auction Proceeds - clean - FINAL Charter - 9 September
2016.pdf"<br>
Content-Disposition: attachment;<br>
<x-tab> </x-tab>
filename="CCWG Auction Proceeds - clean - FINAL Charter - 9
September"<br>
2016.pdf"<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;DM5PR03MB2714;9:1gmqnEhp7gkCouELrLqnZyNOqReRcVRm6NYT5thEWR36TD1tnCgjJL/PlgcB0SdatHpmKhDmZUbEzBvB6AoEKNqG9VjIUmW9DThrIu0Ejx92/6ruy0N4kEDXc395WldzfI+EmEZ/j5DSERwf9MzBb6FpVQCUVJAwJoqLlFub9ytahPHLevWmvt5o86/ZV60BYHI0UPGqpLgrMu/0Cv25xQ==<br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;DM5PR03MB2714;9:1gmqnEhp7gkCouELrLqnZyNOqReRcVRm6NYT5thEWR36TD1tnCgjJL/PlgcB0SdatHpmKhDmZUbEzBvB6AoEKNqG9VjIUmW9DThrIu0Ejx92/6ruy0N4kEDXc395WldzfI+EmEZ/j5DSERwf9MzBb6FpVQCUVJAwJoqLlFub9ytahPHLevWmvt5o86/ZV60BYHI0UPGqpLgrMu/0Cv25xQ==<br>
<br>
_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" eudora="autourl">
http://www.atlarge.icann.org</a><br>
ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC" eudora="autourl">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
)</blockquote><br><br>
<br>
<pre>_______________________________________________
ALAC mailing list
<a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a>
At-Large Online:
<a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a>
ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
</pre></blockquote><br>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;DM5PR03MB2714;9:TvLIFA685ZIGaQKayB9uLbTkWe/ca69vVGtj4l9Sog8L9yd3NYlK71340ZFZjs58EFp89eGi4H3nG1y7ZR73IRP2XNe4q3Q5GmjyVcqAzj2tjRkmqQFGa4cREO/Oex1WqQiCGxaYjlK6B90vdV3GR62zga8f/2Ft1Zgwjy/DcpGGnOIlZKa9115JDYKx/qJRIw3JYzPxIXDMVdcbFJ/ju7t88JOsDFv/7AzCHzzEuqk=<br>
<br>
_______________________________________________<br>
ALAC mailing list<br>
ALAC@atlarge-lists.icann.org<br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" eudora="autourl">
http://www.atlarge.icann.org</a><br>
ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC" eudora="autourl">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
)</blockquote></body>
</html>