Internet Engineering Task Force (IETF) L. Zhou
Request for Comments: 7485 N. Kong
Category: Informational S. Shen
ISSN: 2070-1721 CNNIC
S. Sheng
ICANN
A. Servin
LACNIC
March 2015
Internet Engineering Task Force (IETF) L. Zhou
Request for Comments: 7485 N. Kong
Category: Informational S. Shen
ISSN: 2070-1721 CNNIC
S. Sheng
ICANN
A. Servin
LACNIC
March 2015
Inventory and Analysis of WHOIS Registration Objects
WHOIS登记对象的清查与分析
Abstract
摘要
WHOIS output objects from registries, including both Regional Internet Registries (RIRs) and Domain Name Registries (DNRs), were collected and analyzed. This document describes the process and results of the statistical analysis of existing WHOIS information. The purpose of this document is to build an object inventory to facilitate discussions of data objects included in Registration Data Access Protocol (RDAP) responses.
收集并分析了来自注册中心（包括区域互联网注册中心（RIR）和域名注册中心（DNR））的WHOIS输出对象。本文件描述了现有WHOIS信息的统计分析过程和结果。本文档的目的是建立对象清单，以便于讨论注册数据访问协议（RDAP）响应中包含的数据对象。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7485.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7485.
Copyright Notice
版权公告
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2015 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. RIR Objects Analysis . . . . . . . . . . . . . . . . . . . . 7
4.1. WHOIS Data for Organizations Holding a Resource . . . . . 7
4.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . . . 9
4.3. WHOIS Data for IP Addresses . . . . . . . . . . . . . . . 10
4.4. WHOIS Data for ASNs . . . . . . . . . . . . . . . . . . . 12
4.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 13
5. DNR Object Analysis . . . . . . . . . . . . . . . . . . . . . 14
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 14
5.2. Public Objects . . . . . . . . . . . . . . . . . . . . . 14
5.2.1. WHOIS Data for Domains . . . . . . . . . . . . . . . 15
5.2.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . 16
5.2.2.1. Registrant . . . . . . . . . . . . . . . . . . . 16
5.2.2.2. Admin Contact . . . . . . . . . . . . . . . . . . 18
5.2.2.3. Tech Contact . . . . . . . . . . . . . . . . . . 19
5.2.2.4. Billing Contact . . . . . . . . . . . . . . . . . 20
5.2.3. WHOIS Data for Nameservers . . . . . . . . . . . . . 21
5.2.4. WHOIS Data for Registrars . . . . . . . . . . . . . . 21
5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 22
5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 24
5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 24
5.4.2. Data Element Analysis . . . . . . . . . . . . . . . . 26
5.4.3. Label Analysis . . . . . . . . . . . . . . . . . . . 28
5.4.4. Analysis of Other Objects . . . . . . . . . . . . . . 28
5.5. Limitations . . . . . . . . . . . . . . . . . . . . . . . 29
6. Reference Extension Objects . . . . . . . . . . . . . . . . . 30
6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 30
6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 30
7. Security Considerations . . . . . . . . . . . . . . . . . . . 30
8. Informative References . . . . . . . . . . . . . . . . . . . 31
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. RIR Objects Analysis . . . . . . . . . . . . . . . . . . . . 7
4.1. WHOIS Data for Organizations Holding a Resource . . . . . 7
4.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . . . 9
4.3. WHOIS Data for IP Addresses . . . . . . . . . . . . . . . 10
4.4. WHOIS Data for ASNs . . . . . . . . . . . . . . . . . . . 12
4.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 13
5. DNR Object Analysis . . . . . . . . . . . . . . . . . . . . . 14
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 14
5.2. Public Objects . . . . . . . . . . . . . . . . . . . . . 14
5.2.1. WHOIS Data for Domains . . . . . . . . . . . . . . . 15
5.2.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . 16
5.2.2.1. Registrant . . . . . . . . . . . . . . . . . . . 16
5.2.2.2. Admin Contact . . . . . . . . . . . . . . . . . . 18
5.2.2.3. Tech Contact . . . . . . . . . . . . . . . . . . 19
5.2.2.4. Billing Contact . . . . . . . . . . . . . . . . . 20
5.2.3. WHOIS Data for Nameservers . . . . . . . . . . . . . 21
5.2.4. WHOIS Data for Registrars . . . . . . . . . . . . . . 21
5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 22
5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 24
5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 24
5.4.2. Data Element Analysis . . . . . . . . . . . . . . . . 26
5.4.3. Label Analysis . . . . . . . . . . . . . . . . . . . 28
5.4.4. Analysis of Other Objects . . . . . . . . . . . . . . 28
5.5. Limitations . . . . . . . . . . . . . . . . . . . . . . . 29
6. Reference Extension Objects . . . . . . . . . . . . . . . . . 30
6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 30
6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 30
7. Security Considerations . . . . . . . . . . . . . . . . . . . 30
8. Informative References . . . . . . . . . . . . . . . . . . . 31
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
Regional Internet Registries (RIRs) and Domain Name Registries (DNRs) have historically maintained a lookup service to permit public access to some portion of the registry database. Most registries offer the service via the WHOIS protocol [RFC3912], with additional services being offered via World Wide Web pages, bulk downloads, and other services, such as Routing Policy Specification Language (RPSL) [RFC2622].
区域互联网注册中心（RIR）和域名注册中心（DNR）在历史上一直维护查找服务，以允许公众访问注册数据库的某些部分。大多数注册中心通过WHOIS协议[RFC3912]提供服务，通过万维网页面、批量下载和其他服务（如路由策略规范语言（RPSL）[RFC2622]提供附加服务。
Although the WHOIS protocol is widely adopted and supported, it has several shortcomings that limit its usefulness to the evolving needs of the Internet community. Specifically:
虽然WHOIS协议被广泛采用和支持，但它有几个缺点，限制了它对互联网社区不断变化的需求的有用性。明确地：
o It has no query and response format.
o 它没有查询和响应格式。
o It does not support user authentication or access control for differentiated access.
o 它不支持区分访问的用户身份验证或访问控制。
o It has not been internationalized and thus does not consistently support Internationalized Domain Names (IDNs) as described in [RFC5890].
o 它尚未国际化，因此不一贯支持[RFC5890]中所述的国际化域名（IDN）。
This document records an inventory of registry data objects to facilitate discussions of registration data objects. The Registration Data Access Protocol (RDAP) ([RFC7480], [RFC7482], [RFC7483], and [RFC7484]) was developed using this inventory as input.
本文件记录了登记册数据对象的清单，以便于讨论登记数据对象。注册数据访问协议（RDAP）（[RFC7480]、[RFC7482]、[RFC7483]和[RFC7484]）是使用该清单作为输入开发的。
In the number space, there were altogether five RIRs. Although all RIRs provided information about IP addresses, Autonomous System Numbers (ASNs), and contacts, the data model used was different for each RIR. In the domain name space, there were over 200 country code Top-Level Domains (ccTLDs) and over 400 generic Top-Level Domains (gTLDs) when this document was published. Different Domain Name Registries may have different WHOIS response objects and formats. A common understanding of all these data formats was critical to construct a single data model for each object.
在数字空间中，总共有五个里尔。尽管所有RIR都提供了有关IP地址、自治系统号码（ASN）和联系人的信息，但每个RIR使用的数据模型不同。在域名领域，本文件发布时，共有200多个国家代码顶级域（CCTLD）和400多个通用顶级域（GTLD）。不同的域名注册中心可能有不同的WHOIS响应对象和格式。对所有这些数据格式的共同理解对于为每个对象构建单个数据模型至关重要。
This document describes the WHOIS data collection procedures and gives an inventory analysis of data objects based on the collected data from the five RIRs, 106 ccTLDs, and 18 gTLDs from DNRs. The RIR data objects are classified by the five RIRs into IP address, ASN, person or contact, and the organization that held the resource. According to SPECIFICATION 4 ("SPECIFICATION FOR REGISTRATION DATA PUBLICATION SERVICES") of the new gTLD applicant guidebook [ICANN.AGB-201206] and the Extensible Provisioning Protocol (EPP) ([RFC5730], [RFC5731], [RFC5732], and [RFC5733]), the DNR data
本文件描述了WHOIS数据收集程序，并根据从5个RIR、106个CCTLD和18个DNR GTLD收集的数据对数据对象进行了清单分析。RIR数据对象由五个RIR分类为IP地址、ASN、个人或联系人以及持有资源的组织。根据新gTLD申请人指南[ICANN.AGB-201206]的规范4（“注册数据发布服务规范”）和可扩展资源调配协议（EPP）（[RFC5730]、[RFC5731]、[RFC5732]和[RFC5733]），DNR数据
objects are classified by whether they relate to the domain, contact, nameserver, or registrar. Objects that do not belong to the categories above are viewed as privately specified objects. In this document, there is no intent to analyze all the query and response types that exist in RIRs and DNRs. The most common query objects are discussed, but other objects such as RPSL data structures used by Internet Routing Registries (IRRs) can be documented later if the community feels it is necessary.
对象按是否与域、联系人、名称服务器或注册器相关进行分类。不属于上述类别的对象将被视为私人指定的对象。在本文档中，无意分析RIRs和DNRs中存在的所有查询和响应类型。讨论了最常见的查询对象，但如果社区认为有必要，可以稍后记录Internet路由注册中心（IRR）使用的其他对象，如RPSL数据结构。
o Data element - The name of a specific response object.
o 数据元素-特定响应对象的名称。
o Label - The name given to a particular data element; it may vary between registries.
o 标签-指定给特定数据元素的名称；登记处之间可能有所不同。
o Most popular label - The label that is most supported by the registries.
o 最受欢迎的标签-注册中心最支持的标签。
o Number of labels - The number of different labels.
o 标签数量-不同标签的数量。
o No. of TLDs - The number of registries that support a certain data element.
o TLD数量-支持某个数据元素的注册表数量。
WHOIS information, including port 43 response and web response data, was collected between July 9, 2012, and July 20, 2012, following the procedures described below.
WHOIS信息，包括端口43响应和web响应数据，是在2012年7月9日至2012年7月20日期间按照下述程序收集的。
(1) First, find the RIR WHOIS servers of the five RIRs, which are AFRINIC, APNIC, ARIN, LACNIC, and RIPE NCC. All the RIRs provide information about IP addresses, ASNs, and contacts.
(1) 首先，找到五个RIR的RIR WHOIS服务器，它们是AFRINIC、APNIC、ARIN、LACNIC和成熟的NCC。所有RIR都提供有关IP地址、ASN和联系人的信息。
(2) Query the corresponding IP addresses, ASNs, contacts, and organizations registered in the five RIRs. Then, make a comparative analysis of the response data.
(2) 查询在五个RIR中注册的相应IP地址、ASN、联系人和组织。然后，对响应数据进行对比分析。
(3) Group together the data elements that have the same meaning but use different labels.
(3) 将具有相同含义但使用不同标签的数据元素组合在一起。
DNR object collection process:
DNR对象收集过程：
(1) A programming script was applied to collect port 43 response data from 294 ccTLDs. "nic.ccTLD" was used as the query string, which is usually registered in a domain registry. Responses for 106 ccTLDs were received. 18 gTLDs' port 43 response data was collected from their contracts with ICANN. Thus, the sample size of port 43 WHOIS response data is 124 registries in total.
(1) 应用编程脚本从294个CCTLD收集端口43响应数据。“nic.ccTLD”用作查询字符串，该字符串通常在域注册表中注册。收到了106个国家/地区的答复。18 gTLDs的端口43响应数据是从其与ICANN的合同中收集的。因此，端口43 WHOIS响应数据的样本量总共为124个注册表。
(2) WHOIS data from the web was collected manually from the 124 registries that send port 43 WHOIS responses.
(2) 来自web的WHOIS数据是从发送端口43 WHOIS响应的124个注册中心手动收集的。
(3) Some of the response that which were collected by the program did not seem to be correct, so data for the top 10 ccTLD registries, like .de, .eu, and .uk, was re-verified by querying domain names other than "nic.ccTLD".
(3) 程序收集到的一些响应似乎不正确，因此通过查询“nic.ccTLD”以外的域名，重新验证了前10个ccTLD注册中心（如.de、.eu和.uk）的数据。
(4) In accordance with SPECIFICATION 4 of the new gTLD applicant guidebook [ICANN.AGB-201206] and EPP ([RFC5730], [RFC5731], [RFC5732] and [RFC5733]), the response data objects are classified into public and other data objects. Public data objects are those that are defined in the above references. Other objects are those that are privately specified data elements or objects in different registries.
(4) 根据新gTLD申请人指南[ICANN.AGB-201206]和EPP（[RFC5730]、[RFC5731]、[RFC5732]和[RFC5733]）的规范4，响应数据对象分为公共数据对象和其他数据对象。公共数据对象是在上述引用中定义的对象。其他对象是私人指定的数据元素或不同注册表中的对象。
(5) Data elements with the same meaning, but using different labels, were grouped together. The number of registries that support each data element is shown in the "No. of TLDs" column.
(5) 具有相同含义但使用不同标签的数据元素被分组在一起。“TLD数量”列中显示了支持每个数据元素的注册表数量。
Table 1 shows the organization objects of the five RIRs.
表1显示了五个RIR的组织对象。
+--------------+------------+-----+----------+-----------+------------+
| RIR | AFRINIC |APNIC| ARIN | LACNIC | RIPE NCC |
| Objects | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Organization |organisation| NA | Name | Owner | org-name |
| name | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Organization | org-name | NA | Handle | owner-id |organisation|
| ID | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Company | NA | NA | Company | NA | NA |
+--------------+------------+-----+----------+-----------+------------+
| Name of | NA | NA | NA |responsible| NA |
| person | | | | | |
| responsible | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Type of | org-type | NA | NA | NA | org-type |
| organization | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Country | country | NA | country | country | country |
+--------------+------------+-----+----------+-----------+------------+
| Postal | address | NA | address | address | address |
| Address | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| City | NA | NA | city | NA | address |
+--------------+------------+-----+----------+-----------+------------+
| State | NA | NA | StateProv| NA | address |
+--------------+------------+-----+----------+-----------+------------+
| Postal | NA | NA |PostalCode| NA | address |
| Code | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Phone | phone | NA | NA | phone | phone |
+--------------+------------+-----+----------+-----------+------------+
| Fax Number | fax-no | NA | NA | NA | fax-no |
+--------------+------------+-----+----------+-----------+------------+
| ID of | admin-c | NA | Admin | owner-c | admin-c |
|administrative| | | POC | | |
| contact | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| ID of | tech-c | NA | Tech POC | tech-c | tech-c |
| technical | | | | | |
| contact | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| RIR | AFRINIC |APNIC| ARIN | LACNIC | RIPE NCC |
| Objects | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Organization |organisation| NA | Name | Owner | org-name |
| name | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Organization | org-name | NA | Handle | owner-id |organisation|
| ID | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Company | NA | NA | Company | NA | NA |
+--------------+------------+-----+----------+-----------+------------+
| Name of | NA | NA | NA |responsible| NA |
| person | | | | | |
| responsible | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Type of | org-type | NA | NA | NA | org-type |
| organization | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Country | country | NA | country | country | country |
+--------------+------------+-----+----------+-----------+------------+
| Postal | address | NA | address | address | address |
| Address | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| City | NA | NA | city | NA | address |
+--------------+------------+-----+----------+-----------+------------+
| State | NA | NA | StateProv| NA | address |
+--------------+------------+-----+----------+-----------+------------+
| Postal | NA | NA |PostalCode| NA | address |
| Code | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Phone | phone | NA | NA | phone | phone |
+--------------+------------+-----+----------+-----------+------------+
| Fax Number | fax-no | NA | NA | NA | fax-no |
+--------------+------------+-----+----------+-----------+------------+
| ID of | admin-c | NA | Admin | owner-c | admin-c |
|administrative| | | POC | | |
| contact | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| ID of | tech-c | NA | Tech POC | tech-c | tech-c |
| technical | | | | | |
| contact | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Maintainer | mnt-ref | NA | NOC POC | NA | mnt-ref |
| organization | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Maintainer | mnt-by | NA | Abuse | NA | mnt-by |
| object | | | POC | | |
+--------------+------------+-----+----------+-----------+------------+
| Remarks | remarks | NA | NA | NA | remarks |
+--------------+------------+-----+----------+-----------+------------+
| Date of | Changed | NA | RegDate | created | Changed |
| record | | | | | |
| creation | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Date of | changed | NA | Updated | changed | changed |
| record | | | | | |
| changed | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| List of | NA | NA | NA | list of | NA |
| resources | | | | resources | |
+--------------+------------+-----+----------+-----------+------------+
| Source | source | NA | NA | NA | source |
+--------------+------------+-----+----------+-----------+------------+
| Reference | NA | NA | Ref | NA | NA |
+--------------+------------+-----+----------+-----------+------------+
+--------------+------------+-----+----------+-----------+------------+
| Maintainer | mnt-ref | NA | NOC POC | NA | mnt-ref |
| organization | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Maintainer | mnt-by | NA | Abuse | NA | mnt-by |
| object | | | POC | | |
+--------------+------------+-----+----------+-----------+------------+
| Remarks | remarks | NA | NA | NA | remarks |
+--------------+------------+-----+----------+-----------+------------+
| Date of | Changed | NA | RegDate | created | Changed |
| record | | | | | |
| creation | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| Date of | changed | NA | Updated | changed | changed |
| record | | | | | |
| changed | | | | | |
+--------------+------------+-----+----------+-----------+------------+
| List of | NA | NA | NA | list of | NA |
| resources | | | | resources | |
+--------------+------------+-----+----------+-----------+------------+
| Source | source | NA | NA | NA | source |
+--------------+------------+-----+----------+-----------+------------+
| Reference | NA | NA | Ref | NA | NA |
+--------------+------------+-----+----------+-----------+------------+
Table 1. WHOIS Data for Organizations Holding a Resource
表1。持有资源的组织的WHOIS数据
Table 2 shows the contact objects of the five RIRs.
表2显示了五个RIR的接触对象。
+--------------+---------+---------+------------+---------+---------+
| Data Element | AFRINIC | APNIC | ARIN | LACNIC | RIPE |
| | | | | | NCC |
+--------------+---------+---------+------------+---------+---------+
| Name | person | person | Name | person | person |
+--------------+---------+---------+------------+---------+---------+
| Company | NA | NA | Company | NA | NA |
+--------------+---------+---------+------------+---------+---------+
| Postal | address | address | Address | address | address |
| Address | | | | | |
+--------------+---------+---------+------------+---------+---------+
| City | NA | NA | City | NA | address |
+--------------+---------+---------+------------+---------+---------+
| State | NA | NA | StateProv | NA | address |
+--------------+---------+---------+------------+---------+---------+
| Postal Code | NA | NA | PostalCode | NA | address |
+--------------+---------+---------+------------+---------+---------+
| Country | NA | country | Country | country | NA |
+--------------+---------+---------+------------+---------+---------+
| Phone | phone | phone | Mobile | phone | phone |
+--------------+---------+---------+------------+---------+---------+
| Fax Number | fax-no | fax-no | Fax | NA | fax-no |
+--------------+---------+---------+------------+---------+---------+
| Email | e-mail | e-mail | Email | e-mail | NA |
+--------------+---------+---------+------------+---------+---------+
| ID | nic-hdl | nic-hdl | Handle | nic-hdl | nic-hdl |
+--------------+---------+---------+------------+---------+---------+
| Remarks | remarks | remarks | Remarks | NA | remarks |
+--------------+---------+---------+------------+---------+---------+
| Notify | notify | notify | NA | NA | notify |
+--------------+---------+---------+------------+---------+---------+
| ID of | mnt-by | mnt-by | NA | NA | mnt-by |
| maintainer | | | | | |
+--------------+---------+---------+------------+---------+---------+
| Registration | changed | NA | RegDate | created | changed |
| Date | | | | | |
+--------------+---------+---------+------------+---------+---------+
| Registration | changed | changed | Updated | changed | changed |
| update | | | | | |
+--------------+---------+---------+------------+---------+---------+
| Source | source | source | NA | NA | source |
+--------------+---------+---------+------------+---------+---------+
| Data Element | AFRINIC | APNIC | ARIN | LACNIC | RIPE |
| | | | | | NCC |
+--------------+---------+---------+------------+---------+---------+
| Name | person | person | Name | person | person |
+--------------+---------+---------+------------+---------+---------+
| Company | NA | NA | Company | NA | NA |
+--------------+---------+---------+------------+---------+---------+
| Postal | address | address | Address | address | address |
| Address | | | | | |
+--------------+---------+---------+------------+---------+---------+
| City | NA | NA | City | NA | address |
+--------------+---------+---------+------------+---------+---------+
| State | NA | NA | StateProv | NA | address |
+--------------+---------+---------+------------+---------+---------+
| Postal Code | NA | NA | PostalCode | NA | address |
+--------------+---------+---------+------------+---------+---------+
| Country | NA | country | Country | country | NA |
+--------------+---------+---------+------------+---------+---------+
| Phone | phone | phone | Mobile | phone | phone |
+--------------+---------+---------+------------+---------+---------+
| Fax Number | fax-no | fax-no | Fax | NA | fax-no |
+--------------+---------+---------+------------+---------+---------+
| Email | e-mail | e-mail | Email | e-mail | NA |
+--------------+---------+---------+------------+---------+---------+
| ID | nic-hdl | nic-hdl | Handle | nic-hdl | nic-hdl |
+--------------+---------+---------+------------+---------+---------+
| Remarks | remarks | remarks | Remarks | NA | remarks |
+--------------+---------+---------+------------+---------+---------+
| Notify | notify | notify | NA | NA | notify |
+--------------+---------+---------+------------+---------+---------+
| ID of | mnt-by | mnt-by | NA | NA | mnt-by |
| maintainer | | | | | |
+--------------+---------+---------+------------+---------+---------+
| Registration | changed | NA | RegDate | created | changed |
| Date | | | | | |
+--------------+---------+---------+------------+---------+---------+
| Registration | changed | changed | Updated | changed | changed |
| update | | | | | |
+--------------+---------+---------+------------+---------+---------+
| Source | source | source | NA | NA | source |
+--------------+---------+---------+------------+---------+---------+
| Reference | NA | NA | Ref | NA | NA |
+--------------+---------+---------+------------+---------+---------+
+--------------+---------+---------+------------+---------+---------+
| Reference | NA | NA | Ref | NA | NA |
+--------------+---------+---------+------------+---------+---------+
Table 2. WHOIS Data for Contacts
表2。谁是联系人的数据
Table 4 shows the IP address objects of the five RIRs.
表4显示了五个RIR的IP地址对象。
Note: Due to the 72-character limit on line length, strings in some cells of the table are split into two or more parts, which are placed on separate lines within the same cell. A hyphen in the final position of a string indicates that the string has been split due to the length limit.
注意：由于行长度限制为72个字符，表中某些单元格中的字符串被拆分为两个或多个部分，这些部分放在同一单元格中的单独行上。字符串最后位置的连字符表示该字符串由于长度限制而被拆分。
+----------+----------+----------+
| Adminis- | | abuse-- |
| trative | admin-c | mailbox |
| contact | | |
+----------+----------+----------+
+----------+----------+----------+
| Adminis- | | abuse-- |
| trative | admin-c | mailbox |
| contact | | |
+----------+----------+----------+
Table 3. Example of String Splitting
表3。字符串拆分示例
For instance, the original strings in the cells of Table 3 are "Administrative contact", "admin-c", and "abuse-mailbox", respectively.
例如，表3单元格中的原始字符串分别是“管理联系人”、“管理员-c”和“滥用邮箱”。
+------------+--------+----------+--------------+--------+-------------+
| Data | AFRINIC| APNIC | ARIN | LACNIC | RIPE NCC |
| Element | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| IP | inetnum| inetnum | NetRange | NA | inetnum |
| address | | | | | |
| range | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| IPv6 |inet6num| inet6num | CIDR |inetnum | inet6num |
| address | | | | | |
| range | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Description| descr | descr | NetName | NA | descr |
| | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Remarks | remarks| remarks | NA | NA | remarks |
| | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Origin AS | NA | NA | OriginAS |OriginAS| NA |
| | | | |(future)| |
+------------+--------+----------+--------------+--------+-------------+
| Network | netname| netname | NetHandle |inetrev | netname |
| name/ID | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Maintainer | mnt-by | NA | NA | NA | mnt-by |
| Object | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Maintainer | mnt-- | NA | NA | NA | NA |
| Sub- | lower | | | | |
| assignments| | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Adminis- | admin-c| admin-c | OrgId | ownerid| admin-c |
| trative | | | | | |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Parent | parent | NA | Parent | NA | NA |
| range | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Status | status | status | NetType | status | status |
+------------+--------+----------+--------------+--------+-------------+
|Registration| changed| NA | RegDate | created| changed |
| Date | | | | | |
+------------+--------+----------+--------------+--------+-------------+
|Registration| changed| changed | Updated | changed| changed |
| update | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Reference | NA | NA | Ref | NA | NA |
+------------+--------+----------+--------------+--------+-------------+
| Data | AFRINIC| APNIC | ARIN | LACNIC | RIPE NCC |
| Element | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| IP | inetnum| inetnum | NetRange | NA | inetnum |
| address | | | | | |
| range | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| IPv6 |inet6num| inet6num | CIDR |inetnum | inet6num |
| address | | | | | |
| range | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Description| descr | descr | NetName | NA | descr |
| | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Remarks | remarks| remarks | NA | NA | remarks |
| | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Origin AS | NA | NA | OriginAS |OriginAS| NA |
| | | | |(future)| |
+------------+--------+----------+--------------+--------+-------------+
| Network | netname| netname | NetHandle |inetrev | netname |
| name/ID | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Maintainer | mnt-by | NA | NA | NA | mnt-by |
| Object | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Maintainer | mnt-- | NA | NA | NA | NA |
| Sub- | lower | | | | |
| assignments| | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Adminis- | admin-c| admin-c | OrgId | ownerid| admin-c |
| trative | | | | | |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Parent | parent | NA | Parent | NA | NA |
| range | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Status | status | status | NetType | status | status |
+------------+--------+----------+--------------+--------+-------------+
|Registration| changed| NA | RegDate | created| changed |
| Date | | | | | |
+------------+--------+----------+--------------+--------+-------------+
|Registration| changed| changed | Updated | changed| changed |
| update | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Reference | NA | NA | Ref | NA | NA |
+------------+--------+----------+--------------+--------+-------------+
| ID | org | NA | OrgId | owner |organisation |
|organization| | | | | |
|holding the | | | | | |
| resource | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Referral | NA | NA |ReferralServer| NA | NA |
| server | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Technical | tech-c | tech-c |OrgTechHandle | tech-c | tech-c |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Abuse | NA | NA |OrgAbuseHandle| abuse-c|abuse-mailbox|
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Referral | NA | NA | RTechHandle | NA | NA |
| technical | | | | | |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Referral | mnt-irt| mnt-irt | RAbuseHandle | NA | NA |
| abuse | | | | | |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Referral | NA | NA | RNOCHandle | NA | NA |
| NOC | | | | | |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Name | NA | NA | NA | nserver| NA |
| server | | | | | |
+------------+--------+----------+--------------+--------+-------------+
+------------+--------+----------+--------------+--------+-------------+
| ID | org | NA | OrgId | owner |organisation |
|organization| | | | | |
|holding the | | | | | |
| resource | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Referral | NA | NA |ReferralServer| NA | NA |
| server | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Technical | tech-c | tech-c |OrgTechHandle | tech-c | tech-c |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Abuse | NA | NA |OrgAbuseHandle| abuse-c|abuse-mailbox|
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Referral | NA | NA | RTechHandle | NA | NA |
| technical | | | | | |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Referral | mnt-irt| mnt-irt | RAbuseHandle | NA | NA |
| abuse | | | | | |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Referral | NA | NA | RNOCHandle | NA | NA |
| NOC | | | | | |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Name | NA | NA | NA | nserver| NA |
| server | | | | | |
+------------+--------+----------+--------------+--------+-------------+
Table 4. WHOIS Data for IP Addresses
表4。IP地址的WHOIS数据
+--------------+---------+----------+-------------+---------+----------+
| Data | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC |
| Element | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| ID | aut-num | aut-num | ASNumber | aut-num | aut-num |
| | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Description | descr | descr | NA | NA | descr |
| | | | | | |
+--------------+---------+----------+-------------+---------+----------+
|Organization | org | NA | OrgId | owner | org |
| | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Data | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC |
| Element | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| ID | aut-num | aut-num | ASNumber | aut-num | aut-num |
| | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Description | descr | descr | NA | NA | descr |
| | | | | | |
+--------------+---------+----------+-------------+---------+----------+
|Organization | org | NA | OrgId | owner | org |
| | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Comment | remarks | NA | Comment | NA | remarks |
+--------------+---------+----------+-------------+---------+----------+
|Administrative| admin-c | admin-c | ASHandle |owner-id | admin-c |
| contact ID | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Technical | tech-c | tech-c |OrgTechHandle|routing-c| tech-c |
| contact ID | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Organization | NA | nic-hdl | NA | owner-c | organi- |
| ID | | | | | sation |
+--------------+---------+----------+-------------+---------+----------+
| Notify | notify | notify | NA | NA | NA |
+--------------+---------+----------+-------------+---------+----------+
| Abuse | NA | NA | OrgAbuse | abuse-c | NA |
| contact | | | Handle | | |
+--------------+---------+----------+-------------+---------+----------+
| Maintainer | mnt-by | mnt-by | NA | NA | mnt-by |
| Object | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Maintainer |mnt-lower| mnt-lower| NA | NA |mnt-lower |
| Sub- | | | | | |
| assignments | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Maintainer | NA | NA | NA | NA | mnt-ref |
| Organization | | | | | |
+--------------+---------+----------+-------------+---------+----------+
|Registration | changed | NA | RegDate | created | NA |
| Date | | | | | |
+--------------+---------+----------+-------------+---------+----------+
|Registration | changed | changed | Updated | changed | NA |
| update | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Source | source | source | NA | NA | source |
+--------------+---------+----------+-------------+---------+----------+
+--------------+---------+----------+-------------+---------+----------+
| Comment | remarks | NA | Comment | NA | remarks |
+--------------+---------+----------+-------------+---------+----------+
|Administrative| admin-c | admin-c | ASHandle |owner-id | admin-c |
| contact ID | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Technical | tech-c | tech-c |OrgTechHandle|routing-c| tech-c |
| contact ID | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Organization | NA | nic-hdl | NA | owner-c | organi- |
| ID | | | | | sation |
+--------------+---------+----------+-------------+---------+----------+
| Notify | notify | notify | NA | NA | NA |
+--------------+---------+----------+-------------+---------+----------+
| Abuse | NA | NA | OrgAbuse | abuse-c | NA |
| contact | | | Handle | | |
+--------------+---------+----------+-------------+---------+----------+
| Maintainer | mnt-by | mnt-by | NA | NA | mnt-by |
| Object | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Maintainer |mnt-lower| mnt-lower| NA | NA |mnt-lower |
| Sub- | | | | | |
| assignments | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Maintainer | NA | NA | NA | NA | mnt-ref |
| Organization | | | | | |
+--------------+---------+----------+-------------+---------+----------+
|Registration | changed | NA | RegDate | created | NA |
| Date | | | | | |
+--------------+---------+----------+-------------+---------+----------+
|Registration | changed | changed | Updated | changed | NA |
| update | | | | | |
+--------------+---------+----------+-------------+---------+----------+
| Source | source | source | NA | NA | source |
+--------------+---------+----------+-------------+---------+----------+
Table 5. WHOIS Data for ASNs
表5。谁是ASN的数据
As can be observed, some data elements were not supported by all RIRs, and some were given different labels by different RIRs. Also, there were identical labels used for different data elements by different RIRs. In order to construct a single data model for each object, a selection of the most common and useful fields was made. That initial selection was the starting point for [RFC7483].
正如可以观察到的，一些数据元素并没有得到所有RIR的支持，一些数据元素被不同的RIR赋予了不同的标签。此外，不同的RIR为不同的数据元素使用相同的标签。为了为每个对象构建单个数据模型，选择了最常见和最有用的字段。最初的选择是[RFC7483]的起点。
WHOIS data was collected from 124 registries, including 106 ccTLDs and 18 gTLDs. All 124 registries support domain queries. Among 124 registries, eight ccTLDs and 15 gTLDs support queries for specific contact persons or roles. 10 ccTLDs and 18 gTLDs support queries by nameserver. Four ccTLDs and 18 gTLDs support registrar queries. Domain WHOIS data contain 68 data elements that use a total of 550 labels. There is a total of 392 other objects for domain WHOIS data.
WHOIS的数据收集自124个登记处，包括106个CCTLD和18个GTLD。所有124个注册中心都支持域查询。在124个注册中心中，8个CCTLD和15个GTLD支持查询特定联系人或角色。10个CCTLD和18个GTLD支持名称服务器查询。四个CCTLD和18个GTLD支持注册器查询。域WHOIS数据包含68个数据元素，共使用550个标签。域WHOIS数据共有392个其他对象。
As mentioned above, public objects are those data elements selected according to the new gTLD applicant guidebook and EPP. They are generally classified into four categories by whether they are related to the domain, contact, nameserver, or registrar.
如上所述，公共对象是根据新的gTLD申请人指南和EPP选择的数据元素。根据它们是否与域、联系人、名称服务器或注册器相关，它们通常分为四类。
WHOIS replies about domains include "Domain Name", "Creation Date", "Domain Status", "Expiration Date", "Updated Date", "Domain ID", "DNSSEC", and "Last Transferred Date". Table 6 gives the element name, most popular label, and the corresponding numbers of TLDs and labels.
WHOIS对域名的回复包括“域名”、“创建日期”、“域名状态”、“到期日期”、“更新日期”、“域名ID”、“DNSSEC”和“上次转移日期”。表6给出了元素名称、最流行的标签以及TLD和标签的相应编号。
+-------------------+-------------------+------------+--------------+
| Data Element | Most Popular | No. of | No. of |
| | Label | TLDs | Labels |
+-------------------+-------------------+------------+--------------+
| Domain Name | Domain Name | 118 | 6 |
+-------------------+-------------------+------------+--------------+
| Creation Date | Created | 106 | 24 |
+-------------------+-------------------+------------+--------------+
| Domain Status | Status | 95 | 8 |
+-------------------+-------------------+------------+--------------+
| Expiration Date | Expiration Date | 81 | 21 |
+-------------------+-------------------+------------+--------------+
| Updated Date | Modified | 70 | 20 |
+-------------------+-------------------+------------+--------------+
| Domain ID | Domain ID | 34 | 5 |
+-------------------+-------------------+------------+--------------+
| DNSSEC | DNSSEC | 14 | 4 |
+-------------------+-------------------+------------+--------------+
| Last Transferred | Last Transferred | 4 | 3 |
| Date | Date | | |
+-------------------+-------------------+------------+--------------+
+-------------------+-------------------+------------+--------------+
| Data Element | Most Popular | No. of | No. of |
| | Label | TLDs | Labels |
+-------------------+-------------------+------------+--------------+
| Domain Name | Domain Name | 118 | 6 |
+-------------------+-------------------+------------+--------------+
| Creation Date | Created | 106 | 24 |
+-------------------+-------------------+------------+--------------+
| Domain Status | Status | 95 | 8 |
+-------------------+-------------------+------------+--------------+
| Expiration Date | Expiration Date | 81 | 21 |
+-------------------+-------------------+------------+--------------+
| Updated Date | Modified | 70 | 20 |
+-------------------+-------------------+------------+--------------+
| Domain ID | Domain ID | 34 | 5 |
+-------------------+-------------------+------------+--------------+
| DNSSEC | DNSSEC | 14 | 4 |
+-------------------+-------------------+------------+--------------+
| Last Transferred | Last Transferred | 4 | 3 |
| Date | Date | | |
+-------------------+-------------------+------------+--------------+
Table 6. WHOIS Data for Domains
表6。域的WHOIS数据
Several statistical conclusions obtained from above data are:
从上述数据中得出的几个统计结论如下：
o 95.16% of the 124 registries support a "Domain Name" data element.
o 124个注册中心中有95.16%支持“域名”数据元素。
o 85.48% of the 124 registries support a "Creation Date" data element.
o 124个登记册中85.48%支持“创建日期”数据元素。
o 76.61% of the 124 registries support a "Domain Status" data element.
o 124个登记册中有76.61%支持“域状态”数据元素。
o On the other hand, some elements such as "DNSSEC" and "Last Transferred Date" are only supported by 11.29% and 3.23% of the registries, respectively.
o 另一方面，“DNSSEC”和“最后转让日期”等要素分别只得到11.29%和3.23%的登记册的支持。
In the domain name space, contacts are typically divided into registrant, administrative contact, technical contact, and billing contact.
在域名空间中，联系人通常分为注册人、管理联系人、技术联系人和计费联系人。
Table 7 shows all the contact information for a registrant. 14 data elements are listed below.
表7显示了注册人的所有联系信息。下面列出了14个数据元素。
+--------------------+---------------------+-----------+------------+
| Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels |
+--------------------+---------------------+-----------+------------+
| Registrant Name | Name | 65 | 7 |
+--------------------+---------------------+-----------+------------+
| Registrant Email | Registrant Email | 59 | 7 |
+--------------------+---------------------+-----------+------------+
| Registrant ID | Registrant ID | 50 | 12 |
+--------------------+---------------------+-----------+------------+
| Registrant Phone | Registrant Phone | 48 | 6 |
+--------------------+---------------------+-----------+------------+
| Registrant Fax | Registrant Fax | 44 | 6 |
+--------------------+---------------------+-----------+------------+
| Registrant | Registrant | 42 | 4 |
| Organization | Organization | | |
+--------------------+---------------------+-----------+------------+
| Registrant Country | Country | 42 | 6 |
| Code | | | |
+--------------------+---------------------+-----------+------------+
| Registrant City | Registrant City | 38 | 4 |
+--------------------+---------------------+-----------+------------+
| Registrant Postal | Registrant Postal | 37 | 5 |
| Code | Code | | |
+--------------------+---------------------+-----------+------------+
| Registrant | Registrant | 32 | 4 |
| State/Province | State/Province | | |
+--------------------+---------------------+-----------+------------+
| Registrant Street | Registrant Street1 | 31 | 16 |
+--------------------+---------------------+-----------+------------+
| Registrant Country | Registrant Country | 19 | 4 |
+--------------------+---------------------+-----------+------------+
| Registrant Phone | Registrant Phone | 18 | 2 |
| Ext. | Ext. | | |
+--------------------+---------------------+-----------+------------+
| Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels |
+--------------------+---------------------+-----------+------------+
| Registrant Name | Name | 65 | 7 |
+--------------------+---------------------+-----------+------------+
| Registrant Email | Registrant Email | 59 | 7 |
+--------------------+---------------------+-----------+------------+
| Registrant ID | Registrant ID | 50 | 12 |
+--------------------+---------------------+-----------+------------+
| Registrant Phone | Registrant Phone | 48 | 6 |
+--------------------+---------------------+-----------+------------+
| Registrant Fax | Registrant Fax | 44 | 6 |
+--------------------+---------------------+-----------+------------+
| Registrant | Registrant | 42 | 4 |
| Organization | Organization | | |
+--------------------+---------------------+-----------+------------+
| Registrant Country | Country | 42 | 6 |
| Code | | | |
+--------------------+---------------------+-----------+------------+
| Registrant City | Registrant City | 38 | 4 |
+--------------------+---------------------+-----------+------------+
| Registrant Postal | Registrant Postal | 37 | 5 |
| Code | Code | | |
+--------------------+---------------------+-----------+------------+
| Registrant | Registrant | 32 | 4 |
| State/Province | State/Province | | |
+--------------------+---------------------+-----------+------------+
| Registrant Street | Registrant Street1 | 31 | 16 |
+--------------------+---------------------+-----------+------------+
| Registrant Country | Registrant Country | 19 | 4 |
+--------------------+---------------------+-----------+------------+
| Registrant Phone | Registrant Phone | 18 | 2 |
| Ext. | Ext. | | |
+--------------------+---------------------+-----------+------------+
| Registrant Fax Ext | Registrant Fax Ext | 17 | 2 |
+--------------------+---------------------+-----------+------------+
+--------------------+---------------------+-----------+------------+
| Registrant Fax Ext | Registrant Fax Ext | 17 | 2 |
+--------------------+---------------------+-----------+------------+
Table 7. Registrant
表7。注册人
Among all the data elements, only "Registrant Name" is supported by more than one half of registries. Those supported by more than one third of registries are: "Registrant Name", "Registrant Email", "Registrant ID", "Registrant Phone", "Registrant Fax", "Registrant Organization", and "Registrant Country Code".
在所有数据元素中，只有一半以上的登记处支持“登记人姓名”。三分之一以上的注册机构支持的是：“注册人姓名”、“注册人电子邮件”、“注册人ID”、“注册人电话”、“注册人传真”、“注册人组织”和“注册人国家代码”。
Table 8 shows all the contact information for an administrative contact. 14 data elements are listed below.
表8显示了管理联系人的所有联系信息。下面列出了14个数据元素。
+--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+
| Admin Street | Address | 64 | 19 |
+--------------------+--------------------+-----------+-------------+
| Admin Name | Admin Name | 60 | 9 |
+--------------------+--------------------+-----------+-------------+
| Admin Email | Admin Email | 54 | 12 |
+--------------------+--------------------+-----------+-------------+
| Admin ID | Admin ID | 52 | 16 |
+--------------------+--------------------+-----------+-------------+
| Admin Fax | Admin Fax | 44 | 8 |
+--------------------+--------------------+-----------+-------------+
| Admin Phone | Admin Phone | 43 | 9 |
+--------------------+--------------------+-----------+-------------+
| Admin Organization | Admin Organization | 42 | 9 |
+--------------------+--------------------+-----------+-------------+
| Admin Country Code | Country | 42 | 7 |
+--------------------+--------------------+-----------+-------------+
| Admin City | Admin City | 35 | 5 |
+--------------------+--------------------+-----------+-------------+
| Admin Postal Code | Admin Postal Code | 35 | 7 |
+--------------------+--------------------+-----------+-------------+
| Admin | Admin | 28 | 5 |
| State/Province | State/Province | | |
+--------------------+--------------------+-----------+-------------+
| Admin Country | Admin Country | 17 | 5 |
+--------------------+--------------------+-----------+-------------+
| Admin Phone Ext. | Admin Phone Ext. | 17 | 3 |
+--------------------+--------------------+-----------+-------------+
| Admin Fax Ext. | Admin Fax Ext. | 17 | 3 |
+--------------------+--------------------+-----------+-------------+
+--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+
| Admin Street | Address | 64 | 19 |
+--------------------+--------------------+-----------+-------------+
| Admin Name | Admin Name | 60 | 9 |
+--------------------+--------------------+-----------+-------------+
| Admin Email | Admin Email | 54 | 12 |
+--------------------+--------------------+-----------+-------------+
| Admin ID | Admin ID | 52 | 16 |
+--------------------+--------------------+-----------+-------------+
| Admin Fax | Admin Fax | 44 | 8 |
+--------------------+--------------------+-----------+-------------+
| Admin Phone | Admin Phone | 43 | 9 |
+--------------------+--------------------+-----------+-------------+
| Admin Organization | Admin Organization | 42 | 9 |
+--------------------+--------------------+-----------+-------------+
| Admin Country Code | Country | 42 | 7 |
+--------------------+--------------------+-----------+-------------+
| Admin City | Admin City | 35 | 5 |
+--------------------+--------------------+-----------+-------------+
| Admin Postal Code | Admin Postal Code | 35 | 7 |
+--------------------+--------------------+-----------+-------------+
| Admin | Admin | 28 | 5 |
| State/Province | State/Province | | |
+--------------------+--------------------+-----------+-------------+
| Admin Country | Admin Country | 17 | 5 |
+--------------------+--------------------+-----------+-------------+
| Admin Phone Ext. | Admin Phone Ext. | 17 | 3 |
+--------------------+--------------------+-----------+-------------+
| Admin Fax Ext. | Admin Fax Ext. | 17 | 3 |
+--------------------+--------------------+-----------+-------------+
Table 8. Admin Contact
表8。管理员联系人
Among all the data elements, only "Admin Street" is supported by more than one half of registries. Those supported by more than one third of registries are: "Admin Street", "Admin Name", "Admin Email", "Admin ID", "Admin Fax", "Admin Phone", "Admin Organization", and "Admin Country Code".
在所有数据元素中，只有一半以上的注册中心支持“Admin Street”。超过三分之一的注册中心支持的是：“管理员街道”、“管理员姓名”、“管理员电子邮件”、“管理员ID”、“管理员传真”、“管理员电话”、“管理员组织”和“管理员国家代码”。
Table 9 shows all the information for a domain name technical contact. 14 data elements are listed below.
表9显示了域名技术联系人的所有信息。下面列出了14个数据元素。
+--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+
| Tech Email | Tech Email | 59 | 9 |
+--------------------+--------------------+-----------+-------------+
| Tech ID | Tech ID | 55 | 16 |
+--------------------+--------------------+-----------+-------------+
| Tech Name | Tech Name | 47 | 6 |
+--------------------+--------------------+-----------+-------------+
| Tech Fax | Tech Fax | 45 | 9 |
+--------------------+--------------------+-----------+-------------+
| Tech Phone | Tech Phone | 45 | 10 |
+--------------------+--------------------+-----------+-------------+
| Tech Country Code | Country | 43 | 9 |
+--------------------+--------------------+-----------+-------------+
| Tech Organization | Tech Organization | 39 | 7 |
+--------------------+--------------------+-----------+-------------+
| Tech City | Tech City | 36 | 4 |
+--------------------+--------------------+-----------+-------------+
| Tech Postal Code | Tech Postal Code | 36 | 7 |
+--------------------+--------------------+-----------+-------------+
| Tech | Tech | 30 | 4 |
| State/Province | State/Province | | |
+--------------------+--------------------+-----------+-------------+
| Tech Street | Tech Street1 | 27 | 16 |
+--------------------+--------------------+-----------+-------------+
| Tech Country | Tech Country | 18 | 5 |
+--------------------+--------------------+-----------+-------------+
| Tech Fax Ext | Tech Fax Ext | 18 | 3 |
+--------------------+--------------------+-----------+-------------+
| Tech Phone Ext. | Tech Phone Ext. | 13 | 3 |
+--------------------+--------------------+-----------+-------------+
+--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+
| Tech Email | Tech Email | 59 | 9 |
+--------------------+--------------------+-----------+-------------+
| Tech ID | Tech ID | 55 | 16 |
+--------------------+--------------------+-----------+-------------+
| Tech Name | Tech Name | 47 | 6 |
+--------------------+--------------------+-----------+-------------+
| Tech Fax | Tech Fax | 45 | 9 |
+--------------------+--------------------+-----------+-------------+
| Tech Phone | Tech Phone | 45 | 10 |
+--------------------+--------------------+-----------+-------------+
| Tech Country Code | Country | 43 | 9 |
+--------------------+--------------------+-----------+-------------+
| Tech Organization | Tech Organization | 39 | 7 |
+--------------------+--------------------+-----------+-------------+
| Tech City | Tech City | 36 | 4 |
+--------------------+--------------------+-----------+-------------+
| Tech Postal Code | Tech Postal Code | 36 | 7 |
+--------------------+--------------------+-----------+-------------+
| Tech | Tech | 30 | 4 |
| State/Province | State/Province | | |
+--------------------+--------------------+-----------+-------------+
| Tech Street | Tech Street1 | 27 | 16 |
+--------------------+--------------------+-----------+-------------+
| Tech Country | Tech Country | 18 | 5 |
+--------------------+--------------------+-----------+-------------+
| Tech Fax Ext | Tech Fax Ext | 18 | 3 |
+--------------------+--------------------+-----------+-------------+
| Tech Phone Ext. | Tech Phone Ext. | 13 | 3 |
+--------------------+--------------------+-----------+-------------+
Table 9. Tech Contact
表9。技术联系人
Among all the data elements, there are no elements supported by more than one half of registries. Those supported by more than one third of registries are: "Tech Email", "Tech ID", "Tech Name", "Tech Fax", "Tech Phone", and "Tech Country Code".
在所有数据元素中，没有超过一半的登记册支持的元素。超过三分之一的注册机构支持的是：“技术电子邮件”、“技术ID”、“技术名称”、“技术传真”、“技术电话”和“技术国家代码”。
Table 10 shows all the information for a domain name billing contact. 14 data elements are listed below.
表10显示了域名计费联系人的所有信息。下面列出了14个数据元素。
+--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+
| Billing Name | Name | 47 | 5 |
+--------------------+--------------------+-----------+-------------+
| Billing Fax | Fax | 43 | 6 |
+--------------------+--------------------+-----------+-------------+
| Billing Email | Email Address | 42 | 7 |
+--------------------+--------------------+-----------+-------------+
| Billing Country | Country | 38 | 4 |
| Code | | | |
+--------------------+--------------------+-----------+-------------+
| Billing Phone | Phone Number | 34 | 6 |
+--------------------+--------------------+-----------+-------------+
| Billing ID | Billing ID | 28 | 9 |
+--------------------+--------------------+-----------+-------------+
| Billing City | Billing City | 28 | 4 |
+--------------------+--------------------+-----------+-------------+
| Billing | Billing | 28 | 5 |
| Organization | Organization | | |
+--------------------+--------------------+-----------+-------------+
| Billing Postal | Billing Postal | 27 | 4 |
| Code | Code | | |
+--------------------+--------------------+-----------+-------------+
| Billing | Billing | 21 | 4 |
| State/Province | State/Province | | |
+--------------------+--------------------+-----------+-------------+
| Billing Street | Billing Street1 | 19 | 13 |
+--------------------+--------------------+-----------+-------------+
| Billing Country | Billing Country | 13 | 5 |
+--------------------+--------------------+-----------+-------------+
| Billing Phone Ext. | Billing Phone Ext. | 10 | 2 |
+--------------------+--------------------+-----------+-------------+
| Billing Fax Ext | Billing Fax Ext | 10 | 2 |
+--------------------+--------------------+-----------+-------------+
+--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+
| Billing Name | Name | 47 | 5 |
+--------------------+--------------------+-----------+-------------+
| Billing Fax | Fax | 43 | 6 |
+--------------------+--------------------+-----------+-------------+
| Billing Email | Email Address | 42 | 7 |
+--------------------+--------------------+-----------+-------------+
| Billing Country | Country | 38 | 4 |
| Code | | | |
+--------------------+--------------------+-----------+-------------+
| Billing Phone | Phone Number | 34 | 6 |
+--------------------+--------------------+-----------+-------------+
| Billing ID | Billing ID | 28 | 9 |
+--------------------+--------------------+-----------+-------------+
| Billing City | Billing City | 28 | 4 |
+--------------------+--------------------+-----------+-------------+
| Billing | Billing | 28 | 5 |
| Organization | Organization | | |
+--------------------+--------------------+-----------+-------------+
| Billing Postal | Billing Postal | 27 | 4 |
| Code | Code | | |
+--------------------+--------------------+-----------+-------------+
| Billing | Billing | 21 | 4 |
| State/Province | State/Province | | |
+--------------------+--------------------+-----------+-------------+
| Billing Street | Billing Street1 | 19 | 13 |
+--------------------+--------------------+-----------+-------------+
| Billing Country | Billing Country | 13 | 5 |
+--------------------+--------------------+-----------+-------------+
| Billing Phone Ext. | Billing Phone Ext. | 10 | 2 |
+--------------------+--------------------+-----------+-------------+
| Billing Fax Ext | Billing Fax Ext | 10 | 2 |
+--------------------+--------------------+-----------+-------------+
Table 10. Billing Contact
表10。付款联系人
Among all the data elements, there are no elements supported by more than one half of registries. Those supported by more than one third of registries are "Billing Name", "Billing Fax", and "Billing Email".
在所有数据元素中，没有超过一半的登记册支持的元素。超过三分之一的注册机构支持的是“账单名称”、“账单传真”和“账单电子邮件”。
114 registries (about 92% of the 124 registries) have the "nameserver" data element in their WHOIS responses. However, there are 63 different labels for this element, as shown in Table 11. The top three labels for this element are "Name Server" (which is supported by 25% of the registries), "Name Servers" (which is supported by 16% of the registries), and "nserver" (which is supported by 12% of the registries).
114个注册中心（124个注册中心中约92%）在其WHOIS响应中具有“名称服务器”数据元素。但是，该元素有63个不同的标签，如表11所示。此元素的前三个标签是“名称服务器”（25%的注册表支持该标签）、“名称服务器”（16%的注册表支持该标签）和“nserver”（12%的注册表支持该标签）。
+--------------+--------------------+-------------+---------------+
| Data Element | Most Popular Label | No. of TLDs | No. of Labels |
+--------------+--------------------+-------------+---------------+
| NameServer | Name Server | 114 | 63 |
+--------------+--------------------+-------------+---------------+
+--------------+--------------------+-------------+---------------+
| Data Element | Most Popular Label | No. of TLDs | No. of Labels |
+--------------+--------------------+-------------+---------------+
| NameServer | Name Server | 114 | 63 |
+--------------+--------------------+-------------+---------------+
Table 11. WHOIS Data for Nameservers
表11。名称服务器的WHOIS数据
Some registries have nameserver elements such like "nameserver 1", "nameserver 2" till "nameserver n". Thus, there are more labels than of other data elements.
有些注册表具有名称服务器元素，如“名称服务器1”、“名称服务器2”到“名称服务器n”。因此，有比其他数据元素更多的标签。
There are three data elements about registrar information.
关于注册信息，有三个数据元素。
+-------------------+---------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels |
+-------------------+---------------------+-----------+-------------+
| Sponsoring | Registrar | 84 | 6 |
| Registrar | | | |
+-------------------+---------------------+-----------+-------------+
| Created by | Created by | 14 | 3 |
| Registrar | | | |
+-------------------+---------------------+-----------+-------------+
| Updated by | Last Updated by | 11 | 3 |
| Registrar | Registrar | | |
+-------------------+---------------------+-----------+-------------+
+-------------------+---------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels |
+-------------------+---------------------+-----------+-------------+
| Sponsoring | Registrar | 84 | 6 |
| Registrar | | | |
+-------------------+---------------------+-----------+-------------+
| Created by | Created by | 14 | 3 |
| Registrar | | | |
+-------------------+---------------------+-----------+-------------+
| Updated by | Last Updated by | 11 | 3 |
| Registrar | Registrar | | |
+-------------------+---------------------+-----------+-------------+
Table 12. WHOIS Data for Registrars
表12。登记员的WHOIS数据
67.7% of the registries have the "Sponsoring Registrar" data element. The elements "Created by Registrar" and "Updated by Registrar" are supported by 11.3% and 8.9% of the registries, respectively.
67.7%的登记处拥有“主办登记处”数据元。11.3%和8.9%的登记处分别支持“由登记处创建”和“由登记处更新”这两个要素。
So-called "other objects" are those data elements that are privately specified or are difficult to be classified. There are 392 other objects altogether. Table 13 lists the top 50 other objects found during data collection.
所谓的“其他对象”是那些私下指定或难以分类的数据元素。总共有392个其他对象。表13列出了数据收集期间发现的前50个其他对象。
+----------------------------------------+-------------+
| Data Element | No. of TLDs |
+----------------------------------------+-------------+
| Registrant | 41 |
+----------------------------------------+-------------+
| Phone | 32 |
+----------------------------------------+-------------+
| Technical contact | 26 |
+----------------------------------------+-------------+
| Administrative contact | 15 |
+----------------------------------------+-------------+
| source | 14 |
+----------------------------------------+-------------+
| fax-no | 13 |
+----------------------------------------+-------------+
| nic-hdl | 13 |
+----------------------------------------+-------------+
| Billing Contact | 12 |
+----------------------------------------+-------------+
| referral url | 11 |
+----------------------------------------+-------------+
| e-mail | 10 |
+----------------------------------------+-------------+
| WHOIS server | 9 |
+----------------------------------------+-------------+
| Admin Contact | 9 |
+----------------------------------------+-------------+
| Type | 9 |
+----------------------------------------+-------------+
| Website | 9 |
+----------------------------------------+-------------+
| zone-c | 8 |
+----------------------------------------+-------------+
| remarks | 7 |
+----------------------------------------+-------------+
| Registration URL | 6 |
+----------------------------------------+-------------+
| anonymous | 6 |
+----------------------------------------+-------------+
| anniversary | 6 |
+----------------------------------------+-------------+
| Data Element | No. of TLDs |
+----------------------------------------+-------------+
| Registrant | 41 |
+----------------------------------------+-------------+
| Phone | 32 |
+----------------------------------------+-------------+
| Technical contact | 26 |
+----------------------------------------+-------------+
| Administrative contact | 15 |
+----------------------------------------+-------------+
| source | 14 |
+----------------------------------------+-------------+
| fax-no | 13 |
+----------------------------------------+-------------+
| nic-hdl | 13 |
+----------------------------------------+-------------+
| Billing Contact | 12 |
+----------------------------------------+-------------+
| referral url | 11 |
+----------------------------------------+-------------+
| e-mail | 10 |
+----------------------------------------+-------------+
| WHOIS server | 9 |
+----------------------------------------+-------------+
| Admin Contact | 9 |
+----------------------------------------+-------------+
| Type | 9 |
+----------------------------------------+-------------+
| Website | 9 |
+----------------------------------------+-------------+
| zone-c | 8 |
+----------------------------------------+-------------+
| remarks | 7 |
+----------------------------------------+-------------+
| Registration URL | 6 |
+----------------------------------------+-------------+
| anonymous | 6 |
+----------------------------------------+-------------+
| anniversary | 6 |
+----------------------------------------+-------------+
| hold | 6 |
+----------------------------------------+-------------+
| nsl-id | 6 |
+----------------------------------------+-------------+
| obsoleted | 6 |
+----------------------------------------+-------------+
| Customer Service Contact | 5 |
+----------------------------------------+-------------+
| Customer Service Email | 4 |
+----------------------------------------+-------------+
| Registrar ID | 4 |
+----------------------------------------+-------------+
| org | 4 |
+----------------------------------------+-------------+
| person | 4 |
+----------------------------------------+-------------+
| Maintainer | 4 |
+----------------------------------------+-------------+
| Nombre | 3 |
+----------------------------------------+-------------+
| Sponsoring Registrar IANA ID | 3 |
+----------------------------------------+-------------+
| Trademark Number | 3 |
+----------------------------------------+-------------+
| Trademark Country | 3 |
+----------------------------------------+-------------+
| descr | 3 |
+----------------------------------------+-------------+
| url | 3 |
+----------------------------------------+-------------+
| Postal address | 3 |
+----------------------------------------+-------------+
| Registrar URL | 3 |
+----------------------------------------+-------------+
| International Name | 3 |
+----------------------------------------+-------------+
| International Address | 3 |
+----------------------------------------+-------------+
| Admin Contacts | 2 |
+----------------------------------------+-------------+
| Contractual Language | 2 |
+----------------------------------------+-------------+
| Date Trademark Registered | 2 |
+----------------------------------------+-------------+
| Date Trademark Applied For | 2 |
+----------------------------------------+-------------+
| IP Address | 2 |
+----------------------------------------+-------------+
| hold | 6 |
+----------------------------------------+-------------+
| nsl-id | 6 |
+----------------------------------------+-------------+
| obsoleted | 6 |
+----------------------------------------+-------------+
| Customer Service Contact | 5 |
+----------------------------------------+-------------+
| Customer Service Email | 4 |
+----------------------------------------+-------------+
| Registrar ID | 4 |
+----------------------------------------+-------------+
| org | 4 |
+----------------------------------------+-------------+
| person | 4 |
+----------------------------------------+-------------+
| Maintainer | 4 |
+----------------------------------------+-------------+
| Nombre | 3 |
+----------------------------------------+-------------+
| Sponsoring Registrar IANA ID | 3 |
+----------------------------------------+-------------+
| Trademark Number | 3 |
+----------------------------------------+-------------+
| Trademark Country | 3 |
+----------------------------------------+-------------+
| descr | 3 |
+----------------------------------------+-------------+
| url | 3 |
+----------------------------------------+-------------+
| Postal address | 3 |
+----------------------------------------+-------------+
| Registrar URL | 3 |
+----------------------------------------+-------------+
| International Name | 3 |
+----------------------------------------+-------------+
| International Address | 3 |
+----------------------------------------+-------------+
| Admin Contacts | 2 |
+----------------------------------------+-------------+
| Contractual Language | 2 |
+----------------------------------------+-------------+
| Date Trademark Registered | 2 |
+----------------------------------------+-------------+
| Date Trademark Applied For | 2 |
+----------------------------------------+-------------+
| IP Address | 2 |
+----------------------------------------+-------------+
| Keys | 2 |
+----------------------------------------+-------------+
| Language | 2 |
+----------------------------------------+-------------+
| NIC handle | 2 |
+----------------------------------------+-------------+
| Record maintained by | 2 |
+----------------------------------------+-------------+
| Registration Service Provider | 2 |
+----------------------------------------+-------------+
| Registration Service Provided By | 2 |
+----------------------------------------+-------------+
| Registrar URL (registration services) | 2 |
+----------------------------------------+-------------+
+----------------------------------------+-------------+
| Keys | 2 |
+----------------------------------------+-------------+
| Language | 2 |
+----------------------------------------+-------------+
| NIC handle | 2 |
+----------------------------------------+-------------+
| Record maintained by | 2 |
+----------------------------------------+-------------+
| Registration Service Provider | 2 |
+----------------------------------------+-------------+
| Registration Service Provided By | 2 |
+----------------------------------------+-------------+
| Registrar URL (registration services) | 2 |
+----------------------------------------+-------------+
Table 13. The Top 50 Other Objects
表13。前50名的其他对象
Some registries returned things that looked like labels, but were not. For example, in this reply:
有些注册中心返回的东西看起来像标签，但实际上不是。例如，在本答复中：
Registrant: Name: Email: ...
注册人：姓名：电子邮件：。。。
"Name" and "Email" appeared to be data elements, but "Registrant" did not. The inventory work proceeded on that assumption, i.e., there were two data elements to be recorded in this example.
“姓名”和“电子邮件”似乎是数据元素，但“注册人”不是。盘存工作是基于这一假设进行的，即本例中有两个数据元素需要记录。
Some other data elements, like "Remarks", "anniversary", and "Customer service Contact", are designed particularly for their own purpose by different registries.
其他一些数据元素，如“备注”、“周年纪念”和“客户服务联系人”，是由不同的登记处专门为自己的目的设计的。
Some preliminary conclusions could be drawn from the raw data.
从原始数据中可以得出一些初步结论。
o All of the 124 domain registries have the object names in their responses, although they are in various formats.
o 所有124个域注册中心的响应中都有对象名，尽管它们的格式不同。
o Of the 118 WHOIS services contacted, 65 registries show their registrant contact. About half of the registries (60 registries) support admin contact information. There are 47 registries, which is about one third of the total number, that have technical and
o 在接触的118个WHOIS服务中，65个登记处显示了他们的注册联系人。大约一半的注册中心（60个注册中心）支持管理员联系信息。共有47个登记处，约占总数的三分之一，拥有技术和技术资料
billing contact information. Only seven of the 124 registries give their abuse email in a "remarks" section. No explicit abuse contact information is provided.
账单联系信息。在124家登记处中，只有7家在“备注”部分发送了滥用电子邮件。没有提供明确的虐待联系信息。
o There are mainly two presentation formats. One is key-value; the other is data block format. Example of key-value format:
o 主要有两种演示格式。一是关键价值；二是数据块格式。键值格式示例：
Domain Information Query: nic.example.com Status: Delegated Created: 17 Apr 2004 Modified: 14 Nov 2010 Expires: 31 Dec 9999 Name Servers: ns.example.net ns1.na.example.net ns2.na.example.net ...
域信息查询：nic.example.com状态：委托创建：2004年4月17日修改：2010年11月14日到期：9999年12月31日名称服务器：ns.example.net ns1.na.example.net ns2.na.example.net。。。
Example of data block format:
数据块格式示例：
WHOIS database domain nic.example.org
谁是数据库域nic.example.org
Domain Name nic.example.org Registered 1998-09-02 Expiry 2012-09-02
域名nic.example.org注册日期：1998-09-02到期日期：2012-09-02
Resource Records
资源记录
a 198.51.100.1 mx 10 test.example.net www a 198.51.100.10
a 198.51.100.1 mx 10 test.example.net www.a 198.51.100.10
Contact details
联系方式
Registrant, Technical Contact, Billing Contact, Admin. Contact AdamsNames Reserved Domains (i) These domains are not available for registration United Kingdom Identifier: test123
注册人、技术联系人、账单联系人、管理员。联系AdamsNames保留域（i）这些域不可注册英国标识符：test123
Servidor WHOIS de NIC-Example
施维多是谁的例子
Este servidor contiene informacion autoritativa exclusivamente de dominios nic.example.org Cualquier consulta sobre este servicio, puede hacerla al correo electronico whois@nic.example.org
Este servidor contiene informacion Autoritiva de dominios nic.example.org独家信息服务咨询公司，puede hacerla al-correo electronicowhois@nic.example.org
Titular: John (nic.example.org) john@nic.example.org NIC Example Av. Veracruz con calle Cali, Edif Aguila, Urb. Las Mercedes Caracas, Distrito Capital VE 0212-1234567 (FAX) +582123456789
标题：约翰（nic.example.org）john@nic.example.orgNIC示例Av。韦拉克鲁斯·卡利，埃迪夫·阿吉拉，城市。拉斯梅赛德斯加拉加斯，首府VE 0212-1234567（传真）+582123456789
o 11 registries give local script responses. The WHOIS information of other registries are all represented in English.
o 11个注册中心提供本地脚本响应。其他登记处的WHOIS信息均以英语表示。
The top 10 data elements are listed in Table 14.
表14列出了前10个数据元素。
+----------------------+-------------+
| Data Element | No. of TLDs |
+----------------------+-------------+
| Domain Name | 118 |
+----------------------+-------------+
| Name Server | 114 |
+----------------------+-------------+
| Creation Date | 106 |
+----------------------+-------------+
| Domain Status | 95 |
+----------------------+-------------+
| Sponsoring Registrar | 84 |
+----------------------+-------------+
| Expiration Date | 81 |
+----------------------+-------------+
| Updated Date | 70 |
+----------------------+-------------+
| Registrant Name | 65 |
+----------------------+-------------+
| Admin Street | 64 |
+----------------------+-------------+
| Admin Name | 60 |
+----------------------+-------------+
+----------------------+-------------+
| Data Element | No. of TLDs |
+----------------------+-------------+
| Domain Name | 118 |
+----------------------+-------------+
| Name Server | 114 |
+----------------------+-------------+
| Creation Date | 106 |
+----------------------+-------------+
| Domain Status | 95 |
+----------------------+-------------+
| Sponsoring Registrar | 84 |
+----------------------+-------------+
| Expiration Date | 81 |
+----------------------+-------------+
| Updated Date | 70 |
+----------------------+-------------+
| Registrant Name | 65 |
+----------------------+-------------+
| Admin Street | 64 |
+----------------------+-------------+
| Admin Name | 60 |
+----------------------+-------------+
Table 14. The Top 10 Data Elements
表14。前10个数据元素
Most of the domain-related WHOIS information is included in the top 10 data elements. Other information like name server and registrar name is also supported by most registries.
大多数与领域相关的WHOIS信息都包含在前10个数据元素中。大多数注册中心还支持名称服务器和注册器名称等其他信息。
A cumulative distribution analysis of all the data elements was done.
对所有数据元素进行了累积分布分析。
(1) About 5% of the data elements discovered by the inventory work are supported by 111 registries (i.e., 90%).
(1) 清单工作发现的数据元素中约有5%得到111个登记册的支持（即90%）。
(2) About 30% of the data elements discovered by the inventory work are supported by 44 registries (i.e., 35%).
(2) 清单工作发现的数据元素中约有30%得到44个登记处的支持（即35%）。
(3) About 60% of the data elements discovered by the inventory work are supported by 32 registries (i.e., 26%).
(3) 清单工作发现的数据元素中约有60%得到32个登记处的支持（即26%）。
(4) About 90% of the data elements discovered by the inventory work are supported by 14 registries (i.e., 11%).
(4) 清单工作发现的大约90%的数据元素得到14个登记处的支持（即11%）。
From the above result, it is clear that only a few registries support all the public objects, most of the registries support just some of the objects.
从上面的结果可以清楚地看出，只有少数注册中心支持所有公共对象，大多数注册中心只支持部分对象。
The top 10 labels of different data elements are listed in Table 15.
表15列出了不同数据元素的前10个标签。
+-------------------+---------------+
| Labels | No. of Labels |
+-------------------+---------------+
| Name Server | 63 |
+-------------------+---------------+
| Creation Date | 24 |
+-------------------+---------------+
| Expiration Date | 21 |
+-------------------+---------------+
| Updated Date | 20 |
+-------------------+---------------+
| Admin Street | 19 |
+-------------------+---------------+
| Tech ID | 18 |
+-------------------+---------------+
| Registrant Street | 16 |
+-------------------+---------------+
| Admin ID | 16 |
+-------------------+---------------+
| Tech Street | 16 |
+-------------------+---------------+
| Billing Street | 13 |
+-------------------+---------------+
+-------------------+---------------+
| Labels | No. of Labels |
+-------------------+---------------+
| Name Server | 63 |
+-------------------+---------------+
| Creation Date | 24 |
+-------------------+---------------+
| Expiration Date | 21 |
+-------------------+---------------+
| Updated Date | 20 |
+-------------------+---------------+
| Admin Street | 19 |
+-------------------+---------------+
| Tech ID | 18 |
+-------------------+---------------+
| Registrant Street | 16 |
+-------------------+---------------+
| Admin ID | 16 |
+-------------------+---------------+
| Tech Street | 16 |
+-------------------+---------------+
| Billing Street | 13 |
+-------------------+---------------+
Table 15. The Top 10 Labels
表15。前十名标签
As explained above, the "Name Server" label is a unique example because many registries define the name server elements from "nameserver 1" through "nameserver n". Thus, the count of labels for name servers is much higher than other elements. Data elements representing dates and street addresses were also common.
如上所述，“名称服务器”标签是一个独特的示例，因为许多注册中心从“名称服务器1”到“名称服务器n”定义名称服务器元素。因此，名称服务器的标签数量远远高于其他元素。表示日期和街道地址的数据元素也很常见。
A cumulative distribution analysis of label numbers was done. About 90% of data elements have more than two labels. It is therefore necessary to specify a standard and unified format for object names in a WHOIS response.
对标签编号进行了累积分布分析。大约90%的数据元素有两个以上的标签。因此，有必要在WHOIS响应中为对象名称指定标准和统一的格式。
The results indicate that there are 392 other data objects in total that are not easy to be classified or are privately defined by various registries. The top 50 other objects are listed in Table 13 in Section 5.3. It is clear that various different objects are
结果表明，总共有392个其他数据对象不容易分类或由各种登记处私下定义。第5.3节表13列出了前50个其他对象。很明显，不同的对象是不同的
designed for some particular purpose. In order to ensure uniqueness of JSON names used in the RDAP service, establishment of an IANA registry is advised.
为某种特殊目的而设计的。为了确保RDAP服务中使用的JSON名称的唯一性，建议建立IANA注册表。
This section lists the limitations of the survey and some assumptions that were made in the execution of this work.
本节列出了调查的局限性以及在执行本工程过程中做出的一些假设。
o The input "nic.ccTLD" may not be a good choice, for the term "nic" is often specially used by the corresponding ccTLD, so the collected WHOIS data may be customized and different from the common data.
o 输入“nic.ccTLD”可能不是一个好的选择，因为术语“nic”通常由相应的ccTLD专门使用，因此收集的WHOIS数据可能是定制的，并且不同于普通数据。
o Since the programming script queried the "nic.ccTLD" in an anonymous way, only the public WHOIS data from WHOIS servers having nic.ccTLD were collected. So, the private WHOIS data were not covered by this document.
o 由于编程脚本以匿名方式查询“nic.ccTLD”，因此仅从具有nic.ccTLD的WHOIS服务器收集公共WHOIS数据。因此，本文件未涵盖WHOIS的私人数据。
o 11 registries did not provide responses in English. The classification of data elements within their responses may not be accurate.
o 11个登记处没有提供英文答复。其响应中的数据元素分类可能不准确。
o The extension data elements are used randomly by different registries. It is difficult to do statistical analysis.
o 扩展数据元素由不同的注册中心随机使用。做统计分析是困难的。
o Sample sizes of contact, name server, and registrar queries are small.
o 联系人、姓名服务器和注册者查询的样本量很小。
* Only WHOIS queries for contact ID, nameserver, and registrar were used.
* 仅使用WHOIS查询联系人ID、名称服务器和注册器。
* Some registries may not support contact, name server, or registrar queries.
* 某些注册表可能不支持联系人、名称服务器或注册器查询。
* Some may not support query contact by ID.
* 有些可能不支持按ID查询联系人。
* Contact information of some registries may be protected.
* 某些登记处的联系信息可能受到保护。
There are some objects that are included in the existing WHOIS system but not mentioned in [RFC7483]. This document is intended to give a list of reference extension objects for discussion.
有些对象包括在现有WHOIS系统中，但在[RFC7483]中未提及。本文档旨在提供参考扩展对象列表供讨论。
o company - the company name registered by the registrant.
o 公司-由注册人注册的公司名称。
o maintainer - authentication information that identifies who can modify the contents of this object.
o maintainer—标识谁可以修改此对象内容的身份验证信息。
o list of resources - a list of IPv4 addresses, IPv6 addresses, and Autonomous System numbers.
o 资源列表—IPv4地址、IPv6地址和自治系统编号的列表。
o referral NOC contact - the Network Operations Center contact.
o 转介NOC联系人-网络运营中心联系人。
The following objects are selected from the top 50 other objects in Section 5.3 that are supported by more than five registries. These objects are considered as possible extension objects.
以下对象是从第5.3节中受五个以上注册表支持的前50个其他对象中选择的。这些对象被视为可能的扩展对象。
o zone-c - The identifier of a 'role' object with authority over a zone.
o zone-c—对区域具有权限的“角色”对象的标识符。
o maintainer - authentication information that identifies who can modify the contents of this object.
o maintainer—标识谁可以修改此对象内容的身份验证信息。
o Registration URL - typically the website address of a registry.
o 注册URL-通常是注册表的网站地址。
o anonymous - whether the registration information is anonymous or not.
o 匿名-注册信息是否匿名。
o hold - whether the domain is "on hold" or not.
o 保留-域是否处于“保留”状态。
o nsl-id - nameserver list ID.
o nsl id-名称服务器列表id。
o obsoleted - whether a domain is obsoleted or not.
o 已过时-域是否已过时。
o Customer Service Contact - a kind of contact.
o 客户服务联系人-一种联系人。
This document does not provide any security services or introduce additional considerations to those discussed in [RFC7481].
本文件不提供任何安全服务，也不引入[RFC7481]中讨论的其他注意事项。
[ICANN.AGB-201206] ICANN, "gTLD Applicant Guidebook", June 2012, <http://newgtlds.icann.org/en/applicants/agb/ guidebook-full-04jun12-en.pdf>.
[ICANN.AGB-201206]ICANN，“gTLD申请人指南”，2012年6月<http://newgtlds.icann.org/en/applicants/agb/ 指南-full-04jun12-en.pdf>。
[RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D., Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra, "Routing Policy Specification Language (RPSL)", RFC 2622, June 1999, <http://www.rfc-editor.org/info/rfc2622>.
[RFC2622]Alaettinoglu，C.，Villamizar，C.，Gerich，E.，Kessens，D.，Meyer，D.，Bates，T.，Karrenberg，D.，和M.Terpstra，“路由策略规范语言（RPSL）”，RFC 2622，1999年6月<http://www.rfc-editor.org/info/rfc2622>.
[RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, September 2004, <http://www.rfc-editor.org/info/rfc3912>.
[RFC3912]Daigle，L.，“WHOIS协议规范”，RFC 3912，2004年9月<http://www.rfc-editor.org/info/rfc3912>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, August 2009, <http://www.rfc-editor.org/info/rfc5730>.
[RFC5730]Hollenbeck，S.，“可扩展资源调配协议（EPP）”，STD 69，RFC 5730，2009年8月<http://www.rfc-editor.org/info/rfc5730>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, August 2009, <http://www.rfc-editor.org/info/rfc5731>.
[RFC5731]Hollenbeck，S.，“可扩展供应协议（EPP）域名映射”，STD 69，RFC 57312009年8月<http://www.rfc-editor.org/info/rfc5731>.
[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Host Mapping", STD 69, RFC 5732, August 2009, <http://www.rfc-editor.org/info/rfc5732>.
[RFC5732]Hollenbeck，S.，“可扩展资源调配协议（EPP）主机映射”，STD 69，RFC 5732，2009年8月<http://www.rfc-editor.org/info/rfc5732>.
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Contact Mapping", STD 69, RFC 5733, August 2009, <http://www.rfc-editor.org/info/rfc5733>.
[RFC5733]Hollenbeck，S.，“可扩展资源调配协议（EPP）联系人映射”，STD 69，RFC 57332009年8月<http://www.rfc-editor.org/info/rfc5733>.
[RFC5890] Klensin, J., "Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", RFC 5890, August 2010, <http://www.rfc-editor.org/info/rfc5890>.
[RFC5890]Klensin，J.“应用程序的国际化域名（IDNA）：定义和文档框架”，RFC 58902010年8月<http://www.rfc-editor.org/info/rfc5890>.
[RFC7480] Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the Registration Data Access Protocol (RDAP)", RFC 7480, March 2015, <http://www.rfc-editor.org/info/rfc7480>.
[RFC7480]Newton，A.，Ellacott，B.，和N.Kong，“注册数据访问协议（RDAP）中的HTTP使用”，RFC 7480，2015年3月<http://www.rfc-editor.org/info/rfc7480>.
[RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the Registration Data Access Protocol (RDAP)", RFC 7481, March 2015, <http://www.rfc-editor.org/info/rfc7481>.
[RFC7481]Hollenbeck，S.和N.Kong，“注册数据访问协议（RDAP）的安全服务”，RFC 74812015年3月<http://www.rfc-editor.org/info/rfc7481>.
[RFC7482] Newton, A. and S. Hollenbeck, "Registration Data Access Protocol (RDAP) Query Format", RFC 7482, March 2015, <http://www.rfc-editor.org/info/rfc7482>.
[RFC7482]Newton，A.和S.Hollenbeck，“注册数据访问协议（RDAP）查询格式”，RFC 7482，2015年3月<http://www.rfc-editor.org/info/rfc7482>.
[RFC7483] Newton, A. and S. Hollenbeck, "JSON Responses for the Registration Data Access Protocol (RDAP)", RFC 7483, March 2015, <http://www.rfc-editor.org/info/rfc7483>.
[RFC7483]Newton，A.和S.Hollenbeck，“注册数据访问协议（RDAP）的JSON响应”，RFC 7483，2015年3月<http://www.rfc-editor.org/info/rfc7483>.
[RFC7484] Blanchet, M., "Finding the Authoritative Registration Data (RDAP) Service", RFC 7484, March 2015, <http://www.rfc-editor.org/info/rfc7484>.
[RFC7484]Blanchet，M.“查找权威注册数据（RDAP）服务”，RFC 7484，2015年3月<http://www.rfc-editor.org/info/rfc7484>.
Acknowledgements
致谢
This document is the work product of the IETF's WEIRDS working group, of which Olaf Kolkman and Murray Kucherawy were chairs.
本文件是IETF的WEIRDS工作组的工作成果，Olaf Kolkman和Murray Kucherawy是该工作组的主席。
The authors especially thank the following individuals who gave their suggestions and contributions to this document: Guangqing Deng, Frederico A C Neves, Ray Bellis, Edward Shryane, Kaveh Ranjbar, Murray Kucherawy, Edward Lewis, Pete Resnick, Juergen Schoenwaelder, Ben Campbell, and Claudio Allocchio.
作者特别感谢以下为本文件提供建议和贡献的个人：邓广清、弗雷德里科·内维斯、雷·贝利斯、爱德华·什里安、卡维·兰杰巴尔、默里·库奇拉维、爱德华·刘易斯、皮特·雷斯尼克、于尔根·舍恩瓦埃尔德、本·坎贝尔和克劳迪奥·阿洛奇。
Authors' Addresses
作者地址
Linlin Zhou CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing 100190 China
中国北京市海淀区中关村南四街4号林林洲CNNIC 100190
Phone: +86 10 5881 2677
EMail: zhoulinlin@cnnic.cn
Phone: +86 10 5881 2677
EMail: zhoulinlin@cnnic.cn
Ning Kong CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing 100190 China
中国北京市海淀区中关村南四街4号宁空CNNIC 100190
Phone: +86 10 5881 3147
EMail: nkong@cnnic.cn
Phone: +86 10 5881 3147
EMail: nkong@cnnic.cn
Sean Shen CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing 100190 China
中国北京市海淀区中关村南四街4号肖恩申CNNIC 100190
Phone: +86 10 5881 3038
EMail: shenshuo@cnnic.cn
Phone: +86 10 5881 3038
EMail: shenshuo@cnnic.cn
Steve Sheng ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 United States
Steve Sheng ICANN美国加利福尼亚州洛杉矶滨水路12025号300室90094-2536
Phone: +1 310 301 5800
EMail: steve.sheng@icann.org
Phone: +1 310 301 5800
EMail: steve.sheng@icann.org
Arturo Servin LACNIC Rambla Mexico 6125 Montevideo 11400 Uruguay
Arturo Servin LACNIC Rambla墨西哥6125蒙得维的亚11400乌拉圭
Phone: +598-2604-2222
EMail: arturo.servin@gmail.com
Phone: +598-2604-2222
EMail: arturo.servin@gmail.com