Operating Standards for Specific Reviews: Difference between revisions

JP (talk | contribs)
No edit summary
m Text replacement - "__NOTOC__" to ""
 
(5 intermediate revisions by 2 users not shown)
Line 12: Line 12:
==Community Consultation and Drafting Process==
==Community Consultation and Drafting Process==
===ICANN 57===
===ICANN 57===
[[Lars Hoffman]] hosted an open session at [[ICANN 57]] in Hyderabad to "...contin[ue]...a dialogue that started during the drafting of the new Bylaws."<ref name="icann57">[https://icann572016.sched.com/event/8czm/operating-standards-workshop-to-socialize-with-community ICANN 57 Archive - Operating Standards Workshop to Socialize with the Community], November 5, 2016</ref> His presentation included a skeleton draft of an operating standards document.<ref name="skeleton">[https://community.icann.org/download/attachments/63145910/Operating%20Standards%20_%20skeleton.pdf Operating Standards for Reviews Workspace - Operating Standards Skeleton], October 27, 2016</ref> The draft proposed a number of questions for the workshop to consider:
[[Lars Hoffmann]] hosted an open session at [[ICANN 57]] in Hyderabad to "...contin[ue]...a dialogue that started during the drafting of the new Bylaws."<ref name="icann57">[https://icann572016.sched.com/event/8czm/operating-standards-workshop-to-socialize-with-community ICANN 57 Archive - Operating Standards Workshop to Socialize with the Community], November 5, 2016</ref> His presentation included a skeleton draft of an operating standards document.<ref name="skeleton">[https://community.icann.org/download/attachments/63145910/Operating%20Standards%20_%20skeleton.pdf Operating Standards for Reviews Workspace - Operating Standards Skeleton], October 27, 2016</ref> The draft proposed a number of questions for the workshop to consider:
* How should the SO/AC Chairs’ selection process work in detail, to assure efficient proceedings, while adhering to all Bylaw requirements?
* How should the SO/AC Chairs’ selection process work in detail, to assure efficient proceedings, while adhering to all Bylaw requirements?
* How to assure diversity in Review Teams?
* How to assure diversity in Review Teams?
Line 23: Line 23:
There were limited comments in the session itself, with Hoffman suggesting that attendees might need to take some time to fully read and absorb the contents of the skeleton draft.<ref>[https://static.sched.com/hosted_files/icann572016/37/I57%20HYD_Sat05Nov2016-Op%20Standards%20Workshop%20to%20Socialize%20with%20Community-en.pdf ICANN 57 Archive - Transcript, Operating Standards Workshop], November 5, 2016</ref> Feedback from the session included a recommendation to generate a more substantive draft compiling best practices already in place (for example, within the GNSO's guidelines for policy development processes). The particulars of specific reviews - notably, the nomination and selection of review team members from the SOs and ACs - could then be developed and refined against that backdrop.<ref name="feb21v1">[https://community.icann.org/download/attachments/64070188/Operating_Standards_WEBINAR__21FEB17__1500_UTC.pdf OSFR Workspace - Transcript of First Webinar], February 21, 2017</ref>
There were limited comments in the session itself, with Hoffman suggesting that attendees might need to take some time to fully read and absorb the contents of the skeleton draft.<ref>[https://static.sched.com/hosted_files/icann572016/37/I57%20HYD_Sat05Nov2016-Op%20Standards%20Workshop%20to%20Socialize%20with%20Community-en.pdf ICANN 57 Archive - Transcript, Operating Standards Workshop], November 5, 2016</ref> Feedback from the session included a recommendation to generate a more substantive draft compiling best practices already in place (for example, within the GNSO's guidelines for policy development processes). The particulars of specific reviews - notably, the nomination and selection of review team members from the SOs and ACs - could then be developed and refined against that backdrop.<ref name="feb21v1">[https://community.icann.org/download/attachments/64070188/Operating_Standards_WEBINAR__21FEB17__1500_UTC.pdf OSFR Workspace - Transcript of First Webinar], February 21, 2017</ref>


The [[MSSI]] hosted two webinars on February 21, 2017, to update the community on recent developments in the OSFR project and discuss next steps.<ref name="feb21hub">[https://community.icann.org/display/OSFR/21+February+2017 OSFR Workspace - February 21, 2017 Webinar Archive], last updated September 1, 2017</ref>  
The [[MSSI]] hosted two webinars on February 21, 2017, to update the community on recent developments in the OSFR project and discuss next steps.<ref name="feb21hub">[https://community.icann.org/display/OSFR/21+February+2017 OSFR Workspace - February 21, 2017 Webinar Archive], last updated September 1, 2017</ref> As proposed, the MSSI team had created a draft with content folded in from various sources regarding current best practices around reviews. Because of a number of novel issues raised by the new language in Article 4.6, there were still many open questions regarding specific reviews.<ref name="feb21v1" /> At the first webinar, [[Katrina Sataki]] expressed concern that the draft document to date did not include more content around standards for specific reviews: first, because the only provision in the Bylaws around operating standards was specifically housed in Article 4.6; and second, because the SSR2 and ATRT3 reviews were due to kick off in a short period of time, and it seemed unlikely that the operating standards would not be in place before then.<ref name="feb21v1" /> Hoffmann and [[Larisa Gurnick]] acknowledged the concerns but noted that because Article 4.6 specifically required a consultative process, there was no way for staff to expedite the creation of the operating standards, and that it would be inappropriate for staff to tell the SOs and ACs what the policy should be.<ref name="feb21v1" />
 
===ICANN 58===
Following the February webinars, MSSI held a session on review operating standards at [[ICANN 58]] in Copenhagen.<ref name="icann58">[https://icann58copenhagen2017.sched.com/event/9nn7/icann-review-operating-standards-next-steps ICANN 58 Archive - ICANN Review Operating Standards: Next Steps], March 13, 2017</ref> The session was much shorter than its scheduled time, consisting largely of the presentation of material that echoed the themes of the February webinars. There was only one question, from [[Lito Ibarra]], regarding if or how the operating standards would discuss the scope of each of the specific reviews. Hoffman responded that Article 4.6 had provisions defining the scope of each of the specific reviews, so that the operating standards would likely not address that detail, and instead focus on processes where all reviews could benefit from a standard approach.<ref>[https://static.sched.com/hosted_files/icann58copenhagen2017/34/I58CPH_Mon13Mar2017-ICANN%20Review%20Operating%20Standards-Next%20Steps-en.pdf ICANN 58 Archive - Transcript, ICANN Review Operating Standards], March 13, 2017</ref>
 
Following the ICANN 58 session, the MSSI team developed a first draft that incorporated the community feedback, as well as offering "strawman" proposals for specific review processes. There was an informational display at [[ICANN 59]] regarding drafting progress, but no session was held at that meeting.<ref name="draft1web">[https://participate.icann.org/p5y3mb6nvk0/ Video Replay - Draft Operating Standards Webinar], October 19, 2017</ref> In addition, the [[Organizational Effectiveness Committee]] discussed both the first draft operating standards, and issues surrounding specific reviews that had been identified in conversation with leaders of the SOs and ACs. It was determined that the draft should be circulated first to SO/AC leadership prior to publication for public comment, and that the OEC meet with the SO/AC leadership at [[ICANN 60]] to further discuss the draft and the issues identified to date.<ref>[https://www.icann.org/resources/board-material/minutes-oec-2017-09-21-en OEC Meeting Minutes], September 21, 2017</ref> In a webinar, Lars Hoffman presented the state of the draft and provided some specific examples of the proposed processes for specific reviews. There were no comments or questions.<ref name="draft1web" />
 
===First Draft===
The first draft was published for public comment on October 17, 2017.<ref>[https://www.icann.org/public-comments/reviews-standards-2017-10-17-en ICANN.org Public Comment Archive - Draft Operating Standards for Specific Reviews], October 17, 2017 - February 16, 2018</ref> The public comment period was initially scheduled to end on January 15, 2018, but it was extended for an additional three weeks.<ref>[https://www.icann.org/en/announcements/details/public-comment-period-extended-operating-standards-for-icanns-specific-reviews-7-1-2018-en ICANN.org Announcement - Public Comment Period Extended, OSFR Draft, January 7, 2018</ref> At the time that the public comment period was extended, no public comments had been received.<ref>[https://mm.icann.org/pipermail/comments-reviews-standards-17oct17/ ICANN.org Listserv Archive - Public Comments, Draft Operating Standards for Specific Reviews]</ref>
===ICANN 60===
In Abu Dhabi, the cross community session<ref>[https://icann60abudhabi2017.sched.com/event/CbHX/cross-community-session-operating-standards-for-specific-reviews ICANN 60 Archive - Cross Community Session on Operating Standards for Specific Reviews], October 30, 2017</ref> on the draft Operating Standards was chaired by [[Cheryl Langdon-Orr]].<ref name="60trans">[https://static.sched.com/hosted_files/icann60abudhabi2017/14/I60AUH_Mon30Oct2017-CC%20Session%20-%20Operating%20Standards%20for%20Specific%20Reviews-en.pdf ICANN 60 Archive - Transcript, Cross Community Session on OSFR], October 30, 2017</ref> [[Thomas Rickert]] provided some background on the origins of the project, and discussed the activities of the [[Cross Community Working Group on Accountability]] in the aftermath of the [[IANA Transition]].
 
==References==
==References==
{{reflist}}
{{reflist}}
__NOTOC__
 
[[Category:Specific Reviews]]
[[Category:Specific Reviews]]