CCWG-Accountability-WS2-ICANN57- FacetoFaceMeeting - Revised agenda and references
All, Please find the revised agenda with references below: CCWG-Accountability Agenda for Face to Face meeting 2 November 2106 – ICANN 57 Hyderabad Hall 4 (GAC) Adobe: https://participate.icann.org/hyd57-hall4 9.00 (3:30TUC) – Session 1 • 9:00 - Introduction and General Administration (10’) • 9:10 - PCST report – 5’ • https://www.icann.org/en/system/files/files/iana-transition-statement-activi... • 9:15 - CCWG-Acct. reporting Dashboard – finalization for publication (15’) • https://drive.google.com/file/d/0Bycchop8VaMWRGN5Vl84UGtqM2s/view?usp=sharin... • 9:30 - ATRT2 update presentation (10’) • 9:40 - ATRT3 discussion following Board response to our request (15’) • Original request from the CCWg-Accountability to the Board: https://community.icann.org/display/WEIA/Documents?preview=/59641302/6239909... • Response from the Board: https://drive.google.com/file/d/0Bycchop8VaMWLTd4a0dLbGczSmc/view?usp=sharin... • 9:55 – Ombudsman – CCWG discussion on going forward strategy considering the confirmation of funding for the evaluation (20’) • Progress Report: https://drive.google.com/file/d/0Bycchop8VaMWRGN5Vl84UGtqM2s/view?usp=sharin... 10.15 (04:45UTC) Coffee break 10:30 (05:00UTC) - Session 2 • 10:30 - Exchange with ICANN CEO re: new complaints office and interaction with WS2, especially staff acct and Ombudsman – 60’ • 11:30 - SO/AC Accountability : draft questions to SOs and ACs - 2nd reading – 45’ • Progress Report - https://community.icann.org/pages/viewpage.action?pageId=59643284&preview=/5... • Questions document - https://community.icann.org/pages/viewpage.action?pageId=59643284&preview=/5... 12.15 (06:45UTC) Lunch 13:15 (07:45UTC) Session 3 • 13:15 - Update on the progress of the Jurisdiction subgroup – 30’ • Progress Report - https://community.icann.org/display/WEIA/Jurisdiction?preview=/59643282/6314... • Multiple Layers of Jurisdiction document - https://community.icann.org/display/WEIA/Jurisdiction?preview=/59643282/6314... • Influence of existing Jurisdictions draft - https://drive.google.com/file/d/0Bycchop8VaMWLW9vRE10MDk2QW8/view?usp=sharin... • 13:45 WS1 Implementation - IRP supplementary rules – 2nd reading – 2nd reading (60’) • Progress Report - https://drive.google.com/file/d/0Bycchop8VaMWa3A0a1Q3MjJYMTQ/view?usp=sharin... • Supplementary Rules Clean - https://drive.google.com/file/d/0Bycchop8VaMWTVBibDNZMnhoQTQ/view?usp=sharin... • Supplementary Rules with markups - https://drive.google.com/file/d/0Bycchop8VaMWQjM0dWRua3BwMmM/view?usp=sharin... • 14:45 - Guidelines for Good faith– discussion – 45’ • Progress Report - https://community.icann.org/display/WEIA/Guidelines+for+Good+Faith+Conduct?p... • Annotated Draft - https://community.icann.org/display/WEIA/Guidelines+for+Good+Faith+Conduct?p... 15:30 (10:00UTC) Coffee break 15:45 (10:15UTC) - Session 4 • 15:45 - Transparency subgroup proposals – 2nd reading – 45’ • First Draft Report - https://community.icann.org/display/WEIA/Transparency?preview=/59643288/6314... • 16:30 - Requests for external support / advice : Ombudsman (External review), Human right, Legal Committee (45’) 17:15 (11:45UTC) AOB (15’) 17:30 (12:00UTC) Conclusion and key messages for co-chairs’ publication (30’) 18.00 (12:30UTC) End of meeting Bernard Turcotte ICANN Staff Support to the CCWG-Accountability for the CCCWG-Accountability Co-Chairs
Dear Bernie Some of us cannot access google drive docs… could you please kindly send them as pdfs/word/google docs? Thanks and regards Jorge Von: accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org] Im Auftrag von Bernard Turcotte Gesendet: Dienstag, 1. November 2016 18:38 An: Accountability Cross Community <accountability-cross-community@icann.org> Betreff: [CCWG-ACCT] CCWG-Accountability-WS2-ICANN57- FacetoFaceMeeting - Revised agenda and references All, Please find the revised agenda with references below: CCWG-Accountability Agenda for Face to Face meeting 2 November 2106 – ICANN 57 Hyderabad Hall 4 (GAC) Adobe: https://participate.icann.org/hyd57-hall4 9.00 (3:30TUC) – Session 1 • 9:00 - Introduction and General Administration (10’) • 9:10 - PCST report – 5’ • https://www.icann.org/en/system/files/files/iana-transition-statement-activi... • 9:15 - CCWG-Acct. reporting Dashboard – finalization for publication (15’) • https://drive.google.com/file/d/0Bycchop8VaMWRGN5Vl84UGtqM2s/view?usp=sharin... • 9:30 - ATRT2 update presentation (10’) • 9:40 - ATRT3 discussion following Board response to our request (15’) • Original request from the CCWg-Accountability to the Board: https://community.icann.org/display/WEIA/Documents?preview=/59641302/6239909... • Response from the Board: https://drive.google.com/file/d/0Bycchop8VaMWLTd4a0dLbGczSmc/view?usp=sharin... • 9:55 – Ombudsman – CCWG discussion on going forward strategy considering the confirmation of funding for the evaluation (20’) • Progress Report: https://drive.google.com/file/d/0Bycchop8VaMWRGN5Vl84UGtqM2s/view?usp=sharin... 10.15 (04:45UTC) Coffee break 10:30 (05:00UTC) - Session 2 • 10:30 - Exchange with ICANN CEO re: new complaints office and interaction with WS2, especially staff acct and Ombudsman – 60’ • 11:30 - SO/AC Accountability : draft questions to SOs and ACs - 2nd reading – 45’ • Progress Report - https://community.icann.org/pages/viewpage.action?pageId=59643284&preview=/5... • Questions document - https://community.icann.org/pages/viewpage.action?pageId=59643284&preview=/5... 12.15 (06:45UTC) Lunch 13:15 (07:45UTC) Session 3 • 13:15 - Update on the progress of the Jurisdiction subgroup – 30’ • Progress Report - https://community.icann.org/display/WEIA/Jurisdiction?preview=/59643282/6314... • Multiple Layers of Jurisdiction document - https://community.icann.org/display/WEIA/Jurisdiction?preview=/59643282/6314... • Influence of existing Jurisdictions draft - https://drive.google.com/file/d/0Bycchop8VaMWLW9vRE10MDk2QW8/view?usp=sharin... • 13:45 WS1 Implementation - IRP supplementary rules – 2nd reading – 2nd reading (60’) • Progress Report - https://drive.google.com/file/d/0Bycchop8VaMWa3A0a1Q3MjJYMTQ/view?usp=sharin... • Supplementary Rules Clean - https://drive.google.com/file/d/0Bycchop8VaMWTVBibDNZMnhoQTQ/view?usp=sharin... • Supplementary Rules with markups - https://drive.google.com/file/d/0Bycchop8VaMWQjM0dWRua3BwMmM/view?usp=sharin... • 14:45 - Guidelines for Good faith– discussion – 45’ • Progress Report - https://community.icann.org/display/WEIA/Guidelines+for+Good+Faith+Conduct?p... • Annotated Draft - https://community.icann.org/display/WEIA/Guidelines+for+Good+Faith+Conduct?p... 15:30 (10:00UTC) Coffee break 15:45 (10:15UTC) - Session 4 • 15:45 - Transparency subgroup proposals – 2nd reading – 45’ • First Draft Report - https://community.icann.org/display/WEIA/Transparency?preview=/59643288/6314... • 16:30 - Requests for external support / advice : Ombudsman (External review), Human right, Legal Committee (45’) 17:15 (11:45UTC) AOB (15’) 17:30 (12:00UTC) Conclusion and key messages for co-chairs’ publication (30’) 18.00 (12:30UTC) End of meeting Bernard Turcotte ICANN Staff Support to the CCWG-Accountability for the CCCWG-Accountability Co-Chairs
Good evening:
This is further to the discussion earlier today about ICANN's open contracting policies, sometimes referred to as procurement policy. I had not planned to write about this, but since audio problems in the Adobe Connect inhibited some aspects of the discussion, allow me to submit the following notes. 1. I do not have a relevant benchmark in the form of ICANN's existing procurement policies. It is quite normal for such entities whether in the private or public sectors to have an open, pro-competitive procurement policy. I assume that there is something in ICANN that responds to this expectation, but I do not know about it. 2. The question, today, came up in the context of the draft report on Transparency. But as far as I can see, the contracting aspects of transparency are only touched upon in the draft report under "questions for further consideration" (p. 9 of 18). Consequently I feel that we do not have the necessary background to reach any conclusions at this time. 3. Meanwhile, an open contracting policy should be a normal corporate practice. Transparency aspects are only one of several considerations. 4, What I would have said earlier today (should Adobe audio have allowed), would have been along the following lines: (a) open contracting is advantageous, creating a portfolio of available suppliers, reducing prices through competition and avoiding risks of favouritism or inertia in procurement practices. (b) in the international context it facilitates access to expertise and specific skills. It also opens markets to lower-cost suppliers. ( c) there is extensive international experience as to how to define and manage the limits to open contracting in terms of thresholds, rigorous specifications, time limits, confidentiality, accounting etc. 5. In the light of the discussion earlier today, may I say that this has very little to do with emulating governmental procurement policies, as such. ICANN and the ICANN community would benefit from open contracting, on its merits. Regards CW
On 2 Nov 2016, at 3:38 PM, Christopher Wilkinson <lists@christopherwilkinson.eu> wrote:
... 1. I do not have a relevant benchmark in the form of ICANN's existing procurement policies. It is quite normal for such entities whether in the private or public sectors to have an open, pro-competitive procurement policy. I assume that there is something in ICANN that responds to this expectation, but I do not know about it.
2. The question, today, came up in the context of the draft report on Transparency. But as far as I can see, the contracting aspects of transparency are only touched upon in the draft report under "questions for further consideration" (p. 9 of 18). Consequently I feel that we do not have the necessary background to reach any conclusions at this time.
3. Meanwhile, an open contracting policy should be a normal corporate practice. Transparency aspects are only one of several considerations.
4, What I would have said earlier today (should Adobe audio have allowed), would have been along the following lines:
(a) open contracting is advantageous, creating a portfolio of available suppliers, reducing prices through competition and avoiding risks of favouritism or inertia in procurement practices.
(b) in the international context it facilitates access to expertise and specific skills. It also opens markets to lower-cost suppliers.
( c) there is extensive international experience as to how to define and manage the limits to open contracting in terms of thresholds, rigorous specifications, time limits, confidentiality, accounting etc.
5. In the light of the discussion earlier today, may I say that this has very little to do with emulating governmental procurement policies, as such. ICANN and the ICANN community would benefit from open contracting, on its merits.
Christopher - You raise an an Interesting concept. For those of us who are unaware of “open contracting policy”, but otherwise addicted to reading, is there common reference (i.e. document or web site) which outlines the specific attributes of an open contracting policy and benefits of same? Thanks! /John Disclaimer: my views alone - these elections are commuting to Hyderabad, as I am not…
Dear John:
is there common reference (i.e. document or web site) which outlines the specific attributes of an open contracting policy and benefits of same?
Thankyou for your question. I guess that we shall find an answer for you, but meanwhile: - this policy is professionally ingrained such that personally I have no knowledge of (nor need for) a common reference - that which I have written for the CCWG List is sui generis. I hope this helps for the time being… CW On 02 Nov 2016, at 20:59, John Curran <jcurran@istaff.org> wrote:
On 2 Nov 2016, at 3:38 PM, Christopher Wilkinson <lists@christopherwilkinson.eu> wrote:
... 1. I do not have a relevant benchmark in the form of ICANN's existing procurement policies. It is quite normal for such entities whether in the private or public sectors to have an open, pro-competitive procurement policy. I assume that there is something in ICANN that responds to this expectation, but I do not know about it.
2. The question, today, came up in the context of the draft report on Transparency. But as far as I can see, the contracting aspects of transparency are only touched upon in the draft report under "questions for further consideration" (p. 9 of 18). Consequently I feel that we do not have the necessary background to reach any conclusions at this time.
3. Meanwhile, an open contracting policy should be a normal corporate practice. Transparency aspects are only one of several considerations.
4, What I would have said earlier today (should Adobe audio have allowed), would have been along the following lines:
(a) open contracting is advantageous, creating a portfolio of available suppliers, reducing prices through competition and avoiding risks of favouritism or inertia in procurement practices.
(b) in the international context it facilitates access to expertise and specific skills. It also opens markets to lower-cost suppliers.
( c) there is extensive international experience as to how to define and manage the limits to open contracting in terms of thresholds, rigorous specifications, time limits, confidentiality, accounting etc.
5. In the light of the discussion earlier today, may I say that this has very little to do with emulating governmental procurement policies, as such. ICANN and the ICANN community would benefit from open contracting, on its merits.
Christopher -
You raise an an Interesting concept.
For those of us who are unaware of “open contracting policy”, but otherwise addicted to reading, is there common reference (i.e. document or web site) which outlines the specific attributes of an open contracting policy and benefits of same?
Thanks! /John
Disclaimer: my views alone - these elections are commuting to Hyderabad, as I am not…
Hello Christopher.
1. I do not have a relevant benchmark in the form of ICANN's existing procurement policies. It is quite normal for such entities whether in the private or public sectors to have an open, pro-competitive procurement policy. I assume that there is something in ICANN that responds to this expectation, but I do not know about it.
ICANN's current procurement guidelines are available at: https://www.icann.org/en/system/files/files/procurement-guidelines-21feb10-e... I have attached for your convenience. Regards, Bruce Tonkin
Thank you Bruce to have shared the information and references below. In addition, relative to the competitive part of the procurement policy, you will find below the link to the page of ICANN.org where all Requests For Proposals (RFPs) conducted by ICANN in accordance with its procurement policy are posted. https://www.icann.org/resources/pages/governance/rfps-en Thank you. Best, Xavier Xavier Calvez ICANN CFO 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 Office : +1 (310) 301 5838 Mobile : +1 (805) 312 0052 Fax : +1 (310) 957-2348 -----Original Message----- From: <accountability-cross-community-bounces@icann.org> on behalf of Bruce Tonkin <Bruce.Tonkin@melbourneit.com.au> Date: Thursday, November 3, 2016 at 9:03 AM To: Accountability Cross Community <accountability-cross-community@icann.org> Subject: Re: [CCWG-ACCT] CCWG-Accountability-WS2-ICANN57- FacetoFaceMeeting - open contracting policies Hello Christopher. >> 1. I do not have a relevant benchmark in the form of ICANN's existing procurement policies. It is quite normal for such entities whether in the private or public sectors to have an open, pro-competitive procurement policy. I assume that there is something in ICANN that responds to this expectation, but I do not know about it. ICANN's current procurement guidelines are available at: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system... I have attached for your convenience. Regards, Bruce Tonkin
participants (6)
-
Bernard Turcotte -
Bruce Tonkin -
Christopher Wilkinson -
John Curran -
Jorge.Cancio＠bakom.admin.ch -
Xavier J. Calvez