Page History

Notes/ Action Items

[Action Items]

1. Staff to prepare the motion and final charter for the leadership to submit to the GNSO Council by Sunday, 3 November.
2. CCOICI Team members to share the updated charter with their respective groups for feedback, if any/confirmation.
3. CCOICI Team members to discuss with each SG/C on who will represent for SCCI.

[Notes]

1. Welcome and SOI Updates

• Looking forward to seeing everyone at ICANN81 (Istanbul) soon!

1. Announcements, Work plan and upcoming meeting schedule

• When the draft charter is stable, leadership/staff will submit the motion/charter by 3 November.
• A “Call for Volunteers” will be sent across the GNSO community after ICANN81 for each SG/C to deliberate on volunteers.
• Councilors will be shared the revised charter for a permanent CCOICI with their respective groups, drawing specific attention to the membership structure Tuesday, 29 October.
• Leadership also requests the CCOICI Team members to share the updated charter with their respective groups for feedback/confirmation.
• Leadership proposed to change the name from CCOICI to something new, as the membership structure will now change from the limited Council members to the broad community of GNSO – some suggestions were made such as, GIC, GCIC, SCCI, SCI, etc. - a poll was conducted, and the results can be found below in agenda item 3c.

*Action Items: 1) Staff to prepare the motion and final charter for the leadership to submit to the GNSO Council by Sunday, 3 November; 2) CCOICI Team members to share the updated charter with their respective groups for feedback, if any/confirmation.

1. Final CCOICI Charter Review

• See charter and comments here:https://docs.google.com/document/d/1FwmmG9EItCEfyIp0CeEQP6lCsQ7IT4pTGvzCL9EMoO4/edit?usp=sharing [docs.google.com] [docs.google.com]

1. Members report back from discussions of the charter in their groups;

• No report back yet from CCOICI Team members
• Leadership requests the CCOICI Team members to share the updated charter with their respective groups for feedback/confirmation.

1. Question from presentation to Council re: deliverables (see page 6)

• During the 17 October GNSO Council Meeting, Jeffrey Neuman asked a question for the CCOICI to consider: So the Task Forces would report directly to the Council or would it send it to the Council Committee?
• As this information was discussed within the Team but not explicitly described in the charter, the Team decided to add a few lines to make this reporting/communication clear.
  • The Team agreed to keep the following additional line that is currently included in the charter, which can be found in p.6 of the charter:
    “For avoidance of doubt, though the CCOICI would initially suggest the need/formation of a TF, the TF’s final outcome will be sent directly to and considered by the Council, as the Council has oversight.”
  • Staff will add an additional line to the charter, as agreed upon by the Team, which describes the TF-CCOICI relationship (report-wise/leadership-wise)
  • E.g.: “The TF leadership team will join CCOICI team calls periodically to provide updates of the project prior to its review and consideration by the Council.”

1. Any other resolved issues, if applicable.

• Leadership’s suggestions in pp.4-5 (Board Liaison’s capacity and Leadership Structure) were all agreed upon by the Team.
• CCOICI Team members conducted a poll to change the name to SCCI (candidate names: GCIC, SCCI, and SCI)
• The SCCI will be short for the “Standing Committee on Continuous Improvement”

*Action Item: CCOICI Team members to share the updated charter with their respective groups for feedback, if any/confirmation.

1. Next Steps & AOB

• As announced, shortly after ICANN81, a Call for Volunteers will be sent out
• Please discuss with each SC/C who will represent for SCCI
• A busy 2025 lies ahead

*Action Item: CCOICI Team members to discuss with each SG/C on who will represent for SCCI.