Network Working Group A. Newton
Request for Comments: 3982 VeriSign, Inc.
Category: Standards Track M. Sanz
DENIC eG
January 2005
Network Working Group A. Newton
Request for Comments: 3982 VeriSign, Inc.
Category: Standards Track M. Sanz
DENIC eG
January 2005
IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)
IRIS：Internet注册表信息服务（IRIS）的域注册表（dreg）类型
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）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This document describes an Internet Registry Information Service (IRIS) registry schema for registered DNS information. The schema extends the necessary query and result operations of IRIS to provide the functional information service needs for syntaxes and results used by domain registries and registrars.
本文档描述用于注册DNS信息的Internet注册表信息服务（IRIS）注册表模式。该模式扩展了IRIS的必要查询和结果操作，为域注册中心和注册中心使用的语法和结果提供功能信息服务需求。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Document Terminology . . . . . . . . . . . . . . . . . . . . . 3
3. Schema Description . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Query Derivatives . . . . . . . . . . . . . . . . . . . 3
3.1.1. <findRegistrarsByName> Query . . . . . . . . . . 3
3.1.2. <findDomainsByContact> Query . . . . . . . . . . 4
3.1.3. <findDomainsByName> Query . . . . . . . . . . . 4
3.1.4. <findDomainsByIDN> Query . . . . . . . . . . . . 4
3.1.5. <findContacts> Query . . . . . . . . . . . . . . 5
3.1.6. <findDomainsByHost> Query . . . . . . . . . . . 5
3.1.7. Contact Search Group . . . . . . . . . . . . . . 5
3.2. Result Derivatives . . . . . . . . . . . . . . . . . . . 6
3.2.1. Privacy Labels . . . . . . . . . . . . . . . . . 6
3.2.2. <domain> Result . . . . . . . . . . . . . . . . 7
3.2.3. <host> Result . . . . . . . . . . . . . . . . . 10
3.2.4. <contact> Result . . . . . . . . . . . . . . . . 11
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Document Terminology . . . . . . . . . . . . . . . . . . . . . 3
3. Schema Description . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Query Derivatives . . . . . . . . . . . . . . . . . . . 3
3.1.1. <findRegistrarsByName> Query . . . . . . . . . . 3
3.1.2. <findDomainsByContact> Query . . . . . . . . . . 4
3.1.3. <findDomainsByName> Query . . . . . . . . . . . 4
3.1.4. <findDomainsByIDN> Query . . . . . . . . . . . . 4
3.1.5. <findContacts> Query . . . . . . . . . . . . . . 5
3.1.6. <findDomainsByHost> Query . . . . . . . . . . . 5
3.1.7. Contact Search Group . . . . . . . . . . . . . . 5
3.2. Result Derivatives . . . . . . . . . . . . . . . . . . . 6
3.2.1. Privacy Labels . . . . . . . . . . . . . . . . . 6
3.2.2. <domain> Result . . . . . . . . . . . . . . . . 7
3.2.3. <host> Result . . . . . . . . . . . . . . . . . 10
3.2.4. <contact> Result . . . . . . . . . . . . . . . . 11
3.2.5. <registrationAuthority> . . . . . . . . . . . . 13
3.3. Generic Code Derivatives . . . . . . . . . . . . . . . . 13
3.3.1. <searchTooWide> . . . . . . . . . . . . . . . . 13
3.3.2. <languageNotSupported> . . . . . . . . . . . . . 14
3.4. Support for <iris:lookupEntity> . . . . . . . . . . . . 14
4. Formal XML Syntax . . . . . . . . . . . . . . . . . . . . . . 15
5. BEEP Transport Compliance . . . . . . . . . . . . . . . . . . 36
5.1. Message Pattern . . . . . . . . . . . . . . . . . . . . 36
5.2. Server Authentication . . . . . . . . . . . . . . . . . 36
6. URI Resolution . . . . . . . . . . . . . . . . . . . . . . . . 36
6.1. Application Service Label . . . . . . . . . . . . . . . 36
6.2. Bottom-Up Resolution . . . . . . . . . . . . . . . . . . 37
6.3. Top-Down Resolution . . . . . . . . . . . . . . . . . . 37
7. Internationalization Considerations . . . . . . . . . . . . . 38
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
8.1. XML Namespace URN Registration . . . . . . . . . . . . . 38
8.2. S-NAPTR Registration . . . . . . . . . . . . . . . . . . 39
8.3. BEEP Registration . . . . . . . . . . . . . . . . . . . 39
9. Security Considerations . . . . . . . . . . . . . . . . . . . 39
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.1. Normative References . . . . . . . . . . . . . . . . . . 39
10.2. Informative References . . . . . . . . . . . . . . . . . 40
A. Examples of Requests and Responses . . . . . . . . . . . . . . 41
A.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . 41
A.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . 42
A.3. Example 3 . . . . . . . . . . . . . . . . . . . . . . . 43
B. An Example of Database Serialization . . . . . . . . . . . . . 47
C. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 49
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 50
3.2.5. <registrationAuthority> . . . . . . . . . . . . 13
3.3. Generic Code Derivatives . . . . . . . . . . . . . . . . 13
3.3.1. <searchTooWide> . . . . . . . . . . . . . . . . 13
3.3.2. <languageNotSupported> . . . . . . . . . . . . . 14
3.4. Support for <iris:lookupEntity> . . . . . . . . . . . . 14
4. Formal XML Syntax . . . . . . . . . . . . . . . . . . . . . . 15
5. BEEP Transport Compliance . . . . . . . . . . . . . . . . . . 36
5.1. Message Pattern . . . . . . . . . . . . . . . . . . . . 36
5.2. Server Authentication . . . . . . . . . . . . . . . . . 36
6. URI Resolution . . . . . . . . . . . . . . . . . . . . . . . . 36
6.1. Application Service Label . . . . . . . . . . . . . . . 36
6.2. Bottom-Up Resolution . . . . . . . . . . . . . . . . . . 37
6.3. Top-Down Resolution . . . . . . . . . . . . . . . . . . 37
7. Internationalization Considerations . . . . . . . . . . . . . 38
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
8.1. XML Namespace URN Registration . . . . . . . . . . . . . 38
8.2. S-NAPTR Registration . . . . . . . . . . . . . . . . . . 39
8.3. BEEP Registration . . . . . . . . . . . . . . . . . . . 39
9. Security Considerations . . . . . . . . . . . . . . . . . . . 39
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.1. Normative References . . . . . . . . . . . . . . . . . . 39
10.2. Informative References . . . . . . . . . . . . . . . . . 40
A. Examples of Requests and Responses . . . . . . . . . . . . . . 41
A.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . 41
A.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . 42
A.3. Example 3 . . . . . . . . . . . . . . . . . . . . . . . 43
B. An Example of Database Serialization . . . . . . . . . . . . . 47
C. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 49
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 50
This document describes an IRIS registry schema for Internet domain registries using an XML Schema [4] derived from and using the IRIS [5] schema. The query and result types outlined in this document are based on the functional requirements described in CRISP [17].
本文档使用从IRIS[5]模式派生并使用该模式的XML模式[4]描述了Internet域注册表的IRIS注册表模式。本文档中概述的查询和结果类型基于CRISP[17]中描述的功能需求。
The schema given is this document is specified by using the Extensible Markup Language (XML) 1.0, as described in XML [1]; XML Schema notation, as described in XML_SD [3] and XML_SS [4]; and XML Namespaces, as described in XML_NS [2].
本文给出的模式是使用XML[1]中描述的可扩展标记语言（XML）1.0指定的；如XML[3，U]中描述的XML模式；和XML名称空间，如XML_NS[2]中所述。
Examples of client/server XML exchanges with this registry type are available in Appendix A.
附录A中提供了这种注册表类型的客户机/服务器XML交换示例。
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 BCP 14, RFC 2119 [10].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[10]中的描述进行解释。
IRIS requires the derivation of both query and result elements by a registry schema. These descriptions follow.
IRIS需要通过注册表模式派生查询元素和结果元素。这些描述如下。
References to XML elements without a namespace qualifier are from the schema defined in Section 4. References to elements and attributes with the "iris" XML namespace qualifier are from the schema defined in IRIS [5].
对没有名称空间限定符的XML元素的引用来自第4节中定义的模式。使用“iris”XML名称空间限定符对元素和属性的引用来自iris[5]中定义的模式。
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. This section will use terms defined by RFC 2119 [10] to describe these. While reading this section, please reference Section 4 for needed details on the formal XML syntax.
本节中包含的描述涉及XML元素和属性及其与协议内数据交换的关系。这些描述还包含正式XML语法范围之外的规范。本节将使用RFC 2119[10]定义的术语来描述这些。在阅读本节时，请参考第4节，以了解有关正式XML语法的必要详细信息。
<findRegistrarsByName> searches for a registration authority designated as a registrar for the registry of the server.
<findRegistrarsByName>搜索指定为服务器注册表注册人的注册机构。
If present, the <baseDomain> element MUST restrict the results of the search to registrars capable of registering subdomains in the domain signified by the content of this element.
如果存在，<baseDomain>元素必须将搜索结果限制为能够在该元素的内容所表示的域中注册子域的注册者。
The <namePart> element restricts the scope of the query with its child elements. The <beginsWith> element specifies the beginning of the registrar's name. The <endsWith> element specifies the end of the registrar's name. The <exactMatch> element specifies equivalence to the registrar's name.
元素用其子元素限制查询的范围。元素指定注册器名称的开头。元素指定注册器名称的结尾。<exactMatch>元素指定与注册器名称的等价性。
If the <namePart> element is not present, the query MUST return all registrars applicable (i.e., in consideration of <baseDomain>).
如果<namePart>元素不存在，查询必须返回所有适用的注册器（即，考虑到<baseDomain>）。
This query MUST return a result set of zero or more <registrationAuthority> elements. See Section 3.2.5.
此查询必须返回零个或多个<registrationAuthority>元素的结果集。见第3.2.5节。
<findDomainsByContact> finds domains by searches on fields associated with a domain's contact. A search constraint of <baseDomain> MUST restrict the results to domains underneath the domain specified by its content, if it is present.
<findDomainsByContact>通过搜索与域联系人关联的字段来查找域。<baseDomain>的搜索约束必须将结果限制在由其内容指定的域下的域（如果存在）。
The allowable search fields are handled with either the <contactHandle> element or one of the elements in the "contactSearchGroup" (see Section 3.1.7). The <contactHandle> element allows the domains to be selected based on the contact having the specified contact handle.
允许的搜索字段由<contactHandle>元素或“contactSearchGroup”中的一个元素处理（见第3.1.7节）。元素允许根据具有指定联系人句柄的联系人选择域。
The query MAY also be constrained further by using the optional <role> element. The contents of this element signify the role the contact has with the domain.
还可以使用可选的<role>元素进一步约束查询。此元素的内容表示联系人在域中的角色。
This query also provides optional <language> elements containing language tags. Clients MAY use these elements to hint about the natural language(s) of the affected element. Servers MAY use this information in processing the query, such as in tailoring normalization routines to aid in more effective searches.
此查询还提供包含语言标记的可选<language>元素。客户端可以使用这些元素来提示受影响元素的自然语言。服务器可以在处理查询时使用此信息，例如定制规范化例程以帮助进行更有效的搜索。
The <findDomainsByName> query finds domains by the name of a domain as it is known in DNS. The <namePart> element restricts the scope of the query with its child elements. The <beginsWith> element specifies the beginning of the domain name. The <endsWith> element specifies the end of the domain name.
<findDomainsByName>查询通过DNS中已知的域名查找域。元素用其子元素限制查询的范围。元素指定域名的开头。元素指定域名的结尾。
This query differs from the <findDomainsByName> query by allowing the scope of the query to take internationalized domain names into consideration. This query will return the union of the desired domain and any associated variants, therefore differing from a lookup in the "idn" entity class (Section 3.4) (which only returns the domain or no results).
此查询与<findDomainsByName>查询不同，它允许查询范围考虑国际化域名。此查询将返回所需域和任何关联变量的并集，因此不同于“idn”实体类中的查找（第3.4节）（仅返回域或不返回结果）。
The <namePart> element restricts the scope of the query with its child element. Its child, the <exactMatch> element, is designed to contain IDNs and not ACE labels, and thus MUST match only against equivalent IDNs, according to the notion of equivalence defined in RFC 3490 [14].
元素通过其子元素限制查询的范围。其子元素<exactMatch>元素被设计为包含IDN而非ACE标签，因此根据RFC 3490[14]中定义的等效概念，必须仅与等效IDN匹配。
This query also provides optional <language> elements containing language tags. Clients MAY use these elements to hint about the
此查询还提供包含语言标记的可选<language>元素。客户端可以使用这些元素来提示
natural language(s) of the affected element. Servers MAY use this information in processing the query, such as in tailoring normalization routines to aid in more effective searches.
受影响元素的自然语言。服务器可以在处理查询时使用此信息，例如定制规范化例程以帮助进行更有效的搜索。
<findContacts> searches for contacts given search constraints. The allowable search fields are handled by one of the elements in the "contactSearchGroup" (see Section 3.1.7).
<findContacts>搜索给定搜索约束的联系人。允许的搜索字段由“contactSearchGroup”中的一个元素处理（见第3.1.7节）。
This query also provides optional <language> elements containing language tags. Clients MAY use these elements to hint about the natural language(s) of the affected element. Servers MAY use this information in processing the query, such as in tailoring normalization routines to aid in more effective searches.
此查询还提供包含语言标记的可选<language>元素。客户端可以使用这些元素来提示受影响元素的自然语言。服务器可以在处理查询时使用此信息，例如定制规范化例程以帮助进行更有效的搜索。
This query does a simple search for the domains being hosted by a name server. The search is constrained by using either the host name [12], host handle, IPv4 address, or IPv6 address of the name server.
此查询对名称服务器承载的域进行简单搜索。通过使用名称服务器的主机名[12]、主机句柄、IPv4地址或IPv6地址来限制搜索。
Some of the queries above have similar query constraints for searching on contacts. This section describes those common parameters.
上面的一些查询在搜索联系人时具有类似的查询约束。本节介绍这些常用参数。
<commonName> allows the query to be constrained based on the common name of the contact. The constraint can constrain the query either by an exact match using the <exactMatch> element, or by a subset of the common name using the <beginsWith> and <endsWith> elements.
<commonName>允许根据联系人的常用名称约束查询。该约束可以通过使用<exactMatch>元素的精确匹配或使用<BeginWith>和<endsWith>元素的公共名称子集来约束查询。
<organization> allows the query to be constrained based on the organization name of the contact. It has the same semantics as the <commonName> element.
<organization>允许根据联系人的组织名称约束查询。它与<commonName>元素具有相同的语义。
<eMail> constrains the query based on the e-mail address of the contact. This may be done by an exact e-mail address using the <exactMatch> element or by any e-mail address in a domain using the <inDomain> element. The <inDomain> element MUST only contain a valid domain name (i.e., without an '@' symbol), and the matching SHOULD take place only on the domain given (i.e., no partial matches with respect to substrings or parent domains). If either the contents of the <inDomain> element or the domain part of the contents of the <exactMatch> element contain a name with non-ASCII characters, they MUST be normalized according to the processes of RFC 3491 [15].
<eMail>根据联系人的电子邮件地址限制查询。这可以通过使用<exactMatch>元素的确切电子邮件地址或使用<inDomain>元素的域中的任何电子邮件地址来实现。<inDomain>元素必须只包含一个有效的域名（即，没有“@”符号），并且匹配应该只在给定的域上进行（即，没有关于子字符串或父域的部分匹配）。如果<inDomain>元素的内容或<exactMatch>元素内容的域部分包含具有非ASCII字符的名称，则必须根据RFC 3491[15]的过程对其进行规范化。
The <city>, <region>, and <postalCode> elements restrict the scope of the query based on the city, region, or postal code of the contact, respectively. Each must only contain an <exactMatch> element containing the exact city, region, or postal code (i.e., no substring searches).
<city>、<region>和<postalCode>元素分别基于联系人的城市、地区或邮政编码限制查询范围。每个元素必须仅包含一个<exactMatch>元素，该元素包含准确的城市、地区或邮政编码（即，无子字符串搜索）。
Several of the results in this registry type have values that cannot be given but must be specified as present or must be flagged so that clients do not divulge them. In order to achieve this, some of the results use the following element types:
此注册表类型中的多个结果具有无法给定的值，但必须指定为存在，或者必须进行标记，以便客户端不会泄露这些值。为了实现这一点，某些结果使用以下元素类型：
o "dateTimePrivacyType" -- contains the XML Schema [3] data type "dateTime". The contents of this element MUST be specified by using the 'Z' indicator for Coordinated Universal Time (UTC).
o “dateTimePrivacyType”--包含XML架构[3]数据类型“dateTime”。必须使用协调世界时（UTC）的“Z”指示器指定此元素的内容。
o "stringPrivacyType" -- contains the XML Schema [3] data type "string".
o “stringPrivacyType”--包含XML架构[3]数据类型“string”。
o "normalizedStringPrivacyType" -- contains the XML Schema [3] data type "normalizedString".
o “normalizedStringPrivacyType”--包含XML架构[3]数据类型“normalizedString”。
o "tokenPrivacyType" -- contains the XML Schema [3] data type "token".
o “tokenPrivacyType”--包含XML架构[3]数据类型“token”。
o "domainStatusType" -- contains the optional element of <appliedDate>, indicating the date and time when the status was applied, and the optional element of <description> with the required attribute 'language', indicating a description of the status. This element also has the optional attribute 'scope', indicating the scope or origin of the status value.
o “domainStatusType”--包含可选元素<appliedDate>，表示应用状态的日期和时间；可选元素<description>具有必需属性“language”，表示状态描述。此元素还具有可选属性“scope”，指示状态值的范围或来源。
o "contactTypeType" -- contains optional <description> child elements. Each <description> child element requires a 'language' attribute.
o “contactTypeType”--包含可选的<description>子元素。每个<description>子元素都需要一个“language”属性。
As specified, these elements can have nil values and therefore may be present with empty content or present with their specified content. The use of these elements is also optional.
如指定的，这些元素可以具有nil值，因此可能存在于空内容中，也可能存在于其指定内容中。这些元素的使用也是可选的。
If present without content, each of these element types MUST have one or more of the following boolean attributes:
如果不包含内容，则这些元素类型中的每一个都必须具有以下一个或多个布尔属性：
o 'private' -- If true, this specifies that the content is absent because it may never be published.
o “private”——如果为true，则指定内容不存在，因为它可能永远不会发布。
o 'denied' -- If true, this specifies that the content is absent because policy does not allow it to be given at the current level of access.
o “拒绝”-如果为true，则指定内容不存在，因为策略不允许在当前访问级别提供内容。
If present with content, each of these element types MAY have one or more of the following boolean attributes:
如果存在内容，则这些元素类型中的每一个都可能具有以下一个或多个布尔属性：
o 'doNotRedistribute' -- If true, this specifies that the content is not to be redistributed.
o 'doNotRedistribute'——如果为true，则指定不重新分发内容。
o 'specialAccess' -- If true, this specifies that the content has been provided due to special access rights.
o “specialAccess”-如果为true，则指定由于特殊访问权限而提供内容。
These boolean attributes SHOULD be used in accordance with the level of access granted to the recipient of the data. For example, marking data as 'private' or 'denied' is to be expected if the user is anonymous or has some other low level of access that does not warrant viewing that particular data. Likewise, data marked with 'doNotRedistribute' or 'specialAccess' is to be expected if the user is authenticated and has a high level of access.
应根据授予数据接收者的访问级别使用这些布尔属性。例如，如果用户是匿名用户或具有其他不保证查看特定数据的低访问级别，则应将数据标记为“私有”或“拒绝”。同样，如果用户经过身份验证且具有较高的访问级别，则预期会出现标有“doNotRedistribute”或“specialAccess”的数据。
An example of a <domain> result:
<domain>结果示例：
<domain
authority="iana.org" registryType="dreg1"
entityClass="domain-handle" entityName="example-com-1">
<domainName>example.com</domainName>
<domainHandle>tcs-com-1</domainHandle>
<nameServer
iris:referentType="host"
authority="iana.org" registryType="dreg1"
entityClass="host-handle" entityName="research7" />
<nameServer
iris:referentType="host"
authority="iana.org" registryType="dreg1"
entityClass="host-handle" entityName="nsol184" />
<registry
iris:referentType="registrationAuthority"
authority="com"
registryType="dreg1"
entityClass="contact-handle"
entityName="VGRS" />
<registrar
iris:referentType="registrationAuthority"
authority="iana.org" registryType="dreg1"
entityClass="contact-handle" entityName="dbarton" />
<domain
authority="iana.org" registryType="dreg1"
entityClass="domain-handle" entityName="example-com-1">
<domainName>example.com</domainName>
<domainHandle>tcs-com-1</domainHandle>
<nameServer
iris:referentType="host"
authority="iana.org" registryType="dreg1"
entityClass="host-handle" entityName="research7" />
<nameServer
iris:referentType="host"
authority="iana.org" registryType="dreg1"
entityClass="host-handle" entityName="nsol184" />
<registry
iris:referentType="registrationAuthority"
authority="com"
registryType="dreg1"
entityClass="contact-handle"
entityName="VGRS" />
<registrar
iris:referentType="registrationAuthority"
authority="iana.org" registryType="dreg1"
entityClass="contact-handle" entityName="dbarton" />
<initialDelegationDateTime xsi:nil="true"/>
</domain>
<initialDelegationDateTime xsi:nil="true"/>
</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 [9].
o <domainName>——域名在DNS中的全名。此元素的内容必须是RFC 1035[9]指定的域名。
o <idn> -- the name of the domain in nameprep form, if applicable. See RFC 3491 [15].
o <idn>——nameprep表单中的域名（如果适用）。见RFC 3491[15]。
o <domainHandle> -- a registry unique assigned identifier for a domain.
o <domainHandle>——为域分配的注册表唯一标识符。
o <nameServer> -- MUST contain an entity reference to a referent of type <host> (Section 3.2.3).
o <nameServer>--必须包含对<host>类型的引用对象的实体引用（第3.2.3节）。
o <registrant> -- contains an entity reference to the registrant of this domain. The referent MUST be a <contact> result (Section 3.2.4).
o <注册人>--包含对该域注册人的实体引用。参考物必须是<contact>结果（第3.2.4节）。
o Domain contacts -- the following elements contain an entity reference with a relationship to the domain. The referent of each MUST be a <contact> (Section 3.2.4). * <billingContacts> * <technicalContacts> * <administrativeContacts> * <legalContacts> * <zoneContacts> * <abuseContacts> * <securityContacts> * <otherContacts>
o 域联系人——以下元素包含与域有关系的实体引用。每个的参照物必须是<contact>（第3.2.4节）。*<billingContacts>*<technicalContacts>*<administrativeContacts>*<legalContacts>*<zoneContacts>*<abuseContacts>*<securityContacts>*<otherContacts>
o <status> -- This may contain at least one of the following
elements of type 'domainStatusType' (see Section 3.2.1), but none
of these elements may appear more than once.
* <reservedDelegation> -- permanently inactive
* <assignedAndActive> -- normal state
* <assignedAndInactive> -- registration assigned but delegation
inactive
* <assignedAndOnHold> -- dispute
* <revoked> -- database purge pending
* <transferPending> -- change of authority pending
* <registryLock> -- on hold by registry
* <registrarLock> -- on hold by registrar
o <status> -- This may contain at least one of the following
elements of type 'domainStatusType' (see Section 3.2.1), but none
of these elements may appear more than once.
* <reservedDelegation> -- permanently inactive
* <assignedAndActive> -- normal state
* <assignedAndInactive> -- registration assigned but delegation
inactive
* <assignedAndOnHold> -- dispute
* <revoked> -- database purge pending
* <transferPending> -- change of authority pending
* <registryLock> -- on hold by registry
* <registrarLock> -- on hold by registrar
o <domainVariant> -- contains an entity reference, the referent of which MUST be a <domain> (Section 3.2.2).
o <domainVariant>——包含实体引用，其引用对象必须是<domain>（第3.2.2节）。
o <registrationReference> -- contains an entity reference, the referent of which MUST be a <domain> (Section 3.2.2). This element is intended 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>——包含实体引用，其引用对象必须是<domain>（第3.2.2节）。此元素旨在指向下游注册参考。因此，如果这是域注册表返回的结果，它应该指向域注册器或注册者服务中的域。
o <registry> -- contains an entity reference specifying the domain registry operator for this domain, which MUST be a <registrationAuthority> (Section 3.2.5). This element has an optional boolean 'hosting' attribute. When the value of this attribute is positive, it indicates that the registry is responsible for authoritatively answering DNS queries for this domain.
o <registry>--包含一个实体引用，指定此域的域注册表运算符，该运算符必须是<registrationAuthority>（第3.2.5节）。此元素具有可选的布尔“宿主”属性。当此属性的值为正值时，表示注册表负责对此域的DNS查询进行授权应答。
o <registrar> -- contains an entity reference specifying the domain registrar operator for this domain, which MUST be a <registrationAuthority> (Section 3.2.5). This element has an optional boolean 'hosting' attribute. When the value of this attribute is positive, it indicates that the registrar is responsible for authoratively answering DNS queries for this domain.
o <registrator>--包含一个实体引用，指定此域的域注册操作员，该操作员必须是<registrationAuthority>（第3.2.5节）。此元素具有可选的布尔“宿主”属性。当此属性的值为正值时，表示注册器负责以授权方式回答此域的DNS查询。
o <initialDelegationDateTime> -- contains the date and time of the initial delegation of this domain.
o <initialDelegationDateTime>——包含此域的初始委派的日期和时间。
o <lastRenewalDateTime> -- contains the date and time of last renewal of this domain.
o <lastRenewalDateTime>——包含此域上次续订的日期和时间。
o <expirationDateTime> -- contains the date and time of the expiration of this domain.
o <expirationDateTime>--包含此域的过期日期和时间。
o <lastContactModificationDateTime> -- specifies the last time a contact for the domain was added or removed.
o <lastContactModificationDateTime>——指定上次添加或删除域联系人的时间。
o <lastContactModificationBy> -- contains an entity reference. The referent MUST be a <contact> (Section 3.2.4) responsible for the last addition or removal of a contact for this domain.
o <lastContactModificationBy>——包含实体引用。引用人必须是负责最后添加或删除此域联系人的<contact>（第3.2.4节）。
o <lastDelegationModificationDateTime> -- contains the date and time of the last time one of the nameservers was added or removed for the delegation of this domain.
o <lastDelegationModificationDateTime>--包含上次为此域的委派添加或删除一个名称服务器的日期和时间。
o <lastDelegationModificationBy> -- contains an entity reference. The referent MUST be a <contact> result (Section 3.2.4) and MUST be responsible for the last addition or removal of a nameserver for this domain.
o <lastDelegationModificationBy>--包含实体引用。引用方必须是<contact>结果（第3.2.4节），并且必须负责最后添加或删除此域的名称服务器。
o <lastVerificationDateTime> -- contains the date and time of the last time the data for this domain was verified by the responsible registration authority.
o <lastVerificationDateTime>——包含责任注册机构上次验证此域数据的日期和时间。
o <iris:seeAlso> -- contains an entity reference specifying a referent indirectly associated with this domain.
o <iris:seeAlls>--包含一个实体引用，指定与此域间接关联的引用对象。
An example of a <host> result:
<host>结果示例：
<host
authority="iana.org" registryType="dreg1"
entityClass="host-handle" entityName="nsol184" >
<hostHandle>nsol184</hostHandle>
<hostName>a.iana-servers.net</hostName>
<ipV4Address>192.0.2.43</ipV4Address>
<hostContact
iris:referentType="contact"
authority="iana.org" registryType="dreg1"
entityClass="contact-handle" entityName="dbarton" />
</host>
<host
authority="iana.org" registryType="dreg1"
entityClass="host-handle" entityName="nsol184" >
<hostHandle>nsol184</hostHandle>
<hostName>a.iana-servers.net</hostName>
<ipV4Address>192.0.2.43</ipV4Address>
<hostContact
iris:referentType="contact"
authority="iana.org" registryType="dreg1"
entityClass="contact-handle" entityName="dbarton" />
</host>
The <host> element represents an instance of a host registration. The children of the <host> element are as follows:
元素表示主机注册的实例。<host>元素的子元素如下所示：
o <hostHandle> -- a registry unique assigned identifier for the host.
o <hostHandle>--为主机分配的注册表唯一标识符。
o <hostName> -- the fully qualified domain name of the host. The contents of this element are a domain name and MUST conform to RFC 1035 [9].
o <hostName>--主机的完全限定域名。此元素的内容是域名，必须符合RFC 1035[9]。
o <ipV4Address> -- the content of this MUST conform to the a valid IP version 4 host address, as specified by RFC 791 [8].
o <ipV4Address>--此内容必须符合RFC 791[8]指定的有效IP版本4主机地址。
o <ipV6Address> -- the content of this MUST conform to the a valid IP version 6 host address, as specified by RFC 3513 [7].
o <ipV6Address>——此内容必须符合RFC 3513[7]指定的有效IP版本6主机地址。
o <hostContact> -- contains an entity reference specifying a contact associated with this host. The referent MUST be <contact> (Section 3.2.4) results.
o <hostContact>--包含一个实体引用，指定与此主机关联的联系人。参考物必须是<contact>（第3.2.4节）结果。
o <createdDateTime> -- contains the date and time when this host was created.
o <createdDateTime>——包含创建此主机的日期和时间。
o <lastModificationDateTime> -- contains the date and time when this host was last modified.
o <lastModificationDateTime>——包含上次修改此主机的日期和时间。
o <lastVerificationDateTime> -- contains the date and time when this data for this host was last verified to be correct by the appropriate registration authority.
o <lastVerificationDateTime>——包含此主机的此数据上次被相应的注册机构验证为正确的日期和时间。
o <iris:seeAlso> -- contains an entity reference specifying a referent indirectly associated with this host.
o <iris:seeAllow>--包含一个实体引用，指定与此主机间接关联的引用对象。
An example of a <contact> result:
<contact>结果示例：
<contact
authority="iana.org" registryType="dreg1"
entityClass="contact-handle" entityName="dbarton" >
<contactHandle>dbarton</contactHandle>
<commonName>IANA Manager</commonName>
<organization>Internet Assigned Numbers Authority</organization>
<eMail>res-dom@iana.org</eMail>
<postalAddress>
<address>4676 Admiralty Way, Suite 330</address>
<city>Marina del Rey</city>
<region>CA</region>
<postalCode>92092</postalCode>
<country>US</country>
</postalAddress>
<phone>+1.3108239358</phone>
</contact>
<contact
authority="iana.org" registryType="dreg1"
entityClass="contact-handle" entityName="dbarton" >
<contactHandle>dbarton</contactHandle>
<commonName>IANA Manager</commonName>
<organization>Internet Assigned Numbers Authority</organization>
<eMail>res-dom@iana.org</eMail>
<postalAddress>
<address>4676 Admiralty Way, Suite 330</address>
<city>Marina del Rey</city>
<region>CA</region>
<postalCode>92092</postalCode>
<country>US</country>
</postalAddress>
<phone>+1.3108239358</phone>
</contact>
The <contact> element represents an instance of a contact registration. The children of the <contact> element are as follows:
<contact>元素表示联系人注册的实例。<contact>元素的子元素如下所示：
o <contactHandle> -- a registry unique assigned identifier for this contact.
o <contactHandle>--此联系人的注册表唯一分配标识符。
o <commonName> -- the name of the contact.
o <commonName>——联系人的姓名。
o <language> -- a specification of the language code to use to localize the data in this result.
o <language>——用于本地化此结果中数据的语言代码规范。
o <type> -- contains one of the following child elements: <person>, <organization>, <role>, or <other>. Each of these elements is a "contactTypeType" as defined in Section 3.2.1.
o <type>--包含以下子元素之一：<person>、<organization>、<role>或<other>。这些元素中的每一个都是第3.2.1节中定义的“contactTypeType”。
o <organization> -- contains the organization name of the contact.
o <organization>--包含联系人的组织名称。
o <eMail> -- contains an e-mail address for this contact.
o <eMail>--包含此联系人的电子邮件地址。
o <IDNeMail> -- contains an e-mail address within an internationalized domain name [14].
o <IDNeMail>——包含国际化域名内的电子邮件地址[14]。
o <sip> -- contains a SIP URI for this contact.
o <sip>--包含此联系人的sip URI。
o <postalAddress> -- contains children representing a postal address. <postalAddress> has the following children: * <address> -- contains the street address for this contact. * <city> -- contains the city for this contact. * <region> -- contains the national region for this contact. * <postalCode> -- contains the postal code for this contact. * <country> -- contains the country for this contact. This SHOULD be a two-letter country code compliant with ISO 3166 [11].
o <PostaladAddress>--包含表示邮政地址的子项<postalAddress>具有以下子项：*<address>--包含此联系人的街道地址。*<城市>--包含此联系人的城市。*<地区>--包含此联系人的国家地区。*<postalCode>--包含此联系人的邮政编码。*<国家>--包含此联系人的国家/地区。这应该是符合ISO 3166[11]的两个字母的国家代码。
o <phone> -- contains a voice phone number for this contact. If it begins with a '+' (plus) character, it MUST be a number defined by E164 [13]. The format number defined in E164 [13] is RECOMMENDED.
o <phone>--包含此联系人的语音电话号码。如果以“+”（加号）字符开头，则必须是E164[13]定义的数字。建议使用E164[13]中定义的格式编号。
o <fax> -- contains a facsimile phone number for this contact. If it begins with a '+' (plus) character, it MUST be a number defined by E164 [13]. The format number defined in E164 [13] is RECOMMENDED.
o <fax>--包含此联系人的传真电话号码。如果以“+”（加号）字符开头，则必须是E164[13]定义的数字。建议使用E164[13]中定义的格式编号。
o <createdDateTime> -- contains the date and time when this contact was created.
o <createdDateTime>——包含创建此联系人的日期和时间。
o <lastModificationDateTime> -- contains the date and time when this contact was last modified.
o <lastModificationDateTime>——包含上次修改此联系人的日期和时间。
o <lastVerificationDateTime> -- contains the date and time when this data for this contact was last verified to be correct by the appropriate registration authority.
o <lastVerificationDateTime>——包含此联系人的此数据上次被相应的注册机构验证为正确的日期和时间。
o <translatedContacts> -- contains an entity reference specifying equivalents of this contact that have been translated into other languages. The referent MUST be <contact> results (Section 3.2.4).
o <translatedContacts>--包含一个实体引用，指定此联系人已翻译成其他语言的等效项。参考物必须是<contact>结果（第3.2.4节）。
o <iris:seeAlso> -- contains an entity reference specifying a referent indirectly associated with this contact.
o <iris:see也>--包含实体引用，指定与此联系人间接关联的引用对象。
An example of a <registrationAuthority> result:
<registrationAuthority>结果示例：
<registrationAuthority
authority="iana.org" registryType="dreg1"
entityClass="registration-authority" entityName="iana" >
<serviceInstance
iris:referentType="iris:serviceIdentification"
authority="iana.org" registryType="dreg1"
entityClass="iris" entityName="id" />
<organizationName>
Internet Assigned Numbers Authority
</organizationName>
<registrar />
</registrationAuthority>
<registrationAuthority
authority="iana.org" registryType="dreg1"
entityClass="registration-authority" entityName="iana" >
<serviceInstance
iris:referentType="iris:serviceIdentification"
authority="iana.org" registryType="dreg1"
entityClass="iris" entityName="id" />
<organizationName>
Internet Assigned Numbers Authority
</organizationName>
<registrar />
</registrationAuthority>
The <registrationAuthority> result represents an entity capable of registering domains.
<registrationAuthority>结果表示能够注册域的实体。
The <serviceInstance> child element of <registrationAuthority> contains an entity reference pointing to the entity "id" in the entity class "iris". The authority areas found in the referent MUST be domains for which a given registration authority has control.
<registrationAuthority>的<serviceInstance>子元素包含一个实体引用，指向实体类“iris”中的实体“id”。在引用对象中找到的权限区域必须是给定注册机构控制的域。
The <organizationName> child element contains the name of the registration authority.
<organizationName>子元素包含注册机构的名称。
The registration authority type child elements <registry>, <registrar>, and <other> determine the role this registration authority plays in the process of registering domains. This element is intended to explain the various roles a registration authority may have in the authority areas pointed to by the <serviceInstance> element. A client MAY understand the relationship of a registration authority with respect to a domain by the placement of the reference in the domain (e.g., <registry> or <registrar>).
注册机构类型的子元素<registry>、<registrator>和<other>确定此注册机构在注册域过程中所起的作用。此元素旨在解释注册机构在<serviceInstance>元素所指的权限区域中可能扮演的各种角色。客户可以通过在域中放置引用（例如，<registry>或<registrator>）来理解注册机构与域的关系。
The <domain> child elements each contain one domain name signifying the domains for which this registration authority may register sub-domains.
<domain>子元素每个都包含一个域名，表示该注册机构可以注册子域的域。
Servers MAY use the <searchTooWide> error code when a query must be narrowed to yield a result set acceptable under the policies of the server operator.
当必须缩小查询范围以生成服务器操作员策略下可接受的结果集时，服务器可能会使用<searchTooWide>错误代码。
The queries <findDomainsByRegistrant>, <findDomainsByIDNName>, and <findContacts> support optional language tags that allow a client to suggest to a server the languages in which to scope the queries. If a client passes to the server a language that the server does not support, the server MAY use this error code to indicate that one of the languages is not supported.
查询<findDomainsByRegistrant>、<finddomainsbyidname>和<findContacts>支持可选的语言标记，这些标记允许客户端向服务器建议用于确定查询范围的语言。如果客户端将服务器不支持的语言传递给服务器，服务器可能会使用此错误代码指示其中一种语言不受支持。
This element contains child elements named <unsupportedLanguage>. Each of these child elements specifies a language not supported by the server. When a server returns this error, it MUST give the languages from the query which are not supported.
此元素包含名为<unsupportedLanguage>的子元素。这些子元素中的每一个都指定了服务器不支持的语言。当服务器返回此错误时，它必须提供查询中不支持的语言。
The following types of entity classes are recognized by the <lookupEntity> query of IRIS for this registry:
此注册表的IRIS的<lookupEntity>查询可识别以下类型的实体类：
o host-name -- The fully qualified domain name of a nameserver. It yields a <host> (Section 3.2.3) in the response.
o 主机名--名称服务器的完全限定域名。它在响应中产生一个<host>（第3.2.3节）。
o host-handle -- The registry unique identifier given a nameserver. It yields a <host> (Section 3.2.3) in the response.
o 主机句柄——给定名称服务器的注册表唯一标识符。它在响应中产生一个<host>（第3.2.3节）。
o domain-name -- The fully qualified name of a domain. This a domain name as specified by RFC 1035 [9]. It yields a <domain> (Section 3.2.2) in the response.
o 域名——域的完全限定名。这是RFC 1035[9]指定的域名。它在响应中产生一个<domain>（第3.2.2节）。
o idn -- The fully qualified name of a domain in nameprep form (see RFC 3491 [15]). It yields a <domain> (Section 3.2.2) in the response.
o idn——以nameprep格式表示的域的完全限定名（参见RFC 3491[15]）。它在响应中产生一个<domain>（第3.2.2节）。
o domain-handle -- The registry unique identifier given a domain. It yields a <domain> (Section 3.2.2) in the response.
o 域句柄--给定域的注册表唯一标识符。它在响应中产生一个<domain>（第3.2.2节）。
o contact-handle -- The registry unique identifier given a contact. It yields a <contact> (Section 3.2.4) in the response.
o 联系人句柄--给定联系人的注册表唯一标识符。它在响应中产生<触点>（第3.2.4节）。
o ipv4-address -- The IPv4 address of a nameserver. It yields a <host> (Section 3.2.3) in the response.
o ipv4地址--名称服务器的ipv4地址。它在响应中产生一个<host>（第3.2.3节）。
o ipv6-address -- The IPv6 address of a nameserver. It yields a <host> (Section 3.2.3) in the response.
o ipv6地址--名称服务器的ipv6地址。它在响应中产生一个<host>（第3.2.3节）。
o registration-authority -- The name of a registration authority. It yields a <registrationAuthority> (Section 3.2.5) in the response.
o 登记机关——登记机关的名称。它在响应中产生<registrationAuthority>（第3.2.5节）。
All names in these entity classes are case insensitive.
这些实体类中的所有名称都不区分大小写。
This registry schema is specified in the XML Schema notation. The formal syntax presented here is a complete schema representation suitable for automated validation of an XML instance when combined with the formal schema syntax of IRIS.
这个注册表模式是用XML模式表示法指定的。这里介绍的形式语法是一个完整的模式表示，当与IRIS的形式模式语法结合使用时，它适合于XML实例的自动验证。
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:dreg="urn:ietf:params:xml:ns:dreg1"
xmlns:iris="urn:ietf:params:xml:ns:iris1"
targetNamespace="urn:ietf:params:xml:ns:dreg1"
elementFormDefault="qualified" >
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:dreg="urn:ietf:params:xml:ns:dreg1"
xmlns:iris="urn:ietf:params:xml:ns:iris1"
targetNamespace="urn:ietf:params:xml:ns:dreg1"
elementFormDefault="qualified" >
<import namespace="urn:ietf:params:xml:ns:iris1" />
<import namespace="urn:ietf:params:xml:ns:iris1" />
<annotation>
<documentation>
Domain registry schema
derived from IRIS schema
</documentation>
</annotation>
<annotation>
<documentation>
Domain registry schema
derived from IRIS schema
</documentation>
</annotation>
<!-- ========================================= -->
<!-- -->
<!-- Query Types -->
<!-- -->
<!-- ========================================= -->
<!-- ========================================= -->
<!-- -->
<!-- Query Types -->
<!-- -->
<!-- ========================================= -->
<!-- -->
<!-- Find Registrars By Name -->
<!-- -->
<!-- -->
<!-- Find Registrars By Name -->
<!-- -->
<complexType
name="findRegistrarsByNameType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<element
ref="dreg:baseDomain"
minOccurs="0"
maxOccurs="1" />
<element
name="namePart"
type="dreg:exactOrPartialMatchParameter"
<complexType
name="findRegistrarsByNameType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<element
ref="dreg:baseDomain"
minOccurs="0"
maxOccurs="1" />
<element
name="namePart"
type="dreg:exactOrPartialMatchParameter"
minOccurs="0"
maxOccurs="1" />
</sequence>
</extension>
</complexContent>
</complexType>
minOccurs="0"
maxOccurs="1" />
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="findRegistrarsByName"
type="dreg:findRegistrarsByNameType"
substitutionGroup="iris:query" />
<element
name="findRegistrarsByName"
type="dreg:findRegistrarsByNameType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find Domains By Contact -->
<!-- -->
<!-- -->
<!-- Find Domains By Contact -->
<!-- -->
<complexType
name="findDomainsByContactType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<element
ref="dreg:baseDomain"
minOccurs="0"
maxOccurs="1" />
<choice>
<group
ref="dreg:contactSearchGroup" />
<element
name="contactHandle"
type="dreg:exactMatchParameter" />
</choice>
<element
name="role"
minOccurs="0"
maxOccurs="1" >
<simpleType>
<restriction
base="string" >
<enumeration
value="registrant" />
<enumeration
value="billingContact" />
<enumeration
value="technicalContact" />
<enumeration
value="administrativeContact" />
<complexType
name="findDomainsByContactType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<element
ref="dreg:baseDomain"
minOccurs="0"
maxOccurs="1" />
<choice>
<group
ref="dreg:contactSearchGroup" />
<element
name="contactHandle"
type="dreg:exactMatchParameter" />
</choice>
<element
name="role"
minOccurs="0"
maxOccurs="1" >
<simpleType>
<restriction
base="string" >
<enumeration
value="registrant" />
<enumeration
value="billingContact" />
<enumeration
value="technicalContact" />
<enumeration
value="administrativeContact" />
<enumeration
value="legalContact" />
<enumeration
value="zoneContact" />
<enumeration
value="abuseContact" />
<enumeration
value="securityContact" />
<enumeration
value="otherContact" />
</restriction>
</simpleType>
</element>
<element
name="language"
type="language"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<enumeration
value="legalContact" />
<enumeration
value="zoneContact" />
<enumeration
value="abuseContact" />
<enumeration
value="securityContact" />
<enumeration
value="otherContact" />
</restriction>
</simpleType>
</element>
<element
name="language"
type="language"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="findDomainsByContact"
type="dreg:findDomainsByContactType"
substitutionGroup="iris:query" />
<element
name="findDomainsByContact"
type="dreg:findDomainsByContactType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find Domains By Name -->
<!-- -->
<!-- -->
<!-- Find Domains By Name -->
<!-- -->
<complexType
name="findDomainsByNameType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<element
name="namePart"
type="dreg:partialMatchParameter" />
</sequence>
</extension>
</complexContent>
</complexType>
<complexType
name="findDomainsByNameType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<element
name="namePart"
type="dreg:partialMatchParameter" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findDomainsByName"
<element name=“findDomainsByName”
type="dreg:findDomainsByNameType"
substitutionGroup="iris:query" />
type="dreg:findDomainsByNameType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find Domains By Internationalized Name -->
<!-- -->
<!-- -->
<!-- Find Domains By Internationalized Name -->
<!-- -->
<complexType
name="findDomainsByIDNType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<element
name="namePart"
type="dreg:exactMatchParameter" />
<element
name="language"
type="language"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType
name="findDomainsByIDNType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<element
name="namePart"
type="dreg:exactMatchParameter" />
<element
name="language"
type="language"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="findDomainsByIDN"
type="dreg:findDomainsByIDNType"
substitutionGroup="iris:query" />
<element
name="findDomainsByIDN"
type="dreg:findDomainsByIDNType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find Contacts -->
<!-- -->
<!-- -->
<!-- Find Contacts -->
<!-- -->
<complexType
name="findContactsType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<group
ref="dreg:contactSearchGroup" />
<element
name="language"
type="language"
minOccurs="0"
maxOccurs="unbounded"/>
<complexType
name="findContactsType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<group
ref="dreg:contactSearchGroup" />
<element
name="language"
type="language"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="findContacts"
type="dreg:findContactsType"
substitutionGroup="iris:query" />
<element
name="findContacts"
type="dreg:findContactsType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find Domains By Host -->
<!-- -->
<!-- -->
<!-- Find Domains By Host -->
<!-- -->
<complexType
name="findDomainsByHostType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<element
ref="dreg:baseDomain"
minOccurs="0"
maxOccurs="1" />
<choice>
<element
name="hostName"
type="dreg:exactMatchParameter" />
<element
name="hostHandle"
type="dreg:exactMatchParameter" />
<element
name="ipV4Address"
type="dreg:exactMatchParameter" />
<element
name="ipV6Address"
type="dreg:exactMatchParameter" />
</choice>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType
name="findDomainsByHostType">
<complexContent>
<extension
base="iris:queryType">
<sequence>
<element
ref="dreg:baseDomain"
minOccurs="0"
maxOccurs="1" />
<choice>
<element
name="hostName"
type="dreg:exactMatchParameter" />
<element
name="hostHandle"
type="dreg:exactMatchParameter" />
<element
name="ipV4Address"
type="dreg:exactMatchParameter" />
<element
name="ipV6Address"
type="dreg:exactMatchParameter" />
</choice>
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="findDomainsByHost"
type="dreg:findDomainsByHostType"
substitutionGroup="iris:query" />
<element
name="findDomainsByHost"
type="dreg:findDomainsByHostType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Contact Search Group -->
<!-- -->
<!-- -->
<!-- Contact Search Group -->
<!-- -->
<group
name="contactSearchGroup">
<choice>
<element
name="commonName"
type="dreg:exactOrPartialMatchParameter" />
<element
name="organization"
type="dreg:exactOrPartialMatchParameter" />
<element
name="eMail"
type="dreg:domainResourceParameter" />
<element
name="city"
type="dreg:exactMatchParameter" />
<element
name="region"
type="dreg:exactMatchParameter" />
<element
name="postalCode"
type="dreg:exactMatchParameter" />
</choice>
</group>
<group
name="contactSearchGroup">
<choice>
<element
name="commonName"
type="dreg:exactOrPartialMatchParameter" />
<element
name="organization"
type="dreg:exactOrPartialMatchParameter" />
<element
name="eMail"
type="dreg:domainResourceParameter" />
<element
name="city"
type="dreg:exactMatchParameter" />
<element
name="region"
type="dreg:exactMatchParameter" />
<element
name="postalCode"
type="dreg:exactMatchParameter" />
</choice>
</group>
<complexType
name="exactOrPartialMatchParameter">
<choice>
<group
ref="dreg:partialMatchGroup" />
<group
ref="dreg:exactMatchGroup" />
</choice>
</complexType>
<complexType
name="exactOrPartialMatchParameter">
<choice>
<group
ref="dreg:partialMatchGroup" />
<group
ref="dreg:exactMatchGroup" />
</choice>
</complexType>
<complexType
name="exactMatchParameter">
<group
ref="dreg:exactMatchGroup" />
</complexType>
<complexType
name="exactMatchParameter">
<group
ref="dreg:exactMatchGroup" />
</complexType>
<complexType
name="partialMatchParameter">
<sequence>
<group
<complexType
name="partialMatchParameter">
<sequence>
<group
ref="dreg:partialMatchGroup" />
</sequence>
</complexType>
ref="dreg:partialMatchGroup" />
</sequence>
</complexType>
<complexType
name="domainResourceParameter" >
<choice>
<group
ref="dreg:exactMatchGroup" />
<element
name="inDomain"
type="token" />
</choice>
</complexType>
<complexType
name="domainResourceParameter" >
<choice>
<group
ref="dreg:exactMatchGroup" />
<element
name="inDomain"
type="token" />
</choice>
</complexType>
<element
name="baseDomain"
type="normalizedString" />
<element
name="baseDomain"
type="normalizedString" />
<group
name="partialMatchGroup">
<choice>
<sequence>
<element
name="beginsWith">
<simpleType>
<restriction
base="token">
<minLength
value="1"/>
</restriction>
</simpleType>
</element>
<element
minOccurs="0"
name="endsWith">
<simpleType>
<restriction
base="token">
<minLength
value="1"/>
</restriction>
</simpleType>
</element>
</sequence>
<element
name="endsWith">
<simpleType>
<group
name="partialMatchGroup">
<choice>
<sequence>
<element
name="beginsWith">
<simpleType>
<restriction
base="token">
<minLength
value="1"/>
</restriction>
</simpleType>
</element>
<element
minOccurs="0"
name="endsWith">
<simpleType>
<restriction
base="token">
<minLength
value="1"/>
</restriction>
</simpleType>
</element>
</sequence>
<element
name="endsWith">
<simpleType>
<restriction
base="token">
<minLength
value="1"/>
</restriction>
</simpleType>
</element>
</choice>
</group>
<restriction
base="token">
<minLength
value="1"/>
</restriction>
</simpleType>
</element>
</choice>
</group>
<group
name="exactMatchGroup">
<sequence>
<element
name="exactMatch"
type="normalizedString" />
</sequence>
</group>
<group
name="exactMatchGroup">
<sequence>
<element
name="exactMatch"
type="normalizedString" />
</sequence>
</group>
<!-- ========================================= -->
<!-- -->
<!-- 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="domainHandle"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
<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="domainHandle"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="nameServer"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="registrant"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="billingContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="technicalContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="administrativeContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="legalContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="zoneContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="abuseContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="securityContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="otherContact"
maxOccurs="1" />
<element
name="nameServer"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="registrant"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="billingContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="technicalContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="administrativeContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="legalContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="zoneContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="abuseContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="securityContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="otherContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="lastContactModificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastContactModificationBy"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="status"
minOccurs="0"
maxOccurs="1">
<complexType>
<all>
<element
name="reservedDelegation"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="assignedAndActive"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="assignedAndInactive"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="assignedAndOnHold"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="revoked"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="transferPending"
minOccurs="0"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="lastContactModificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastContactModificationBy"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="status"
minOccurs="0"
maxOccurs="1">
<complexType>
<all>
<element
name="reservedDelegation"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="assignedAndActive"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="assignedAndInactive"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="assignedAndOnHold"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="revoked"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="transferPending"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="registryLock"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="registrarLock"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="other"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
</all>
</complexType>
</element>
<element
name="domainVariant"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="registrationReference"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="registry"
minOccurs="0"
maxOccurs="1">
<complexType>
<complexContent>
<extension
base="iris:entityType">
<attribute
name="hosting"
type="boolean" />
</extension>
</complexContent>
</complexType>
</element>
<element
name="registrar"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="registryLock"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="registrarLock"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
<element
name="other"
minOccurs="0"
maxOccurs="1"
type="dreg:domainStatusType" />
</all>
</complexType>
</element>
<element
name="domainVariant"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="registrationReference"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="registry"
minOccurs="0"
maxOccurs="1">
<complexType>
<complexContent>
<extension
base="iris:entityType">
<attribute
name="hosting"
type="boolean" />
</extension>
</complexContent>
</complexType>
</element>
<element
name="registrar"
minOccurs="0"
maxOccurs="1">
<complexType>
<complexContent>
<extension
base="iris:entityType">
<attribute
name="hosting"
type="boolean" />
</extension>
</complexContent>
</complexType>
</element>
<element
name="initialDelegationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastRenewalDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="expirationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastDelegationModificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastDelegationModificationBy"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="lastVerificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
maxOccurs="1">
<complexType>
<complexContent>
<extension
base="iris:entityType">
<attribute
name="hosting"
type="boolean" />
</extension>
</complexContent>
</complexType>
</element>
<element
name="initialDelegationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastRenewalDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="expirationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastDelegationModificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastDelegationModificationBy"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="lastVerificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
ref="iris:seeAlso"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
ref="iris:seeAlso"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="domain"
type="dreg:domainType"
substitutionGroup="iris:result" />
<element
name="domain"
type="dreg:domainType"
substitutionGroup="iris:result" />
<!-- -->
<!-- Host -->
<!-- -->
<!-- -->
<!-- Host -->
<!-- -->
<complexType
name="hostType">
<complexContent>
<extension
base="iris:resultType">
<sequence>
<element
name="hostHandle"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="hostName"
type="normalizedString" />
<element
name="ipV4Address"
type="token"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="ipV6Address"
type="token"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="hostContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
<complexType
name="hostType">
<complexContent>
<extension
base="iris:resultType">
<sequence>
<element
name="hostHandle"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="hostName"
type="normalizedString" />
<element
name="ipV4Address"
type="token"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="ipV6Address"
type="token"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="hostContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="createdDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastModificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastVerificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
ref="iris:seeAlso"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
name="createdDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastModificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastVerificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
ref="iris:seeAlso"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="host"
type="dreg:hostType"
substitutionGroup="iris:result" />
<element
name="host"
type="dreg:hostType"
substitutionGroup="iris:result" />
<!-- -->
<!-- Contact -->
<!-- -->
<!-- -->
<!-- Contact -->
<!-- -->
<complexType
name="contactType">
<complexContent>
<extension
base="iris:resultType">
<sequence>
<element
name="contactHandle"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
<complexType
name="contactType">
<complexContent>
<extension
base="iris:resultType">
<sequence>
<element
name="contactHandle"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="commonName"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1"/>
<element
name="language"
type="language"
minOccurs="0"
maxOccurs="1" />
<element
name="type"
minOccurs="0"
maxOccurs="1">
<complexType>
<choice>
<element
name="person"
type="dreg:contactTypeType" />
<element
name="organization"
type="dreg:contactTypeType" />
<element
name="role"
type="dreg:contactTypeType" />
<element
name="other"
type="dreg:contactTypeType" />
</choice>
</complexType>
</element>
<element
name="organization"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="eMail"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="IDNeMail"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
name="commonName"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1"/>
<element
name="language"
type="language"
minOccurs="0"
maxOccurs="1" />
<element
name="type"
minOccurs="0"
maxOccurs="1">
<complexType>
<choice>
<element
name="person"
type="dreg:contactTypeType" />
<element
name="organization"
type="dreg:contactTypeType" />
<element
name="role"
type="dreg:contactTypeType" />
<element
name="other"
type="dreg:contactTypeType" />
</choice>
</complexType>
</element>
<element
name="organization"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="eMail"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="IDNeMail"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="sip"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="postalAddress"
minOccurs="0"
maxOccurs="unbounded" >
<complexType>
<sequence>
<element
name="address"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="city"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="region"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="postalCode"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="country"
type="dreg:tokenPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
</sequence>
</complexType>
</element>
<element
name="phone"
maxOccurs="unbounded" />
<element
name="sip"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="postalAddress"
minOccurs="0"
maxOccurs="unbounded" >
<complexType>
<sequence>
<element
name="address"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="city"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="region"
type="dreg:stringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="postalCode"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="country"
type="dreg:tokenPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
</sequence>
</complexType>
</element>
<element
name="phone"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="fax"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="createdDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastModificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastVerificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="translatedContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
ref="iris:seeAlso"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="fax"
type="dreg:normalizedStringPrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="createdDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastModificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="lastVerificationDateTime"
type="dreg:dateTimePrivacyType"
nillable="true"
minOccurs="0"
maxOccurs="1" />
<element
name="translatedContact"
type="iris:entityType"
minOccurs="0"
maxOccurs="unbounded" />
<element
ref="iris:seeAlso"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="contact"
type="dreg:contactType"
substitutionGroup="iris:result" />
<element
name="contact"
type="dreg:contactType"
substitutionGroup="iris:result" />
<!-- -->
<!-- -->
<!-- Registration Authority -->
<!-- -->
<!-- Registration Authority -->
<!-- -->
<complexType
name="registrationAuthorityType">
<complexContent>
<extension
base="iris:resultType">
<sequence>
<element
name="serviceInstance"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="organizationName"
type="string"
minOccurs="0"
maxOccurs="1" />
<choice
minOccurs="0"
maxOccurs="3">
<element
name="registry">
<complexType/>
</element>
<element
name="registrar">
<complexType/>
</element>
<element
name="other">
<complexType/>
</element>
</choice>
<element
name="domain"
type="token"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
<complexType
name="registrationAuthorityType">
<complexContent>
<extension
base="iris:resultType">
<sequence>
<element
name="serviceInstance"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="organizationName"
type="string"
minOccurs="0"
maxOccurs="1" />
<choice
minOccurs="0"
maxOccurs="3">
<element
name="registry">
<complexType/>
</element>
<element
name="registrar">
<complexType/>
</element>
<element
name="other">
<complexType/>
</element>
</choice>
<element
name="domain"
type="token"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="registrationAuthority" type="dreg:registrationAuthorityType"
<element name=“registrationAuthority”type=“dreg:registrationAuthorityType”
substitutionGroup="iris:result" />
substitutionGroup="iris:result" />
<!-- -->
<!-- Privacy Label Types -->
<!-- -->
<!-- -->
<!-- Privacy Label Types -->
<!-- -->
<attributeGroup
name="privacyLabelAttributeGroup">
<attribute
name="private"
type="boolean" />
<attribute
name="denied"
type="boolean" />
<attribute
name="doNotRedistribute"
type="boolean" />
<attribute
name="specialAccess"
type="boolean" />
</attributeGroup>
<attributeGroup
name="privacyLabelAttributeGroup">
<attribute
name="private"
type="boolean" />
<attribute
name="denied"
type="boolean" />
<attribute
name="doNotRedistribute"
type="boolean" />
<attribute
name="specialAccess"
type="boolean" />
</attributeGroup>
<complexType
name="dateTimePrivacyType">
<simpleContent>
<extension
base="dateTime">
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
</extension>
</simpleContent>
</complexType>
<complexType
name="dateTimePrivacyType">
<simpleContent>
<extension
base="dateTime">
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
</extension>
</simpleContent>
</complexType>
<complexType
name="stringPrivacyType">
<simpleContent>
<extension
base="string">
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
</extension>
</simpleContent>
</complexType>
<complexType
name="stringPrivacyType">
<simpleContent>
<extension
base="string">
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
</extension>
</simpleContent>
</complexType>
<complexType
name="normalizedStringPrivacyType">
<simpleContent>
<extension
<complexType
name="normalizedStringPrivacyType">
<simpleContent>
<extension
base="normalizedString">
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
</extension>
</simpleContent>
</complexType>
base="normalizedString">
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
</extension>
</simpleContent>
</complexType>
<complexType
name="tokenPrivacyType">
<simpleContent>
<extension
base="token">
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
</extension>
</simpleContent>
</complexType>
<complexType
name="tokenPrivacyType">
<simpleContent>
<extension
base="token">
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
</extension>
</simpleContent>
</complexType>
<complexType
name="domainStatusType">
<sequence>
<element
name="appliedDate"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="description"
minOccurs="0"
maxOccurs="unbounded">
<complexType>
<simpleContent>
<extension
base="string">
<attribute
name="language"
type="language"
use="required" />
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
<attribute
name="scope"
type="string" />
<complexType
name="domainStatusType">
<sequence>
<element
name="appliedDate"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="description"
minOccurs="0"
maxOccurs="unbounded">
<complexType>
<simpleContent>
<extension
base="string">
<attribute
name="language"
type="language"
use="required" />
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
<attribute
name="scope"
type="string" />
</complexType>
</complexType>
<complexType
name="contactTypeType">
<sequence>
<element
name="description"
minOccurs="0"
maxOccurs="unbounded">
<complexType>
<simpleContent>
<extension
base="string">
<attribute
name="language"
type="language"
use="required" />
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
</complexType>
<complexType
name="contactTypeType">
<sequence>
<element
name="description"
minOccurs="0"
maxOccurs="unbounded">
<complexType>
<simpleContent>
<extension
base="string">
<attribute
name="language"
type="language"
use="required" />
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
<attributeGroup
ref="dreg:privacyLabelAttributeGroup" />
</complexType>
<!-- ========================================= -->
<!-- -->
<!-- Error Codes -->
<!-- -->
<!-- ========================================= -->
<!-- ========================================= -->
<!-- -->
<!-- Error Codes -->
<!-- -->
<!-- ========================================= -->
<!-- -->
<!-- Search Too Wide -->
<!-- -->
<!-- -->
<!-- Search Too Wide -->
<!-- -->
<element
name="searchTooWide"
type="iris:codeType"
substitutionGroup="iris:genericCode" />
<element
name="searchTooWide"
type="iris:codeType"
substitutionGroup="iris:genericCode" />
<!-- -->
<!-- Language Not Supported -->
<!-- -->
<!-- -->
<!-- Language Not Supported -->
<!-- -->
<complexType
name="languageNotSupportedType">
<complexContent>
<complexType
name="languageNotSupportedType">
<complexContent>
<extension
base="iris:codeType">
<sequence>
<element
name="unsupportedLanguage"
type="language"
minOccurs="1"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
<extension
base="iris:codeType">
<sequence>
<element
name="unsupportedLanguage"
type="language"
minOccurs="1"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="languageNotSupported"
type="dreg:languageNotSupportedType"
substitutionGroup="iris:genericCode" />
<element
name="languageNotSupported"
type="dreg:languageNotSupportedType"
substitutionGroup="iris:genericCode" />
</schema>
</schema>
Figure 5: dreg.xsd
图5:dreg.xsd
IRIS allows several extensions of the core capabilities. This section outlines extensions allowable by IRIS-BEEP [6].
IRIS允许对核心功能进行若干扩展。本节概述了IRIS-BEEP允许的扩展[6]。
This registry type uses the default message pattern described in IRIS-BEEP [6].
此注册表类型使用IRIS-BEEP[6]中描述的默认消息模式。
This registry type only uses the basic TLS server authentication method, as described in IRIS-BEEP [6].
此注册表类型仅使用基本TLS服务器身份验证方法，如IRIS-BEEP[6]中所述。
The application service label associated with this registry type MUST be "DREG1". This is the abbreviated form of the URN for this registry type: urn:ietf:params:xml:ns:dreg1.
与此注册表类型关联的应用程序服务标签必须为“DREG1”。这是此注册表类型的URN的缩写形式：URN:ietf:params:xml:ns:dreg1。
The bottom-up alternative resolution method MUST be identified as 'bottom' in IRIS URI's.
自下而上的备选解析方法必须在IRIS URI中标识为“bottom”。
The process for this resolution method differs from the direct-resolution method if the authority is only a domain name (i.e., without the port number). The process for this condition is as follows:
如果授权机构只是一个域名（即没有端口号），则此解析方法的过程与直接解析方法不同。这种情况的处理过程如下：
1. The IRIS [5] direct-resolution process is tried on the domain name (e.g., "example.com").
1. IRIS[5]直接解析过程在域名上进行了尝试（例如，“example.com”）。
2. If the direct-resolution process yields no server for which a connection can be made, then the leftmost label of the domain name is removed, and the first step is repeated again (e.g., "com").
2. 如果直接解析过程没有产生可以建立连接的服务器，则删除域名最左边的标签，并再次重复第一步（例如，“com”）。
3. If all the labels of the domain name are removed and no server connections have been made, then the DNS is queried for the address records corresponding to the original domain name, and the port used is the well-known port for the default protocol of IRIS.
3. 如果删除了域名的所有标签，并且没有进行服务器连接，则会在DNS中查询与原始域名对应的地址记录，并且使用的端口是IRIS默认协议的已知端口。
The top-down alternative resolution method MUST be identified as 'top' in IRIS URIs.
在IRIS URI中，自上而下的替代解析方法必须标识为“top”。
The process for this resolution method differs from the direct-resolution method if the authority is only a domain name (i.e., without the port number). The process for this condition is as follows:
如果授权机构只是一个域名（即没有端口号），则此解析方法的过程与直接解析方法不同。这种情况的处理过程如下：
1. The domain name is reduced to its rightmost label. This is always '.'.
1. 域名将缩减为其最右边的标签。这永远是“.”。
2. The IRIS [5] direct-resolution process is tried on the domain name.
2. IRIS[5]直接解析过程在域名上进行了尝试。
3. If the direct-resolution process yields no server for which a connection can be made, then the original label to the left of the rightmost label of the domain name is prepended, and the second step is repeated again (e.g., if ".", then "com"; if "com", then "example.com").
3. 如果直接解析过程没有产生可用于建立连接的服务器，则在域名最右边标签左侧的原始标签前面加上前缀，并再次重复第二步（例如，如果“.”，则为“com”；如果“com”，则为“example.com”）。
4. If all the labels of the original domain are present and no server connections have been made, then the DNS is queried for the address records corresponding to the original domain name, and the port used is the well-known port for the default protocol of IRIS.
4. 如果原始域的所有标签都存在，并且没有进行服务器连接，则会在DNS中查询与原始域名对应的地址记录，并且使用的端口是IRIS默认协议的已知端口。
Implementers should be aware of considerations for internationalization in IRIS [5].
实现者应该了解IRIS中国际化的注意事项[5]。
This document specifies the lookup of domain names, both the traditional ASCII form and the IDN form. In addition, the social data associated with contacts may also be non-ASCII and could contain virtually any Unicode character. The <language> element is provided in queries that have the potential to traverse such data. Clients should use this element to indicate the desired target languages to the server, and servers should use this element to better enable normalization and search processes (see [18]).
本文档规定了域名的查找，包括传统ASCII格式和IDN格式。除此之外，任何非Unicode字符也可能与非社交联系人相关联。<language>元素在有可能遍历此类数据的查询中提供。客户端应使用此元素向服务器指示所需的目标语言，服务器应使用此元素更好地启用规范化和搜索过程（请参见[18]）。
For clients needing to localize the data tags in this protocol, 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 that of elements containing date and time information.
对于需要在此协议中本地化数据标记的客户机，请注意，本地化只需要在XML元素和属性的名称上进行，包含日期和时间信息的元素除外。此注册表的模式设计为，除了包含日期和时间信息的元素的内容外，客户端无需解释本地化元素或属性的内容。
Clients should also make use of the <language> elements provided in many of the results. Results containing data that may be in Unicode are accompanied by these elements in order to aid better presentation of the data to the user.
客户还应该使用许多结果中提供的<language>元素。包含可能是Unicode格式的数据的结果会附带这些元素，以便更好地向用户展示数据。
The "dateTimePrivacyType" element type contains the XML Schema [3] data type "dateTime". The contents of this element MUST be specified by using the 'Z' indicator for Coordinated Universal Time (UTC).
“dateTimePrivacyType”元素类型包含XML模式[3]数据类型“dateTime”。必须使用协调世界时（UTC）的“Z”指示器指定此元素的内容。
This document makes use of a proposed XML namespace and schema registry specified in XML_URN [16]. Accordingly, the following registration information is provided for the IANA:
本文档使用了XML_URN[16]中指定的提议的XML名称空间和模式注册表。因此，为IANA提供了以下注册信息：
o URN/URI: * urn:ietf:params:xml:ns:dreg1 o Contact: * Andrew Newton <andy@hxr.us> * Marcos Sanz <sanz@denic.de> o XML: * The XML Schema specified in Section 4
o URN/URI:*URN:ietf:params:xml:ns:dreg1 o联系人：*安德鲁·牛顿<andy@hxr.us>*马科斯·桑兹<sanz@denic.de>o XML:*第4节中指定的XML模式
The following S-NAPTR application service label has been registered with IANA according to the IANA considerations defined in IRIS [5]:
根据IRIS[5]中定义的IANA注意事项，已向IANA注册了以下S-NAPTR应用程序服务标签：
DREG1
沉闷
The following BEEP Profile URI has been registered with IANA, in addition to the registration provided in IRIS-BEEP [6].
除了IRIS-BEEP[6]中提供的注册外，以下BEEP配置文件URI已向IANA注册。
http://iana.org/beep/iris1/dreg1
http://iana.org/beep/iris1/dreg1
This document lays out no new considerations for security precautions beyond that specified in IRIS [5].
除IRIS[5]中规定的安全预防措施外，本文件未对安全预防措施提出新的注意事项。
[1] World Wide Web Consortium, "Extensible Markup Language (XML) 1.0", W3C XML, February 1998, <http://www.w3.org/TR/1998/REC-xml-19980210>.
[1] 万维网联盟，“可扩展标记语言（XML）1.0”，W3C XML，1998年2月<http://www.w3.org/TR/1998/REC-xml-19980210>.
[2] World Wide Web Consortium, "Namespaces in XML", W3C XML Namespaces, January 1999, <http://www.w3.org/TR/1999/REC-xml-names-19990114>.
[2] 万维网联盟，“XML中的名称空间”，W3C XML名称空间，1999年1月<http://www.w3.org/TR/1999/REC-xml-names-19990114>.
[3] World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C XML Schema, October 2000, <http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/>.
[3] 万维网联盟，“XML模式第2部分：数据类型”，W3C XML模式，2000年10月<http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/>.
[4] World Wide Web Consortium, "XML Schema Part 1: Structures", W3C XML Schema, October 2000, <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/>.
[4] 万维网联盟，“XML模式第1部分：结构”，W3C XML模式，2000年10月<http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/>.
[5] Newton, A. and M. Sanz, "IRIS: The Internet Registry Information Service (IRIS) Core Protocol", RFC 3981, December 2005.
[5] Newton，A.和M.Sanz，“IRIS：互联网注册信息服务（IRIS）核心协议”，RFC 39812005年12月。
[6] Newton, A. and M. Sanz, "Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)", RFC 3983, December 2005.
[6] Newton，A.和M.Sanz，“通过块可扩展交换协议（BEEP）使用互联网注册信息服务（IRIS）”，RFC 3983，2005年12月。
[7] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6) Addressing Architecture", RFC 3513, April 2003.
[7] Hinden，R.和S.Deering，“互联网协议版本6（IPv6）寻址体系结构”，RFC 3513，2003年4月。
[8] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981.
[8] Postel，J.，“互联网协议”，STD 5，RFC 7911981年9月。
[9] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[9] Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 10351987年11月。
[10] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[10] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[11] International Organization for Standardization, "Codes for the representation of names of countries, 3rd edition", ISO Standard 3166, August 1988.
[11] 国际标准化组织，“国家名称表示代码，第3版”，ISO标准3166，1988年8月。
[12] Braden, R., "Requirements for Internet Hosts - Application and Support", STD 3, RFC 1123, October 1989.
[12] Braden，R.，“互联网主机的要求-应用和支持”，STD 3，RFC 1123，1989年10月。
[13] International Telecommunications Union, "The International Public Telecommunication Numbering Plan", ITU-T Recommendation E.164, 1991.
[13] 国际电信联盟，“国际公共电信编号计划”，ITU-T建议E.164，1991年。
[14] Faltstrom, P., Hoffman, P., and A. Costello, "Internationalizing Domain Names in Applications (IDNA)", RFC 3490, March 2003.
[14] Faltstrom，P.，Hoffman，P.，和A.Costello，“应用程序中的域名国际化（IDNA）”，RFC 34902003年3月。
[15] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)", RFC 3491, March 2003.
[15] Hoffman，P.和M.Blanchet，“Nameprep：国际化域名（IDN）的Stringprep配置文件”，RFC 34912003年3月。
[16] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[16] Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[17] Newton, A., "Cross Registry Internet Service Protocol (CRISP) Requirements", RFC 3707, February 2004.
[17] Newton，A.，“跨注册互联网服务协议（CRISP）要求”，RFC 3707，2004年2月。
URIs
URI
[18] <http://www.unicode.org/reports/tr15/>
[18] <http://www.unicode.org/reports/tr15/>
The examples in this section use the string "C:" to denote data sent by a client to a server and the string "S:" to denote data sent by a server to a client.
本节中的示例使用字符串“C:”表示客户机发送到服务器的数据，使用字符串“S:”表示服务器发送到客户机的数据。
The following is an example of an entity lookup in a dreg1 registry for the domain-name of 'example.com'. The response shows the ability to specify data as being withheld because it is private.
以下是在dreg1注册表中查找域名“example.com”的实体的示例。响应显示了将数据指定为被保留的能力，因为它是私有的。
C: <?xml version="1.0"?>
C: <request xmlns="urn:ietf:params:xml:ns:iris1"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
C:
C: <searchSet>
C:
C: <lookupEntity
C: registryType="urn:ietf:params:xml:ns:dreg1"
C: entityClass="domain-name"
C: entityName="example.com" />
C:
C: </searchSet>
C:
C: </request>
C: <?xml version="1.0"?>
C: <request xmlns="urn:ietf:params:xml:ns:iris1"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
C:
C: <searchSet>
C:
C: <lookupEntity
C: registryType="urn:ietf:params:xml:ns:dreg1"
C: entityClass="domain-name"
C: entityName="example.com" />
C:
C: </searchSet>
C:
C: </request>
S: <?xml version="1.0"?>
S: <iris:response xmlns:iris="urn:ietf:params:xml:ns:iris1"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
S:
S: <iris:resultSet>
S: <iris:answer>
S:
S: <domain xmlns="urn:ietf:params:xml:ns:dreg1"
S: authority="iana.org" registryType="dreg1"
S: entityClass="domain-handle" entityName="example-com-1">
S:
S: <domainName>example.com</domainName>
S: <domainHandle>tcs-com-1</domainHandle>
S:
S: <nameServer iris:referentType="host" authority="iana.org"
S: registryType="dreg1" entityClass="host-handle"
S: entityName="research7" />
S:
S: <nameServer iris:referentType="host" authority="iana.org"
S: registryType="dreg1" entityClass="host-handle"
S: entityName="nsol184" />
S: <?xml version="1.0"?>
S: <iris:response xmlns:iris="urn:ietf:params:xml:ns:iris1"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
S:
S: <iris:resultSet>
S: <iris:answer>
S:
S: <domain xmlns="urn:ietf:params:xml:ns:dreg1"
S: authority="iana.org" registryType="dreg1"
S: entityClass="domain-handle" entityName="example-com-1">
S:
S: <domainName>example.com</domainName>
S: <domainHandle>tcs-com-1</domainHandle>
S:
S: <nameServer iris:referentType="host" authority="iana.org"
S: registryType="dreg1" entityClass="host-handle"
S: entityName="research7" />
S:
S: <nameServer iris:referentType="host" authority="iana.org"
S: registryType="dreg1" entityClass="host-handle"
S: entityName="nsol184" />
S:
S: <technicalContact iris:referentType="contact"
S: authority="iana.org" registryType="dreg1"
S: entityClass="contact-handle" entityName="dbarton" />
S:
S: <status>
S: <assignedAndActive denied="true" />
S: </status>
S:
S: <registry iris:referentType="registrationAuthority"
S: authority="com" registryType="dreg1"
S: entityClass="contact-handle" entityName="VGRS" />
S:
S: <initialDelegationDateTime xsi:nil="true"/>
S:
S: <iris:seeAlso iris:referentType="ANY" authority="iana.org"
S: registryType="dreg1" entityClass="local"
S: entityName="notice" />
S:
S: </domain>
S:
S: </iris:answer>
S: </iris:resultSet>
S: </iris:response>
S:
S: <technicalContact iris:referentType="contact"
S: authority="iana.org" registryType="dreg1"
S: entityClass="contact-handle" entityName="dbarton" />
S:
S: <status>
S: <assignedAndActive denied="true" />
S: </status>
S:
S: <registry iris:referentType="registrationAuthority"
S: authority="com" registryType="dreg1"
S: entityClass="contact-handle" entityName="VGRS" />
S:
S: <initialDelegationDateTime xsi:nil="true"/>
S:
S: <iris:seeAlso iris:referentType="ANY" authority="iana.org"
S: registryType="dreg1" entityClass="local"
S: entityName="notice" />
S:
S: </domain>
S:
S: </iris:answer>
S: </iris:resultSet>
S: </iris:response>
Figure 6: Example 1
图6：示例1
The following is an example of an entity lookup in a dreg1 registry for the contact-handle of 'mak21'. The response shows the ability to specify data as being withheld because it is private.
以下是dreg1注册表中实体查找“mak21”联系人句柄的示例。响应显示了将数据指定为被保留的能力，因为它是私有的。
C: <?xml version="1.0"?>
C: <request xmlns="urn:ietf:params:xml:ns:iris1"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
C:
C: <searchSet>
C:
C: <lookupEntity
C: registryType="urn:ietf:params:xml:ns:dreg1"
C: entityClass="contact-handle"
C: entityName="mak21" />
C:
C: </searchSet>
C:
C: </request>
S: <?xml version="1.0"?>
C: <?xml version="1.0"?>
C: <request xmlns="urn:ietf:params:xml:ns:iris1"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
C:
C: <searchSet>
C:
C: <lookupEntity
C: registryType="urn:ietf:params:xml:ns:dreg1"
C: entityClass="contact-handle"
C: entityName="mak21" />
C:
C: </searchSet>
C:
C: </request>
S: <?xml version="1.0"?>
S: <response xmlns="urn:ietf:params:xml:ns:iris1"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
S:
S: <resultSet>
S: <answer>
S:
S: <contact xmlns="urn:ietf:params:xml:ns:dreg1"
S: authority="com" registryType="dreg1"
S: entityClass="contact-handle" entityName="mak21" >
S:
S: <contactHandle>mak21</contactHandle>
S:
S: <commonName>
S: Mark Kosters
S: </commonName>
S:
S: <organization>
S: VeriSign, Inc.
S: </organization>
S:
S: <eMail>markk@verisignlabs.com</eMail>
S:
S: <phone private="true" xsi:nil="true" />
S:
S: </contact>
S:
S: </answer>
S: </resultSet>
S:
S: </response>
S: <response xmlns="urn:ietf:params:xml:ns:iris1"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
S:
S: <resultSet>
S: <answer>
S:
S: <contact xmlns="urn:ietf:params:xml:ns:dreg1"
S: authority="com" registryType="dreg1"
S: entityClass="contact-handle" entityName="mak21" >
S:
S: <contactHandle>mak21</contactHandle>
S:
S: <commonName>
S: Mark Kosters
S: </commonName>
S:
S: <organization>
S: VeriSign, Inc.
S: </organization>
S:
S: <eMail>markk@verisignlabs.com</eMail>
S:
S: <phone private="true" xsi:nil="true" />
S:
S: </contact>
S:
S: </answer>
S: </resultSet>
S:
S: </response>
Figure 7: Example 2
图7：示例2
The following is an example of a domain search based on a registrant's name beginning with the string 'The Cobbler Shoppe'. This example also shows the use of bags.
下面是一个基于注册人姓名（以字符串“The Cobbler Shoppe”开头）的域搜索示例。此示例还显示了行李的使用。
C: <?xml version="1.0"?>
C: <request xmlns="urn:ietf:params:xml:ns:iris1"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
C:
C: <searchSet>
C:
C: <findDomainsByContact
C: xmlns="urn:ietf:params:xml:ns:dreg1" >
C: <baseDomain>com</baseDomain>
C: <?xml version="1.0"?>
C: <request xmlns="urn:ietf:params:xml:ns:iris1"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
C:
C: <searchSet>
C:
C: <findDomainsByContact
C: xmlns="urn:ietf:params:xml:ns:dreg1" >
C: <baseDomain>com</baseDomain>
C: <commonName>
C: <beginsWith>
C: The Cobbler Shoppe
C: </beginsWith>
C: </commonName>
C: <role>registrant</role>
C: </findDomainsByContact>
C:
C: </searchSet>
C:
C: </request>
C: <commonName>
C: <beginsWith>
C: The Cobbler Shoppe
C: </beginsWith>
C: </commonName>
C: <role>registrant</role>
C: </findDomainsByContact>
C:
C: </searchSet>
C:
C: </request>
S: <?xml version="1.0"?>
S: <response xmlns="urn:ietf:params:xml:ns:iris1"
S: xmlns:iris="urn:ietf:params:xml:ns:iris1"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
S:
S: <resultSet>
S: <answer>
S: <dreg:domain
S: xmlns="urn:ietf:params:xml:ns:dreg1"
S: xmlns:dreg="urn:ietf:params:xml:ns:dreg1"
S: authority="com" registryType="dreg1"
S: entityClass="domain-handle" entityName="tcs-com-1" >
S: <domainName>example.com</domainName>
S: <nameServer
S: iris:referentType="dreg:host"
S: authority="com" registryType="dreg1"
S: entityClass="host-handle" entityName="research7" />
S: <nameServer
S: iris:referentType="dreg:host"
S: authority="com" registryType="dreg1"
S: entityClass="host-handle" entityName="nsol184" />
S: <registrant
S: iris:referentType="dreg:contact"
S: authority="com" registryType="dreg1"
S: entityClass="contact-handle" entityName="beb140">
S: <iris:displayName language="en">
S: Bill Eckels
S: </iris:displayName>
S: </registrant>
S: <technicalContact
S: bagRef="x1"
S: iris:referentType="dreg:contact"
S: authority="com" registryType="dreg1"
S: entityClass="contact-handle" entityName="mak21">
S: <iris:displayName language="en">
S: Mark Kosters
S: <?xml version="1.0"?>
S: <response xmlns="urn:ietf:params:xml:ns:iris1"
S: xmlns:iris="urn:ietf:params:xml:ns:iris1"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
S:
S: <resultSet>
S: <answer>
S: <dreg:domain
S: xmlns="urn:ietf:params:xml:ns:dreg1"
S: xmlns:dreg="urn:ietf:params:xml:ns:dreg1"
S: authority="com" registryType="dreg1"
S: entityClass="domain-handle" entityName="tcs-com-1" >
S: <domainName>example.com</domainName>
S: <nameServer
S: iris:referentType="dreg:host"
S: authority="com" registryType="dreg1"
S: entityClass="host-handle" entityName="research7" />
S: <nameServer
S: iris:referentType="dreg:host"
S: authority="com" registryType="dreg1"
S: entityClass="host-handle" entityName="nsol184" />
S: <registrant
S: iris:referentType="dreg:contact"
S: authority="com" registryType="dreg1"
S: entityClass="contact-handle" entityName="beb140">
S: <iris:displayName language="en">
S: Bill Eckels
S: </iris:displayName>
S: </registrant>
S: <technicalContact
S: bagRef="x1"
S: iris:referentType="dreg:contact"
S: authority="com" registryType="dreg1"
S: entityClass="contact-handle" entityName="mak21">
S: <iris:displayName language="en">
S: Mark Kosters
S: </iris:displayName>
S: </technicalContact>
S: <status>
S: <transferPending denied="true" />
S: <assignedAndActive denied="true" />
S: </status>
S: <registry
S: iris:referentType="dreg:registrationAuthority"
S: authority="com" registryType="dreg1"
S: entityClass="local" entityName="VRSN"
S: hosting="false" />
S: <iris:seeAlso
S: iris:referentType="ANY"
S: authority="com" registryType="dreg1"
S: entityClass="local" entityName="notice" />
S: </dreg:domain>
S: </answer>
S: <additional>
S: <dreg:contact
S: xmlns="urn:ietf:params:xml:ns:dreg1"
S: xmlns:dreg="urn:ietf:params:xml:ns:dreg1"
S: authority="com" registryType="dreg1"
S: entityClass="contact-handle" entityName="beb140" >
S: <contactHandle>beb140</contactHandle>
S: <commonName>
S: Bill Eckels
S: </commonName>
S: <language>en</language>
S: <type>
S: <person>
S: <description language="en">
S: Bill sells shoes down by the sea shore.
S: </description>
S: <description language="de">
S: Rechnung verkauft Schuhe unten durch das Seeufer.
S: </description>
S: </person>
S: </type>
S: <organization>
S: The Cobbler Shoppe
S: </organization>
S: <eMail private="true" xsi:nil="true" />
S: <postalAddress>
S: <address>
S: 21 North Main Street
S: </address>
S: <city>
S: Britt
S: </iris:displayName>
S: </technicalContact>
S: <status>
S: <transferPending denied="true" />
S: <assignedAndActive denied="true" />
S: </status>
S: <registry
S: iris:referentType="dreg:registrationAuthority"
S: authority="com" registryType="dreg1"
S: entityClass="local" entityName="VRSN"
S: hosting="false" />
S: <iris:seeAlso
S: iris:referentType="ANY"
S: authority="com" registryType="dreg1"
S: entityClass="local" entityName="notice" />
S: </dreg:domain>
S: </answer>
S: <additional>
S: <dreg:contact
S: xmlns="urn:ietf:params:xml:ns:dreg1"
S: xmlns:dreg="urn:ietf:params:xml:ns:dreg1"
S: authority="com" registryType="dreg1"
S: entityClass="contact-handle" entityName="beb140" >
S: <contactHandle>beb140</contactHandle>
S: <commonName>
S: Bill Eckels
S: </commonName>
S: <language>en</language>
S: <type>
S: <person>
S: <description language="en">
S: Bill sells shoes down by the sea shore.
S: </description>
S: <description language="de">
S: Rechnung verkauft Schuhe unten durch das Seeufer.
S: </description>
S: </person>
S: </type>
S: <organization>
S: The Cobbler Shoppe
S: </organization>
S: <eMail private="true" xsi:nil="true" />
S: <postalAddress>
S: <address>
S: 21 North Main Street
S: </address>
S: <city>
S: Britt
S: </city>
S: <region>
S: IA
S: </region>
S: <postalCode>
S: 50423
S: </postalCode>
S: <country>
S: US
S: </country>
S: </postalAddress>
S: <phone>
S: +1.5158433521
S: </phone>
S: </dreg:contact>
S: <simpleEntity
S: authority="com" registryType="dreg1"
S: entityClass="local" entityName="notice" >
S: <property name="legal" language="en">
S: It is illegal to use information from this service
S: for the purposes of sending unsolicited bulk email.
S: </property>
S: </simpleEntity>
S: </additional>
S: </resultSet>
S: <bags>
S: <bag id="x1">
S: <simpleBag xmlns="http://example.com/">
S: AAAAB3NzaC1yc2EAAAABIwAAAIEA0ddD+W3Agl0Lel98G1r77fZ
S: c3nBl8CHdkmKuVGUy/ijmvdO5QxuSlU0R4BoCLZk/Sob22RApTn
S: T+ROMbXFQBrxGH08daAOy98WqpfAutWJri61JLpubIbaqhGyB48
S: Qt69V6OhYfFsJjvoNEOh1k2dgzXhSlzP3OMVSKRlBzGcO8=
S: </simpleBag>
S: </bag>
S: </bags>
S:
S: </response>
S: </city>
S: <region>
S: IA
S: </region>
S: <postalCode>
S: 50423
S: </postalCode>
S: <country>
S: US
S: </country>
S: </postalAddress>
S: <phone>
S: +1.5158433521
S: </phone>
S: </dreg:contact>
S: <simpleEntity
S: authority="com" registryType="dreg1"
S: entityClass="local" entityName="notice" >
S: <property name="legal" language="en">
S: It is illegal to use information from this service
S: for the purposes of sending unsolicited bulk email.
S: </property>
S: </simpleEntity>
S: </additional>
S: </resultSet>
S: <bags>
S: <bag id="x1">
S: <simpleBag xmlns="http://example.com/">
S: AAAAB3NzaC1yc2EAAAABIwAAAIEA0ddD+W3Agl0Lel98G1r77fZ
S: c3nBl8CHdkmKuVGUy/ijmvdO5QxuSlU0R4BoCLZk/Sob22RApTn
S: T+ROMbXFQBrxGH08daAOy98WqpfAutWJri61JLpubIbaqhGyB48
S: Qt69V6OhYfFsJjvoNEOh1k2dgzXhSlzP3OMVSKRlBzGcO8=
S: </simpleBag>
S: </bag>
S: </bags>
S:
S: </response>
Figure 8: Example 3
图8：示例3
The following is an example of serializing domain data.
下面是序列化域数据的示例。
This example shows the serialization of a domain, a host, and a referral.
此示例显示域、主机和引用的序列化。
<iris:serialization
xmlns:iris="urn:ietf:params:xml:ns:iris1"
xmlns:dreg="urn:ietf:params:xml:ns:dreg1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<iris:serialization
xmlns:iris="urn:ietf:params:xml:ns:iris1"
xmlns:dreg="urn:ietf:params:xml:ns:dreg1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<dreg:domain
xmlns="urn:ietf:params:xml:ns:dreg1"
authority="com" registryType="dreg1"
entityClass="domain-handle" entityName="tcs-com-1" >
<domainName>example.com</domainName>
<nameServer
iris:referentType="dreg:host"
authority="" registryType="dreg1"
entityClass="host-handle" entityName="research7" />
<nameServer
iris:referentType="dreg:host"
authority="" registryType="dreg1"
entityClass="host-handle" entityName="nsol184" />
<registrant
iris:referentType="dreg:contact"
authority="iana.org" registryType="dreg1"
entityClass="contact-handle" entityName="beb140" />
<technicalContact
iris:referentType="dreg:contact"
authority="net" registryType="dreg1"
entityClass="contact-handle"
entityName="mak21" >
<iris:displayName language="en">
IANA Administrator
</iris:displayName>
</technicalContact>
</dreg:domain>
<dreg:domain
xmlns="urn:ietf:params:xml:ns:dreg1"
authority="com" registryType="dreg1"
entityClass="domain-handle" entityName="tcs-com-1" >
<domainName>example.com</domainName>
<nameServer
iris:referentType="dreg:host"
authority="" registryType="dreg1"
entityClass="host-handle" entityName="research7" />
<nameServer
iris:referentType="dreg:host"
authority="" registryType="dreg1"
entityClass="host-handle" entityName="nsol184" />
<registrant
iris:referentType="dreg:contact"
authority="iana.org" registryType="dreg1"
entityClass="contact-handle" entityName="beb140" />
<technicalContact
iris:referentType="dreg:contact"
authority="net" registryType="dreg1"
entityClass="contact-handle"
entityName="mak21" >
<iris:displayName language="en">
IANA Administrator
</iris:displayName>
</technicalContact>
</dreg:domain>
<dreg:host
xmlns="urn:ietf:params:xml:ns:dreg1"
authority="com" registryType="dreg1"
entityClass="host-handle" entityName="nsol184" >
<hostHandle>nsol184</hostHandle>
<hostName>ns1.iana.org</hostName>
<ipV4Address>192.0.2.1</ipV4Address>
<hostContact
<dreg:host
xmlns="urn:ietf:params:xml:ns:dreg1"
authority="com" registryType="dreg1"
entityClass="host-handle" entityName="nsol184" >
<hostHandle>nsol184</hostHandle>
<hostName>ns1.iana.org</hostName>
<ipV4Address>192.0.2.1</ipV4Address>
<hostContact
iris:referentType="dreg:contact"
authority="com" registryType="dreg1"
entityClass="contact-handle"
entityName="dbarton" >
<iris:displayName language="en">
IANA Techie
</iris:displayName>
</hostContact>
</dreg:host>
iris:referentType="dreg:contact"
authority="com" registryType="dreg1"
entityClass="contact-handle"
entityName="dbarton" >
<iris:displayName language="en">
IANA Techie
</iris:displayName>
</hostContact>
</dreg:host>
<iris:serializedReferral>
<iris:source
authority="com" registryType="dreg1"
entityClass="contact-handle"
entityName="dbarton" />
<iris:searchContinuation
authority="net">
<iris:serializedReferral>
<iris:source
authority="com" registryType="dreg1"
entityClass="contact-handle"
entityName="dbarton" />
<iris:searchContinuation
authority="net">
<dreg:findRegistrarsByName>
<dreg:baseDomain>com</dreg:baseDomain>
</dreg:findRegistrarsByName>
<dreg:findRegistrarsByName>
<dreg:baseDomain>com</dreg:baseDomain>
</dreg:findRegistrarsByName>
</iris:searchContinuation>
</iris:serializedReferral>
</iris:searchContinuation>
</iris:serializedReferral>
</iris:serialization>
</iris:serialization>
Figure 9: dreg-serialization.xml
图9:dreg-serialization.xml
Many of the concepts concerning the use of SRV records for step-wise refinement toward finding authoritative servers and many of the details of result objects in this document were originally created by Eric A. Hall in his memos regarding the use of LDAP to satisfy the CRISP requirements. These concepts have contributed significantly to the development of this protocol.
本文档中关于使用SRV记录逐步优化以查找权威服务器的许多概念以及结果对象的许多细节最初是由Eric A.Hall在其关于使用LDAP以满足CRISP要求的备忘录中创建的。这些概念对本议定书的发展作出了重大贡献。
David Blacka made many technical contributions based on his work on IRIS implementation and his experienced judgment. He also contributed many editorial clarifications.
David Blacka基于他在IRIS实现方面的工作和经验丰富的判断力做出了许多技术贡献。他还提供了许多编辑澄清。
Authors' Addresses
作者地址
Andrew L. Newton VeriSign, Inc. 21345 Ridgetop Circle Sterling, VA 20166 USA
Andrew L.Newton VeriSign，Inc.美国弗吉尼亚州斯特林Ridgetop Circle 21345，邮编20166
Phone: +1 703 948 3382
EMail: anewton@verisignlabs.com; andy@hxr.us
URI: http://www.verisignlabs.com/
Phone: +1 703 948 3382
EMail: anewton@verisignlabs.com; andy@hxr.us
URI: http://www.verisignlabs.com/
Marcos Sanz DENIC eG Wiesenhuettenplatz 26 D-60329 Frankfurt Germany
Marcos Sanz DENIC eG Wiesenhuettenplatz 26 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 Internet Society (2005).
版权所有（C）互联网协会（2005年）。
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 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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 IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关IETF文件中权利的IETF程序信息，请参见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.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。