Preparation Material ccNSO Council Call 12 April 2011
Council Call Agenda: http://www.ccnso.icann.org/workinggroups/agenda-council-12apr11-en.pdf 1. Confirmation of Approval of Minutes and Actions 16 March 2011 See attachment 1 – Draft Minutes 3. Process of Working Group Candidates Proposals to appoint additional members intersessionally See attachment 2 - Compilation of conversation on this topic 4. Implementation Contact Repository Working Group See attachment 3 - Draft Charter 5. NoI on IANA Contract - ccNSO submission See http://www.ntia.doc.gov/comments/110207099-1099-01/attachments/ACF31A%2Epdf - ccTLD submissions See http://www.ntia.doc.gov/comments/110207099-1099-01/ 8. Approval of ccNSO DSSA Working Group Volunteers The ccNSO Council mandated its chair and vice-chair at the time to suggest volunteers for the DSA working group to the council for appointment (council resolution 1 March 2011). The list of suggested DSSA members: Roy Arends, .uk Sean Copeland, .vi Luis Diego Espinoza, .cr, Mark Elkins, .za Jaques Latour, .ca Takayasu Matsuura, .jp Jörg Schweiger, .de, designated co-chair Sean Shen, .cn Chris Wright, .au Katrina Sataki, .lv Otmar Lendl, CERT .at Ondrej Filip, .cz Proposed resolution: The ccNSO council appoints the volunteers as proposed by the Chair and Vice-Chairs. The ccNSO Council appoints Jörg Schweiger as the ccNSO co-chair of the DSSA WG. 9. Other Working Group Updates: 9.1 IDN PDP Working Group 1 See attachment 4 10. ccNSO Website: Closed Section See email copied in below* 11. Status Implementation Recommendations Board Working Group ccNSO Review See attachment 5 – Overview ccNSO Review Recommendations 12. GAC-ccNSO Liaison Working Group See: http://www.ccnso.icann.org/workinggroups/gacwg.htm and http://www.icann.org/presentations/vastenburg-ccnso-ct-02dec04.pdf 13. Liaison Updates: 13.1 At-Large Liaison (Ron Sherwood) See attachment 6, 7, 8, 9, 10: 6) April 12th. 2011 ccNSO Council Meeting - ALAC Liaison Report. 7) ALAC Statement on NTIA NOI. 8) ALAC Statement on the GAC New TLD Scorecard. 9) Comments on the ICANN Board triple x decision. 10) ALAC Statement on Interim Report of the IRDWG. 13.2 GNSO Liaison (Han Chuan Lee) Not provided on time =========== *To agenda point 10 ccNSO Website: Closed Section From: Gabriella Schittek <gabriella.schittek@icann.org <gabriella.schittek@icann.org> > Date: Wed, 26 Jan 2011 06:17:03 -0800 To: "ccnso-council@icann.org <ccnso-council@icann.org> " <ccnso-council@icann.org <ccnso-council@icann.org> > Subject: [ccnso-council] Regarding closed ccNSO website sections Dear Councillors, As per yesterday’s discussion on the Council call, I’m sending you some information about the closed website section: * When conducting interviews with the community on the new website, it was mentioned several times that there is a wish for a closed section. To follow up on this, a small survey was conducted before the Cartagena meeting. Only 7 replies were received, however, 6 of the respondents indicated that they would wish to see some kind of closed section on the website. * Most frequently mentioned was the wish to be able to discuss Working Group issues on the closed website. However, it was also mentioned that a closed section would be useful for voting or for sharing sensitive data, such as statistics, financial reports or for setting up an “Address book” (where contact details of community members, presenters etc. could be listed). So, the Council needs to decide: 1. Should there be closed sections at all 2. If so: What sections should be closed (only Working Group sections, or also more general sections, containing information such as an Address Book, statistics etc.) 3. Who should have access To point 3: In case the Council decides to close some of the page with general information, the definition, which currently is used by the ccTLD community email list for granting email list access, could be used - namely: “ccTLD Managers, administrative contacts and technical contacts of ccTLDs; Staff and board members of ccTLD registries, as approved by the ccTLD Manager or administrative contact; Observers from Regional ccTLD registry organisations, identified by their manager or board; The ccNSO secretariat, the ICANN ccNSO Policy Support Officer and the IANA ccTLD Liaison Officer.” (see Community email list charter: http://www.ccnso.icann.org/about/charter-cctld-community-list.pdf <http://www.ccnso.icann.org/about/charter-cctld-community-list.pdf> ) - other solutions are of course also possible. Regarding implementing a closed section: ICANN has introduced a new tool called Confluence, which is a type of Wiki (a website that allows the creation and editing of pages by those invited to the space). It seems that this tool could support most of the wishes which we received for a closed website. Confluence pages can either be open for everyone, or closed to certain groups. This means that, for instance, working group members could receive passwords for “their” working group and only they can access that space (we have, in fact, already been trying to use this for some working groups with another wiki called Socialtext - but it was not very popular – perhaps due the fact that it wasn’t very user friendly). Confluence also allows for “message board” functions (where participants can leave short comments on topics/documents discussed) and it can be set up so that those who wish receive email alerts of the activities. Once a Working Group is closed, its Wiki space can be archived, if wished for. Furthermore, Confluence can also support some voting functions (keeping the voter anonymous to the community, but open to the manager of the space). So it doesn’t seem that there will be much extra work needed to create closed sections, in case you think this is the way to go. Kind regards, Gabi
participants (1)
-
Gabriella Schittek