Perfect. Thxx On Mon, Dec 21, 2020 at 11:03 AM Joke Braeken <joke.braeken@icann.org> wrote:
Dear Councillors.
This is a follow-up to the update from last week, regarding the progress of the Drafting Team.
The team met a few hours ago, and found consensus on the way forward. The proposed text is about to be finalized, but based on today’s discussion, it requires some minor additional tweaks and a final review by the drafting team members. As we approach the end-of-year holiday break, you may expect the proposed draft response on 8 January. The deadline for your review and comments remains unchanged: 19 January (23:59 UTC). Thank you.
Best regards,
Joke Braeken
ccNSO Policy Advisor
joke.braeken@icann.org
*From: *Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Joke Braeken <joke.braeken@icann.org> *Date: *Thursday, 17 December 2020 at 16:30 *To: *ccnso-council <ccnso-council@icann.org> *Subject: *[ccnso-council] Written update: Agenda item 10 | Council meeting 168 (17 December 2020 | 18 UTC)
Dear Councilors,
Below please find a written update regarding agenda item number 10 on the agenda for today’s Council meeting, scheduled to be held on 17 December at 18 UTC. I am sending you the update on behalf of Ai-Chin Lu (.tw), designated Councilor leading the drafting team.
= = =
A drafting team is currently preparing a response to questions from ICANN legal regarding a Bylaw change to include IDN ccTLDs as members to the ccNSO. Since its appointment, the drafting team met twice, and its last meeting was on 16 December. The drafting team will use the ccNSO Statement procedure as described in the applicable guideline [ccnso.icann.org] <https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/filef...> and is expected to submit its proposed draft to the ccNSO Council before the end-of-year holiday break. The original timeline previously sent to the Council was adjusted slightly. Please find the latest version below. The deadline for comments by Councilors is mid-January. Once the input from the ccNSO Council was taken into account, the draft will be sent to the ccNSO membership for input. Council is expected to adopt the statement around mid-February.
As a heads up: During its January meeting, the Drafting Team will discuss the submission of a note to Council, regarding an issue to be addressed in future around the topic of ccTLD managers that manage more than one ASCII ccTLD, their membership in the ccNSO, and the implications related to for instance voting.
Timeline (v2)
· Opening call for volunteers Drafting Team 24 November
· Closure call for volunteers Drafting Team 2 Dec. (noon UTC)
· Secretariat asks Council to appoint the Drafting Team 2 Dec. (> noon UTC)
· Council deadline to appoint the DT 4 Dec. (23:59 UTC)
· Drafting Team meeting #1 7 Dec. (10:00 UTC)
· Drafting Team meeting #2 16 Dec. (10:00 UTC)
· Drafting Team meeting #3 21 Dec. (10:00 UTC)
· Drafting team sends its draft statement to Council for review 21 December
· End-of-year holiday season. ICANN closes between 24 Dec. and 3 Jan.
· Deadline for Council input: 19 Jan. (23:59 UTC)
· Drafting Team meeting #4: 20 January (10:00 UTC)
· Draft statement sent to ccNSO members for input 21 January
· Deadline for comments by ccNSO members 29 January (23:59 UTC)
· Drafting Team sends final version to Council for adoption 1 February
· Deadline adoption ccNSO statement by Council mid-February
Ai-Chin Lu
= = =
Best regards,
Joke Braeken
ccNSO Policy Advisor
joke.braeken@icann.org
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.