Difference between revisions of "ODP"

From ICANNWiki
Jump to navigation Jump to search
Line 1: Line 1:
An '''Operational Design Phase''' ('''ODP''') is an ICANN organization-level assessment of a [[GNSO#GNSO Council|GNSO Council]]-approved [[PDP|Policy Development Process]] recommendation that is initiated and scoped by the [[ICANN Board]].
+
An '''Operational Design Phase''' ('''ODP''') is an [[ICANN]] organization-level assessment of a [[GNSO#GNSO Council|GNSO Council]]-approved [[PDP|Policy Development Process]] (PDP) recommendation that is initiated and scoped by the [[ICANN Board]].<ref>[https://www.icann.org/en/system/files/files/odp-form-concept-paper-18dec20-en.pdf ODP Concept Paper December 2020]</ref>
  
 
==Overview==
 
==Overview==
This mechanism is meant to provide the Board with the necessary operational information to determine the impact of implementing a GNSO Council-approved recommendation. The assessment helps the Board decide whether the recommendations are in the best interests of the ICANN community (ICANN Bylaws, Annex A, Section 9 (a)). An ODP cannot amend or change the substance or intent of the GNSO Council recommendation. It does not allow the reopening or revisiting of the policy discussions that occurred during the PDP. If ICANN staff, the Board, or the community do not understand the intent of a recommendation or feel that questions remain, they must convey their concerns to the GNSO Council.  
+
This mechanism is meant to provide the Board with the necessary operational information to determine the impact of implementing a GNSO Council-approved recommendation. The assessment helps the Board decide whether the recommendations are in the best interests of the ICANN community.<ref>[https://www.icann.org/resources/pages/governance/bylaws-en/#annexA ICANN Bylaws, Annex A.9 (a)]</ref> An ODP cannot amend or change the substance or intent of the GNSO Council recommendation. It does not allow the reopening or revisiting of the policy discussions that occurred during the PDP. If ICANN staff, the Board, or the community do not understand the intent of a recommendation or feel that questions remain, they must convey their concerns to the GNSO Council.  
 +
 
 +
===History===
 +
The initial draft of the ODP Concept Paper was shared with the [[SO]]/[[AC]] leadership and posted on a blog in early October 2020. THe ODP Concept Paper was then discussed during several [[ICANN 69]] sessions. Written community feedback was gathered throughout November and December 2020. An updated version was shared with community leaders on December 17, 2020, and their feedback was gathered until January 22, 2021. The ICANN Board will vote on the updated version, to be posted on January 29, 2021, and consider whether to launch ODPs for [[EPDP#Phase 2 Report|EPDP Phase 2]] or other consensus recommendations adopted by the GNSO Council.<ref>[https://community.icann.org/display/ODP/Webinar+January+2021?preview=/153520877/155190937/Presentation_ODP_Webinar_final.pdf ODP Presentation January 2021]]</ref>
  
 
==Requirements==
 
==Requirements==
Line 21: Line 24:
  
 
==References==
 
==References==
<ref>https://www.icann.org/en/system/files/files/odp-form-concept-paper-18dec20-en.pdf ODP Concept Paper December 2020]</ref>
 

Revision as of 19:01, 22 January 2021

An Operational Design Phase (ODP) is an ICANN organization-level assessment of a GNSO Council-approved Policy Development Process (PDP) recommendation that is initiated and scoped by the ICANN Board.[1]

Overview

This mechanism is meant to provide the Board with the necessary operational information to determine the impact of implementing a GNSO Council-approved recommendation. The assessment helps the Board decide whether the recommendations are in the best interests of the ICANN community.[2] An ODP cannot amend or change the substance or intent of the GNSO Council recommendation. It does not allow the reopening or revisiting of the policy discussions that occurred during the PDP. If ICANN staff, the Board, or the community do not understand the intent of a recommendation or feel that questions remain, they must convey their concerns to the GNSO Council.

History

The initial draft of the ODP Concept Paper was shared with the SO/AC leadership and posted on a blog in early October 2020. THe ODP Concept Paper was then discussed during several ICANN 69 sessions. Written community feedback was gathered throughout November and December 2020. An updated version was shared with community leaders on December 17, 2020, and their feedback was gathered until January 22, 2021. The ICANN Board will vote on the updated version, to be posted on January 29, 2021, and consider whether to launch ODPs for EPDP Phase 2 or other consensus recommendations adopted by the GNSO Council.[3]

Requirements

Timing

The ICANN Board may initiate the ODP in the final phase of a PDP or after the GNSO Council has approved a recommendation.

Concerns

The Board
  1. feels the complexity of the implementation and the resources it will require necessitate their own assessment, or
  2. needs more information to decide whether the recommendation is in the ICANN community's best interest.

Scope

Initiating an ODP will require the Board to specify its scope, which in most cases should be limited to operational design.

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