Registry Services Evaluation Policy: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
The '''Registry Services Evaluation | The '''Registry Services Evaluation Policy (RSEP)''' Process is a set of protocols designed to screen and approve proposals made by [[gTLD]] operators to add or modify registry services. To submit a request for the implementation of new Registry Services, all [[gTLD]]s must take into account RSEP's provisions. The RSEP is required by [[ICANN]] in order to make sure that no significant competition issues are raised. | ||
==History== | |||
The | RSEP was created through [[ICANN|ICANN's]] consensus for policy development process.<ref>[http://www.icann.org/en/registries/rsep/prelim-competition-issues-en.htm ICANN.org]</ref> | ||
On June 30, 2005, the GNSO released its [[PDP]] Final Report on the "Procedure for use by ICANN in considering requests for consent and related contractual amendments to allow changes in the architecture or operation of a gTLD registry."<ref>[https://gnso.icann.org/en/issues/registry-services/final-rpt-registry-approval-10july05.htm#1. RSEP Final Report, GNSO]</ref> | |||
November 8, 2005, the ICANN Board directed that this procedure for considering requests for new Registry Services be guided by the provisions in the [[.net]] [[Registry Agreement]], per the GNSO's recommendation, which became the Registry Services Evaluation Policy process.<ref>[https://www.icann.org/resources/pages/rsep-implementation-notes-2019-04-30-en RSEP Implementation, ICANN Resources]</ref> | |||
[[File:RSEP 2006 to 2017.png|600px|thumbnail|right|Summary Analysis of RSEP Requests: 2006-2017 ([https://www.icann.org/resources/pages/rsep-requests-summary-2016-04-20-en ICANN Resources])]] | |||
{| cellpadding=10 style="vertical-align:top; text-align:left; color: green; vertical-align:top" | |||
! Years !! Requests !! Factors !! | |||
|- | |||
| 2006 || 4 || First year | |||
|- | |||
| 2006 to 2012 || 8 on average || | |||
|- | |||
| 2013 to 2017 || 54 on average || The increase in the number of gTLDs | |||
Alignment of service offerings across gTLDs supported by common back-end registry service providers | |||
Requests for release of reserved names | |||
|- | |||
| 2015 to 2017 || drop from 101 to 42 || | |||
|} | |||
In 2019, [[RySG]] and [[ICANN]] org updated how to implement the policy without altering it to make it easier to understand and more predictable. | |||
==RSEP request assessment== | ==RSEP request assessment== | ||
When determining whether the RSEP request could raise significant competition issues, a review is necessary. The stages and steps followed are listed below: | When determining whether the RSEP request could raise significant competition issues, a review is necessary. The stages and steps followed are listed below: | ||
#The General | #The General Counsel reviews the request for determining whether the RSEP request could raise significant competition issues. The following factors are taken into consideration: | ||
#* | #*The pricing influence over the price of registry service; | ||
#* | #*Market issues: identification of the market which could be affected, and the effects of the change; | ||
#* | #*Allocation issues | ||
#* | #*Impact on other markets | ||
# Preliminary determination on competition issues by the General Council | # Preliminary determination on competition issues by the General Council | ||
# If no | # If no competition issues are determined, the competition review is considered complete. | ||
# If there are significant competition issues determined by [[ICANN]] or RSEP request, the appropriate competition authority will be contacted and the jurisdiction applied.<ref>[http://www.icann.org/en/registries/rsep/prelim-competition-issues-en.htm Analysis of the RESP request regarding significant competition issues]</ref> | # If there are significant competition issues determined by [[ICANN]] or RSEP request, the appropriate competition authority will be contacted and the jurisdiction applied.<ref>[http://www.icann.org/en/registries/rsep/prelim-competition-issues-en.htm Analysis of the RESP request regarding significant competition issues]</ref> | ||
==Registry Services== | ==Registry Services== | ||
The registry services which are proposed based on RSEP requests are defined as: | The registry services which are proposed based on RSEP requests are defined as: | ||
* Services | * Services that are critical for the [[RIR]] (Regional Internet Registry) to perform tasks related to registrations of domain names, registrars, and other related issues. | ||
* Other services and products that the [[RIR]] must provide based on the consensus policy adopted. | * Other services and products that the [[RIR]] must provide based on the consensus policy adopted. | ||
* Services which only that specific [[RIR]] is able to provide. <ref>[http://www.icann.org/en/registries/rsep/rsep.html Registry Services ICANN]</ref> | * Services which only that specific [[RIR]] is able to provide. <ref>[http://www.icann.org/en/registries/rsep/rsep.html Registry Services ICANN]</ref> | ||
Line 25: | Line 48: | ||
[[Category: Glossary]] | [[Category: Glossary]] | ||
__NOTOC__ | __NOTOC__ |
Revision as of 18:37, 12 May 2021
The Registry Services Evaluation Policy (RSEP) Process is a set of protocols designed to screen and approve proposals made by gTLD operators to add or modify registry services. To submit a request for the implementation of new Registry Services, all gTLDs must take into account RSEP's provisions. The RSEP is required by ICANN in order to make sure that no significant competition issues are raised.
History[edit | edit source]
RSEP was created through ICANN's consensus for policy development process.[1]
On June 30, 2005, the GNSO released its PDP Final Report on the "Procedure for use by ICANN in considering requests for consent and related contractual amendments to allow changes in the architecture or operation of a gTLD registry."[2]
November 8, 2005, the ICANN Board directed that this procedure for considering requests for new Registry Services be guided by the provisions in the .net Registry Agreement, per the GNSO's recommendation, which became the Registry Services Evaluation Policy process.[3]
Years | Requests | Factors | |
---|---|---|---|
2006 | 4 | First year | |
2006 to 2012 | 8 on average | ||
2013 to 2017 | 54 on average | The increase in the number of gTLDs
Alignment of service offerings across gTLDs supported by common back-end registry service providers Requests for release of reserved names | |
2015 to 2017 | drop from 101 to 42 |
In 2019, RySG and ICANN org updated how to implement the policy without altering it to make it easier to understand and more predictable.
RSEP request assessment[edit | edit source]
When determining whether the RSEP request could raise significant competition issues, a review is necessary. The stages and steps followed are listed below:
- The General Counsel reviews the request for determining whether the RSEP request could raise significant competition issues. The following factors are taken into consideration:
- The pricing influence over the price of registry service;
- Market issues: identification of the market which could be affected, and the effects of the change;
- Allocation issues
- Impact on other markets
- Preliminary determination on competition issues by the General Council
- If no competition issues are determined, the competition review is considered complete.
- If there are significant competition issues determined by ICANN or RSEP request, the appropriate competition authority will be contacted and the jurisdiction applied.[4]
Registry Services[edit | edit source]
The registry services which are proposed based on RSEP requests are defined as:
- Services that are critical for the RIR (Regional Internet Registry) to perform tasks related to registrations of domain names, registrars, and other related issues.
- Other services and products that the RIR must provide based on the consensus policy adopted.
- Services which only that specific RIR is able to provide. [5]
References[edit | edit source]