Network Working Group E. Gunduz
Request for Comments: 4698 RIPE NCC
Category: Standards Track A. Newton
VeriSign, Inc.
S. Kerr
RIPE NCC
October 2006
Network Working Group E. Gunduz
Request for Comments: 4698 RIPE NCC
Category: Standards Track A. Newton
VeriSign, Inc.
S. Kerr
RIPE NCC
October 2006
IRIS: An Address Registry (areg) Type for the Internet Registry Information Service
IRIS：Internet注册表信息服务的地址注册表（areg）类型
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 (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
This document describes an IRIS registry schema for IP address and Autonomous System Number 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 Internet Protocol address registries.
本文档描述了IP地址和自主系统号信息的IRIS注册表模式。该模式扩展了IRIS的必要查询和结果操作，为Internet协议地址注册所使用的语法和结果提供功能信息服务需求。
Table of Contents
目录
1. Introduction ....................................................3
2. Document Terminology ............................................3
3. Schema Description ..............................................3
3.1. Query Derivatives ..........................................4
3.1.1. <findContacts> Query ................................4
3.1.2. <findOrganizations> .................................4
3.1.3. <findAutonomousSystemsByName> and
<findNetworksByName> ................................5
3.1.4. <findNetworksByAddress> .............................5
3.1.5. <findNetworksByHandle> ..............................6
3.1.6. <findASByNumber> ....................................6
3.1.7. <findByContact> .....................................7
3.1.8. <findNetworksByNameServer> ..........................7
3.1.9. Contact Search Group ................................8
3.1.10. Common Search Group ................................8
3.1.11. Match Parameters ...................................8
3.2. Result Derivatives .........................................9
3.2.1. <ipv4Network> and <ipv6Network> Results .............9
3.2.2. <autonomousSystem> Result ..........................10
3.2.3. <contact> Result ...................................11
3.2.4. <organization> Result ..............................12
3.2.5. Contact References .................................12
3.2.6. Common Result Child Elements .......................13
3.3. Support for <iris:lookupEntity> ...........................13
4. Terminology for Nesting of Networks ............................14
5. Formal XML Syntax ..............................................18
6. BEEP Transport Compliance ......................................31
6.1. Message Pattern ...........................................31
6.2. Server Authentication .....................................31
7. URI Resolution .................................................31
7.1. Application Service Label .................................31
7.2. Operational Considerations ................................31
7.3. Top-Down Resolution .......................................31
8. Internationalization Considerations ............................32
9. IANA Considerations ............................................32
10. Security Considerations .......................................32
11. References ....................................................33
11.1. Normative References .....................................33
11.2. Informative References ...................................33
Appendix A. Privacy Considerations ................................34
Appendix B. Example Requests and Responses ........................34
B.1. Example 1 .................................................34
B.2. Example 2 .................................................36
Appendix C. Specificity Examples ..................................39
Appendix D. Contributors ..........................................46
Appendix E. Acknowledgements ......................................46
1. Introduction ....................................................3
2. Document Terminology ............................................3
3. Schema Description ..............................................3
3.1. Query Derivatives ..........................................4
3.1.1. <findContacts> Query ................................4
3.1.2. <findOrganizations> .................................4
3.1.3. <findAutonomousSystemsByName> and
<findNetworksByName> ................................5
3.1.4. <findNetworksByAddress> .............................5
3.1.5. <findNetworksByHandle> ..............................6
3.1.6. <findASByNumber> ....................................6
3.1.7. <findByContact> .....................................7
3.1.8. <findNetworksByNameServer> ..........................7
3.1.9. Contact Search Group ................................8
3.1.10. Common Search Group ................................8
3.1.11. Match Parameters ...................................8
3.2. Result Derivatives .........................................9
3.2.1. <ipv4Network> and <ipv6Network> Results .............9
3.2.2. <autonomousSystem> Result ..........................10
3.2.3. <contact> Result ...................................11
3.2.4. <organization> Result ..............................12
3.2.5. Contact References .................................12
3.2.6. Common Result Child Elements .......................13
3.3. Support for <iris:lookupEntity> ...........................13
4. Terminology for Nesting of Networks ............................14
5. Formal XML Syntax ..............................................18
6. BEEP Transport Compliance ......................................31
6.1. Message Pattern ...........................................31
6.2. Server Authentication .....................................31
7. URI Resolution .................................................31
7.1. Application Service Label .................................31
7.2. Operational Considerations ................................31
7.3. Top-Down Resolution .......................................31
8. Internationalization Considerations ............................32
9. IANA Considerations ............................................32
10. Security Considerations .......................................32
11. References ....................................................33
11.1. Normative References .....................................33
11.2. Informative References ...................................33
Appendix A. Privacy Considerations ................................34
Appendix B. Example Requests and Responses ........................34
B.1. Example 1 .................................................34
B.2. Example 2 .................................................36
Appendix C. Specificity Examples ..................................39
Appendix D. Contributors ..........................................46
Appendix E. Acknowledgements ......................................46
An Internet address registry stores information about:
Internet地址注册表存储有关以下内容的信息：
o address ranges
o 地址范围
o autonomous system number ranges
o 自治系统编号范围
o associated contacts and organizations
o 联系联系人和组织
o name servers
o 名称服务器
This information is interrelated, and Internet address registries store this information and the information's interrelationships in a manner befitting the needs of each Internet address registry and its constituents. This document specifies a method for accessing and retrieving this information in a common XML format.
这些信息是相互关联的，Internet地址注册中心以适合每个Internet地址注册中心及其组成部分的需要的方式存储这些信息和信息的相互关系。本文档指定了以通用XML格式访问和检索此信息的方法。
This document describes an IRIS namespace for Internet address registries using an XML Schema [8] derived from and using the IRIS [2] schema. This schema and registry type are provided to demonstrate the extensibility of the IRIS framework beyond the use of domains, a criteria defined in CRISP [4].
本文档描述了使用从IRIS[2]模式派生并使用该模式的XML模式[8]的Internet地址注册表的IRIS命名空间。提供此模式和注册表类型是为了证明IRIS框架的可扩展性，超出了CRISP[4]中定义的域的使用范围。
The schema given is this document is specified using the Extensible Markup Language (XML) 1.0 as described in XML [5], XML Schema notation as described in XML_SD [7] and XML_SS [8], and XML Namespaces as described in XML_NS [6].
本文给出的模式是使用XML[5]中所述的可扩展标记语言（XML）1.0、XML_SD[7]和XML_SS[8]中所述的XML模式表示法以及XML_NS[6]中所述的XML名称空间指定的。
Examples of client/server XML exchanges with this registry type are available in Appendix B.
附录B中提供了这种注册表类型的客户机/服务器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 RFC 2119 [1].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[1]中所述进行解释。
IRIS requires the derivation of both query and result elements by a registry schema. Descriptions for these follow.
IRIS需要通过注册表模式派生查询元素和结果元素。以下是对这些问题的描述。
The descriptions contained within this section refer to XML elements and attributes and their relation to the exchange of data within the protocol. These descriptions also contain specifications outside the scope of the formal XML syntax. Therefore, this section will use terms defined by RFC 2119 [1] to describe the specification outside
本节中包含的描述涉及XML元素和属性及其与协议内数据交换的关系。这些描述还包含正式XML语法范围之外的规范。因此，本节将使用RFC 2119[1]定义的术语来描述外部规范
the scope of the formal XML syntax. While reading this section, please reference Section 5 for needed details on the formal XML syntax.
正式XML语法的范围。在阅读本节时，请参考第5节，以了解有关正式XML语法的必要详细信息。
<findContacts> searches for contacts given search constraints.
<findContacts>搜索给定搜索约束的联系人。
The allowable search fields are handled by one of the elements in the "contactSearchGroup" (see Section 3.1.9) or the element <organizationId>. The <organizationId> element constrains the query based on the organization ID (handle) associated with contacts. This element is an "exactMatchParameter" (see Section 3.1.11).
允许的搜索字段由“contactSearchGroup”（参见第3.1.9节）中的一个元素或元素<organizationId>处理。元素根据与联系人关联的组织ID（句柄）约束查询。该元素为“exactMatchParameter”（见第3.1.11节）。
This query also provides optional <language> elements containing language tags. Clients MAY use these elements to give a hint about the natural language(s) of the affected element. Servers MAY use this information in processing the query, such as tailoring normalization routines to aid in more effective searches.
此查询还提供包含语言标记的可选<language>元素。客户端可以使用这些元素来提示受影响元素的自然语言。服务器可以在处理查询时使用此信息，例如定制规范化例程以帮助进行更有效的搜索。
The client SHOULD pass the names unchanged to the server, and the implementation of the server decides if the search is case sensitive or not.
客户端应将名称不变地传递给服务器，服务器的实现决定搜索是否区分大小写。
<findOrganizations> searches for organizations given search constraints.
<findOrganizations>搜索给定搜索约束的组织。
The allowable search fields are handled by one of the elements in the "commonSearchGroup" (see Section 3.1.10) or the element <organizationName>. This element is an "exactOrPartialMatchParameter" (see Section 3.1.11).
允许的搜索字段由“commonSearchGroup”（参见第3.1.10节）中的一个元素或元素<organizationName>处理。该元件为“ExactorPartialMachParameter”（见第3.1.11节）。
This query also provides optional <language> elements containing language tags. Clients MAY use these elements to give a hint about the natural language(s) of the affected element. Servers MAY use this information in processing the query, such as tailoring normalization routines to aid in more effective searches.
此查询还提供包含语言标记的可选<language>元素。客户端可以使用这些元素来提示受影响元素的自然语言。服务器可以在处理查询时使用此信息，例如定制规范化例程以帮助进行更有效的搜索。
The client SHOULD pass the names unchanged to the server, and the implementation of the server decides if the search is case sensitive or not.
客户端应将名称不变地传递给服务器，服务器的实现决定搜索是否区分大小写。
The <findAutonomousSystemsByName> and <findNetworksByName> elements allow searches by name of autonomous systems and networks, respectively. Both have the same format.
<findAutonomousSystemsByName>和<findNetworksByName>元素分别允许按自治系统和网络的名称进行搜索。两者的格式相同。
The child element <name> is an "exactOrPartialMatchParameter" (see Section 3.1.11).
子元素<name>是“exactOrPartialMatchParameter”（见第3.1.11节）。
This query also provides optional <language> elements containing language tags. Clients MAY use these elements to give a hint about the natural language(s) of the affected element. Servers MAY use this information in processing the query, such as tailoring normalization routines to aid in more effective searches.
此查询还提供包含语言标记的可选<language>元素。客户端可以使用这些元素来提示受影响元素的自然语言。服务器可以在处理查询时使用此信息，例如定制规范化例程以帮助进行更有效的搜索。
The client SHOULD pass the names unchanged to the server, and the implementation of the server decides if the search is case sensitive or not.
客户端应将名称不变地传递给服务器，服务器的实现决定搜索是否区分大小写。
The <findNetworksByAddress> element is a query for a network given a related IP address or IP address range. It has the following child elements:
元素是给定相关IP地址或IP地址范围的网络查询。它具有以下子元素：
o <ipv4Address> - has a child <start> element containing the starting IPv4 address of the network and an optional child of <end> containing the ending IPv4 address of the network. Clients MUST convert any short-form notation to the fully-qualified notation.
o <ipv4Address>-有一个子<start>元素包含网络的起始IPv4地址，还有一个子<end>可选，包含网络的终止IPv4地址。客户机必须将任何简短形式的表示法转换为完全限定的表示法。
o <ipv6Address> - same as <ipv4Address>, but the child addresses contain IPv6 addresses. Clients MUST convert any short-form notation to the fully-qualified notation.
o <ipv6Address>-与<ipv4Address>相同，但子地址包含IPv6地址。客户机必须将任何简短形式的表示法转换为完全限定的表示法。
o <specificity> - determines the network specificity for the search (see Section 4). Valid values are "exact-match", "all-less-specific", "one-level-less-specific", "all-more-specific", and "one-level-more-specific". This element may have the optional attribute 'allowEquivalences'. When it is set to "true", the result set should include networks with equivalent starting and ending addresses. The default value for 'allowEquivalences' is "false".
o <specificity>-确定搜索的网络特异性（参见第4节）。有效值为“精确匹配”、“所有不太具体”、“一级不太具体”、“所有更具体”和“一级更具体”。此元素可能具有可选属性“allowEquivalences”。当设置为“true”时，结果集应包括具有等效起始地址和结束地址的网络。“allowEquivalences”的默认值为“false”。
The results from this query MUST be either <ipv4Network> or <ipv6Network> results. More than one network result MAY be returned.
此查询的结果必须是<ipv4Network>或<ipv6Network>结果。可以返回多个网络结果。
The <findNetworksByHandle> element is a query for a network given a the handle of a related network. It has the following child elements:
<findNetworksByHandle>元素是对给定相关网络句柄的网络的查询。它具有以下子元素：
o <networkHandle> - specifies the network handle.
o <networkHandle>-指定网络句柄。
o <specificity> - determines the network specificity for the search (see Section 4). Valid values are "all-less-specifics", "one-level-less-specifics", "all-more-specifics", and "one-level-more-specifics".
o <specificity>-确定搜索的网络特异性（参见第4节）。有效值为“所有较少的细节”、“一级较少的细节”、“所有较多的细节”和“一级较多的细节”。
The results from this query MUST be either <ipv4Network> or <ipv6Network> results. More than one network result MAY be returned.
此查询的结果必须是<ipv4Network>或<ipv6Network>结果。可以返回多个网络结果。
This query could be used to discover the parentage relationships between networks that have the same starting and ending addresses.
此查询可用于发现具有相同起始地址和结束地址的网络之间的亲子关系。
The client SHOULD pass handles unchanged to the server, and the implementation of the server decides if the search is case sensitive or not.
客户机应该将句柄不变地传递给服务器，服务器的实现决定搜索是否区分大小写。
The <findASByNumber> element allows a search for autonomous systems given an autonomous system number (ASN) range. It has the following child elements:
<findASByNumber>元素允许搜索给定自治系统编号（ASN）范围的自治系统。它具有以下子元素：
o <asNumberStart> - specifies the start of the ASN range.
o <asNumberStart>-指定ASN范围的开始。
o <asNumberEnd> - specifies the end of the ASN range.
o <ASNumberRend>-指定ASN范围的结束。
o <specificity> - determines the range specificity for the search (see Section 4). Valid values are "exact-match", "all-less-specific", "one-level-less-specific", "all-more-specific", and "one-level-more-specific". This element may have the optional attribute 'allowEquivalences'. When it is set to "true", the result set should include ranges with equivalent starting and ending numbers. The default value for 'allowEquivalences' is "false".
o <特异性>-确定搜索的范围特异性（见第4节）。有效值为“精确匹配”、“所有不太具体”、“一级不太具体”、“所有更具体”和“一级更具体”。此元素可能具有可选属性“allowEquivalences”。当设置为“true”时，结果集应包括具有等效起始和结束数字的范围。“allowEquivalences”的默认值为“false”。
The results from this query MUST be <autonomousSystem> results. More than one result MAY be returned.
此查询的结果必须是<autonomousSystem>结果。可以返回多个结果。
The <findByContact> element allows a search for autonomous systems, IP networks, and organizations on fields associated with that entity's contact. The optional search element <returnedResultType> MUST restrict the results to autonomous systems, IPv4 networks, IPv6 networks, or organizations using the values 'returnASs', 'returnIPv4Networks', 'returnIPv6Networks', and 'returnOrganizations', respectively.
<findByContact>元素允许在与该实体的联系人相关联的字段上搜索自治系统、IP网络和组织。可选搜索元素<returnedResultType>必须将结果限制为自治系统、IPv4网络、IPv6网络或分别使用值“returnASs”、“returnIPv4Networks”、“returnIPv6Networks”和“returnOrganizations”的组织。
The allowable search fields are handled with either the <contactHandle> element or one of the elements in the "contactSearchGroup" (see Section 3.1.9). The <contactHandle> element allows for the entities to be selected based on the contact having the specified contact handle, and it is an "exactMatchParameter" type (see Section 3.1.11). The client SHOULD pass these search fields unchanged to the server, and the implementation of the server decides if the search is case sensitive or not.
允许的搜索字段由<contactHandle>元素或“contactSearchGroup”中的一个元素处理（见第3.1.9节）。<contactHandle>元素允许根据具有指定触点手柄的触点选择实体，并且是“exactMatchParameter”类型（见第3.1.11节）。客户端应该将这些搜索字段原封不动地传递给服务器，服务器的实现决定搜索是否区分大小写。
The query MAY also be constrained further using the optional <role> element. The contents of this element signify the role the contact has with the entity. The allowable values for this element are "adminContact", "nocContact", "techContact", "abuseContact", and "otherContact".
还可以使用可选的<role>元素进一步约束查询。此元素的内容表示联系人与实体的角色。此元素的允许值为“adminContact”、“nocContact”、“techContact”、“abuseContact”和“otherContact”。
This query also provides optional <language> elements containing language tags. Clients MAY use these elements to give a hint about the natural language(s) of the affected element. Servers MAY use this information in processing the query, such as tailoring normalization routines to aid in more effective searches.
此查询还提供包含语言标记的可选<language>元素。客户端可以使用这些元素来提示受影响元素的自然语言。服务器可以在处理查询时使用此信息，例如定制规范化例程以帮助进行更有效的搜索。
The results from this query MUST be <ipv4Network> results, <ipv6Network> results, <autonomousSystem> results, or <organization> results. More than one result MAY be returned, and the results MAY be of mixed types.
此查询的结果必须是<ipv4Network>结果、<ipv6Network>结果、<autonomousSystem>结果或<organization>结果。可以返回多个结果，并且结果可能是混合类型。
The <findNetworksByNameServer> element allows a search for IP networks based on their associated name servers. The <nameServer> element contains the fully qualified domain name of the name server. The optional search element <returnedResultType> MUST restrict the results to IPv4 networks or IPv6 networks using the values 'returnIPv4Networks' and 'returnIPv6Networks', respectively.
<findNetworksByNameServer>元素允许基于关联的名称服务器搜索IP网络。<nameServer>元素包含名称服务器的完全限定域名。可选搜索元素<returnedResultType>必须分别使用值“returnIPv4Networks”和“returnIPv6Networks”将结果限制为IPv4网络或IPv6网络。
The results from this query MUST be <ipv4Network> or <ipv6Network> results. More than one result MAY be returned, and the results MAY be of mixed types.
此查询的结果必须是<ipv4Network>或<ipv6Network>结果。可以返回多个结果，并且结果可能是混合类型。
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. This constraint is an "exactOrPartialMatchParameter" (see Section 3.1.11).
<commonName>允许根据联系人的常用名称约束查询。该约束为“ExactorPartialMachParameter”（见第3.1.11节）。
This group also contains all the members of the "commonSearchGroup" (see Section 3.1.10).
该组还包含“commonSearchGroup”的所有成员（见第3.1.10节）。
Some of the queries above have similar query constraints for searching on contacts. This section describes those common parameters.
上面的一些查询在搜索联系人时具有类似的查询约束。本节介绍这些常用参数。
<eMail> constrains the query based on the e-mail address of the contact. This constraint is a "domainResource" type (see Section 3.1.11).
<e-mail>根据联系人的电子邮件地址进行查询。该约束为“域资源”类型（见第3.1.11节）。
The <city>, <region>, <country>, and <postalCode> elements restrict the scope of the query based on the city, region, country, or postal code of the contact, respectively. These constraints are all "exactMatchParameter" types (see Section 3.1.11). The contents of <country> MUST be compliant with ISO 3166 [9] two-character country codes.
<city>、<region>、<country>和<postalCode>元素分别基于联系人的城市、地区、国家或邮政编码限制查询范围。这些约束均为“exactMatchParameter”类型（见第3.1.11节）。<country>的内容必须符合ISO 3166[9]两个字符的国家代码。
Some of the queries above have constraints that match strings using matching parameters. This section describes those matching parameters.
上面的一些查询具有使用匹配参数匹配字符串的约束。本节介绍这些匹配参数。
Elements of type "exactMatchParameter" will have one child element of <exactMatch>. The contents of this child element are to match exactly in the use of the constraint.
“exactMatchParameter”类型的元素将有一个子元素<exactMatch>。此子元素的内容将在约束的使用中完全匹配。
Elements of type "partialMatchParameter" will have either a
<beginsWith> child element with an optional <endsWith> child element
or an <endsWith> child element. The content of the <beginsWith>
Elements of type "partialMatchParameter" will have either a
<beginsWith> child element with an optional <endsWith> child element
or an <endsWith> child element. The content of the <beginsWith>
element specifies the beginning character sequence for the constraint. The content of the <endsWith> element specifies the ending character sequence for the constraint.
元素指定约束的起始字符序列。元素的内容指定约束的结束字符序列。
Elements of type "exactOrPartialMatchParameter" can have either the child element allowed with the "exactMatchParameter" type or the child elements allowed with the "partialMatchParameter" type.
“exactOrPartialMatchParameter”类型的元素可以具有“exactMatchParameter”类型允许的子元素，也可以具有“partialMatchParameter”类型允许的子元素。
Elements of type "domainResource" can have either the child element allowed with the "exactMatchParameter" type or a child element of <inDomain>. This parameter type is meant to match email, SIP, Extensible Messaging and Presence Protocol (XMPP), and other types of "user@domain" addresses. When this parameter is specified with the <exactMatch> child element, the constraint is based on the whole email address. When this parameter is specified with the <inDomain> child element, the constraint is based on any email address within the domain given. The <inDomain> MUST only contain a valid domain name (i.e., no '@' symbol), and the matching SHOULD take place only on the domain given (i.e., no partial matches with respect to substrings or parent domains).
类型为“domainResource”的元素可以具有“exactMatchParameter”类型所允许的子元素，也可以具有<inDomain>的子元素。此参数类型用于匹配电子邮件、SIP、可扩展消息和状态协议（XMPP）以及其他类型的“user@domain“地址。当使用<exactMatch>子元素指定此参数时，约束基于整个电子邮件地址。当使用<inDomain>子元素指定此参数时，约束基于给定域中的任何电子邮件地址。<inDomain>必须只包含一个有效的域名（即，没有'@'符号），并且匹配只能在给定的域上进行（即，没有关于子字符串或父域的部分匹配）。
The <ipv4Network> and <ipv6Network> share a common definition of 'ipNetworkType'. It has the following child elements:
<ipv4Network>和<ipv6Network>共享“ipNetworkType”的共同定义。它具有以下子元素：
o <networkHandle> contains the registry-unique assigned handle for this network.
o <networkHandle>包含为此网络分配的注册表唯一句柄。
o <name> contains a human-friendly name for the network.
o <name>包含网络的人性化名称。
o <startAddress> contains the first IP address of the network.
o <startAddress>包含网络的第一个IP地址。
o <endAddress> contains the last IP address of the network.
o <endAddress>包含网络的最后一个IP地址。
o <networkType> contains a string denoting the type of network.
o <networkType>包含一个表示网络类型的字符串。
o <networkTypeInfo> is an entity reference to a definition of the values explained in a plain natural language. The referent MUST be a <simpleEntity> as defined by [2].
o <networkTypeInfo>是一个实体引用，它引用了用普通自然语言解释的值的定义。参照物必须是[2]定义的<simpleEntity>。
o <nameServer> contains the domain name of a nameserver responsible for reverse-DNS mapping for this network.
o <nameServer>包含负责此网络反向DNS映射的名称服务器的域名。
o <organization> contains an entity reference to the organization assigned this network. The referent MUST be an <organization> (Section 3.2.4) result.
o <organization>包含分配给此网络的组织的实体引用。引用对象必须是<组织>（第3.2.4节）结果。
o One of the following:
o 以下其中一项：
* <parent> contains an entity reference to the parent network of this network. The referent MUST be an <ipv4Network> (Section 3.2.1) result if this reference is a child of <ipv4Network>. The referent MUST be an <ipv6Network> (Section 3.2.1) result if this reference is a child of <ipv6Network>.
* <parent>包含对此网络的父网络的实体引用。如果引用是<ipv4Network>的子级，则引用对象必须是<ipv4Network>（第3.2.1节）结果。如果引用是<ipv6Network>的子对象，则引用对象必须是<ipv6Network>（第3.2.1节）结果。
* <noParent> signifies that this network has no parent network.
* <noParent>表示此网络没有父网络。
o Contact references (see Section 3.2.5).
o 联系参考（见第3.2.5节）。
o Common child elements (see Section 3.2.6).
o 通用子元素（见第3.2.6节）。
The <autonomousSystem> element represents an assigned or allocated autonomous system number range. It has the following children:
<autonomousSystem>元素表示分配或分配的自治系统编号范围。它有以下子项：
o <asHandle> contains a registry-unique assigned handle for this autonomous system number range.
o <asHandle>包含此自主系统编号范围的注册表唯一分配句柄。
o <asNumberStart> contains an integer indicating the starting number for the autonomous system number range.
o <asNumberStart>包含一个整数，指示自治系统编号范围的起始编号。
o <asNumberEnd> contains an integer indicating the ending number for the autonomous system number range.
o <AsNumberRend>包含一个整数，指示自治系统编号范围的结束编号。
o <name> contains a human-readable name for this autonomous system.
o <name>包含此自治系统的可读名称。
o <organization> contains an entity reference to the organization assigned or allocated this autonomous system number range. The referent MUST be an <organization> (Section 3.2.4) result.
o <organization>包含分配或分配给该自治系统编号范围的组织的实体引用。引用对象必须是<组织>（第3.2.4节）结果。
o One of the following:
o 以下其中一项：
* <parent> contains an entity reference to the parent autonomous system of this autonomous system. The referent MUST be an <autonomousSystem> (Section 3.2.2) result.
* <parent>包含对此自治系统的父自治系统的实体引用。引用对象必须是<autonomousSystem>（第3.2.2节）结果。
* <noParent> signifies that this autonomous system has no parent autonomous system.
* <noParent>表示此自治系统没有父自治系统。
o Contact references (see Section 3.2.5).
o 联系参考（见第3.2.5节）。
o Common child elements (see Section 3.2.6).
o 通用子元素（见第3.2.6节）。
The <contact> element represents the registration of a point of contact. It has the following child elements:
<contact>元素表示接触点的注册。它具有以下子元素：
o <contactHandle> contains the registry-unique assigned handle for this contact.
o <contactHandle>包含为此联系人分配的注册表唯一句柄。
o <commonName> specifies the name of the contact.
o <commonName>指定联系人的名称。
o <eMail> contains the email address for this contact.
o <eMail>包含此联系人的电子邮件地址。
o <sip> contains the sip address for this contact.
o <sip>包含此联系人的sip地址。
o <organization> contains an entity reference to the organization associated with this contact. The referent MUST be an <organization> (Section 3.2.4) result.
o <organization>包含对与此联系人关联的组织的实体引用。引用对象必须是<组织>（第3.2.4节）结果。
o <postalAddress> contains information for reaching the contact via postal mail. It is composed of the following child elements:
o <postalAddress>包含通过邮政邮件联系联系人的信息。它由以下子元素组成：
* <address> contains the address for this contact.
* <address>包含此联系人的地址。
* <city> contains the city where this contact is located.
* <city>包含此联系人所在的城市。
* <region> contains the national region where this contact is located.
* <region>包含此联系人所在的国家地区。
* <postalCode> contains the postal code where this contact is located.
* <postalCode>包含此联系人所在的邮政编码。
* <country> contains the country code where this contact is located. This MUST be compliant with ISO 3166 [9] two-character country codes.
* <country>包含此联系人所在的国家代码。这必须符合ISO 3166[9]两个字符的国家代码。
o <phone> contains child elements describing the phone number of the contact. The child elements are <number>, <extension>, and <type>.
o <phone>包含描述联系人电话号码的子元素。子元素是<number>、<extension>和<type>。
o Common child elements (see Section 3.2.6).
o 通用子元素（见第3.2.6节）。
The <organization> element represents an organization. It has the following child elements:
<organization>元素表示一个组织。它具有以下子元素：
o <name> contains the name of the organization.
o <name>包含组织的名称。
o <id> contains a registry-unique identifier for this organization.
o <id>包含此组织的注册表唯一标识符。
o <eMail> contains the email address for this organization.
o <eMail>包含此组织的电子邮件地址。
o <postalAddress> contains a information for reaching the organization via postal mail. It is composed of the following child elements:
o <postalAddress>包含通过邮政邮件到达组织的信息。它由以下子元素组成：
* <address> contains the address for this organization.
* <address>包含此组织的地址。
* <city> contains the city where this organization is located.
* <city>包含此组织所在的城市。
* <region> contains the national region where this organization is located.
* <region>包含该组织所在的国家区域。
* <postalCode> contains the postal code where this organization is located.
* <postalCode>包含此组织所在的邮政编码。
* <country> contains the country code where this organization is located. This MUST be compliant with ISO 3166 [9] two-character country codes.
* <country>包含此组织所在的国家代码。这必须符合ISO 3166[9]两个字符的国家代码。
o <phone> contains child elements describing the phone number of the contact. The child elements are <number>, <extension>, and <type>.
o <phone>包含描述联系人电话号码的子元素。子元素是<number>、<extension>和<type>。
o Contact references (see Section 3.2.5).
o 联系参考（见第3.2.5节）。
o Common child elements (see Section 3.2.6).
o 通用子元素（见第3.2.6节）。
The registry schema defined in Section 5 normalizes out a group of elements used to reference contacts. This group is used by many of the result types for this registry. The group has the following elements, each of which may appear as many times as needed. The referent of each MUST be <contact> (Section 3.2.3) results.
第5节中定义的注册表模式规范化了一组用于引用联系人的元素。此注册表的许多结果类型都使用此组。该组具有以下元素，每个元素可以根据需要多次出现。每个结果的参照物必须是<contact>（第3.2.3节）结果。
o <adminContact>
o <adminContact>
o <techContact>
o <techContact>
o <nocContact>
o <nocontact>
o <abuseContact>
o <abuseContact>
o <otherContact>
o <otherContact>
The registry schema defined in Section 5 normalizes out a group of common elements that are used most among the result types. The group has the following elements:
第5节中定义的注册表模式规范化了一组在结果类型中使用最多的公共元素。该集团具有以下要素：
o <numberResourceRegistry> contains an entity reference to the number resource registry of record. The referent MUST be an <organization> (Section 3.2.4) result.
o <numberResourceRegistry>包含对记录的数字资源注册表的实体引用。引用对象必须是<组织>（第3.2.4节）结果。
o <registrationDate> contains the date of first registration.
o <registrationDate>包含首次注册的日期。
o <lastUpdatedDate> contains the date when the registration was last updated.
o <LastUpdateDate>包含上次更新注册的日期。
o The <iris:seeAlso> element contains an entity reference specifying an entity that is indirectly associated with this result object. This element can be used for comments and remarks.
o 元素包含一个实体引用，指定一个与这个结果对象间接关联的实体。此元素可用于注释和备注。
The following types of entity classes are recognized by the <lookupEntity> query of IRIS for this registry:
此注册表的IRIS的<lookupEntity>查询可识别以下类型的实体类：
o ipv4-handle - a registry-unique identifier specifying an IPv4 network. Queries with these names will yield a <ipv4Network> result.
o ipv4句柄-指定ipv4网络的注册表唯一标识符。使用这些名称的查询将产生<ipv4Network>结果。
o ipv6-handle - a registry-unique identifier specifying an IPv6 network. Queries with these names will yield a <ipv6Network> result.
o ipv6句柄-指定ipv6网络的注册表唯一标识符。使用这些名称的查询将产生<ipv6Network>结果。
o as-handle - a registry-unique identifier specifying an autonomous system. It yields a result of <autonomousSystem>.
o as handle—指定自治系统的注册表唯一标识符。它产生一个<autonomousSystem>的结果。
o contact-handle - a registry-unique identifier of a contact. Yields a result of <contact>.
o 联系人句柄-联系人的注册表唯一标识符。产生<contact>的结果。
o organization-id - a registry-unique identifier of an organization. Yields a result of <organization>.
o 组织id—组织的注册表唯一标识符。产生<organization>的结果。
o The entity names of these entity classes are case insensitive.
o 这些实体类的实体名称不区分大小写。
The following terms are defined for describing the nesting of IP networks.
以下术语用于描述IP网络的嵌套。
o More specific: Given two networks, A and B, A is more specific than B if network B includes all space of network A, and if network B is larger than network A.
o 更具体：给定两个网络A和B，如果网络B包含网络A的所有空间，并且如果网络B大于网络A，则A比B更具体。
o Less specific: Opposite of more specific. The network B is less specific than network A if network A's space is completely included in network B and if network A is smaller than network B.
o 不太具体：与更具体相反。如果网络A的空间完全包含在网络B中并且如果网络A小于网络B，则网络B不如网络A具体。
o Most specific: Given a set of networks, the network or networks that are more specific than zero or more specific of the other networks in the set, and that are not less specific of any of the networks in the set.
o 最具体的：给定一组网络，一个或多个网络比集合中的零个或更多其他网络更具体，并且不比集合中的任何网络更具体。
o Least specific: Given a set of networks, the network or networks that are not more specific to any of the other networks in the set.
o 最不特定：给定一组网络，该网络或多个网络不特定于该组中的任何其他网络。
Examples:
示例：
+-------------------------------------------------------+
| |
| Given the networks A, B, C, and D as follows: |
| |
| A |---------------------------------| |
| B |-----------------| |
| C |---------| |
| D |-------| |
| |
| |
| Network A is less specific than B, C, and D. |
| Network B is more specific than A. |
| Among these four networks, A is the least specific, |
| and C and D are the most specific. |
| |
+-------------------------------------------------------+
+-------------------------------------------------------+
| |
| Given the networks A, B, C, and D as follows: |
| |
| A |---------------------------------| |
| B |-----------------| |
| C |---------| |
| D |-------| |
| |
| |
| Network A is less specific than B, C, and D. |
| Network B is more specific than A. |
| Among these four networks, A is the least specific, |
| and C and D are the most specific. |
| |
+-------------------------------------------------------+
Figure 1: Nesting Example 1
图1：嵌套示例1
+-------------------------------------------------------+
| |
| Given networks E, F, and G: |
| |
| E |----------| |
| F |--------------| |
| G |---| |
| |
| Networks E and F are least specific networks. |
| Networks F and G are most specific networks. |
| |
+-------------------------------------------------------+
+-------------------------------------------------------+
| |
| Given networks E, F, and G: |
| |
| E |----------| |
| F |--------------| |
| G |---| |
| |
| Networks E and F are least specific networks. |
| Networks F and G are most specific networks. |
| |
+-------------------------------------------------------+
Figure 2: Nesting Example 2
图2：嵌套示例2
The following definitions assume that there are no overlapping networks in the database. A network overlaps with another one when they encompass each other's space partially. Examples:
以下定义假定数据库中没有重叠的网络。当一个网络部分地包围彼此的空间时，它与另一个网络重叠。示例：
A |---------------------|
B |----------------------------|
A |---------------------|
B |----------------------------|
Figure 3: Nesting Example 3
图3：嵌套示例3
Here, networks A and B are overlapping networks because network A encompasses network B's space partially, and network B encompasses network A's space partially.
这里，网络A和B是重叠的网络，因为网络A部分包含网络B的空间，而网络B部分包含网络A的空间。
C |------------------|
D |---------|
C |------------------|
D |---------|
Figure 4: Nesting Example 4
图4：嵌套示例4
Here, networks C and D are NOT overlapping networks because even if network D encompasses a part of network C's space, network C does not encompass network D's space partially (it encompasses network D completely).
这里，网络C和D不是重叠网络，因为即使网络D包含网络C空间的一部分，网络C也不部分包含网络D空间（它完全包含网络D）。
The address directory can contain more than one network with the same range. They are said to be exact match networks.
地址目录可以包含多个具有相同范围的网络。据说它们是精确的匹配网络。
The parent/child relationship in the internet address directory is unidirectional. That is, there might also be parent/child relationship with exact match networks, but a network cannot be a parent and a child of its exact match network at the same time.
internet地址目录中的父/子关系是单向的。也就是说，也可能存在与精确匹配网络的父/子关系，但网络不能同时是其精确匹配网络的父网络和子网络。
The following are nested matching searches:
以下是嵌套匹配搜索：
(1) all less specifics search: Given a range, find all the networks that contain that range (i.e., all less specifics and exact matches). These networks are the networks that fulfill the following condition:
(1) 所有不太详细的搜索：给定一个范围，查找包含该范围的所有网络（即所有不太详细的和精确的匹配）。这些网络是满足以下条件的网络：
(start(network) <= start(search)) AND (end(network) >= end(search))
(start(network) <= start(search)) AND (end(network) >= end(search))
(2) one-level less specifics search: Given a range, find only the most specific network that contains that range (could be multiple networks, but usually single). This is the set of networks from (1), with the provision that no network in the return set is contained by any other network in the set. If there are exact match networks in the set from (1), they both must appear in the result set. The result set may contain a network that is exact match to the query range, if the search allows exact matches.
(2) 少一级细节搜索：给定一个范围，只查找包含该范围的最具体的网络（可以是多个网络，但通常是单个网络）。这是（1）中的网络集，前提是返回集中的任何网络都不包含在该集中的任何其他网络中。如果（1）中的集合中存在精确匹配网络，则它们都必须出现在结果集中。如果网络允许搜索集包含精确的搜索范围，则该搜索集可能匹配。
A |-------------------------------|
B |---------------------------|
C |-------|
Query |- - - - - - - - - -|
A |-------------------------------|
B |---------------------------|
C |-------|
Query |- - - - - - - - - -|
Figure 5: Nesting Example 5
图5：嵌套示例5
In the above case, the query must return B.
在上述情况下，查询必须返回B。
A |-------------------------------|
B |---------------------------|
C |---------------------------|
D |-------|
Query |- - - - - - - - - -|
A |-------------------------------|
B |---------------------------|
C |---------------------------|
D |-------|
Query |- - - - - - - - - -|
Figure 6: Nesting Example 6
图6：嵌套示例6
Here, the query must return B and C (they are exact matches of each other).
在这里，查询必须返回B和C（它们彼此完全匹配）。
A |-------------------------------|
B |---------------------------|
C |---------------------------|
D |-------|
Query |- - - -|
A |-------------------------------|
B |---------------------------|
C |---------------------------|
D |-------|
Query |- - - -|
Figure 7: Nesting Example 7
图7：嵌套示例7
Here, the query must return B and C (they are exact matches of each other). D must not be in the result set, as it is exact match to the query if the search specifies that exact matches of query range should not appear in the result set.
在这里，查询必须返回B和C（它们彼此完全匹配）。D不能在结果集中，因为如果搜索指定查询范围的精确匹配不应出现在结果集中，则它与查询完全匹配。
In Figure 7, if the search specifies that exact matches to the query range are allowed in the result set, then only D must be returned.
在图7中，如果搜索指定在结果集中允许与查询范围完全匹配，那么只能返回D。
(3) all more specifics search: Given a range, find all the networks that are fully within that range. The search contains a flag that specifies if an exact match to the query range should appear in the result set or not. Thus, the result set may or may not contain the exact match to the query range, as instructed by the search.
(3) 更多详细信息搜索：给定一个范围，查找完全在该范围内的所有网络。搜索包含一个标志，指定与查询范围完全匹配的内容是否应出现在结果集中。因此，根据搜索的指示，结果集可能包含也可能不包含与查询范围的精确匹配。
(start(network) >= start(search)) AND (end(network) <= end(search))
(start(network) >= start(search)) AND (end(network) <= end(search))
(4) one-level more specifics search: Given a range, find only the least specific networks that are fully within that range. This is the set of networks from (3), with the provision that no network in the return set contains any other network in the return set.
(4) 更详细的一级搜索：给定一个范围，只查找完全在该范围内的最不特定的网络。这是（3）中的网络集，前提是返回集中的网络不包含返回集中的任何其他网络。
Query |- - - - - - - - - - - - - - - - - - - - - - -|
Query |- - - - - - - - - - - - - - - - - - - - - - -|
A |------------------|
B |-------------------------|
C |--------|
D |---------|
A |------------------|
B |-------------------------|
C |--------|
D |---------|
Figure 8: Nesting Example 8
图8：嵌套示例8
(5) exact match search: Given a range, find the networks that begin and end on the same IP addresses as the range. That is, the networks that fulfill the following condition:
(5) 精确匹配搜索：给定一个范围，查找以该范围相同的IP地址开始和结束的网络。即满足以下条件的网络：
(start(network) = start(search)) AND (end(network) = end(search))
(start(network) = start(search)) AND (end(network) = end(search))
(6) Given a range, find the exact match network if it exists, and if it does not, perform the (2) search.
(6) 给定一个范围，找到精确匹配的网络（如果存在），如果不存在，则执行（2）搜索。
The following are parent-child relationship searches:
以下是父子关系搜索：
(7) Given a network handle, find the network that is the direct (one level up) parent of the network with the given handle.
(7) 给定网络句柄，查找具有给定句柄的网络的直接（向上一级）父网络。
(8) Given a network handle, find the network or networks that are direct (one level down) children of the network with the handle given.
(8) 给定网络句柄，查找具有给定句柄的网络的直接（向下一级）子网络。
This IP address registry 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.
这个IP地址注册表是用XML模式表示法指定的。这里介绍的形式语法是一个完整的模式表示，当与IRIS的形式模式语法结合使用时，它适合于XML实例的自动验证。
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:areg="urn:ietf:params:xml:ns:areg1"
xmlns:iris="urn:ietf:params:xml:ns:iris1"
targetNamespace="urn:ietf:params:xml:ns:areg1"
elementFormDefault="qualified" >
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:areg="urn:ietf:params:xml:ns:areg1"
xmlns:iris="urn:ietf:params:xml:ns:iris1"
targetNamespace="urn:ietf:params:xml:ns:areg1"
elementFormDefault="qualified" >
<import namespace="urn:ietf:params:xml:ns:iris1" />
<import namespace="urn:ietf:params:xml:ns:iris1" />
<annotation>
<documentation> IP address registry schema derived from IRIS
schema </documentation>
</annotation>
<annotation>
<documentation> IP address registry schema derived from IRIS
schema </documentation>
</annotation>
<!-- ========================================= -->
<!-- -->
<!-- Query Types -->
<!-- -->
<!-- ========================================= -->
<!-- -->
<!-- Query Types -->
<!-- -->
<!-- ========================================= -->
<!-- -->
<!-- Find Autonomous Systems By Name -->
<!-- Find Networks By Name -->
<!-- -->
<!-- ========================================= -->
<!-- -->
<!-- Find Autonomous Systems By Name -->
<!-- Find Networks By Name -->
<!-- -->
<complexType name="findByNameType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="name"
type="areg:exactOrPartialMatchParameter" />
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
<complexType name="findByNameType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="name"
type="areg:exactOrPartialMatchParameter" />
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
</complexType>
<element name="findNetworksByName" type="areg:findByNameType"
substitutionGroup="iris:query" />
<element name="findAutonomousSystemsByName"
type="areg:findByNameType"
substitutionGroup="iris:query" />
<element name="findNetworksByName" type="areg:findByNameType"
substitutionGroup="iris:query" />
<element name="findAutonomousSystemsByName"
type="areg:findByNameType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Address/Address Range type for -->
<!-- Find Network -->
<!-- -->
<!-- -->
<!-- Address/Address Range type for -->
<!-- Find Network -->
<!-- -->
<complexType name="addressRangeType">
<sequence>
<element name="start" type="token" />
<element name="end" type="token" minOccurs="0" maxOccurs="1" />
</sequence>
</complexType>
<complexType name="addressRangeType">
<sequence>
<element name="start" type="token" />
<element name="end" type="token" minOccurs="0" maxOccurs="1" />
</sequence>
</complexType>
<!-- -->
<!-- Find Networks By Address -->
<!-- -->
<!-- -->
<!-- Find Networks By Address -->
<!-- -->
<complexType name="findNetworksByAddressType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<element name="ipv4Address" type="areg:addressRangeType"
/>
<element name="ipv6Address" type="areg:addressRangeType"
/>
</choice>
<element name="specificity">
<complexType>
<simpleContent>
<extension base="areg:specificityType" >
<attribute name="allowEquivalences" type="boolean"
default="false" />
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="findNetworksByAddressType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<element name="ipv4Address" type="areg:addressRangeType"
/>
<element name="ipv6Address" type="areg:addressRangeType"
/>
</choice>
<element name="specificity">
<complexType>
<simpleContent>
<extension base="areg:specificityType" >
<attribute name="allowEquivalences" type="boolean"
default="false" />
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findNetworksByAddress"
type="areg:findNetworksByAddressType"
substitutionGroup="iris:query" />
<element name="findNetworksByAddress"
type="areg:findNetworksByAddressType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find AS By Number -->
<!-- -->
<!-- -->
<!-- Find AS By Number -->
<!-- -->
<complexType name="findASByNumberType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="asNumberStart" type="token" />
<element name="asNumberEnd" type="token" minOccurs="0"
maxOccurs="1" />
<element name="specificity">
<complexType>
<simpleContent>
<extension base="areg:specificityType" >
<attribute name="allowEquivalences" type="boolean"
default="false" />
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="findASByNumberType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="asNumberStart" type="token" />
<element name="asNumberEnd" type="token" minOccurs="0"
maxOccurs="1" />
<element name="specificity">
<complexType>
<simpleContent>
<extension base="areg:specificityType" >
<attribute name="allowEquivalences" type="boolean"
default="false" />
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findASByNumber" type="areg:findASByNumberType"
substitutionGroup="iris:query" />
<element name="findASByNumber" type="areg:findASByNumberType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Specificity Type -->
<!-- -->
<!-- -->
<!-- Specificity Type -->
<!-- -->
<simpleType name="specificityType">
<restriction base="string">
<enumeration value="exact-match" />
<enumeration value="all-less-specific" />
<enumeration value="one-level-less-specific" />
<enumeration value="all-more-specific" />
<enumeration value="one-level-more-specific" />
</restriction>
</simpleType>
<simpleType name="specificityType">
<restriction base="string">
<enumeration value="exact-match" />
<enumeration value="all-less-specific" />
<enumeration value="one-level-less-specific" />
<enumeration value="all-more-specific" />
<enumeration value="one-level-more-specific" />
</restriction>
</simpleType>
<!-- -->
<!-- -->
<!-- Find By Contact -->
<!-- -->
<!-- Find By Contact -->
<!-- -->
<complexType name="findByContactType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<group ref="areg:contactSearchGroup" />
<element name="contactHandle"
type="areg:exactMatchParameter" />
</choice>
<element name="returnedResultType" minOccurs="0"
maxOccurs="1" >
<simpleType>
<restriction base="string" >
<enumeration value="returnASs" />
<enumeration value="returnIPv4Networks" />
<enumeration value="returnIPv6Networks" />
<enumeration value="returnOrganizations" />
</restriction>
</simpleType>
</element>
<element name="role" minOccurs="0" maxOccurs="1" >
<simpleType>
<restriction base="string" >
<enumeration value="adminContact" />
<enumeration value="techContact" />
<enumeration value="nocContact" />
<enumeration value="abuseContact" />
<enumeration value="otherContact" />
</restriction>
</simpleType>
</element>
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="findByContactType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<group ref="areg:contactSearchGroup" />
<element name="contactHandle"
type="areg:exactMatchParameter" />
</choice>
<element name="returnedResultType" minOccurs="0"
maxOccurs="1" >
<simpleType>
<restriction base="string" >
<enumeration value="returnASs" />
<enumeration value="returnIPv4Networks" />
<enumeration value="returnIPv6Networks" />
<enumeration value="returnOrganizations" />
</restriction>
</simpleType>
</element>
<element name="role" minOccurs="0" maxOccurs="1" >
<simpleType>
<restriction base="string" >
<enumeration value="adminContact" />
<enumeration value="techContact" />
<enumeration value="nocContact" />
<enumeration value="abuseContact" />
<enumeration value="otherContact" />
</restriction>
</simpleType>
</element>
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findByContact" type="areg:findByContactType"
substitutionGroup="iris:query" />
<element name="findByContact" type="areg:findByContactType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find Networks By Handle -->
<!-- -->
<!-- -->
<!-- Find Networks By Handle -->
<!-- -->
<complexType name="findNetworksByHandleType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="networkHandle" type="token" />
<element name="specificity"
type="areg:specificitySubsetType" />
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="findNetworksByHandleType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="networkHandle" type="token" />
<element name="specificity"
type="areg:specificitySubsetType" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findNetworksByHandle"
type="areg:findNetworksByHandleType"
substitutionGroup="iris:query" />
<element name="findNetworksByHandle"
type="areg:findNetworksByHandleType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Specificity Subtype -->
<!-- -->
<!-- -->
<!-- Specificity Subtype -->
<!-- -->
<simpleType name="specificitySubsetType">
<restriction base="string">
<enumeration value="all-less-specific" />
<enumeration value="one-level-less-specific" />
<enumeration value="all-more-specific" />
<enumeration value="one-level-more-specific" />
</restriction>
</simpleType>
<simpleType name="specificitySubsetType">
<restriction base="string">
<enumeration value="all-less-specific" />
<enumeration value="one-level-less-specific" />
<enumeration value="all-more-specific" />
<enumeration value="one-level-more-specific" />
</restriction>
</simpleType>
<!-- -->
<!-- Find Contacts -->
<!-- -->
<!-- -->
<!-- Find Contacts -->
<!-- -->
<complexType name="findContactsType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<group ref="areg:contactSearchGroup" />
<element name="organizationId"
type="areg:exactMatchParameter" />
</choice>
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="findContactsType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<group ref="areg:contactSearchGroup" />
<element name="organizationId"
type="areg:exactMatchParameter" />
</choice>
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findContacts" type="areg:findContactsType"
substitutionGroup="iris:query" />
<element name="findContacts" type="areg:findContactsType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find Organizations -->
<!-- -->
<!-- -->
<!-- Find Organizations -->
<!-- -->
<complexType name="findOrganizationsType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<element name="organizationName"
type="areg:exactOrPartialMatchParameter" />
<group ref="areg:commonSearchGroup" />
</choice>
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="findOrganizationsType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<element name="organizationName"
type="areg:exactOrPartialMatchParameter" />
<group ref="areg:commonSearchGroup" />
</choice>
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findOrganizations" type="areg:findOrganizationsType"
substitutionGroup="iris:query" />
<element name="findOrganizations" type="areg:findOrganizationsType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find Networks by Name Server -->
<!-- -->
<!-- -->
<!-- Find Networks by Name Server -->
<!-- -->
<complexType name="findNetworksByNameServerType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="nameServer" type="normalizedString" />
<element name="returnedResultType" minOccurs="0"
maxOccurs="1" >
<simpleType>
<restriction base="string" >
<enumeration value="returnIPv4Networks" />
<enumeration value="returnIPv6Networks" />
</restriction>
</simpleType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="findNetworksByNameServerType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="nameServer" type="normalizedString" />
<element name="returnedResultType" minOccurs="0"
maxOccurs="1" >
<simpleType>
<restriction base="string" >
<enumeration value="returnIPv4Networks" />
<enumeration value="returnIPv6Networks" />
</restriction>
</simpleType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findNetworksByNameServer"
type="areg:findNetworksByNameServerType"
substitutionGroup="iris:query" />
<element name="findNetworksByNameServer"
type="areg:findNetworksByNameServerType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Contact Search Group -->
<!-- -->
<!-- -->
<!-- Contact Search Group -->
<!-- -->
<group name="contactSearchGroup">
<choice>
<element name="commonName"
type="areg:exactOrPartialMatchParameter" />
<group ref="areg:commonSearchGroup" />
</choice>
</group>
<group name="contactSearchGroup">
<choice>
<element name="commonName"
type="areg:exactOrPartialMatchParameter" />
<group ref="areg:commonSearchGroup" />
</choice>
</group>
<!-- -->
<!-- Common Search Group -->
<!-- -->
<!-- -->
<!-- Common Search Group -->
<!-- -->
<group name="commonSearchGroup">
<choice>
<element name="eMail" type="areg:domainResourceParameter" />
<element name="city" type="areg:exactMatchParameter" />
<element name="region" type="areg:exactMatchParameter" />
<element name="country" type="areg:exactMatchParameter" />
<element name="postalCode" type="areg:exactMatchParameter" />
</choice>
</group>
<group name="commonSearchGroup">
<choice>
<element name="eMail" type="areg:domainResourceParameter" />
<element name="city" type="areg:exactMatchParameter" />
<element name="region" type="areg:exactMatchParameter" />
<element name="country" type="areg:exactMatchParameter" />
<element name="postalCode" type="areg:exactMatchParameter" />
</choice>
</group>
<!-- -->
<!-- Parameters for Search Groups -->
<!-- -->
<!-- -->
<!-- Parameters for Search Groups -->
<!-- -->
<complexType name="exactOrPartialMatchParameter">
<choice>
<group ref="areg:partialMatchGroup" />
<group ref="areg:exactMatchGroup" />
</choice>
</complexType>
<complexType name="exactOrPartialMatchParameter">
<choice>
<group ref="areg:partialMatchGroup" />
<group ref="areg:exactMatchGroup" />
</choice>
</complexType>
<complexType name="exactMatchParameter">
<group ref="areg:exactMatchGroup" />
</complexType>
<complexType name="exactMatchParameter">
<group ref="areg:exactMatchGroup" />
</complexType>
<complexType name="partialMatchParameter">
<sequence>
<group ref="areg:partialMatchGroup" />
<complexType name="partialMatchParameter">
<sequence>
<group ref="areg:partialMatchGroup" />
</sequence>
</complexType>
</sequence>
</complexType>
<complexType name="domainResourceParameter" >
<choice>
<group ref="areg:exactMatchGroup" />
<element name="inDomain" type="token" />
</choice>
</complexType>
<complexType name="domainResourceParameter" >
<choice>
<group ref="areg:exactMatchGroup" />
<element name="inDomain" type="token" />
</choice>
</complexType>
<group name="partialMatchGroup">
<choice>
<sequence>
<element name="beginsWith">
<simpleType>
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
</element>
<element minOccurs="0" ref="areg:endsWith"/>
</sequence>
<element ref="areg:endsWith" />
</choice>
</group>
<group name="partialMatchGroup">
<choice>
<sequence>
<element name="beginsWith">
<simpleType>
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
</element>
<element minOccurs="0" ref="areg:endsWith"/>
</sequence>
<element ref="areg:endsWith" />
</choice>
</group>
<element name="endsWith">
<simpleType>
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
</element>
<element name="endsWith">
<simpleType>
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
</element>
<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 -->
<!-- -->
<!-- ========================================= -->
<!-- -->
<!-- IPv4 and IPv6 Network Results -->
<!-- -->
<!-- IPv4 and IPv6 Network Results -->
<!-- -->
<!-- -->
<complexType name="ipNetworkType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="networkHandle" type="token"
minOccurs="0" maxOccurs="1" />
<element name="name" minOccurs="0" maxOccurs="1"
type="normalizedString" />
<element name="startAddress" type="token" />
<element name="endAddress" type="token" />
<sequence minOccurs="0" maxOccurs="1">
<element name="networkType" type="normalizedString"
minOccurs="1" maxOccurs="1" />
<element name="networkTypeInfo" type="iris:entityType"
minOccurs="0" maxOccurs="1" />
</sequence>
<element name="nameServer" type="normalizedString"
minOccurs="0" maxOccurs="unbounded" />
<element name="organization" type="iris:entityType"
minOccurs="0" maxOccurs="1" />
<choice minOccurs="0" maxOccurs="1" >
<element name="parent" type="iris:entityType" />
<element name="noParent">
</element>
</choice>
<group ref="areg:contactGroup" />
<group ref="areg:commonGroup" />
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="ipNetworkType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="networkHandle" type="token"
minOccurs="0" maxOccurs="1" />
<element name="name" minOccurs="0" maxOccurs="1"
type="normalizedString" />
<element name="startAddress" type="token" />
<element name="endAddress" type="token" />
<sequence minOccurs="0" maxOccurs="1">
<element name="networkType" type="normalizedString"
minOccurs="1" maxOccurs="1" />
<element name="networkTypeInfo" type="iris:entityType"
minOccurs="0" maxOccurs="1" />
</sequence>
<element name="nameServer" type="normalizedString"
minOccurs="0" maxOccurs="unbounded" />
<element name="organization" type="iris:entityType"
minOccurs="0" maxOccurs="1" />
<choice minOccurs="0" maxOccurs="1" >
<element name="parent" type="iris:entityType" />
<element name="noParent">
</element>
</choice>
<group ref="areg:contactGroup" />
<group ref="areg:commonGroup" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="ipv4Network" type="areg:ipNetworkType"
substitutionGroup="iris:result" />
<element name="ipv4Network" type="areg:ipNetworkType"
substitutionGroup="iris:result" />
<element name="ipv6Network" type="areg:ipNetworkType"
substitutionGroup="iris:result" />
<element name="ipv6Network" type="areg:ipNetworkType"
substitutionGroup="iris:result" />
<!-- -->
<!-- Autonomous System -->
<!-- -->
<!-- -->
<!-- Autonomous System -->
<!-- -->
<complexType name="autonomousSystemType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<complexType name="autonomousSystemType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="asHandle" type="token"
minOccurs="0" maxOccurs="1" />
<element name="asNumberStart" type="integer" minOccurs="0"
maxOccurs="1" />
<element name="asNumberEnd" type="integer" minOccurs="0"
maxOccurs="1" />
<element name="name" type="normalizedString" minOccurs="0"
maxOccurs="1" />
<element name="organization" type="iris:entityType"
minOccurs="0" maxOccurs="1" />
<choice minOccurs="0" maxOccurs="1">
<element name="parent" type="iris:entityType" />
<element name="noParent" />
</choice>
<group ref="areg:contactGroup" />
<group ref="areg:commonGroup" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="asHandle" type="token"
minOccurs="0" maxOccurs="1" />
<element name="asNumberStart" type="integer" minOccurs="0"
maxOccurs="1" />
<element name="asNumberEnd" type="integer" minOccurs="0"
maxOccurs="1" />
<element name="name" type="normalizedString" minOccurs="0"
maxOccurs="1" />
<element name="organization" type="iris:entityType"
minOccurs="0" maxOccurs="1" />
<choice minOccurs="0" maxOccurs="1">
<element name="parent" type="iris:entityType" />
<element name="noParent" />
</choice>
<group ref="areg:contactGroup" />
<group ref="areg:commonGroup" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="autonomousSystem" type="areg:autonomousSystemType"
substitutionGroup="iris:result" />
<element name="autonomousSystem" type="areg:autonomousSystemType"
substitutionGroup="iris:result" />
<!-- -->
<!-- Contact -->
<!-- -->
<!-- -->
<!-- Contact -->
<!-- -->
<complexType name="contactType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="contactHandle" type="token"
minOccurs="0" maxOccurs="1" />
<element name="commonName" type="normalizedString"
minOccurs="0" maxOccurs="1" />
<element name="eMail" type="normalizedString" minOccurs="0"
maxOccurs="unbounded" />
<element name="sip" type="normalizedString" minOccurs="0"
maxOccurs="unbounded" />
<element name="organization" type="iris:entityType"
minOccurs="0" maxOccurs="unbounded" />
<element name="postalAddress" minOccurs="0"
maxOccurs="unbounded">
<complexType>
<sequence>
<element name="address" type="string" minOccurs="0"
maxOccurs="1" />
<complexType name="contactType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="contactHandle" type="token"
minOccurs="0" maxOccurs="1" />
<element name="commonName" type="normalizedString"
minOccurs="0" maxOccurs="1" />
<element name="eMail" type="normalizedString" minOccurs="0"
maxOccurs="unbounded" />
<element name="sip" type="normalizedString" minOccurs="0"
maxOccurs="unbounded" />
<element name="organization" type="iris:entityType"
minOccurs="0" maxOccurs="unbounded" />
<element name="postalAddress" minOccurs="0"
maxOccurs="unbounded">
<complexType>
<sequence>
<element name="address" type="string" minOccurs="0"
maxOccurs="1" />
<element name="city" type="string" minOccurs="0"
maxOccurs="1" />
<element name="region" type="string" minOccurs="0"
maxOccurs="1" />
<element name="postalCode" type="normalizedString"
minOccurs="0" maxOccurs="1" />
<element name="country" type="token" minOccurs="0"
maxOccurs="1" />
</sequence>
</complexType>
</element>
<element name="phone" minOccurs="0" maxOccurs="unbounded" >
<complexType>
<sequence>
<element name="number" type="normalizedString" />
<element name="extension" type="normalizedString"
minOccurs="0" maxOccurs="unbounded" />
<element name="type" type="normalizedString"
minOccurs="0" maxOccurs="1" />
</sequence>
</complexType>
</element>
<group ref="areg:commonGroup" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="city" type="string" minOccurs="0"
maxOccurs="1" />
<element name="region" type="string" minOccurs="0"
maxOccurs="1" />
<element name="postalCode" type="normalizedString"
minOccurs="0" maxOccurs="1" />
<element name="country" type="token" minOccurs="0"
maxOccurs="1" />
</sequence>
</complexType>
</element>
<element name="phone" minOccurs="0" maxOccurs="unbounded" >
<complexType>
<sequence>
<element name="number" type="normalizedString" />
<element name="extension" type="normalizedString"
minOccurs="0" maxOccurs="unbounded" />
<element name="type" type="normalizedString"
minOccurs="0" maxOccurs="1" />
</sequence>
</complexType>
</element>
<group ref="areg:commonGroup" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="contact" type="areg:contactType"
substitutionGroup="iris:result" />
<element name="contact" type="areg:contactType"
substitutionGroup="iris:result" />
<!-- -->
<!-- Organization -->
<!-- -->
<!-- -->
<!-- Organization -->
<!-- -->
<complexType name="organizationType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="name" type="normalizedString"
minOccurs="0" maxOccurs="1" />
<element name="eMail" type="normalizedString" minOccurs="0"
maxOccurs="unbounded" />
<element name="id" type="token" />
<element name="postalAddress" minOccurs="0"
maxOccurs="unbounded">
<complexType>
<sequence>
<complexType name="organizationType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="name" type="normalizedString"
minOccurs="0" maxOccurs="1" />
<element name="eMail" type="normalizedString" minOccurs="0"
maxOccurs="unbounded" />
<element name="id" type="token" />
<element name="postalAddress" minOccurs="0"
maxOccurs="unbounded">
<complexType>
<sequence>
<element name="address" type="string" minOccurs="0"
maxOccurs="1" />
<element name="city" type="string" minOccurs="0"
maxOccurs="1" />
<element name="region" type="string" minOccurs="0"
maxOccurs="1" />
<element name="postalCode" type="normalizedString"
minOccurs="0" maxOccurs="1" />
<element name="country" type="token" minOccurs="0"
maxOccurs="1" />
</sequence>
</complexType>
</element>
<element name="phone" minOccurs="0" maxOccurs="unbounded" >
<complexType>
<sequence>
<element name="number" type="normalizedString" />
<element name="extension" type="normalizedString"
minOccurs="0" maxOccurs="unbounded" />
<element name="type" type="normalizedString"
minOccurs="0" maxOccurs="1" />
</sequence>
</complexType>
</element>
<group ref="areg:contactGroup" />
<group ref="areg:commonGroup" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="address" type="string" minOccurs="0"
maxOccurs="1" />
<element name="city" type="string" minOccurs="0"
maxOccurs="1" />
<element name="region" type="string" minOccurs="0"
maxOccurs="1" />
<element name="postalCode" type="normalizedString"
minOccurs="0" maxOccurs="1" />
<element name="country" type="token" minOccurs="0"
maxOccurs="1" />
</sequence>
</complexType>
</element>
<element name="phone" minOccurs="0" maxOccurs="unbounded" >
<complexType>
<sequence>
<element name="number" type="normalizedString" />
<element name="extension" type="normalizedString"
minOccurs="0" maxOccurs="unbounded" />
<element name="type" type="normalizedString"
minOccurs="0" maxOccurs="1" />
</sequence>
</complexType>
</element>
<group ref="areg:contactGroup" />
<group ref="areg:commonGroup" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="organization" type="areg:organizationType"
substitutionGroup="iris:result" />
<element name="organization" type="areg:organizationType"
substitutionGroup="iris:result" />
<!-- -->
<!-- Contact Group -->
<!-- -->
<!-- -->
<!-- Contact Group -->
<!-- -->
<group name="contactGroup">
<sequence>
<element name="adminContact" type="iris:entityType"
minOccurs="0" maxOccurs="unbounded" />
<element name="techContact" type="iris:entityType"
minOccurs="0" maxOccurs="unbounded" />
<element name="nocContact" type="iris:entityType" minOccurs="0"
maxOccurs="unbounded" />
<element name="abuseContact" type="iris:entityType"
minOccurs="0" maxOccurs="unbounded" />
<group name="contactGroup">
<sequence>
<element name="adminContact" type="iris:entityType"
minOccurs="0" maxOccurs="unbounded" />
<element name="techContact" type="iris:entityType"
minOccurs="0" maxOccurs="unbounded" />
<element name="nocContact" type="iris:entityType" minOccurs="0"
maxOccurs="unbounded" />
<element name="abuseContact" type="iris:entityType"
minOccurs="0" maxOccurs="unbounded" />
<element name="otherContact" type="iris:entityType"
minOccurs="0" maxOccurs="unbounded" />
</sequence>
</group>
<element name="otherContact" type="iris:entityType"
minOccurs="0" maxOccurs="unbounded" />
</sequence>
</group>
<!-- -->
<!-- Common Group -->
<!-- -->
<!-- -->
<!-- Common Group -->
<!-- -->
<group name="commonGroup">
<sequence>
<element name="numberResourceRegistry" type="iris:entityType"
minOccurs="0" maxOccurs="1" />
<element name="registrationDate" type="dateTime" minOccurs="0"
maxOccurs="1" />
<element name="lastUpdatedDate" type="dateTime" minOccurs="0"
maxOccurs="1" />
<element ref="iris:seeAlso" minOccurs="0" maxOccurs="unbounded"
/>
</sequence>
</group>
</schema>
<group name="commonGroup">
<sequence>
<element name="numberResourceRegistry" type="iris:entityType"
minOccurs="0" maxOccurs="1" />
<element name="registrationDate" type="dateTime" minOccurs="0"
maxOccurs="1" />
<element name="lastUpdatedDate" type="dateTime" minOccurs="0"
maxOccurs="1" />
<element ref="iris:seeAlso" minOccurs="0" maxOccurs="unbounded"
/>
</sequence>
</group>
</schema>
Figure 9
图9
IRIS allows several extensions of the core capabilities. This section outlines those extensions allowable by IRIS-BEEP [3].
IRIS允许对核心功能进行若干扩展。本节概述了IRIS-BEEP[3]允许的扩展。
This registry type uses the default message pattern as described in IRIS-BEEP [3].
此注册表类型使用IRIS-BEEP[3]中所述的默认消息模式。
This registry type uses the default server authentication method as described in IRIS-BEEP [3].
此注册表类型使用IRIS-BEEP[3]中所述的默认服务器身份验证方法。
See Section 9 for the application service label registration.
有关应用程序服务标签注册，请参见第9节。
Address registries do not have natural links to DNS. Using reverse DNS tree presents problems for IP address delegation (for example, delegations do not fall into byte boundaries, unlike reverse DNS), and DNS does not currently contain any information regarding autonomous system delegation.
地址注册中心没有到DNS的自然链接。使用反向DNS树会给IP地址委派带来问题（例如，委派不属于字节边界，与反向DNS不同），并且DNS当前不包含任何有关自治系统委派的信息。
Therefore, in order for the top-down resolution to operate properly, it is requested that the IAB instruct IANA to insert and maintain a NAPTR DNS resource record for areg.iris.arpa, as described in Section 9.
因此，为了使自上而下的分辨率正常工作，请求IAB指示IANA插入并维护areg.iris.arpa的NAPTR DNS资源记录，如第9节所述。
The top-down alternative resolution method MUST be identified as 'top' in IRIS URIs.
在IRIS URI中，自上而下的替代解析方法必须标识为“top”。
The process for this condition is as follows:
这种情况的处理过程如下：
1. The IRIS [2] direct-resolution process is tried against areg.iris.arpa.
1. IRIS[2]直接解析过程是针对areg.IRIS.arpa进行试验的。
2. If the direct-resolution process yields no server for which a connection can be made, then a negative response is returned, and no further action is taken.
2. 如果直接解析过程没有产生可以建立连接的服务器，则返回否定响应，并且不采取进一步的操作。
It is RECOMMENDED that IRIS clients issuing AREG1 requests use the 'top' resolution method when no resolution method has been explicitly given by a user. IRIS servers accepting AREG1 requests that seek information for which they are not authoritative SHOULD refer clients using the 'top' resolution method.
当用户未明确给出解析方法时，建议发出AREG1请求的IRIS客户端使用“top”解析方法。IRIS服务器接受AREG1请求时，如果请求的信息不是其权威性的，则应使用“top”解析方法向客户端推荐。
This document lays out no new considerations for internationalization beyond those specified in IRIS [2].
除了IRIS[2]中规定的国际化考虑因素外，本文件没有提出任何新的国际化考虑因素。
The following URN has been registered with IANA according to the IANA considerations defined in IRIS [2]:
根据IRIS[2]中定义的IANA注意事项，以下URN已向IANA注册：
urn:ietf:params:xml:ns:areg1
urn:ietf:params:xml:ns:areg1
The following S-NAPTR application service label has been registered with IANA according to the IANA considerations defined in IRIS [2]:
根据IRIS[2]中定义的IANA注意事项，已向IANA注册了以下S-NAPTR应用程序服务标签：
AREG1
AREG1
Under instructions from the IAB, the IANA will create a new second level domain under .arpa called iris (i.e., iris.arpa.). The contents of this new domain are to be under the control of the IAB. Under instructions from the IAB, the IANA will insert and maintain a NAPTR DNS resource record in the iris.arpa. domain for the name areg.iris.arpa. The initial contents for that record is:
根据IAB的指示，IANA将在.arpa下创建一个新的二级域，称为iris（即iris.arpa.）。这个新域名的内容将由IAB控制。根据IAB的指示，IANA将在iris.arpa中插入并维护NAPTR DNS资源记录。域名为areg.iris.arpa。该记录的初始内容为：
areg.iris.arpa. ;; order pref flags service re replacement IN NAPTR 100 10 "" "AREG1:iris.xpc:iris.lwz" "" areg.nro.net
areg.iris.arpa；；订单预处理标志服务在NAPTR 100 10“AREG1:iris.xpc:iris.lwz”“areg.nro.net”中重新更换
This document lays out no new considerations for security precautions beyond those specified in IRIS [2].
除了IRIS[2]中规定的安全注意事项外，本文件未列出其他安全注意事项。
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[1] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[2] Newton, A. and M. Sanz, "IRIS: The Internet Registry Information Service (IRIS) Core Protocol", RFC 3981, January 2005.
[2] Newton，A.和M.Sanz，“IRIS：互联网注册信息服务（IRIS）核心协议”，RFC 3981，2005年1月。
[3] Newton, A. and M. Sanz, "Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)", RFC 3983, January 2005.
[3] Newton，A.和M.Sanz，“通过块可扩展交换协议（BEEP）使用互联网注册信息服务（IRIS）”，RFC 3983，2005年1月。
[4] Newton, A., "Cross Registry Internet Service Protocol (CRISP) Requirements", RFC 3707, February 2004.
[4] Newton，A.，“跨注册互联网服务协议（CRISP）要求”，RFC 3707，2004年2月。
[5] World Wide Web Consortium, "Extensible Markup Language (XML) 1.0", W3C XML, February 1998, <http://www.w3.org/TR/1998/REC-xml-19980210>.
[5] 万维网联盟，“可扩展标记语言（XML）1.0”，W3C XML，1998年2月<http://www.w3.org/TR/1998/REC-xml-19980210>.
[6] World Wide Web Consortium, "Namespaces in XML", W3C XML Namespaces, January 1999, <http://www.w3.org/TR/1999/REC-xml-names-19990114>.
[6] 万维网联盟，“XML中的名称空间”，W3C XML名称空间，1999年1月<http://www.w3.org/TR/1999/REC-xml-names-19990114>.
[7] World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C XML Schema, October 2000, <http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/>.
[7] 万维网联盟，“XML模式第2部分：数据类型”，W3C XML模式，2000年10月<http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/>.
[8] World Wide Web Consortium, "XML Schema Part 1: Structures", W3C XML Schema, October 2000, <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/>.
[8] 万维网联盟，“XML模式第1部分：结构”，W3C XML模式，2000年10月<http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/>.
[9] International Organization for Standardization, "Codes for the representation of names of countries, 3rd edition", ISO Standard 3166, August 1988.
[9] 国际标准化组织，“国家名称表示代码，第3版”，ISO标准3166，1988年8月。
Internet address registries store contact details and other information that may be abused. The XML Schema defined in this document purposefully makes the inclusion of any data in a response an option that is dependent on the needs and policies of the Internet address registry serving the data.
Internet地址注册表存储联系人详细信息和其他可能被滥用的信息。本文档中定义的XML模式有意使响应中包含任何数据成为一种选项，这取决于为数据提供服务的Internet地址注册表的需要和策略。
Combined with the authentication mechanisms of an IRIS transfer protocol, Internet address registries may derive authorization policies to meet their needs without compromising general privacy policies. As an example, the constituents of an Internet address registry may create a policy whereby NOC contact email addresses are only to be available to members of the Internet address registry. To institute this policy, the XML elements for NOC contacts will never appear in a response to a user that has not been authenticated to be a member of the Internet address registry.
结合IRIS传输协议的身份验证机制，Internet地址注册中心可以派生授权策略以满足其需求，而不会影响一般隐私策略。例如，因特网地址登记册的组成部分可以制定一项政策，根据该政策，国家奥委会联系人电子邮件地址只能供因特网地址登记册的成员使用。为了制定此策略，NOC联系人的XML元素永远不会出现在对未经验证为Internet地址注册中心成员的用户的响应中。
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 entity lookup for the contact-handle of 'JN560-RIR1'.
以下是“JN560-RIR1”联系人句柄的实体查找示例。
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: xsi:schemaLocation="urn:ietf:params:xml:ns:iris1 iris.xsd" >
C:
C: <searchSet>
C:
C: <lookupEntity
C: registryType="urn:ietf:params:xml:ns:areg1"
C: entityClass="contact-handle"
C: entityName="JN560-RIR1" />
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: xsi:schemaLocation="urn:ietf:params:xml:ns:iris1 iris.xsd" >
C:
C: <searchSet>
C:
C: <lookupEntity
C: registryType="urn:ietf:params:xml:ns:areg1"
C: entityClass="contact-handle"
C: entityName="JN560-RIR1" />
C:
C: </searchSet>
C:
C: </request>
S: <?xml version="1.0"?>
S: <iris:response
S: xmlns:iris="urn:ietf:params:xml:ns:iris1"
S: <?xml version="1.0"?>
S: <iris:response
S: xmlns:iris="urn:ietf:params:xml:ns:iris1"
S: xmlns="urn:ietf:params:xml:ns:areg1"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
S:
S: <iris:resultSet>
S: <iris:answer>
S:
S: <contact
S: authority="rir.example.net"
S: registryType="areg1"
S: entityClass="contact-handle"
S: entityName="JN560-RIR1">
S:
S: <contactHandle>JN560-RIR1</contactHandle>
S:
S: <commonName>Bob Smurd</commonName>
S:
S: <organization
S: iris:referentType="organization"
S: authority="rir.example.net"
S: registryType="areg1"
S: entityClass="organization-id"
S: entityName="ORGX">
S: <iris:displayName
S: language="en">
S: Organization X, Inc.
S: </iris:displayName>
S: </organization>
S:
S: <phone>
S: <number>+1-703-555-5555</number>
S: <type>office</type>
S: </phone>
S:
S: </contact>
S:
S: </iris:answer>
S: </iris:resultSet>
S:
S: </iris:response>
S: xmlns="urn:ietf:params:xml:ns:areg1"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
S:
S: <iris:resultSet>
S: <iris:answer>
S:
S: <contact
S: authority="rir.example.net"
S: registryType="areg1"
S: entityClass="contact-handle"
S: entityName="JN560-RIR1">
S:
S: <contactHandle>JN560-RIR1</contactHandle>
S:
S: <commonName>Bob Smurd</commonName>
S:
S: <organization
S: iris:referentType="organization"
S: authority="rir.example.net"
S: registryType="areg1"
S: entityClass="organization-id"
S: entityName="ORGX">
S: <iris:displayName
S: language="en">
S: Organization X, Inc.
S: </iris:displayName>
S: </organization>
S:
S: <phone>
S: <number>+1-703-555-5555</number>
S: <type>office</type>
S: </phone>
S:
S: </contact>
S:
S: </iris:answer>
S: </iris:resultSet>
S:
S: </iris:response>
Figure 11: Example 1
图11：示例1
The following example shows a query to find the IP networks containing a given address.
下面的示例显示了一个查找包含给定地址的IP网络的查询。
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: <findNetworksByAddress
C: xmlns="urn:ietf:params:xml:ns:areg1">
C:
C: <ipv4Address>
C: <start>192.0.2.134</start>
C: </ipv4Address>
C:
C: <specificity
C: allowEquivalences="true"
C: >one-level-less-specific</specificity>
C:
C: </findNetworksByAddress>
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: <findNetworksByAddress
C: xmlns="urn:ietf:params:xml:ns:areg1">
C:
C: <ipv4Address>
C: <start>192.0.2.134</start>
C: </ipv4Address>
C:
C: <specificity
C: allowEquivalences="true"
C: >one-level-less-specific</specificity>
C:
C: </findNetworksByAddress>
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: <areg:ipv4Network
S: xmlns="urn:ietf:params:xml:ns:areg1"
S: xmlns:areg="urn:ietf:params:xml:ns:areg1"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:areg1 areg.xsd"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-128-1" >
S: <networkHandle>
S: NET-192-0-2-128-1
S: </networkHandle>
S: <name>
S: UU-192-0-2-D6
S: </name>
S: <startAddress>
S: 192.0.2.128
S: </startAddress>
S: <endAddress>
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: <areg:ipv4Network
S: xmlns="urn:ietf:params:xml:ns:areg1"
S: xmlns:areg="urn:ietf:params:xml:ns:areg1"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:areg1 areg.xsd"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-128-1" >
S: <networkHandle>
S: NET-192-0-2-128-1
S: </networkHandle>
S: <name>
S: UU-192-0-2-D6
S: </name>
S: <startAddress>
S: 192.0.2.128
S: </startAddress>
S: <endAddress>
S: 192.0.2.255
S: </endAddress>
S: <networkType>reassigned</networkType>
S: <organization
S: iris:referentType="areg:organization"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="organization-id" entityName="ORGX">
S: <iris:displayName language="en">
S: Organization X, Inc.
S: </iris:displayName>
S: </organization>
S: <parent
S: iris:referentType="areg:ipv4Network"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-0-1"/>
S: <techContact
S: iris:referentType="areg:contact"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="contact-handle" entityName="JN560-RIR1">
S: <iris:displayName language="en">
S: Smurd, Bob
S: </iris:displayName>
S: </techContact>
S: <registrationDate>
S: 2002-11-18T00:00:00-00:00
S: </registrationDate>
S: <lastUpdatedDate>
S: 2002-11-18T00:00:00-00:00
S: </lastUpdatedDate>
S: <iris:seeAlso
S: iris:referentType="ANY"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="local" entityName="portability-notice"/>
S: </areg:ipv4Network>
S: <areg:ipv4Network
S: xmlns="urn:ietf:params:xml:ns:areg1"
S: xmlns:areg="urn:ietf:params:xml:ns:areg1"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:areg1 areg.xsd"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-0-2" >
S: <networkHandle>
S: NET-192-0-2-0-2
S: </networkHandle>
S: <name>
S: UU-192-0-2-0-D5
S: </name>
S: <startAddress>
S: 192.0.2.0
S: 192.0.2.255
S: </endAddress>
S: <networkType>reassigned</networkType>
S: <organization
S: iris:referentType="areg:organization"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="organization-id" entityName="ORGX">
S: <iris:displayName language="en">
S: Organization X, Inc.
S: </iris:displayName>
S: </organization>
S: <parent
S: iris:referentType="areg:ipv4Network"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-0-1"/>
S: <techContact
S: iris:referentType="areg:contact"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="contact-handle" entityName="JN560-RIR1">
S: <iris:displayName language="en">
S: Smurd, Bob
S: </iris:displayName>
S: </techContact>
S: <registrationDate>
S: 2002-11-18T00:00:00-00:00
S: </registrationDate>
S: <lastUpdatedDate>
S: 2002-11-18T00:00:00-00:00
S: </lastUpdatedDate>
S: <iris:seeAlso
S: iris:referentType="ANY"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="local" entityName="portability-notice"/>
S: </areg:ipv4Network>
S: <areg:ipv4Network
S: xmlns="urn:ietf:params:xml:ns:areg1"
S: xmlns:areg="urn:ietf:params:xml:ns:areg1"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:areg1 areg.xsd"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-0-2" >
S: <networkHandle>
S: NET-192-0-2-0-2
S: </networkHandle>
S: <name>
S: UU-192-0-2-0-D5
S: </name>
S: <startAddress>
S: 192.0.2.0
S: </startAddress>
S: <endAddress>
S: 192.0.2.255
S: </endAddress>
S: <networkType>direct allocation</networkType>
S: <nameServer>auth03.ns.example.org</nameServer>
S: <nameServer>auth00.ns.example.org</nameServer>
S: <organization
S: iris:referentType="areg:organization"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="organization-id" entityName="ORGY">
S: <iris:displayName language="en">
S: Organization Y, Inc.
S: </iris:displayName>
S: </organization>
S: <parent
S: iris:referentType="areg:ipv4Network"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-0-1"/>
S: <techContact
S: iris:referentType="areg:contact"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="contact-handle" entityName="OA12-RIR1" />
S: <registrationDate>
S: 2000-10-27T00:00:00-00:00
S: </registrationDate>
S: <lastUpdatedDate>
S: 2002-02-13T00:00:00-00:00
S: </lastUpdatedDate>
S: <iris:seeAlso
S: iris:referentType="ANY"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="local" entityName="portability-notice"/>
S: </areg:ipv4Network>
S: </iris:answer>
S: <iris:additional>
S: <iris:simpleEntity
S: authority="rir.example.net" registryType="areg1"
S: entityClass="local" entityName="portability-notice" >
S: <iris:property name="portability" language="en">
S: Addresses within this block are non-portable.
S: </iris:property>
S: </startAddress>
S: <endAddress>
S: 192.0.2.255
S: </endAddress>
S: <networkType>direct allocation</networkType>
S: <nameServer>auth03.ns.example.org</nameServer>
S: <nameServer>auth00.ns.example.org</nameServer>
S: <organization
S: iris:referentType="areg:organization"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="organization-id" entityName="ORGY">
S: <iris:displayName language="en">
S: Organization Y, Inc.
S: </iris:displayName>
S: </organization>
S: <parent
S: iris:referentType="areg:ipv4Network"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-0-1"/>
S: <techContact
S: iris:referentType="areg:contact"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="contact-handle" entityName="OA12-RIR1" />
S: <registrationDate>
S: 2000-10-27T00:00:00-00:00
S: </registrationDate>
S: <lastUpdatedDate>
S: 2002-02-13T00:00:00-00:00
S: </lastUpdatedDate>
S: <iris:seeAlso
S: iris:referentType="ANY"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="local" entityName="portability-notice"/>
S: </areg:ipv4Network>
S: </iris:answer>
S: <iris:additional>
S: <iris:simpleEntity
S: authority="rir.example.net" registryType="areg1"
S: entityClass="local" entityName="portability-notice" >
S: <iris:property name="portability" language="en">
S: Addresses within this block are non-portable.
S: </iris:property>
S: </iris:simpleEntity>
S: </iris:additional>
S: </iris:resultSet>
S:
S: </iris:response>
S: </iris:simpleEntity>
S: </iris:additional>
S: </iris:resultSet>
S:
S: </iris:response>
Figure 12: Example 2
图12：示例2
This section includes examples to clarify specificity options for network and ASN searches.
本节包括澄清网络和ASN搜索的特定选项的示例。
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Contents of the DB
数据库的内容
Figure 13: Specificity Example 1
图13：特异性示例1
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - | 192.0.2.0 - 192.0.2.9
Query|- - - - - - - | 192.0.2.0 - 192.0.2.9
Exact match (1)
精确匹配（1）
Result: C
结果：C
Figure 14: Specificity Example 2
图14：特异性示例2
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - - | 192.0.2.0 - 192.0.2.12
Query|- - - - - - - - | 192.0.2.0 - 192.0.2.12
Exact match (2)
精确匹配（2）
Result: None
结果：无
Figure 15: Specificity Example 3
图15：示例3
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
All more specifics, allowEquivalences = false
更多细节，允许等效性=假
Result: C, F, & G (A is not included; exact match)
结果：C、F和G（不包括A；完全匹配）
Figure 16: Specificity Example 4
图16：特异性示例4
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
All more specifics, allowEquivalences = true
更详细地说，AlloweEquivalences=true
Result: A, C, F, & G (A is included; exact match)
结果：A、C、F和G（包括A；完全匹配）
Figure 17: Specificity Example 5
图17：特异性示例5
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
One level more specifics, allowEquivalences = false
更详细一级，允许等效性=假
Result: C
结果：C
Figure 18: Specificity Example 6
图18：特异性示例6
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
One level more specifics, allowEquivalences = true
更详细一级，允许等效性=真
Result: A
结果：A
Figure 19: Specificity Example 7
图19：示例7
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query |- - | 192.0.2.6 - 192.0.2.9
查询|-| 192.0.2.6-192.0.2.9
All less specifics, allowEquivalences = true
所有细节较少，允许等效性=真
Result: A, C, & G (G is included; exact match)
结果：A、C和G（包括G；精确匹配）
Figure 20: Specificity Example 8
图20：示例8
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query |- - | 192.0.2.6 - 192.0.2.9
查询|-| 192.0.2.6-192.0.2.9
All less specifics, allowEquivalences = false
所有不太详细的内容，允许等效性=假
Result: A & C (G is not included; exact match)
结果：A&C（不包括G；精确匹配）
Figure 21: Specificity Example 9
图21：示例9
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query |- - | 192.0.2.6 - 192.0.2.9
查询|-| 192.0.2.6-192.0.2.9
One level less specifics, allowEquivalences = true
少一级细节，允许等效性=真
Result: G (the exact match)
结果：G（精确匹配）
Figure 22: Specificity Example 10
图22：特异性示例10
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query |- - | 192.0.2.6 - 192.0.2.9
查询|-| 192.0.2.6-192.0.2.9
One level less specifics, allowEquivalences = false
少一级细节，允许等效性=假
Result: C
结果：C
Figure 23: Specificity Example 11
图23：示例11
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - | 192.0.2.0 - 192.0.2.8
Query|- - - - - - | 192.0.2.0 - 192.0.2.8
One level less specifics, allowEquivalences = false or true
少一级细节，允许等效性=假或真
Result: C
结果：C
Figure 24: Specificity Example 12
图24：特异性示例12
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query = E
Query = E
Find parent (Query argument is a handle)
查找父项（查询参数是句柄）
Result: D
结果：D
Figure 25: Specificity Example 13
图25：特异性示例13
A |------------------| 192.0.2.0 - 192.0.2.15
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
G |----| 192.0.2.6 - 192.0.2.9
Query = D
Query = D
Find child (Query argument is a handle)
查找子项（查询参数是句柄）
Result: E
结果：E
Figure 26: Specificity Example 14
图26：特异性示例14
David Blacka and Tim Christensen made substantial contributions to this document.
David Black和Tim Christensen对本文件做出了重大贡献。
Eric Hall, William Leibzon, April Marine, George Michaelson, Tim Christensen Cathy Murphy, Andrei Robachevsky, Marcos Sanz, Frederico Neves, Ted Hardie, and many others contributed constructively in the mailing list discussions and IETF Meeting sessions.
Eric Hall、William Leibzon、April Marine、George Michaelson、Tim Christensen Cathy Murphy、Andrei Robachevsky、Marcos Sanz、Frederico Neves、Ted Hardie和许多其他人在邮件列表讨论和IETF会议上做出了建设性的贡献。
Authors' Addresses
作者地址
Engin Gunduz RIPE NCC Singel 258 Amsterdam 1016AB The Netherlands
Engin Gunduz成熟NCC Singel 258阿姆斯特丹1016AB荷兰
Phone: +31 20 535 4444
EMail: e.gunduz@computer.org
Phone: +31 20 535 4444
EMail: e.gunduz@computer.org
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: andy@hxr.us
Phone: +1 703 948 3382
EMail: andy@hxr.us
Shane W. Kerr RIPE NCC Singel 258 Amsterdam 1016AB The Netherlands
Shane W.Kerr NCC Singel 258阿姆斯特丹1016AB荷兰
Phone: +31 20 535 4444
EMail: shane@time-travellers.org
Phone: +31 20 535 4444
EMail: shane@time-travellers.org
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
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 procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。