[PC-NCSG] Fwd: Proposed Charter for Accountability CCWG

[Robin Gross]

Thanks, Avri.  I would like to volunteer to participate on workstream 2 for NCSG, as improving ICANN's accountability mechanisms has become a focus for me in recent years and will continue to be going forward.

Thank you,
Robin

Begin forwarded message:

> From: Avri Doria <avri at ACM.ORG>
> Subject: Re: [NCSG-Discuss] Fwd: [] Proposed Charter for Accountability CCWG
> Date: November 6, 2014 11:52:22 PM PST
> To: NCSG-DISCUSS at LISTSERV.SYR.EDU
> Reply-To: Avri Doria <avri at ACM.ORG>
> 
> 
> Signed PGP part
> 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.
> 
> 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.)
> 
> avri
> 
> * 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.
> 
> 
> 
> On 06-Nov-14 15:07, Robin Gross wrote:
> > fyi
> >
> > Begin forwarded message:
> >
> >> From: Grace Abuhamad <grace.abuhamad at icann.org>
> >> Subject: [Cross-Community] Proposed Charter for Accountability CCWG
> >> Date: November 6, 2014 12:57:01 PM PST
> >> To: "accountability-cross-community at icann.org"
> <accountability-cross-community at icann.org>
> >>
> >> To view the original announcement, see here:
> https://www.icann.org/news/announcement-2014-11-05-en
> >>
> >>
> >> Proposed Charter for Enhancing ICANN Accountability Cross Community
> Working Group (CCWG) Submitted for Consideration
> >>
> >> 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:
> >>
> >>> 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
> >>> 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.
> >>>
> >> Next Steps
> >> 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.
> >>
> >> 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.
> >>
> >> Drafting Team Background
> >> 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.
> >>
> >> 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.
> >>
> >> Additional Information
> >> 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:
> >>
> >> Support and enhance the multistakeholder model
> >> Maintain the security, stability, and resiliency of the Internet DNS
> >> Meet the needs and expectation of the global customers and partners
> of the IANA services
> >> Maintain the openness of the Internet.
> >> NTIA also specified that it would not accept a proposal that replaces
> the NTIA role with a government-led or an intergovernmental organization
> solution.
> >>
> >> 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).
> >>
> >> Links to additional information:
> >> Proposed Charter [DOC, 67 KB]
> >>
> >> Drafting Team Wiki
> >>
> >> Revised Enhancing ICANN Accountability Process
> >>
> >> For further information, please contact accountability-staff at icann.org.
> >>
> >> 1 RSSAC and SSAC were invited to participate in the Drafting Team,
> but were unable to join the effort.
> >>
> >> _______________________________________________
> >> Accountability-Cross-Community mailing list
> >> Accountability-Cross-Community at icann.org
> >> https://mm.icann.org/mailman/listinfo/accountability-cross-community
> >
> >
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ipjustice.org/pipermail/pc-ncsg/attachments/20141108/ed777bb4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman.ipjustice.org/pipermail/pc-ncsg/attachments/20141108/ed777bb4/attachment.sig>