Operational Design Phase: Difference between revisions

Jessica (talk | contribs)
Created page with "An '''Operational Design Phase''' ('''ODP''') is an ICANN organization-level assessment of a GNSO Council-approved Policy Development Process rec..."
 
Jessica (talk | contribs)
No edit summary
Line 10: Line 10:
:The Board  
:The Board  
#feels the complexity of the implementation and the resources it will require necessitate their own assessment, or
#feels the complexity of the implementation and the resources it will require necessitate their own assessment, or
# needs more information to decide whether the recommendation is in the ICANN community's best interest.<br />
#needs more information to decide whether the recommendation is in the ICANN community's best interest.<br />
'''Scope'''
'''Scope'''
:Initiating an ODP will require the Board to specify its scope, which in most cases should be limited to operational design.<br />
:Initiating an ODP will require the Board to specify its scope, which in most cases should be limited to operational design.<br />
'''Structure'''
:The ICANN CEO forms a team led by a subject matter expert, encourages the GNSO Council to provide a liaison to the team, and :includes updates and reports on a webpage dedicated to ODPs.
==Integration with the Existing Consensus Policy Implementation Framework==
In 2015, ICANN organization and the GNSO's Policy and Implementation WG developed the Consensus Policy Implementation Framework ([[CPIF]]), which shapes how ICANN prepares materials for the Board's consideration of
GNSO Council recommendations. The ODP will become part of the CPIF, and after two ODPs have been completed, ICANN will assess the mechanism.
==References==
<ref>https://www.icann.org/en/system/files/files/odp-form-concept-paper-18dec20-en.pdf ODP Concept Paper December 2020]</ref>