[Gnso-sc-budget] SOPC + SCBO Agenda 18 Feb 2020 - ICANN's 5YS&OP + FY21 Budget

[policy at bacinblack.com]

Hi All,

 

Please find below the suggested agenda for the 18 Feb 2020 SCBO call at
16:00 UTC for one hour. CCNSO Policy staff are CCed here and will pass this
agenda over to the SOPC team.

 

1.	Confirm attendance and agenda
2.	Welcome & Introductions
3.	Overview of SOPC draft (attached)
4.	Overview of SCBO draft (attached)
5.	Discuss joint session in Cancun (incl. joint action-item on Evolving
the MSM, now Appx. C of 5YS&OP)
6.	Any other business

a.	Next joint meeting 8 Mar 2020 at 15:00 local time

 

**Note, both attached documents are working drafts and should not be
considered final.

 

Near-term Schedule:

*	18 Feb - Joint meeting of the SOPC & SCBO to share draft positions
at 16:00UTC
*	20 Feb - GNSO Council meeting
*	21 Feb - SOPC last day to submit SOPC comments/changes
*	25 Feb - Deadline to submit comments to comment proceeding
*	08 Mar - Joint session at ICANN67 w/ SOPC

 

Please let me know if you have any questions.

 

B

 

Berry A. Cobb

GNSO Policy Consultant

@berrycobbb

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-sc-budget/attachments/20200217/0ed6ec09/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SOPC-input-ICANN-OP21-25-01.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 42467 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-sc-budget/attachments/20200217/0ed6ec09/SOPC-input-ICANN-OP21-25-01-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ICANN 5YS-OP_FY21 Draft ICANN Budget - GNSO Comments_v0.3.1.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 71591 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-sc-budget/attachments/20200217/0ed6ec09/ICANN5YS-OP_FY21DraftICANNBudget-GNSOComments_v0.3.1-0001.docx>