Jump to content

Policy Development Process: Difference between revisions

From ICANNWiki
← Older edit
VisualWikitext
Jessica (talk | contribs)
Bureaucrats, Check users, lookupuser, Administrators, translator
14,952 edits
Christiane (talk | contribs)
Bureaucrats, steward, Administrators, translator
3,242 edits
m Christiane moved page PDP to Policy Development Process over redirect: Standardize
 
(17 intermediate revisions by one other user not shown)
Line 1: Line 1:
The '''Policy Development Process''' ('''PDP''') is a common set of practices used in the creation or change of policies related to [[ICANN]] and its constituencies.
A '''Policy Development Process''' ('''PDP''') is a set of practices used in the creation or change of policies related to [[ICANN]] and its constituencies. PDP refers to the steps an organization takes to fulfill its objectives, generate its guidelines, and structure its actions.


The '''policy development process''' '''(PDP)''' entails the steps and actions of an organization such as the [[GNSO]]. By means of its policy development process, each ICANN body seeks to fulfill its objectives. [[ICANN]] is an organization that has always been focused on policy development by means of consensus to attract support and generate compliance throughout the entire global Internet community.<ref>[http://www.icann.org/en/committees/evol-reform/working-paper-process-07may02.htm ICANN policy development]</ref>
All policy recommendations are formed and refined by ICANN's Supporting Organizations ([[SO]]s) and influenced by ICANN's Advisory Committees ([[AC]]s).


==ICANN Policy Development Staff==
===ICANN Body Policymaking===  
===Work Products===
Every [[SO]] has its own PDP.<br />
[[PDP Updates]] are one-page documents prepared by ICANN staff to inform the Governmental Advisory Committee ([[GAC]]) and other interested parties about potential opportunities to engage in and contribute to on-going GNSO PDP efforts. They are published on a regular basis and translations of these can be found on the GAC website.
 
'''GNSO'''
:''Main article: [[GNSO#GNSO Policy Development Process|GNSO PDP]]''
: The GNSO is responsible for developing and recommending [[gTLD]] policies to the [[ICANN Board]]. The PDP for the GNSO is outlined in Annex A of the [[ICANN Bylaws]]. Under certain circumstances, the GNSO can initiate an Expedited Policy Development Process ([[EPDP#Background on the EPDP|EPDP]]).
 
'''ccNSO'''
:''Main article: [[ccNSO#ccNSO Policy Development Process|ccNSO PDP]]''
: The ccNSO develops policies on [[ccTLD]]s. The PDP of the ccNSO is outlined in Annex B of the [[ICANN Bylaws]].<br />
 
'''ASO'''
:''Main article: [[ASO#Policymaking Process|ASO PDP]]''
: The role of the ASO in ICANN policymaking, outlined in the [[Memorandum of Understanding]], concerns the operation, assignment, and management of [[IP]] addresses. The ASO compiles and reviews policies that have already undergone the regional PDP within each of the five [[RIR]]s, after which it passes the unified, ratified version of the original policy to the [[ICANN Board]].
 
Every [[AC]] has its own policy advice development process (PADP).<br />
 
'''GAC'''
:''Main article: [[GAC#GAC Policy Advice Development Process|GAC PADP]]''
: The GAC advises the ICANN Board on issues related to governments, especially when ICANN's policies intersect with laws or international agreements.<br />
 
'''ALAC'''
:''Main article: [[ALAC#The Role of the ALAC|ALAC PADP]]''
: The ALAC considers the interests of individual Internet users and develops advice that it shares through the [[Public Comment]] Proceedings.<br />


==The creation of PDP==
'''SSAC'''
The policy development process is proposed by a policy working group from various organizations and members of an [[RIR]]. Based on the PDP, various policies are discussed within a specific community and ratified by the [[RIR]] Board after consensus has been reached.  
:''Main article: [[SSAC#How does SSAC work?|SSAC PADP]]''
: The SSAC, which is invite-only, generates advisories through which it provides guidance to the ICANN Board on the security and integrity of the Internet's naming and address allocation systems.<br />


The specific stages involved in PDP ratification are:
'''RSSAC'''
# The policy development process is proposed (by any member).
:''Main article: [[RSSAC#RSSAC Policy Advice Development|RSSAC PADP]]''
# It is further analyzed by the appropriate [[RIR]] via mailing lists. Anyone can join such discussions.
: The RSSAC generates advisories through which it guides the ICANN community and Board on the operation, administration, security, and integrity of the Internet's Root Server System.<br />
# After a period of 30 days, the PDP is brought to an open public meeting for further discussion and the possibility of consensus.
# If consensus is achieved, then the next step will be applied. If consensus is not achieved, another period of 30 days will be allowed for more discussion and debate, until consensus is achieved. If consensus is still not achieved, the PDP may be abandoned. 
# If consensus is achieved, another period of 15 days will be given for anyone from the community to provide new observations and suggestions for final changes.
# The policy is ratified by the Board of Trustees and the policy is adopted for use.<ref>[http://www.afrinic.net/pdp.htm PDP process]</ref>


==PDP working groups==
==ICANN Policy Development Support Staff==
The working groups that propose such policy development processes consist of volunteer members, who can be either individuals or representatives from an organization. In order to ratify the PDP there is a need for consensus. Due to the fact that working groups consist of volunteers, various problems can occur such as:
ICANN strives to develop policy by means of consensus because the organization believes it offers the best way to attract support and generate compliance throughout the entire global Internet community.<ref>[http://www.icann.org/en/committees/evol-reform/working-paper-process-07may02.htm ICANN policy development]</ref> Toward this end, ICANN provides a 32-person [[Policy Development Support Team]] from around the world to assist and shepherd policy and advice development.<ref>[https://www.icann.org/policy#staff ICANN Policy Staff]</ref>
* If the number of members within a working group is too small, then the development process is slowed down and achievements are more difficult to be achieved;
* If the number of members within a working group is too large, then a consensus is more difficult to be reached due to different opinion and the development process can be delayed;
* The lack of experience and knowledge of some members can complicate the development process.


See [[PDP-WT]].
===Work Products===
'''PDP Updates''' are one-page documents prepared by ICANN staff to inform the Governmental Advisory Committee ([[GAC]]) and other interested parties about potential opportunities to engage in and contribute to on-going GNSO PDP efforts. They are published on a regular basis and translations of these can be found on the GAC website.
To prepare the community for Public Meetings, the Policy Development Support Staff make '''presentations''', which they share a week or two before each meeting.<ref>[https://www.icann.org/resources/pages/presentations-2012-08-27-en ICANN presentations]</ref>


==The GPDP==
==Working Groups==
The GPDP is an acronym used for ''"Generic Policy Development Process"'' and represents a tool used to improve the quality of regulatory interventions by providing explicit but generic processes for clear and effective regulatory development.<ref>[http://www.med.govt.nz/templates/MultipageDocumentTOC____9285.aspx GPDP]</ref>
Every ICANN body relies on [[Working Group]]s or [[Working Group#ICANN Work Parties|Work Parties]] to propose or develop policies or advice. Working groups consist of volunteer members, who can act as individuals or representatives of an organization. They play a key role in the ratification of policies by engaging in dialogue and seek consensus among their members. Working groups can encounter various problems, such as
* Too few members within a working group can slow PDP;
* Too many members within a working group can make a consensus more difficult to reach due to differences in opinion and delays in the PDP; and
* A lack of experience and knowledge can complicate the PDP.


==References==
==References==

Latest revision as of 17:24, 22 June 2024

A Policy Development Process (PDP) is a set of practices used in the creation or change of policies related to ICANN and its constituencies. PDP refers to the steps an organization takes to fulfill its objectives, generate its guidelines, and structure its actions.

All policy recommendations are formed and refined by ICANN's Supporting Organizations (SOs) and influenced by ICANN's Advisory Committees (ACs).

ICANN Body Policymaking[edit | edit source]

Every SO has its own PDP.

GNSO

Main article: GNSO PDP
The GNSO is responsible for developing and recommending gTLD policies to the ICANN Board. The PDP for the GNSO is outlined in Annex A of the ICANN Bylaws. Under certain circumstances, the GNSO can initiate an Expedited Policy Development Process (EPDP).

ccNSO

Main article: ccNSO PDP
The ccNSO develops policies on ccTLDs. The PDP of the ccNSO is outlined in Annex B of the ICANN Bylaws.

ASO

Main article: ASO PDP
The role of the ASO in ICANN policymaking, outlined in the Memorandum of Understanding, concerns the operation, assignment, and management of IP addresses. The ASO compiles and reviews policies that have already undergone the regional PDP within each of the five RIRs, after which it passes the unified, ratified version of the original policy to the ICANN Board.

Every AC has its own policy advice development process (PADP).

GAC

Main article: GAC PADP
The GAC advises the ICANN Board on issues related to governments, especially when ICANN's policies intersect with laws or international agreements.

ALAC

Main article: ALAC PADP
The ALAC considers the interests of individual Internet users and develops advice that it shares through the Public Comment Proceedings.

SSAC

Main article: SSAC PADP
The SSAC, which is invite-only, generates advisories through which it provides guidance to the ICANN Board on the security and integrity of the Internet's naming and address allocation systems.

RSSAC

Main article: RSSAC PADP
The RSSAC generates advisories through which it guides the ICANN community and Board on the operation, administration, security, and integrity of the Internet's Root Server System.

ICANN Policy Development Support Staff[edit | edit source]

ICANN strives to develop policy by means of consensus because the organization believes it offers the best way to attract support and generate compliance throughout the entire global Internet community.[1] Toward this end, ICANN provides a 32-person Policy Development Support Team from around the world to assist and shepherd policy and advice development.[2]

Work Products[edit | edit source]

PDP Updates are one-page documents prepared by ICANN staff to inform the Governmental Advisory Committee (GAC) and other interested parties about potential opportunities to engage in and contribute to on-going GNSO PDP efforts. They are published on a regular basis and translations of these can be found on the GAC website. To prepare the community for Public Meetings, the Policy Development Support Staff make presentations, which they share a week or two before each meeting.[3]

Working Groups[edit | edit source]

Every ICANN body relies on Working Groups or Work Parties to propose or develop policies or advice. Working groups consist of volunteer members, who can act as individuals or representatives of an organization. They play a key role in the ratification of policies by engaging in dialogue and seek consensus among their members. Working groups can encounter various problems, such as

  • Too few members within a working group can slow PDP;
  • Too many members within a working group can make a consensus more difficult to reach due to differences in opinion and delays in the PDP; and
  • A lack of experience and knowledge can complicate the PDP.

References[edit | edit source]

Generic Names Supporting Organization. Develops and recommends to the Board substantive policies relating to generic top-level domains and other responsibilities set forth in the Bylaws (ICANN Bylaws).

Country Code Names Supporting Organization. Develops and recommends to the Board global policies relating to country-code top-level domains (ICANN Bylaws).

Address Supporting Organization. Advises the Board with respect to policy issues relating to the operation, assignment, and management of Internet addresses (ICANN Bylaws).

Governmental Advisory Committee. Considers and provides advice on the activities of ICANN as they relate to concerns of governments, particularly matters where there may be an interaction between ICANN's policies and various laws and international agreements or where they may affect public policy issues (ICANN Bylaws).

At-Large Advisory Committee. Considers and provides advice on the activities of ICANN related to the interests of individual Internet users (ICANN Bylaws). Not to be confused with the Non-Commercial Stakeholder Group.

Security and Stability Advisory Committee. Advises the ICANN community and Board on matters relating to the security and integrity of the Internet's naming and address allocation systems (ICANN Bylaws).

Root Server System Advisory Committee. Advises the ICANN community and Board on matters relating to the operation, administration, security, and integrity of the Internet's Root Server System (ICANN Bylaws).

Retrieved from "https://icannwiki.org/index.php?title=Policy_Development_Process&oldid=1351288"