Skip to main content

持续经营方案 (Continued Operations Instrument, COI)




持续经营方案 (COI) 的目的旨在确保资金的可用性,以便在注册管理机构出现问题时,能够继续向新通用顶级域 (gTLD) 的注册人提供服务。按照基本《注册管理机构协议》规范 8 的要求,注册管理运行机构应制定一套《持续经营方案》,以便在规范 8 第 1 节中规定的具体时间段内,为履行规范 10 第 6 节列出的五项注册管理机构关键职能而提供充足的财务资源。

COI 义务发布服务

《注册管理机构协议》要求,自开始履行合同算起的六年时间里,需维护一个充分的 COI 保障体系。由于注册管理运行机构要履行为期六年的义务,因此将不再要求 TLD 维护 COI。

关于那些依照《注册管理机构协议》规范 8 而不再需要的 COI,"COI 义务终止发布服务"允许 ICANN 组织处理这些 COI 的发布。

COI 义务发布服务处理流程

COI Obligation Release Service Process Flow

*整个处理过程最多可能需要 45 天

处理工作将以月度为间隔分批次(根据履行 COI 义务的截止时间)进行,最多可能需要 45 天完成。

利用了 COI 分配计划的注册管理运行机构,将会收到有关可能从其 COI 文件中移除 gTLD 保障的通知。尽管不需要采取任何措施,但是注册管理运行机构可以选择与其开证银行合作,针对移除不再要求保障的 gTLD,共同提交一份修正意见。

一旦为某个方案的分配计划上列出的所有 gTLD 维护 COI 保障的义务获得通过,ICANN 组织将按照上述处理流程,处理 COI 文件的发布。

如果签约方希望寻找一种更快捷的文件发布方式,他们可以借助 COI 修正服务(一种可作为上述服务的替代方案),主动修正 COI 的最终截止日期,以便匹配其 COI 义务终止日期。

COI 修正服务

COI 修正服务为注册管理运行机构提供了一套方法,可用于向 ICANN 组织申请更改其 COI 资金值的权限,以便将该值与为 gTLD 规划的受管理域名注册数量 (DUM) 相对应。

ICANN 组织将遵循《注册管理机构协议》的规定,确保准备充足的 COI 资金。当某个 gTLD 获得授权后,只要 ICANN 发现该域名的 COI 资金不足,则会将 COI 修正服务转介给相应的注册管理运行机构,并要求该机构在 60 天内修正其 COI。

注册管理运行机构应通过域名服务门户中的服务案例提交相关申请。为了符合申请 COI 修正服务的条件,注册管理机构必须在 ICANN 组织中保持良好的信誉,而且其 TLD 必须至少在提出申请之日的前六个月,就已经可用/注册 (GA)。


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"""" is not an IDN."