Skip to main content
Resources

《注册管理机构-注册服务机构协议》(RRA) 修订案

注:所有语种版本中,英文版为官方版本,其他语种版本仅供参考.

按照基础《gTLD 注册管理机构协议》第 2.9(a) 节中所述,注册管理运行机构需要向 ICANN 组织通知对《注册管理机构-注册服务机构协议》(RRA) 进行的任何修订。

ICANN 组织根据《注册管理机构-注册服务机构协议》(RRA) 修订程序设计了一个流程,以便注册管理运行机构向 ICANN 组织通知拟议的 RRA 修订案。下面描述的流程涵盖了有关所需文件以及如何处理通知的指导。

ICANN 组织为注册管理运行机构制定了一个单独的流程,供其提交 RRA 修订案以包含gTLD 注册数据临时规范(示范条款)的已批准语言。包含示范条款的修订案应作为单独的通知提交,并将遵循简化的审核和批准流程。如需了解更多信息,请参阅将《注册管理机构-注册服务机构协议》(RRA) 修订程序与 gTLD 注册数据临时规范结合使用

资源

RRA 修订流程

以下是关于提交 RRA 修订案请求的一般说明。如需了解更多信息,请参阅《注册管理机构-注册服务机构协议》(RRA) 修订程序

ICANN 组织建议您安排一次电话磋商会议,以审核拟议的修订案并解答您在流程方面存在的任何疑问,但并不要求必须这样做。要安排磋商会议,请打开域名服务门户中的"常规问询"案例。

  • 提交 RRA 修订案请求 - 要启动此流程,请通过域名服务门户打开一个《注册管理机构-注册服务机构协议》(RRA) 修订案案例。您需要向 ICANN 组织提交两份文件以供审核:

    • 用红线标注拟议变更的现有 RRA
    • 说明信,说明拟议变更的目的

    提交上述文件后,ICANN 组织将审核您的文件的完整性。

  • 确定重要性(预计持续时间:15 个日历日)- ICANN 组织将参考《注册管理机构协议》第 2.9 节,确定应将请求的变更视为不重要、可能重要,还是重要。如果这些变更被视为重要或可能重要,ICANN 组织将按照如下所述展开全面审核。如果这些变更被视为不重要,您将绕过全面审核流程,同时 ICANN 组织将向您通知最终处理步骤。
  • 全面审核:注册服务机构利益相关方团体和 ICANN 组织审核(预计持续时间:通常不超过 21 天)- 如果拟议的变更被视为重要或可能重要,ICANN 组织会将拟议 RRA 变更的红线标注版和说明信转发给注册服务机构利益相关方团体 (RrSG) 进行审核。与此同时,ICANN 组织将展开其内部审核。在审核期间,如果 RrSG 或 ICANN 组织提出任何问题,ICANN 组织将在适用的情况下安排注册管理运行机构与 RrSG 举行磋商会议,商讨并解决这些问题。
  • 最终裁定 - ICANN 组织将批准或拒绝拟议的变更。如果 ICANN 组织批准拟议的变更,提出变更请求的注册管理运行机构应将修订后的 RRA 转发给注册服务机构。如果 ICANN 组织拒绝拟议的变更,ICANN 组织将通知提出变更请求的注册管理运行机构并告知拒绝理由。
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."