<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#330033">
<br>
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA1 <br>
<br>
Note: the text of the charter should be same as the one I sent the
group last week.<br>
<br>
Another note: the issue of greater representation for the
Constituencies of the CwG has come up again in the council. I
pointed out that in this case there were neither discussions nor
history of an ad-hoc group having had greater CSG representation and
thus no notion of it being grandmothered in.<br>
<br>
This charter is up for a vote next week. NCSG should start
selecting its member for the group.* The group will be as open to
particIpation as in cwg-stewardship, except that this charter calls
them participants. Each CWG learns from the experiences of the
previous. (In the ordering and learning, CWG-Internet came before
CWG-Stewarship, it is just that is languished on the GNSO Council
schedule a very long time, so it was voted on later.)<br>
<br>
avri<br>
<br>
* the PC is currently trying to get its organizational act together,
with our past-Chair no longer being a member of the PC, and not
having elected a new one yet. According to our charter, as I read
it, it will need to choose a member from among those who put their
names forward or have their names put forward. So those who want to
put the intensive amount of work for the next year or more that may
be required to be the member of this CWG, should consider the task.<br>
<br>
<br>
<br>
On 06-Nov-14 15:07, Robin Gross wrote:<br>
<span style="white-space: pre;">> fyi<br>
><br>
> Begin forwarded message:<br>
><br>
>> From: Grace Abuhamad <a class="moz-txt-link-rfc2396E" href="mailto:grace.abuhamad@icann.org"><grace.abuhamad@icann.org></a><br>
>> Subject: [Cross-Community] Proposed Charter for
Accountability CCWG<br>
>> Date: November 6, 2014 12:57:01 PM PST<br>
>> To: <a class="moz-txt-link-rfc2396E" href="mailto:accountability-cross-community@icann.org">"accountability-cross-community@icann.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:accountability-cross-community@icann.org"><accountability-cross-community@icann.org></a><br>
>><br>
>> To view the original announcement, see here:
<a class="moz-txt-link-freetext" href="https://www.icann.org/news/announcement-2014-11-05-en">https://www.icann.org/news/announcement-2014-11-05-en</a><br>
>><br>
>><br>
>> Proposed Charter for Enhancing ICANN Accountability Cross
Community Working Group (CCWG) Submitted for Consideration<br>
>><br>
>> On 3 November 2014, the Drafting Team that was formed by
the ICANN community to develop a charter for the Enhancing ICANN
Accountability Cross Community Working Group (CCWG) distributed a
charter for adoption by chartering organizations. The charter
includes, among other things, a problem statement, goals &
objectives, scope, and proposed areas for work. The CCWG is
expected to organize its activities in two Work Streams,
consistent with the Revised Enhancing ICANN Accountability
Process:<br>
>><br>
>>> Work Stream 1: focused on mechanisms enhancing ICANN
accountability that must be in place or committed to within the
time frame of the IANA Stewardship Transition; and<br>
>>> Work Stream 2: focused on addressing accountability
topics for which a timeline for developing solutions and full
implementation may extend beyond the IANA Stewardship Transition.<br>
>>><br>
>> Next Steps<br>
>> Each ICANN Supporting Organization (SO) and Advisory
Committee (AC) is expected to consider the proposed charter during
its upcoming November meeting(s). Following the adoption of the
charter, chartering organizations are expected to identify their
representative members to serve on the CCWG (each chartering
organization will appoint a minimum of 2 and a maximum of 5
members to the CCWG). In addition, a call for volunteers to join
the CCWG will be launched, so that anyone interested in this
effort may join and participate. The CCWG is expected to commence
its deliberations in late November or early December.<br>
>><br>
>> All members of the group formerly known as the "Cross
Community Group" will be added to the CCWG as participants, unless
some are appointed by chartering organizations to serve as members
or decide not to join this effort.<br>
>><br>
>> Drafting Team Background<br>
>> Considering the short timeframe ahead and the relation of
part of the Accountability work to the IANAStewardship Transition
process, the Drafting Team worked on an expedited basis to develop
the charter. The publication date was identified to align with the
November meetings of ICANN's SOs and ACs, to allow for the
question of CCWG charter adoption to be discussed. For details of
each of the Drafting Team's meetings, including interim draft
versions of the charter, please see here.<br>
>><br>
>> The Drafting Team was formed following the ICANN51
meeting and includes members appointed by the At-Large Advisory
Committee (ALAC), Address Supporting Organization (ASO), Country
Code Supporting Organization (ccNSO), Governmental Advisory
Committee (GAC) and Generic Names Supporting Organization (GNSO).1
In addition, one representative from outside the ICANN
SO/ACstructure joined the Drafting Team to ensure that the charter
defined an inclusive process for the broader community. For a full
list of Drafting Team members, please see here.<br>
>><br>
>> Additional Information<br>
>> The National Telecommunications and Information
Administration (NTIA) has requested that ICANN"convene a
multistakeholder process to develop a plan to transition the U.S.
government stewardship role" with regard to the IANA Functions and
related root zone management. In making its announcement, the NTIA
specified that the transition proposal must have broad community
support and meet the following principles:<br>
>><br>
>> Support and enhance the multistakeholder model<br>
>> Maintain the security, stability, and resiliency of the
Internet DNS<br>
>> Meet the needs and expectation of the global customers
and partners of the IANA services<br>
>> Maintain the openness of the Internet.<br>
>> NTIA also specified that it would not accept a proposal
that replaces the NTIA role with a government-led or an
intergovernmental organization solution.<br>
>><br>
>> During discussions around the transition process, the
community raised the broader topic of the impact of the change on
ICANN's accountability. The Enhancing ICANN Accountability process
was finalized and posted on 10 October 2014, and can be found
here. The scope of the Enhancing ICANNAccountability process is
defined as ensuring that ICANN remains accountable in the absence
of its historical contractual relationship with the U.S.
Government and the perceived backstop with regard toICANN's
organization-wide accountability provided by that role, such as
the renewal process of theIANA functions contract. It calls for an
examination, from an organizational perspective, of how ICANN's
broader accountability mechanisms should be strengthened to
address the absence of its historical contractual relationship
with the U.S. Government, including looking at strengthening
existing accountability mechanisms (e.g., the ICANN Bylaws and the
Affirmation of Commitments).<br>
>><br>
>> Links to additional information:<br>
>> Proposed Charter [DOC, 67 KB]<br>
>><br>
>> Drafting Team Wiki<br>
>><br>
>> Revised Enhancing ICANN Accountability Process<br>
>><br>
>> For further information, please contact
<a class="moz-txt-link-abbreviated" href="mailto:accountability-staff@icann.org">accountability-staff@icann.org</a>.<br>
>><br>
>> 1 RSSAC and SSAC were invited to participate in the
Drafting Team, but were unable to join the effort.<br>
>><br>
>> _______________________________________________<br>
>> Accountability-Cross-Community mailing list<br>
>> <a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
>>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
><br>
></span><br>
<br>
-----BEGIN PGP SIGNATURE-----
<br>
Version: GnuPG v2.0.22 (MingW32)
<br>
<br>
iQEcBAEBAgAGBQJUXHo2AAoJEOo+L8tCe36H0F0IALyn/gKi/A06JDILB09o2870
<br>
rstl33Q6gwx/7ulT3T+CZmoq8O+m0OO6MbXB7WNTWGBkavh/CGQX1GzTbhSEA2Zo
<br>
Ou2QvikbCD0xK637+P1KULAEY0tmWsiFlX8UKXXT4e5OeoPRU8ipi66C937zheEc
<br>
NiqtGqF8JR7E1b6H3pMb9Ts4jRZRZe5jeWeLv9N28ts6LwpRwQif4rNtbU2SxKAC
<br>
UXHAg1xf3qycRr4LLoOxCn4MX+5Ziykkghb8Bf+uXWT3YggZQvXnxj9xNOz99ABP
<br>
h6RQJlkipiGE1zMpHnZy1t7T1X5WjYwQ53kAyO+QSsoGK/Sb4OwJLnh40cHkDBc=
<br>
=4Pp0
<br>
-----END PGP SIGNATURE-----
<br>
<br>
</body>
</html>