Network Working Group A. Newton
Request for Comments: 5144 American Registry for Internet Numbers
Category: Standards Track M. Sanz
DENIC eG
February 2008
Network Working Group A. Newton
Request for Comments: 5144 American Registry for Internet Numbers
Category: Standards Track M. Sanz
DENIC eG
February 2008
A Domain Availability Check (DCHK) Registry Type for the Internet Registry Information Service (IRIS)
Internet注册表信息服务（IRIS）的域可用性检查（DCHK）注册表类型
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Abstract
摘要
This document describes a lightweight domain availability service using the Internet Registry Information Service (IRIS) framework and the data model of the IRIS Domain Registry (DREG) service.
本文档描述了一个轻量级的域可用性服务，它使用Internet注册表信息服务（IRIS）框架和IRIS域注册表（DREG）服务的数据模型。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Document Terminology . . . . . . . . . . . . . . . . . . . . . 3
3. Domain Availability Check Registry . . . . . . . . . . . . . . 3
3.1. Schema Description . . . . . . . . . . . . . . . . . . . . 4
3.1.1. The <domain> Result . . . . . . . . . . . . . . . . . 4
3.1.2. Support for <iris:lookupEntity> . . . . . . . . . . . 7
3.2. DCHK Formal XML Syntax . . . . . . . . . . . . . . . . . . 7
3.3. Blocks Extensible Exchange Protocol (BEEP) Transport
Compliance . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3.1. Message Pattern . . . . . . . . . . . . . . . . . . . 12
3.3.2. Server Authentication . . . . . . . . . . . . . . . . 12
3.4. URI Resolution . . . . . . . . . . . . . . . . . . . . . . 13
3.4.1. Application Service Label . . . . . . . . . . . . . . 13
3.4.2. Bottom-Up Resolution . . . . . . . . . . . . . . . . . 13
3.4.3. Top-Down Resolution . . . . . . . . . . . . . . . . . 13
4. Internationalization Considerations . . . . . . . . . . . . . 13
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
5.1. XML Namespace Registration . . . . . . . . . . . . . . . . 14
5.2. XML Schema Registration . . . . . . . . . . . . . . . . . 14
5.3. S-NAPTR Registration . . . . . . . . . . . . . . . . . . . 14
5.4. BEEP Registration . . . . . . . . . . . . . . . . . . . . 15
6. Security Considerations . . . . . . . . . . . . . . . . . . . 15
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. Normative References . . . . . . . . . . . . . . . . . . . 15
7.2. Informative References . . . . . . . . . . . . . . . . . . 16
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Document Terminology . . . . . . . . . . . . . . . . . . . . . 3
3. Domain Availability Check Registry . . . . . . . . . . . . . . 3
3.1. Schema Description . . . . . . . . . . . . . . . . . . . . 4
3.1.1. The <domain> Result . . . . . . . . . . . . . . . . . 4
3.1.2. Support for <iris:lookupEntity> . . . . . . . . . . . 7
3.2. DCHK Formal XML Syntax . . . . . . . . . . . . . . . . . . 7
3.3. Blocks Extensible Exchange Protocol (BEEP) Transport
Compliance . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3.1. Message Pattern . . . . . . . . . . . . . . . . . . . 12
3.3.2. Server Authentication . . . . . . . . . . . . . . . . 12
3.4. URI Resolution . . . . . . . . . . . . . . . . . . . . . . 13
3.4.1. Application Service Label . . . . . . . . . . . . . . 13
3.4.2. Bottom-Up Resolution . . . . . . . . . . . . . . . . . 13
3.4.3. Top-Down Resolution . . . . . . . . . . . . . . . . . 13
4. Internationalization Considerations . . . . . . . . . . . . . 13
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
5.1. XML Namespace Registration . . . . . . . . . . . . . . . . 14
5.2. XML Schema Registration . . . . . . . . . . . . . . . . . 14
5.3. S-NAPTR Registration . . . . . . . . . . . . . . . . . . . 14
5.4. BEEP Registration . . . . . . . . . . . . . . . . . . . . 15
6. Security Considerations . . . . . . . . . . . . . . . . . . . 15
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. Normative References . . . . . . . . . . . . . . . . . . . 15
7.2. Informative References . . . . . . . . . . . . . . . . . . 16
This document describes a lightweight service for checking the availability of domain names. This service is based on the IRIS framework and uses the data model defined by RFC 3982 [7]. By doing this, the domain availability service has the advantages provided by IRIS and DREG, such as well-known methods for server navigation, structured queries and results, and layered extensibility.
本文档描述了一种用于检查域名可用性的轻量级服务。该服务基于IRIS框架，并使用RFC 3982[7]定义的数据模型。通过这样做，域可用性服务具有IRIS和DREG提供的优势，例如用于服务器导航、结构化查询和结果以及分层可扩展性的众所周知的方法。
The use of IRIS for this service also allows seamless integration between the domain availability service and the service provided by DREG. This allows a user to find the availability status of a domain and reference the full registration information in DREG.
在该服务中使用IRIS还允许在域可用性服务和DREG提供的服务之间无缝集成。这允许用户查找域的可用性状态并引用DREG中的完整注册信息。
The data model in this service (called a registry schema in IRIS terms) is a strict subset of the DREG data model. This enables implementors to directly reuse DREG code paths and allows operators to deploy the service in either the same server processes as a DREG service (same host and port) or in a different server process (different port) or machine (different host).
此服务中的数据模型（在IRIS术语中称为注册表模式）是DREG数据模型的严格子集。这使实现人员能够直接重用DREG代码路径，并允许操作员在与DREG服务相同的服务器进程（相同的主机和端口）或不同的服务器进程（不同的端口）或机器（不同的主机）中部署服务。
As an example, an operator may wish to deploy both types of service on the same set of machines. As time goes on, the operator may then decide to segregate the services, placing the domain availability service on one set of machines and the DREG service on a separate set of machines with a stricter set of controls. Either deployment scenario is transparent to the end user and always appears to be seamlessly complementary.
例如，操作员可能希望在同一组机器上部署这两种类型的服务。随着时间的推移，运营商可能会决定隔离服务，将域可用性服务放在一组机器上，将DREG服务放在一组具有更严格控制的单独机器上。这两种部署场景对最终用户都是透明的，并且始终是无缝互补的。
When coupled with [9], this domain availability service is lightweight and extremely efficient for high-volume, public-facing service.
当与[9]结合使用时，该域可用性服务对于大容量、面向公众的服务来说是轻量级的，并且非常高效。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [2].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[2]中所述进行解释。
The data model used for the domain availability check (DCHK) service is a strict subset of the DREG data model. This section describes the DCHK registry type.
用于域可用性检查（DCHK）服务的数据模型是DREG数据模型的严格子集。本节介绍DCHK注册表类型。
References to XML elements with no namespace qualifier are from the schema defined in Section 3.2. References to elements and attributes with the "iris" XML namespace qualifier are from the schema defined in IRIS [6].
对没有名称空间限定符的XML元素的引用来自第3.2节中定义的模式。使用“iris”XML命名空间限定符对元素和属性的引用来自iris[6]中定义的模式。
The schema present in this document is tied to the protocol version associated with the XML namespace URI defined in Section 5.2. Extensions to the present DCHK schema are allowed, though not recommended, but would require a new version. Please refer to RFC 3981 [6] for more details about versioning the IRIS protocol.
本文档中的模式与第5.2节中定义的XML名称空间URI关联的协议版本相关联。允许对当前DCHK架构进行扩展，但不建议进行扩展，但需要新版本。有关IRIS协议版本控制的更多详细信息，请参阅RFC 3981[6]。
The descriptions contained within this section refer to XML elements and attributes and their relation to the exchange of data within the protocol. These descriptions also contain specifications outside the scope of the formal XML syntax. Therefore, this section will use terms defined by RFC 2119 [2] to describe the specification outside the scope of the formal XML syntax. While reading this section, please reference Section 3.2 for needed details on the formal XML syntax.
本节中包含的描述涉及XML元素和属性及其与协议内数据交换的关系。这些描述还包含正式XML语法范围之外的规范。因此，本节将使用RFC 2119[2]定义的术语来描述正式XML语法范围之外的规范。阅读本节时，请参考第3.2节，以了解有关正式XML语法的必要详细信息。
An example of a <domain> result:
<domain>结果示例：
<domain
authority="iana.org" registryType="dchk1"
entityClass="domain-name" entityName="example.com">
<domainName>example.com</domainName>
<status><active/></status>
</domain>
<domain
authority="iana.org" registryType="dchk1"
entityClass="domain-name" entityName="example.com">
<domainName>example.com</domainName>
<status><active/></status>
</domain>
<domain> Example
<domain>示例
The <domain> result represents an instance of a domain assignment. The children of the <domain> element are as follows:
<domain>结果表示域分配的实例。<domain>元素的子元素如下所示：
o <domainName> - the full name of the domain as it is in DNS. The contents of this element MUST be a domain name as specified by RFC 1035 [1].
o <domainName>-域名在DNS中的全名。此元素的内容必须是RFC 1035[1]指定的域名。
o <idn> - the name of the domain in nameprep form, if applicable. See RFC 3491 [3].
o <idn>-nameprep表单中的域名（如果适用）。参见RFC 3491[3]。
o <status> - this element may contain child elements representing domain status information. It defines the following status types:
o <status>-此元素可能包含表示域状态信息的子元素。它定义了以下状态类型：
* <active> - available via DNS (either via delegation or direct publication).
* <active>-可通过DNS访问（通过授权或直接发布）。
* <inactive> - unavailable via DNS.
* <inactive>-无法通过DNS访问。
* <dispute> - registrant assignment is in dispute.
* <争议>-注册人转让存在争议。
* <addPeriod> - the domain is in the grace period after creation or activation (see RFC 3915 [5]).
* <addPeriod>-域在创建或激活后处于宽限期（请参阅RFC 3915[5]）。
* <renewPeriod> - the domain is in the grace period after renewal (see RFC 3915 [5]).
* <RenewarPeriod>-域在续订后处于宽限期（请参阅RFC 3915[5]）。
* <autoRenewPeriod> - the domain is in the grace period after automatic renewal (see RFC 3915 [5]).
* <autoRenewPeriod>-域在自动续订后处于宽限期（请参阅RFC 3915[5]）。
* <transferPeriod> - the domain is in the grace period after transfer (see RFC 3915 [5]).
* <transferPeriod>-域在传输后处于宽限期（请参阅RFC 3915[5]）。
* <redemptionPeriod> - the domain is in the grace period after deletion (see RFC 3915 [5]).
* <redemptionPeriod>-域在删除后处于宽限期（请参见RFC 3915[5]）。
* <policyCompliant> - the domain is considered compliant according to a given policy specified by the substatus identifier.
* <policyCompliant>-根据子状态标识符指定的给定策略，域被视为符合。
* <policyNoncompliant> - the domain is not considered compliant according to a given policy specified by the substatus identifier.
* <policyNoncompliant>-根据子状态标识符指定的给定策略，域不被视为符合。
* <reserved> - the domain is reserved and is not available for registration under normal registration procedures.
* <reserved>-该域为保留域，在正常注册过程中不可注册。
* <create> - specifies the creation of the domain in the registration system. This status is usually further refined by the disposition attribute.
* <create>-指定在注册系统中创建域。此状态通常通过“处置”属性进一步细化。
* <delete> - specifies the deletion of the domain in the registration system. This status is usually further refined by the disposition attribute.
* <delete>-指定在注册系统中删除域。此状态通常通过“处置”属性进一步细化。
* <renew> - specifies the renewal of domain registration. This status is usually further refined by the disposition attribute.
* <续订>-指定域注册的续订。此状态通常通过“处置”属性进一步细化。
* <restore> - specifies the restoration to the previous state of the domain before it was deleted. This status is usually further refined by the disposition attribute.
* <restore>-指定将域恢复到删除前的状态。此状态通常通过“处置”属性进一步细化。
* <transfer> - specifies the transfer of the domain from one responsible or owning entity in the registration system to another. This status is usually further refined by the disposition attribute.
* <transfer>-指定域从注册系统中的一个负责或拥有实体转移到另一个负责或拥有实体。此状态通常通过“处置”属性进一步细化。
* <update> - specifies a general modification of the domain information. This status is usually be further refined by the disposition attribute.
* <update>-指定域信息的常规修改。此状态通常由disposition属性进一步细化。
* <other> - specifies a registration system specific status of the domain.
* <other>-指定域的注册系统特定状态。
o <registrationReference> - an element containing an entity reference, the referent of which MUST be either a <domain> (Section 3.1.1) or a <domain> as defined by RFC 3982 [7]. The intent of this element is to point to the downstream registration reference. Therefore, if this is a result given back by a domain registry, it should point to the domain in the domain registrar or registrant service.
o <registrationReference>-包含实体引用的元素，其引用对象必须是RFC 3982[7]定义的<domain>（第3.1.1节）或<domain>。此元素的目的是指向下游注册引用。因此，如果这是域注册表返回的结果，它应该指向域注册器或注册者服务中的域。
o <createdDateTime> - an element containing the date and time of the creation of this domain.
o <createdDateTime>-包含创建此域的日期和时间的元素。
o <initialDelegationDateTime> - an element containing the date and time of the initial delegation of this domain.
o <initialDelegationDateTime>-包含此域初始委派的日期和时间的元素。
o <expirationDateTime> - an element containing the date and time of the expiration of this domain.
o <expirationDateTime>-包含此域过期日期和时间的元素。
o <lastDatabaseUpdateDateTime> - an element containing the date and time of the last actualization of the database that is the source for this result.
o <lastDatabaseUpdateDateTime>-包含作为此结果来源的数据库上次实现的日期和时间的元素。
o <iris:seeAlso> - an element containing an entity reference specifying a referent that is indirectly associated with this domain.
o <iris:see也>-包含实体引用的元素，指定与此域间接关联的引用。
Each element of type 'domainStatusType' has the following composition:
“domainStatusType”类型的每个元素都有以下组成：
o <appliedDate> - an optional child element containing the date applicable to creation of the status.
o <appliedDate>-一个可选的子元素，包含适用于创建状态的日期。
o <ticket> - an optional child element containing a service ticket identifier relevant to the status.
o <ticket>-包含与状态相关的服务票证标识符的可选子元素。
o <description> - zero or more child elements with text to describe the status in natural language. Each of these elements MUST have a 'language' attribute describing the language of the description element.
o <description>-零个或多个子元素，用文本描述自然语言中的状态。这些元素中的每一个都必须有一个“language”属性来描述描述元素的语言。
o <subStatus> - a child element indicating further status information. Values for this element are not defined by this specification. This child element has a required 'authority' attribute to indicate the origin of the specification of the value of this element.
o <subStatus>-表示进一步状态信息的子元素。本规范未定义此元素的值。此子元素具有必需的“authority”属性，以指示此元素值的规范的来源。
o 'actor' - an optional attribute indicating the acting entity for which this status is applied. The values may be "registry", "registrar", or "registrationServiceProvider".
o “actor”-一个可选属性，指示应用此状态的代理实体。这些值可以是“registry”、“Registrator”或“registrationServiceProvider”。
o 'disposition' - an optional attribute indicating the nature of this status. The values may be "pending" or "prohibited".
o “disposition”-表示此状态性质的可选属性。这些值可能是“待定”或“禁止”。
o 'scope' - an optional attribute indicating the context or origin of the status value.
o “scope”-一个可选属性，指示状态值的上下文或来源。
The following types of entity classes are recognized by the <lookupEntity> query of IRIS for this registry:
此注册表的IRIS的<lookupEntity>查询可识别以下类型的实体类：
o domain-name - the fully qualified name of a domain. This is a domain name as specified by RFC 1035 [1]. Yields a <domain> (Section 3.1.1) in the response.
o 域名-域的完全限定名。这是RFC 1035[1]指定的域名。在响应中产生<域>（第3.1.1节）。
o idn - the fully qualified name of a domain in nameprep form (see RFC 3491 [3]). Yields a <domain> (Section 3.1.1) in the response.
o idn—nameprep表单中域的完全限定名（请参见RFC 3491[3]）。在响应中产生<域>（第3.1.1节）。
This registry schema is specified in the XML Schema notation (see [10] and [11]). The formal syntax presented here is a complete schema representation of an XML instance when combined with the formal schema syntax of IRIS.
该注册表模式在XML模式表示法中指定（请参见[10]和[11]）。这里给出的形式语法与IRIS的形式模式语法相结合时，是XML实例的完整模式表示。
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:dchk="urn:ietf:params:xml:ns:dchk1"
xmlns:iris="urn:ietf:params:xml:ns:iris1"
targetNamespace="urn:ietf:params:xml:ns:dchk1"
elementFormDefault="qualified" >
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:dchk="urn:ietf:params:xml:ns:dchk1"
xmlns:iris="urn:ietf:params:xml:ns:iris1"
targetNamespace="urn:ietf:params:xml:ns:dchk1"
elementFormDefault="qualified" >
<import namespace="urn:ietf:params:xml:ns:iris1" />
<import namespace="urn:ietf:params:xml:ns:iris1" />
<annotation>
<documentation>
Domain availability check schema
derived from IRIS schema
</documentation>
</annotation>
<annotation>
<documentation>
Domain availability check schema
derived from IRIS schema
</documentation>
</annotation>
<!-- ========================================= -->
<!-- -->
<!-- Result Types -->
<!-- -->
<!-- ========================================= -->
<!-- ========================================= -->
<!-- -->
<!-- Result Types -->
<!-- -->
<!-- ========================================= -->
<!-- -->
<!-- Domain -->
<!-- -->
<!-- -->
<!-- Domain -->
<!-- -->
<complexType
name="domainType">
<complexContent>
<extension
base="iris:resultType">
<sequence>
<element
name="domainName"
type="token" />
<element
name="idn"
type="token"
minOccurs="0"
maxOccurs="1" />
<element name="status"
minOccurs="0"
maxOccurs="1">
<complexType>
<choice minOccurs="0" maxOccurs="unbounded">
<element
name="active"
type="dchk:domainStatusType" />
<element
name="inactive"
type="dchk:domainStatusType" />
<element
name="dispute"
type="dchk:domainStatusType" />
<element
<complexType
name="domainType">
<complexContent>
<extension
base="iris:resultType">
<sequence>
<element
name="domainName"
type="token" />
<element
name="idn"
type="token"
minOccurs="0"
maxOccurs="1" />
<element name="status"
minOccurs="0"
maxOccurs="1">
<complexType>
<choice minOccurs="0" maxOccurs="unbounded">
<element
name="active"
type="dchk:domainStatusType" />
<element
name="inactive"
type="dchk:domainStatusType" />
<element
name="dispute"
type="dchk:domainStatusType" />
<element
name="renew"
type="dchk:domainStatusType" />
<element
name="addPeriod"
type="dchk:domainStatusType" />
<element
name="renewPeriod"
type="dchk:domainStatusType" />
<element
name="autoRenewPeriod"
type="dchk:domainStatusType" />
<element
name="transferPeriod"
type="dchk:domainStatusType" />
<element
name="redemptionPeriod"
type="dchk:domainStatusType" />
<element
name="restore"
type="dchk:domainStatusType" />
<element
name="policyCompliant"
type="dchk:domainStatusType" />
<element
name="policyNoncompliant"
type="dchk:domainStatusType" />
<element
name="reserved"
type="dchk:domainStatusType" />
<element
name="create"
type="dchk:domainStatusType" />
<element
name="delete"
type="dchk:domainStatusType" />
<element
name="transfer"
type="dchk:domainStatusType" />
<element
name="update"
type="dchk:domainStatusType" />
<element
name="other"
type="dchk:domainStatusType" />
</choice>
</complexType>
</element>
<element
name="renew"
type="dchk:domainStatusType" />
<element
name="addPeriod"
type="dchk:domainStatusType" />
<element
name="renewPeriod"
type="dchk:domainStatusType" />
<element
name="autoRenewPeriod"
type="dchk:domainStatusType" />
<element
name="transferPeriod"
type="dchk:domainStatusType" />
<element
name="redemptionPeriod"
type="dchk:domainStatusType" />
<element
name="restore"
type="dchk:domainStatusType" />
<element
name="policyCompliant"
type="dchk:domainStatusType" />
<element
name="policyNoncompliant"
type="dchk:domainStatusType" />
<element
name="reserved"
type="dchk:domainStatusType" />
<element
name="create"
type="dchk:domainStatusType" />
<element
name="delete"
type="dchk:domainStatusType" />
<element
name="transfer"
type="dchk:domainStatusType" />
<element
name="update"
type="dchk:domainStatusType" />
<element
name="other"
type="dchk:domainStatusType" />
</choice>
</complexType>
</element>
<element
name="registrationReference"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="createdDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="initialDelegationDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="expirationDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="lastDatabaseUpdateDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
ref="iris:seeAlso"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
name="registrationReference"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="createdDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="initialDelegationDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="expirationDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="lastDatabaseUpdateDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
ref="iris:seeAlso"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="domain"
type="dchk:domainType"
substitutionGroup="iris:result" />
<element
name="domain"
type="dchk:domainType"
substitutionGroup="iris:result" />
<complexType
name="domainStatusType">
<sequence>
<element
name="appliedDate"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="ticket"
<complexType
name="domainStatusType">
<sequence>
<element
name="appliedDate"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="ticket"
type="token"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="description"
minOccurs="0"
maxOccurs="unbounded">
<complexType>
<simpleContent>
<extension
base="string">
<attribute
name="language"
type="language"
use="required" />
</extension>
</simpleContent>
</complexType>
</element>
<element
name="subStatus"
minOccurs="0"
maxOccurs="1">
<complexType>
<simpleContent>
<extension
base="token">
<attribute
type="token"
use="required"
name="authority"/>
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
<attribute
name="actor">
<simpleType>
<restriction
base="string">
<enumeration
value="registry"/>
<enumeration
value="registrar"/>
<enumeration
value="registrationServiceProvider"/>
</restriction>
type="token"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="description"
minOccurs="0"
maxOccurs="unbounded">
<complexType>
<simpleContent>
<extension
base="string">
<attribute
name="language"
type="language"
use="required" />
</extension>
</simpleContent>
</complexType>
</element>
<element
name="subStatus"
minOccurs="0"
maxOccurs="1">
<complexType>
<simpleContent>
<extension
base="token">
<attribute
type="token"
use="required"
name="authority"/>
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
<attribute
name="actor">
<simpleType>
<restriction
base="string">
<enumeration
value="registry"/>
<enumeration
value="registrar"/>
<enumeration
value="registrationServiceProvider"/>
</restriction>
</simpleType>
</attribute>
<attribute
name="disposition">
<simpleType>
<restriction
base="string">
<enumeration
value="prohibited"/>
<enumeration
value="pending"/>
</restriction>
</simpleType>
</attribute>
<attribute
name="scope"
type="token" />
</complexType>
</schema>
</simpleType>
</attribute>
<attribute
name="disposition">
<simpleType>
<restriction
base="string">
<enumeration
value="prohibited"/>
<enumeration
value="pending"/>
</restriction>
</simpleType>
</attribute>
<attribute
name="scope"
type="token" />
</complexType>
</schema>
Figure 1: dchk.xsd
图1:dchk.xsd
All DCHK clients and servers MUST implement the Lightweight UDP Transport Protocol (IRIS-LWZ) [9]. The use of other transports like the XML Pipelining with Chunks (IRIS-XPC) transport [12] or the BEEP transport [8] is optional and completely at the discretion of the server operator. The XPC transport is in any case preferable to the BEEP transport.
所有DCHK客户端和服务器必须实现轻量级UDP传输协议（IRIS-LWZ）[9]。其他传输的使用，如带块的XML管道传输（IRIS-XPC）传输[12]或BEEP传输[8]是可选的，完全由服务器操作员决定。XPC传输在任何情况下都优于BEEP传输。
IRIS allows several extensions of the core capabilities. This section outlines those extensions allowable by IRIS-BEEP [8].
IRIS允许对核心功能进行若干扩展。本节概述了IRIS-BEEP[8]允许的扩展。
This registry type uses the default message pattern as described in IRIS-BEEP [8].
此注册表类型使用IRIS-BEEP[8]中所述的默认消息模式。
This registry type uses the default server authentication method as described in IRIS-BEEP [8].
此注册表类型使用IRIS-BEEP[8]中所述的默认服务器身份验证方法。
The application service label associated with this registry type MUST be "DCHK1". This is the abbreviated form of the URN for this registry type, urn:ietf:params:xml:ns:dchk1.
与此注册表类型关联的应用程序服务标签必须为“DCHK1”。这是此注册表类型的URN的缩写形式，URN:ietf:params:xml:ns:dchk1。
The bottom-up alternative resolution method MUST be identified as 'bottom' in IRIS URI's. Its process is identical to the 'bottom' process described by RFC 3982 [7].
自下而上的备选解析方法必须在IRIS URI中标识为“bottom”。其过程与RFC 3982[7]中描述的“底部”过程相同。
The top-down alternative resolution method MUST be identified as 'top' in IRIS URI's. Its process is identical to the 'top' process described by RFC 3982 [7].
自上而下的备选解析方法必须在IRIS URI中标识为“top”。其过程与RFC 3982[7]中描述的“顶部”过程相同。
Implementors should be aware of considerations for internationalization in IRIS [6].
实现者应该了解IRIS中国际化的注意事项[6]。
Clients needing to localize the data tags in this protocol should take note that localization is only needed on the names of XML elements and attributes, with the exception of elements containing date and time information. The schema for this registry has been designed so that clients need not interpret the content of elements or attributes for localization, other than those elements containing date and time information.
需要本地化此协议中的数据标记的客户机应该注意，本地化只需要对XML元素和属性的名称进行，包含日期和时间信息的元素除外。此注册表的模式设计为，除了包含日期和时间信息的元素外，客户端无需解释本地化元素或属性的内容。
Clients should also make use of the <language> elements provided in many of the results. Results containing internationalized data can be accompanied by these elements in order to aid better localization of the data by the user.
客户还应该使用许多结果中提供的<language>元素。包含国际化数据的结果可以附带这些元素，以帮助用户更好地定位数据。
All date and time elements make use of the XML Schema [10] data type "dateTime". If their contents are Coordinated Universal Time (UTC) timestamps, they MUST be specified by using the capitalized 'Z' indicator (instead of 'z').
所有日期和时间元素都使用XML模式[10]数据类型“dateTime”。如果它们的内容是协调世界时（UTC）时间戳，则必须使用大写的“Z”指示器（而不是“Z”）来指定它们。
This document makes use of the XML registry specified in RFC 3688 [4]. Accordingly, IANA has made the following registration:
本文档使用RFC 3688[4]中指定的XML注册表。因此，IANA进行了以下注册：
o XML Namespace URN/URI:
o XML名称空间URN/URI：
* urn:ietf:params:xml:ns:dchk1
* urn:ietf:params:xml:ns:dchk1
o Contact:
o 联系人：
* Andrew Newton <andy@hxr.us>
* 安德鲁·牛顿<andy@hxr.us>
* Marcos Sanz <sanz@denic.de>
* 马科斯·桑兹<sanz@denic.de>
o XML:
o XML:
* None.
* 没有一个
This document makes use of the XML registry specified in RFC 3688 [4]. Accordingly, IANA has made the following registration:
本文档使用RFC 3688[4]中指定的XML注册表。因此，IANA进行了以下注册：
o XML Schema URN/URI:
o XML架构URN/URI：
* urn:ietf:params:xml:schema:dchk1
* urn:ietf:params:xml:schema:dchk1
o Contact:
o 联系人：
* Andrew Newton <andy@hxr.us>
* 安德鲁·牛顿<andy@hxr.us>
* Marcos Sanz <sanz@denic.de>
* 马科斯·桑兹<sanz@denic.de>
o XML:
o XML:
* The XML Schema specified in Section 3.2
* 第3.2节中指定的XML模式
The following Sraightforwarad-NAPTR (S-NAPTR) application service label has been registered with IANA according to the IANA considerations defined in IRIS [6]:
根据IRIS[6]中定义的IANA注意事项，以下Sraightforwarad NAPTR（S-NAPTR）应用程序服务标签已向IANA注册：
DCHK1
DCHK1
The following BEEP Profile URI has been registered with IANA, in addition to the registration provided in IRIS-BEEP [8].
除了IRIS-BEEP[8]中提供的注册外，以下BEEP配置文件URI已向IANA注册。
http://iana.org/beep/iris1/dchk1
http://iana.org/beep/iris1/dchk1
Being a proper subset of RFC 3982 [7], the registry described in this document introduces no security considerations beyond those documented in RFC 3981 [6].
作为RFC 3982[7]的一个适当子集，本文档中描述的注册中心除了RFC 3981[6]中记录的安全注意事项外，没有引入任何其他安全注意事项。
[1] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[1] Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 10351987年11月。
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[2] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[3] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)", RFC 3491, March 2003.
[3] Hoffman，P.和M.Blanchet，“Nameprep：国际化域名（IDN）的Stringprep配置文件”，RFC 34912003年3月。
[4] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[4] Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[5] Hollenbeck, S., "Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)", RFC 3915, September 2004.
[5] Hollenbeck，S.，“可扩展资源调配协议（EPP）的域注册表宽限期映射”，RFC 3915，2004年9月。
[6] Newton, A. and M. Sanz, "IRIS: The Internet Registry Information Service (IRIS) Core Protocol", RFC 3981, January 2005.
[6] Newton，A.和M.Sanz，“IRIS：互联网注册信息服务（IRIS）核心协议”，RFC 3981，2005年1月。
[7] Newton, A. and M. Sanz, "IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)", RFC 3982, January 2005.
[7] Newton，A.和M.Sanz，“IRIS：互联网注册信息服务（IRIS）的域注册（dreg）类型”，RFC 3982，2005年1月。
[8] Newton, A. and M. Sanz, "Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)", RFC 3983, January 2005.
[8] Newton，A.和M.Sanz，“通过块可扩展交换协议（BEEP）使用互联网注册信息服务（IRIS）”，RFC 3983，2005年1月。
[9] Newton, A., "A Lightweight UDP Transfer Protocol for the Internet Registry Information Service", RFC 4993, August 2007.
[9] Newton，A.，“互联网注册信息服务的轻量级UDP传输协议”，RFC 4993，2007年8月。
[10] World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C XML Schema, October 2004, <http://www.w3.org/TR/xmlschema-2/>.
[10] 万维网联盟，“XML模式第2部分：数据类型”，W3C XML模式，2004年10月<http://www.w3.org/TR/xmlschema-2/>.
[11] World Wide Web Consortium, "XML Schema Part 1: Structures", W3C XML Schema, October 2004, <http://www.w3.org/TR/xmlschema-1/>.
[11] 万维网联盟，“XML模式第1部分：结构”，W3C XML模式，2004年10月<http://www.w3.org/TR/xmlschema-1/>.
[12] Newton, A., "XML Pipelining with Chunks for the Internet Registry Information Service", RFC 4992, August 2007.
[12] Newton，A.，“Internet注册表信息服务的XML块流水线”，RFC 4992，2007年8月。
Authors' Addresses
作者地址
Andrew L. Newton American Registry for Internet Numbers 3635 Concorde Parkway, Suite 200 Chantilly, VA 20151 USA
Andrew L.Newton美国注册处，互联网编号3635协和式公园路，美国弗吉尼亚州尚蒂利200号套房，邮编20151
Phone: +1 703 227 9884
EMail: andy@arin.net
URI: http://www.arin.net/
Phone: +1 703 227 9884
EMail: andy@arin.net
URI: http://www.arin.net/
Marcos Sanz DENIC eG Kaiserstrasse 75-77 D-60329 Frankfurt Germany
Marcos Sanz DENIC德国法兰克福凯撒大街75-77 D-60329
EMail: sanz@denic.de
URI: http://www.denic.de/
EMail: sanz@denic.de
URI: http://www.denic.de/
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2008).
版权所有（C）IETF信托基金（2008年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.