Difference between revisions of "Registry/zh"

From ICANNWiki
Jump to navigation Jump to search
(Created page with "在2010年11月5日的一次特别会议期间,ICANN董事会对注册局和注册商纵向分离的立场有所改变。董事会取消了注册局...")
(Created page with "=== ICANN对纵向分离政策做出变动的原因=== ICANN董事会列出了支持其纵向分离政策变动的十大理由: <ref>[http://archive.icann.org/en/topics/new-gt...")
Line 23: Line 23:
 
在2010年11月5日的一次特别会议期间,ICANN董事会对注册局和注册商[[Vertical Separation|纵向分离]]的立场有所改变。董事会取消了注册局协议中对交叉所有权的限制,而改为''"针对由于注册局注册商交叉所有权引起的任何不当或滥用行为的要求和限制……''"这些滥用行为不限于误用数据以及违反注册局行为准则。此外,ICANN还申明其将采取其他执行机制,比如自我审计要求、合同终止和惩罚性损害赔偿。而且,ICANN还强调“它将拥有向相关竞争管理机构递交争议的权力。<ref>[http://www.icann.org/en/groups/board/documents/resolutions-05nov10-en.htm Special Meeting of the ICANN Board of Directors, ICANN's Silicon Valley Office, Palo Alto, California, USA]</ref>
 
在2010年11月5日的一次特别会议期间,ICANN董事会对注册局和注册商[[Vertical Separation|纵向分离]]的立场有所改变。董事会取消了注册局协议中对交叉所有权的限制,而改为''"针对由于注册局注册商交叉所有权引起的任何不当或滥用行为的要求和限制……''"这些滥用行为不限于误用数据以及违反注册局行为准则。此外,ICANN还申明其将采取其他执行机制,比如自我审计要求、合同终止和惩罚性损害赔偿。而且,ICANN还强调“它将拥有向相关竞争管理机构递交争议的权力。<ref>[http://www.icann.org/en/groups/board/documents/resolutions-05nov10-en.htm Special Meeting of the ICANN Board of Directors, ICANN's Silicon Valley Office, Palo Alto, California, USA]</ref>
  
===ICANN's Reasons for Policy Change on Vertical Separation===
+
=== ICANN对纵向分离政策做出变动的原因===
The ICANN Board enumerated ten reasons to support its policy change on vertical separation:<ref>
+
ICANN董事会列出了支持其纵向分离政策变动的十大理由:
[http://archive.icann.org/en/topics/new-gtlds/gac-board-registry-registrar-separation-21feb11-en.pdf ICANN Board-GAC Consultation:Registry-Registrar Separation, February 21, 2011]</ref>
+
<ref>[http://archive.icann.org/en/topics/new-gtlds/gac-board-registry-registrar-separation-21feb11-en.pdf ICANN Board-GAC Consultation:Registry-Registrar Separation, February 21, 2011]</ref>
# None of the proposals submitted by the GNSO reflected a consensus opinion; as a result, the Board supported a model based on its own factual investigation, expert analysis, and concerns expressed by stakeholders and community.
+
# GNSO提交的建议都没有反映一个一致性的观点;因此,董事会支持了一个基于其自身事实调查、专家分析和利益相关方及社区顾虑的模式。
# ICANN's position and mission must be focused on creating more competition as opposed to having rules that restrict competition and innovation.
+
# ICANN的立场和使命必须集中于促进更多的竞争,而不是设立限制竞争和创新的规则。
# Rules permitting cross-ownership foster greater diversity in business models and enhance opportunities offered by new TLDs.
+
#允许交叉所有权的规则能够培养更加多元化的商业模式并增加新顶级域带来的机遇。
# Rules prohibiting cross-ownership require more enforcement and can easily be circumvented.
+
#禁止交叉所有权的规定需要更强的执行力并且可以轻易被规避。
# Preventing cross-ownership would create more exposure to ICANN of lawsuits, including anti-trust lawsuits, which are costly to defend even if ICANN believes (as it does) that it has no proper exposure to such litigation.
+
#限制交叉所有权会让ICANN面临更多的法律诉讼,包括反垄断的诉讼,即使ICANN认为(事实亦如此)其不应面对此类诉讼,但是这些诉讼的辩护成本很高,。
# Rules permitting cross-ownership enhance efficiency and almost certainly will result in benefits to consumers in the form of lower prices and enhanced services.
+
#允许交叉所有权的规定可以提高效率并且几乎必将使消费者受益,比如更低的价格和更好的服务。
# The Rules of Conduct, which is to be part of the base agreement for all new gTLDs include adequate protections designed to address behavior the Board wants to discourage, including abuses of data and market power...
+
#行为准则将作为所有新通用顶级域基础协议的一部分,包含了充分的保护性条款,用以解决董事会希望阻止的行为,包括数据和市场权力滥用……
# Case by case re-negotiation of existing contracts to reflect the new cross ownership rules will permit ICANN to address the risk of abuse of market power contractually.
+
#逐一重新商定现有合同以反应交叉所有权新规将允许ICANN以合约形式处理市场权力滥用的风险。
# In the event ICANN has competition concerns, ICANN will have the ability to to refer those concerns to relevant antitrust authorities.
+
#如果ICANN对竞争方面存有顾虑,ICANN将有权将这些顾虑诉诸相关反垄断管理机构。
# ICANN can amend contracts to address harms that may arise as a direct or indirect result of the new cross-ownership rules.
+
# ICANN可以修订合同以解决由于交叉所有权新规直接或间接引起的损害。
  
 
===EC Concerns Over the Full Removal of Vertical Separation===
 
===EC Concerns Over the Full Removal of Vertical Separation===

Revision as of 20:58, 28 August 2015

注册局是包含注册在一个特定顶级域下的所有域名的数据库。注册局运营者,也称为网络信息中心(NIC),指的是负责提供注册局服务的人或实体。这些服务包括管理客户数据库、发表区域文件、运作域名系统(DNS)域名系统安全扩展(DNSSEC)、制定营销方案和政策。注册局可以将这些服务中的全部或部分外包,或不外包这些服务中的任何一种。不同的 顶级域由不同的注册局管理。
查看我们的注册局公司名册。

注册局和注册商

纵向分离

国家科学基金会网络解决方案公司(Network Solutions)(NSI)签署了一份作为注册局运营者和注册商从1993年-1999年管理顶级域.com、.net 和.org的合作协议。该注册局协议在1999年11月被互联网名称与数字地址分配机构(ICANN)更新。新协议中规定,NSI同意创建一个多元化的注册商系统,也称为共享注册系统(SRS),独立注册商拥有使用该系统的权力。独立注册商需要为每个注册或续费的域名向NSI支付6美元的费用。[1]

此外,ICANN还鼓励注册局和注册商业务分离,在协议中规定如果NSI出售其注册商业务,则其与ICANN的注册局协议只能续约四年,以此鼓励竞争。.[2] 2000年,威瑞信收购了NSI,并且与ICANN重新商定了关于顶级域 .com.net.org的注册局协议。ICANN不要求所有权分离,但是却要求执行结构性分离。ICANN为此解释道: "在当今市场环境下,禁止注册局运营者同时成为一个注册商的附加竞争价值是微乎其微的,只要它没有排斥其他注册商的竞争。" [3] [4]


2000年,ICANN引入了新的通用类顶级域名,包括 .biz.info.name .pro。2001年2月26日,ICANN草拟了一份新的注册局协议,规定了注册局和注册商的法定分离关系,详见第3.5节公平对待ICANN委任注册商(Fair Treatment of ICANN-Accredited Registrars),其中规定注册局运营者不得充当注册局顶级域的注册商的角色。[5]

2005年,ICANN根据赞助类顶级域 .jobs.travel注册局协议执行了注册局和注册商的所有权分离。在注册局协议第7.1节的条款b和c中做出了以下规定:[6]

  • (b)注册局运营者不得作为自己的注册商。注册局运营者不得充当自己顶级域注册商的角色。此规定不应妨碍注册局运营者通过向一个由ICANN委任的注册商请求注册其自身顶级域中的域名。
  • (c)注册商所有权取得或控股权益的限制条件。注册局运营者不应直接或间接完全控制或取得任何ICANN委任注册商百分之十五以上的所有者权益。

目前,这些条款包含在所有赞助类和非赞助类顶级域的注册局协议中。

ICANN对新通用顶级域纵向分离的立场转换

一些观念认为,ICANN为了维护其促进竞争的基本原则,纵向分离是其采取的最重要的方法之一。2002年3月12日,ICANN董事会通过了一项决议,表明该组织对执行新通用顶级域注册局和注册商“严格分离”的坚决立场。ICANN董事会还声明禁止共同所有权的存在。然而,ICANN董事会还指出:"如果是来自通用名称支持组织(GNSO)的已经生效的政策,并且在推出新通用顶级域项目之前已经取得董事会批准,那么该政策将被董事会采纳作为新通用顶级域项目的一部分。”[7]

在2010年11月5日的一次特别会议期间,ICANN董事会对注册局和注册商纵向分离的立场有所改变。董事会取消了注册局协议中对交叉所有权的限制,而改为"针对由于注册局注册商交叉所有权引起的任何不当或滥用行为的要求和限制……"这些滥用行为不限于误用数据以及违反注册局行为准则。此外,ICANN还申明其将采取其他执行机制,比如自我审计要求、合同终止和惩罚性损害赔偿。而且,ICANN还强调“它将拥有向相关竞争管理机构递交争议的权力。[8]

ICANN对纵向分离政策做出变动的原因

ICANN董事会列出了支持其纵向分离政策变动的十大理由: [9]

  1. GNSO提交的建议都没有反映一个一致性的观点;因此,董事会支持了一个基于其自身事实调查、专家分析和利益相关方及社区顾虑的模式。
  2. ICANN的立场和使命必须集中于促进更多的竞争,而不是设立限制竞争和创新的规则。
  3. 允许交叉所有权的规则能够培养更加多元化的商业模式并增加新顶级域带来的机遇。
  4. 禁止交叉所有权的规定需要更强的执行力并且可以轻易被规避。
  5. 限制交叉所有权会让ICANN面临更多的法律诉讼,包括反垄断的诉讼,即使ICANN认为(事实亦如此)其不应面对此类诉讼,但是这些诉讼的辩护成本很高,。
  6. 允许交叉所有权的规定可以提高效率并且几乎必将使消费者受益,比如更低的价格和更好的服务。
  7. 行为准则将作为所有新通用顶级域基础协议的一部分,包含了充分的保护性条款,用以解决董事会希望阻止的行为,包括数据和市场权力滥用……
  8. 逐一重新商定现有合同以反应交叉所有权新规将允许ICANN以合约形式处理市场权力滥用的风险。
  9. 如果ICANN对竞争方面存有顾虑,ICANN将有权将这些顾虑诉诸相关反垄断管理机构。
  10. ICANN可以修订合同以解决由于交叉所有权新规直接或间接引起的损害。

EC Concerns Over the Full Removal of Vertical Separation

On June 17, 2011, the Information Society and Media Directorate General of the European Commission (EC) submitted a non-paper regarding ICANN's proposed full removal of the vertical separation to the ICANN Board. Copies were furnished to the U.S. NTIA Assistant Secretary Larry Strickling and to Assistant Attorney General Christine Varney of the Department of Justice Antitrust Division. The EC cited some issues and recommendations, which include:[10]

  • Vertical separation provides a balanced playing field for competition between registrars. The absence of expert advice to remove vertical separation and stakeholders consensus shows that the move may be premature and might result in negative market output for consumers.
  • Vertical Integration might harm competition. The European Commission cited the CRA International Report of 2008, which emphasized the risk of vertical integration wherein registries may discriminate independent registrars by lowering prices and providing better registry services to their affiliate registrars.
  • ICANN does not have sufficient data to support the full removal of vertical separation.
  • A consensus on the issue within the GNSO and internet stakeholders is lacking.
  • The procedural approach of ICANN to refer an application to relevant antitrust authorities for "expert analysis and ante determination" overlooks the fact that competition authorities have limited powers in implementing rules, which is based on a case to case market analysis. ICANN did not clearly identify specific laws that will serve as basis of its jurisdiction to determine if there are concerns regarding competition. Referral to competition authorities depends on ICANN's discretion.

Thus, The EC encouraged ICANN to reconsider decision to implement the full removal of vertical separation of registries and registrars and to follow these suggestions:

  1. Conduct independent economic and legal expert studies regarding the present situation of the domain name market and evaluate the impact of the existing restrictions on vertical integration. The impact of partially or totally removing the restriction on innovation and to consumers.
  2. Provide new market data on the current degree of competition and cross-ownership at the registry and registrar level.
  3. Provide data and documents supporting ICANN's decision to fully remove vertical separation.
  4. Provide comments regarding the procedural concerns raised by EC.

Emergency Back-up Registry Operators (EBEROs)

In connection with the implementation of new gTLDs, ICANN designed a new program known as Emergency Back-up Registry Operators (EBEROs) to ensure the safety and security of the domain name system. EBEROs are to be activated in circumstances wherein a new registry operator needs help to maintain critical functions for a period or time or during transition from one registry operator to another. A Request for Proposal (RFP) was issued by ICANN to solicit applications from entities interested to serve as EBEROs on September 14, 2011.[11]

gTLD Registry Continuity Framework

ICANN partnered with expert gTLD & ccTLD registries as well as members of the technical community in developing a gTLD Registry Continuity Framework, which aims to protect existing registrants and to ensure confidence in the DNS. Core ICANN values served as guidelines in developing the framework, which aims to:[12]

  • Maintain and develop the operational stability, reliability, security, and global interoperability of the Internet.
  • Apply documented policies neutrally, objectively with integrity and fairness in decision making.
  • Be responsive and speedy in taking actions to resolve the needs of the Internet community and obtain informed input from affected entities during the decision making process.

ICANN's Timeline for its Continuity Initiatives is available here


References