ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

[council] Draft Motion - GNSO Validation of CCWG-Accountability Budget Request

  • To: GNSO Council List <council@xxxxxxxxxxxxxx>
  • Subject: [council] Draft Motion - GNSO Validation of CCWG-Accountability Budget Request
  • From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
  • Date: Mon, 19 Sep 2016 20:02:20 +0000
  • Accept-language: en-US
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=jbladel@xxxxxxxxxxx;
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=secureservernet.onmicrosoft.com; s=selector1-godaddy-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=HcKhjtZ6KStPdT9O9PvBmy/m4MDSQfhOLwZ/eUg7vTU=; b=JvD5V3cx64V4GhCU/k1qTtCzFWiQPPKMmkoStWZN8ESpRl1FYcT3M2znTYZjMlHyXtW0NVtEjAKPmUDxsOdQr304gZu/DmtNHi0fvOXWsjgwuPhMOBpyvD/y/XuHC1xzztRBj2ffcLeojPPdi2BtCVPZioX9LyamWZQ03t8kg4s=
  • List-id: council@xxxxxxxxxxxxxx
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99
  • Thread-index: AQHSErC6jDggEk2IjkWRBb4d5+n8Tw==
  • Thread-topic: Draft Motion - GNSO Validation of CCWG-Accountability Budget Request
  • User-agent: Microsoft-MacOutlook/14.5.6.150930

Council Colleagues -

Attached and copied below, please find a draft motion for consideration during 
our next GNSO Council call (29 SEP), that examines the subject of the proposed 
budget & cost control mechanisms for CCWG-ACCT and Work Stream 2.

In particular, I would like to draw your attention to WHEREAS #4 and RESOLVED 
#4, in which I attempted to capture the concerns raised by Phil and Paul and 
others regarding revisiting the subject of ICANN Jurisdiction in WS2.  Please 
review these provisions closely, and make sure that they accurately reflect 
these points.

Thank you,

J.



Draft Motion - GNSO Validation of CCWG-Accountability Budget Request

WHEREAS,


1.     Per its Charter, the Project Cost Support Team (PCST) has supported the 
CCWG-Accountability in developing a draft budget and cost-control processes for 
the CCWG-Accountability activities for FY17, and has also developed a 
historical analysis of all the transition costs to date (see 
https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf).


2.     The CCWG-Accountability FY17 budget was presented at its plenary meeting 
of June 21st and approved for transmission to the Chartering Organizations for 
validation as per the process agreed with the PCST. This request for validation 
was received on 23 June.


3.     Following review and discussion during ICANN56, the GNSO Council 
requested<https://gnso.icann.org/en/correspondence/bladel-to-bfc-ccwg-accountability-chairs-10jul16-en.pdf>
 a webinar on this topic which was held on 23 August (see transcript at 
https://gnso.icann.org/en/meetings/transcript-ccwg-accountability-webinar-23aug16-en.pdf,
 recording at 
http://audio.icann.org/gnso/gnso-ccwg-accountability-webinar-23aug16-en.mp3 and 
AC recording at https://icann.adobeconnect.com/p8fu99qpt7d/).


4.     The GNSO Council notes that many members of the GNSO community have 
expressed the view that the projected budget does not support revisiting the 
topic of the jurisdiction of ICANN"s organization.


5.     The GNSO Council has discussed and reviewed all the relevant materials.

RESOLVED,


1.     The GNSO Council hereby accepts the proposed CCWG-Accountability FY17 
budget, as well as the cost-control processes presented in conjunction with the 
CCWG budget (see 
https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf).


2.     The GNSO Council expects to receive regular updates on actual 
expenditures as tracked against this adopted budget, and reserves the right to 
provide further input on the budget allocation in relation to the 
CCWG-Accountability related activities.


3.     The GNSO Council expects the CCWG-Accountability and staff to work 
within the constraints of this approved budget, and that excess costs or 
request for additional funding will be considered only in extraordinary 
circumstances.


4.     It is the position of the GNSO Council that revisiting the jurisdiction 
or organization of the ICANN legal entity, as established by 
CCWG-Accountability Work Stream 1, is not supported by this projected budget.


5.     The GNSO Council requests the GNSO Secretariat to communicate this 
resolution to the CCWG-Accountability Chairs, and to the office of the ICANN 
CFO.


Attachment: Draft Motion - Validation CCWG Accountability Budget Request - updated 13 September 2016.docx
Description: Draft Motion - Validation CCWG Accountability Budget Request - updated 13 September 2016.docx



<<< Chronological Index >>>    <<< Thread Index >>>