[council] SCBO - Next Steps

Mon Dec 5 22:11:18 UTC 2022

Thank you, Mason, for your support on this.
The topic is on our AOB agenda for next week's Council meeting.

Kindly,

Sebastien Ducos
GoDaddy Registry / Senior Client Services Manager
Level 8, 10 Queens Road, Melbourne, Australia VIC 3004
Office: +61 3 9886 3710 Mobile: +61 449 623 491 / registry.godaddy

The information contained in this email message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this email message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.
________________________________
From: Cole, Mason (POR) <MCole at perkinscoie.com>
Sent: Monday, December 5, 2022 11:07 pm
To: Sebastien Ducos <Sebastien at registry.godaddy>
Subject: RE: SCBO - Next Steps

Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad at .

Sebastien –

The BC is supportive.  Thanks for the opportunity to weigh in and let me know if you need further information from our constituency.

Thanks –

Mason

Mason Cole | Perkins Coie LLP
INTERNET GOVERNANCE ADVISOR
1120 N.W. Couch Street Tenth Floor
D. +1.503.727.2074
E. MCole at perkinscoie.com<mailto:%20MCole at perkinscoie.com>

From: Sebastien at registry.godaddy<mailto:Sebastien at registry.godaddy> <Sebastien at registry.godaddy<mailto:Sebastien at registry.godaddy>>
Sent: Wednesday, November 16, 2022 3:21 AM
To: COUNCIL at GNSO.ICANN.ORG<mailto:COUNCIL at GNSO.ICANN.ORG>; sdemetriou at verisign.com<mailto:sdemetriou at verisign.com>; aheineman at godaddy.com<mailto:aheineman at godaddy.com>; julf at Julf.com<mailto:julf at Julf.com>; benakin at gmail.com<mailto:benakin at gmail.com>; plommer at gmail.com<mailto:plommer at gmail.com>; lschulman at inta.org<mailto:lschulman at inta.org>; philippe.fouquart at orange.com<mailto:philippe.fouquart at orange.com>; Cole, Mason (POR) <MCole at perkinscoie.com<mailto:MCole at perkinscoie.com>>
Cc: GNSO-Chairs <gnso-chairs at icann.org<mailto:gnso-chairs at icann.org>>; gnso-secs at icann.org<mailto:gnso-secs at icann.org>; secretariat at icannregistrars.org<mailto:secretariat at icannregistrars.org>; secretariat at rysg.info<mailto:secretariat at rysg.info>; Brenda.brewer at icann.org<mailto:Brenda.brewer at icann.org>; andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>
Subject: SCBO - Next Steps

Dear GNSO Council colleagues and SG/C Chairs,

During the GNSO Council & SC/G Chairs call on 26 October, we discussed PDP Improvements and potential next steps for the Standing Committee on ICANN Budget and Operations (SCBO). This message is in regards to the latter. During the call, Council leadership described the proposed path forward, which at a very high level, is to evolve the SCBO away from its limited focus on drafting public comments on behalf of the GNSO Council, towards a central forum for all of the GNSO more broadly to be able to interface with ICANN finance and gather information and ask questions as needed. What is important to note is that this new central forum would NOT be responsible for drafting a singular public comment on behalf of the GNSO; the GNSO Council and SG/Cs would retain the ability to submit individual public comments, as they do now.

Council leadership believes that evolving the SCBO in this manner will meet the needs of both the GNSO Council and GNSO more broadly. Attached, you will find a brief write-up that explains the current state of the SCBO, issues that we have observed with that current state, and then a more detailed description of how we envision the SCBO evolving. We ask that if you have any concerns, please share them with this list by 30 November 2022.

If there are no objections with this approach, we believe it can be put in place as early as the FY24 ICANN Budget & Operating Plan public comment period.

If you have any questions, do not hesitate to ask.

Kindly,

Sebastien Ducos
GoDaddy Registry | Senior Client Services Manager
[signature_4169403054]
+33612284445
France & Australia
sebastien at registry.godaddy<mailto:sebastien at registry.godaddy>

________________________________

NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply email and immediately delete the message and any attachments without copying or disclosing the contents. Thank you.

________________________________

NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply email and immediately delete the message and any attachments without copying or disclosing the contents. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20221205/876ac153/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 44606 bytes
Desc: image001.png
URL: <https://mm.icann.org/pipermail/council/attachments/20221205/876ac153/image001-0001.png>