draft-ietf-weirds-object-inventory-06.txt   rfc7485.txt 
Internet Engineering Task Force L. Zhou Internet Engineering Task Force (IETF) L. Zhou
Internet-Draft N. Kong Request for Comments: 7485 N. Kong
Intended status: Informational S. Shen Category: Informational S. Shen
Expires: April 30, 2015 CNNIC ISSN: 2070-1721 CNNIC
S. Sheng S. Sheng
ICANN ICANN
A. Servin A. Servin
LACNIC LACNIC
October 27, 2014 March 2015
Registration Data Access Protocol Object Inventory Analysis Inventory and Analysis of WHOIS Registration Objects
draft-ietf-weirds-object-inventory-06
Abstract Abstract
WHOIS output objects from registries (including both Regional WHOIS output objects from registries, including both Regional
Internet Registries (RIRs) and Domain Name Registries (DNRs)) were Internet Registries (RIRs) and Domain Name Registries (DNRs), were
collected and analyzed. This document describes the statistical collected and analyzed. This document describes the process and
analysis process and results of the analysis of existing WHOIS results of the statistical analysis of existing WHOIS information.
information. The purpose of this document is to build an object The purpose of this document is to build an object inventory to
inventory to facilitate discussions of data objects included in facilitate discussions of data objects included in Registration Data
Registration Data Access Protocol (RDAP) responses. Access Protocol (RDAP) responses.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for informational purposes.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." 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.
This Internet-Draft will expire on April 30, 2015. 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.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. RIR Objects Analysis . . . . . . . . . . . . . . . . . . . . 5 4. RIR Objects Analysis . . . . . . . . . . . . . . . . . . . . 7
4.1. WHOIS Data for Organizations Holding a Resource . . . . . 5 4.1. WHOIS Data for Organizations Holding a Resource . . . . . 7
4.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . . . 7 4.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . . . 9
4.3. WHOIS data for IP Addresses . . . . . . . . . . . . . . . 9 4.3. WHOIS Data for IP Addresses . . . . . . . . . . . . . . . 10
4.4. WHOIS data for ASNs . . . . . . . . . . . . . . . . . . . 11 4.4. WHOIS Data for ASNs . . . . . . . . . . . . . . . . . . . 12
4.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 13 4.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 13
5. DNR Objects Analysis . . . . . . . . . . . . . . . . . . . . 13 5. DNR Object Analysis . . . . . . . . . . . . . . . . . . . . . 14
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 13 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 14
5.2. Public Objects . . . . . . . . . . . . . . . . . . . . . 13 5.2. Public Objects . . . . . . . . . . . . . . . . . . . . . 14
5.2.1. WHOIS Data for Domains . . . . . . . . . . . . . . . 13 5.2.1. WHOIS Data for Domains . . . . . . . . . . . . . . . 15
5.2.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . 14 5.2.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . 16
5.2.2.1. Registrant . . . . . . . . . . . . . . . . . . . 15 5.2.2.1. Registrant . . . . . . . . . . . . . . . . . . . 16
5.2.2.2. Admin Contact . . . . . . . . . . . . . . . . . . 16 5.2.2.2. Admin Contact . . . . . . . . . . . . . . . . . . 18
5.2.2.3. Tech Contact . . . . . . . . . . . . . . . . . . 17 5.2.2.3. Tech Contact . . . . . . . . . . . . . . . . . . 19
5.2.2.4. Billing Contact . . . . . . . . . . . . . . . . . 18 5.2.2.4. Billing Contact . . . . . . . . . . . . . . . . . 20
5.2.3. WHOIS Data for Nameservers . . . . . . . . . . . . . 19 5.2.3. WHOIS Data for Nameservers . . . . . . . . . . . . . 21
5.2.4. WHOIS Data for Registrars . . . . . . . . . . . . . . 19 5.2.4. WHOIS Data for Registrars . . . . . . . . . . . . . . 21
5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 20 5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 22
5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 22 5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 24
5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 22 5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 24
5.4.2. Data Elements Analysis . . . . . . . . . . . . . . . 24 5.4.2. Data Element Analysis . . . . . . . . . . . . . . . . 26
5.4.3. Labels Analysis . . . . . . . . . . . . . . . . . . . 26 5.4.3. Label Analysis . . . . . . . . . . . . . . . . . . . 28
5.4.4. Other Objects Analysis . . . . . . . . . . . . . . . 26 5.4.4. Analysis of Other Objects . . . . . . . . . . . . . . 28
5.5. Limitations . . . . . . . . . . . . . . . . . . . . . . . 27 5.5. Limitations . . . . . . . . . . . . . . . . . . . . . . . 29
6. Reference Extension Objects . . . . . . . . . . . . . . . . . 27 6. Reference Extension Objects . . . . . . . . . . . . . . . . . 30
6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 28 6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 30
6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 28 6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 30
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 7. Security Considerations . . . . . . . . . . . . . . . . . . . 30
8. Security considerations . . . . . . . . . . . . . . . . . . . 28 8. Informative References . . . . . . . . . . . . . . . . . . . 31
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 32
10. Informative References . . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
Regional Internet Registries (RIRs) and Domain Name Registries (DNRs) Regional Internet Registries (RIRs) and Domain Name Registries (DNRs)
have historically maintained a lookup service to permit public access have historically maintained a lookup service to permit public access
to some portion of the registry database. Most registries offer the to some portion of the registry database. Most registries offer the
service via the WHOIS protocol [RFC3912], with additional services service via the WHOIS protocol [RFC3912], with additional services
being offered via world wide web pages, bulk downloads, and other being offered via World Wide Web pages, bulk downloads, and other
services, such as Routing Policy Specification Language (RPSL) services, such as Routing Policy Specification Language (RPSL)
[RFC2622]. [RFC2622].
Although the WHOIS protocol is widely adopted and supported, it has Although the WHOIS protocol is widely adopted and supported, it has
several shortcomings that limit its usefulness to the evolving needs several shortcomings that limit its usefulness to the evolving needs
of the Internet community. Specifically, of the Internet community. Specifically:
o It has no query and response format. o It has no query and response format.
o It does not support user authentication and access control for o It does not support user authentication or access control for
differentiated access. differentiated access.
o It has not been internationalized and thus does not consistently o It has not been internationalized and thus does not consistently
support Internationalized Domain Names (IDNs, described in support Internationalized Domain Names (IDNs) as described in
[RFC5890]). [RFC5890].
This document records an inventory of registry data objects to This document records an inventory of registry data objects to
facilitate discussions of registration data objects. The facilitate discussions of registration data objects. The
Registration Data Access Protocol (RDAP) Registration Data Access Protocol (RDAP) ([RFC7480], [RFC7482],
([I-D.ietf-weirds-rdap-query], [I-D.ietf-weirds-json-response], [RFC7483], and [RFC7484]) was developed using this inventory as
[I-D.ietf-weirds-using-http] and [I-D.ietf-weirds-bootstrap]) was input.
developed using this inventory as input.
In the number space, there were altogether five RIRs. Although all In the number space, there were altogether five RIRs. Although all
RIRs provided information about IP addresses, Autonomous System RIRs provided information about IP addresses, Autonomous System
Numbers (ASNs) and contacts, the data model used was different for Numbers (ASNs), and contacts, the data model used was different for
each RIR. In the domain name space, there were over 200 country code each RIR. In the domain name space, there were over 200 country code
Top-Level Domains (ccTLDs) and over 400 generic Top-Level Domains Top-Level Domains (ccTLDs) and over 400 generic Top-Level Domains
(gTLDs) when the document was published. Different domain name (gTLDs) when this document was published. Different Domain Name
registries may have different WHOIS response objects and formats. A Registries may have different WHOIS response objects and formats. A
common understanding of all these data formats was critical to common understanding of all these data formats was critical to
construct a single data model for each object. construct a single data model for each object.
This document describes the WHOIS data collection procedures and This document describes the WHOIS data collection procedures and
gives a data object inventory analysis based on the collected data gives an inventory analysis of data objects based on the collected
from five RIRs and 106 ccTLDs and 18 gTLDs from DNRs. The RIR data data from the five RIRs, 106 ccTLDs, and 18 gTLDs from DNRs. The RIR
objects are classified by the five RIRs into IP address, ASN, person data objects are classified by the five RIRs into IP address, ASN,
or contact and the organization that held the resource. According to person or contact, and the organization that held the resource.
the SPECIFICATION 4 (SPECIFICATION FOR REGISTRATION DATA PUBLICATION According to SPECIFICATION 4 ("SPECIFICATION FOR REGISTRATION DATA
SERVICES) of new gTLD applicant guide book [ICANN.AGB-201206] and the PUBLICATION SERVICES") of the new gTLD applicant guidebook
Extensible Provisioning Protocol (EPP) ([RFC5730], [RFC5731], [ICANN.AGB-201206] and the Extensible Provisioning Protocol (EPP)
([RFC5730], [RFC5731], [RFC5732], and [RFC5733]), the DNR data
[RFC5732] and [RFC5733]), the DNR data objects are classified into objects are classified by whether they relate to the domain, contact,
domain, contact, nameserver and registrar related objects. Other nameserver, or registrar. Objects that do not belong to the
objects that do not belong to above categories are viewed as private categories above are viewed as privately specified objects. In this
designed objects. In this document, there is no intent to analyze document, there is no intent to analyze all the query and response
all the query and response types existed in RIRs and DNRs. The most types that exist in RIRs and DNRs. The most common query objects are
common query objects are discussed, but other objects such as RPSL discussed, but other objects such as RPSL data structures used by
data structures used by Internet Routing Registries (IRRs) can be Internet Routing Registries (IRRs) can be documented later if the
documented later if the community feels it is necessary. community feels it is necessary.
2. Terminology 2. Terminology
o Data element -- The name of specific response object. o Data element - The name of a specific response object.
o Label -- The name given to a particular data element, which may o Label - The name given to a particular data element; it may vary
vary between registries. between registries.
o Most popular label -- The label which is most supported by the o Most popular label - The label that is most supported by the
registries. registries.
o Number of labels -- The number of different labels. o Number of labels - The number of different labels.
o Total count -- The number of registries that support a certain o No. of TLDs - The number of registries that support a certain data
data element. element.
3. Methodology 3. Methodology
WHOIS information, including port 43 response and web response data, WHOIS information, including port 43 response and web response data,
was collected between July 9th, 2012 and July 20th, 2012 following was collected between July 9, 2012, and July 20, 2012, following the
the procedures described below. procedures described below.
(1) First, find the RIR WHOIS servers of five RIRs which are (1) First, find the RIR WHOIS servers of the five RIRs, which are
AFRINIC, APNIC, ARIN, LACNIC and RIPE NCC. All the RIRs provide AFRINIC, APNIC, ARIN, LACNIC, and RIPE NCC. All the RIRs
information of IPs, ASNs and contacts. provide information about IP addresses, ASNs, and contacts.
(2) Query the corresponding IPs, ASNs, contacts and organizations (2) Query the corresponding IP addresses, ASNs, contacts, and
registered in five RIRs and make a comparative analysis of the organizations registered in the five RIRs. Then, make a
responses data. comparative analysis of the response data.
(3) Data elements with the same meaning, but using different labels, (3) Group together the data elements that have the same meaning but
were grouped together. use different labels.
DNR objects collections process: DNR object collection process:
(1) A programming script was applied to collect port 43 response (1) A programming script was applied to collect port 43 response
data from 294 ccTLDs. "nic.ccTLD" is used as the query string, data from 294 ccTLDs. "nic.ccTLD" was used as the query string,
which is usually registered in a domain registry. Responses for which is usually registered in a domain registry. Responses for
106 ccTLDs were received. 18 gTLDs' port 43 response data was 106 ccTLDs were received. 18 gTLDs' port 43 response data was
collected from their contracts with ICANN. Thus, the sample collected from their contracts with ICANN. Thus, the sample
size of port 43 WHOIS response data is 124 registries in total. size of port 43 WHOIS response data is 124 registries in total.
(2) WHOIS data from web was collected manually from the 124 (2) WHOIS data from the web was collected manually from the 124
registries that send port 43 WHOIS responses. registries that send port 43 WHOIS responses.
(3) Some of the responses which were collected by the program did (3) Some of the response that which were collected by the program
not seem to be correct, so data of the top 10 ccTLD registries, did not seem to be correct, so data for the top 10 ccTLD
like .de, .eu and .uk etc., was re-verified by querying domain registries, like .de, .eu, and .uk, was re-verified by querying
names other than "nic.ccTLD". domain names other than "nic.ccTLD".
(4) In accordance with the SPECIFICATION 4 of new gTLD applicant (4) In accordance with SPECIFICATION 4 of the new gTLD applicant
guide book [ICANN.AGB-201206] and the Extensible Provisioning guidebook [ICANN.AGB-201206] and EPP ([RFC5730], [RFC5731],
Protocol (EPP) ([RFC5730], [RFC5731], [RFC5732] and [RFC5733]), [RFC5732] and [RFC5733]), the response data objects are
the response data objects are classified into public and other classified into public and other data objects. Public data
data objects. Public data objects are those which are defined objects are those that are defined in the above references.
in the above references. Other objects are those which are Other objects are those that are privately specified data
privately specified data elements or objects in different elements or objects in different registries.
registries.
(5) Data elements with the same meaning, but using different labels, (5) Data elements with the same meaning, but using different labels,
were grouped together. The numbers of registries that support were grouped together. The number of registries that support
the data elements are shown in the total count column. each data element is shown in the "No. of TLDs" column.
4. RIR Objects Analysis 4. RIR Objects Analysis
4.1. WHOIS Data for Organizations Holding a Resource 4.1. WHOIS Data for Organizations Holding a Resource
The table 1 shows the organization objects of five RIRs. Table 1 shows the organization objects of the five RIRs.
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| RIR | AFRINIC |APNIC| ARIN | LACNIC | RIPE NCC | | RIR | AFRINIC |APNIC| ARIN | LACNIC | RIPE NCC |
| Objects | | | | | | | Objects | | | | | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Organization |organisation| NA | Name | Owner | org-name | | Organization |organisation| NA | Name | Owner | org-name |
| name | | | | | | | name | | | | | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Organization | org-name | NA | Handle | owner-id |organisation| | Organization | org-name | NA | Handle | owner-id |organisation|
| ID | | | | | | | ID | | | | | |
skipping to change at page 7, line 4 skipping to change at page 8, line 28
| record | | | | | | | record | | | | | |
| changed | | | | | | | changed | | | | | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| List of | NA | NA | NA | list of | NA | | List of | NA | NA | NA | list of | NA |
| resources | | | | resources | | | resources | | | | resources | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Source | source | NA | NA | NA | source | | Source | source | NA | NA | NA | source |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Reference | NA | NA | Ref | NA | NA | | Reference | NA | NA | Ref | NA | NA |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
Table 1. WHOIS Data for Organizations Holding a Resource Table 1. WHOIS Data for Organizations Holding a Resource
4.2. WHOIS Data for Contacts 4.2. WHOIS Data for Contacts
The table 2 shows the contact objects of five RIRs. Table 2 shows the contact objects of the five RIRs.
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| Data Element | AFRINIC | APNIC | ARIN | LACNIC | RIPE | | Data Element | AFRINIC | APNIC | ARIN | LACNIC | RIPE |
| | | | | | NCC | | | | | | | NCC |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| Name | person | person | Name | person | person | | Name | person | person | Name | person | person |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| Company | NA | NA | Company | NA | NA | | Company | NA | NA | Company | NA | NA |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| Postal | address | address | Address | address | address | | Postal | address | address | Address | address | address |
skipping to change at page 9, line 5 skipping to change at page 10, line 10
| Registration | changed | changed | Updated | changed | changed | | Registration | changed | changed | Updated | changed | changed |
| update | | | | | | | update | | | | | |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| Source | source | source | NA | NA | source | | Source | source | source | NA | NA | source |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| Reference | NA | NA | Ref | NA | NA | | Reference | NA | NA | Ref | NA | NA |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
Table 2. WHOIS Data for Contacts Table 2. WHOIS Data for Contacts
4.3. WHOIS data for IP Addresses 4.3. WHOIS Data for IP Addresses
The table 4 shows the IP address objects of five RIRs. Table 4 shows the IP address objects of the five RIRs.
Note: Because the length limit of each line is 72 characters, too Note: Due to the 72-character limit on line length, strings in some
long strings in some table unites are split into two or more parts, cells of the table are split into two or more parts, which are placed
which are placed in order in different lines of the same table unit. on separate lines within the same cell. A hyphen in the final
A hyphen in the final position of a string indicates this string and position of a string indicates that the string has been split due to
the one in the next line of the same table unit are divided because the length limit.
of the length limit.
+----------+----------+----------+ +----------+----------+----------+
| Adminis- | | abuse-- | | Adminis- | | abuse-- |
| trative | admin-c | mailbox | | trative | admin-c | mailbox |
| contact | | | | contact | | |
+----------+----------+----------+ +----------+----------+----------+
Table 3. Example of String Splitting Table 3. Example of String Splitting
For instance, the original strings in the table units of table 3 are For instance, the original strings in the cells of Table 3 are
"Administrative contact", "admin-c" and "abuse-mailbox", "Administrative contact", "admin-c", and "abuse-mailbox",
respectively. respectively.
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Data | AFRINIC| APNIC | ARIN | LACNIC | RIPE NCC | | Data | AFRINIC| APNIC | ARIN | LACNIC | RIPE NCC |
| Element | | | | | | | Element | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| IP | inetnum| inetnum | NetRange | NA | inetnum | | IP | inetnum| inetnum | NetRange | NA | inetnum |
| address | | | | | | | address | | | | | |
| range | | | | | | | range | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| IPV6 |inet6num| inet6num | CIDR |inetnum | inet6num | | IPv6 |inet6num| inet6num | CIDR |inetnum | inet6num |
| address | | | | | | | address | | | | | |
| range | | | | | | | range | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Description| descr | descr | NetName | NA | descr | | Description| descr | descr | NetName | NA | descr |
| | | | | | | | | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Remarks | remarks| remarks | NA | NA | remarks | | Remarks | remarks| remarks | NA | NA | remarks |
| | | | | | | | | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Origin AS | NA | NA | OriginAS |OriginAS| NA | | Origin AS | NA | NA | OriginAS |OriginAS| NA |
| | | | |(future)| | | | | | |(future)| |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Network | netname| netname | NetHandle |inetrev | netname | | Network | netname| netname | NetHandle |inetrev | netname |
| name/ID | | | | | | | name/ID | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Maintainer | mnt-by | NA | NA | NA | mnt-by | | Maintainer | mnt-by | NA | NA | NA | mnt-by |
| Object | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Maintainer | mnt-- | NA | NA | NA | NA | | Maintainer | mnt-- | NA | NA | NA | NA |
| | lower | | | | | | Sub- | lower | | | | |
| assignments| | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Adminis- | admin-c| admin-c | OrgId | ownerid| admin-c | | Adminis- | admin-c| admin-c | OrgId | ownerid| admin-c |
| trative | | | | | | | trative | | | | | |
| contact | | | | | | | contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Parent | parent | NA | Parent | NA | NA | | Parent | parent | NA | Parent | NA | NA |
| range | | | | | | | range | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Status | status | status | NetType | status | status | | Status | status | status | NetType | status | status |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
skipping to change at page 11, line 9 skipping to change at page 12, line 37
| Referral | NA | NA | RNOCHandle | NA | NA | | Referral | NA | NA | RNOCHandle | NA | NA |
| NOC | | | | | | | NOC | | | | | |
| contact | | | | | | | contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Name | NA | NA | NA | nserver| NA | | Name | NA | NA | NA | nserver| NA |
| server | | | | | | | server | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
Table 4. WHOIS Data for IP Addresses Table 4. WHOIS Data for IP Addresses
4.4. WHOIS data for ASNs 4.4. WHOIS Data for ASNs
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Data | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC | | Data | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC |
| Element | | | | | | | Element | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| ID | aut-num | aut-num | ASNumber | aut-num | aut-num | | ID | aut-num | aut-num | ASNumber | aut-num | aut-num |
| | | | | | | | | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Description | descr | descr | NA | NA | descr | | Description | descr | descr | NA | NA | descr |
| | | | | | | | | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
skipping to change at page 12, line 34 skipping to change at page 13, line 22
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Organization | NA | nic-hdl | NA | owner-c | organi- | | Organization | NA | nic-hdl | NA | owner-c | organi- |
| ID | | | | | sation | | ID | | | | | sation |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Notify | notify | notify | NA | NA | NA | | Notify | notify | notify | NA | NA | NA |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Abuse | NA | NA | OrgAbuse | abuse-c | NA | | Abuse | NA | NA | OrgAbuse | abuse-c | NA |
| contact | | | Handle | | | | contact | | | Handle | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Maintainer | mnt-by | mnt-by | NA | NA | mnt-by | | Maintainer | mnt-by | mnt-by | NA | NA | mnt-by |
| Object | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Maintainer |mnt-lower| mnt-lower| NA | NA |mnt-lower | | Maintainer |mnt-lower| mnt-lower| NA | NA |mnt-lower |
| | | | | | | | Sub- | | | | | |
| assignments | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Maintainer | NA | NA | NA | NA | mnt-ref | | Maintainer | NA | NA | NA | NA | mnt-ref |
| Organization | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
|Registration | changed | NA | RegDate | created | NA | |Registration | changed | NA | RegDate | created | NA |
| Date | | | | | | | Date | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
|Registration | changed | changed | Updated | changed | NA | |Registration | changed | changed | Updated | changed | NA |
| update | | | | | | | update | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Source | source | source | NA | NA | source | | Source | source | source | NA | NA | source |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
Table 5. WHOIS Data for ASNs Table 5. WHOIS Data for ASNs
4.5. Conclusion 4.5. Conclusion
As it could be observed, some data elements were not supported by all As can be observed, some data elements were not supported by all
RIRs and some ones were named as different labels by different RIRs. RIRs, and some were given different labels by different RIRs. Also,
There were identical labels used for different data elements by there were identical labels used for different data elements by
different RIRs. In order to construct a single data model for each different RIRs. In order to construct a single data model for each
object, a selection of the most common and useful fields was made. object, a selection of the most common and useful fields was made.
That initial selection was the starting point for That initial selection was the starting point for [RFC7483].
[I-D.ietf-weirds-json-response].
5. DNR Objects Analysis 5. DNR Object Analysis
5.1. Overview 5.1. Overview
WHOIS data was collected from 124 registries, including 106 ccTLDs WHOIS data was collected from 124 registries, including 106 ccTLDs
and 18 gTLDs. All the 124 registries support domain queries. Among and 18 gTLDs. All 124 registries support domain queries. Among 124
124 registries, eight ccTLDs and 15 gTLDs support queries for registries, eight ccTLDs and 15 gTLDs support queries for specific
specific contact persons or roles. 10 ccTLDs and 18 gTLDs support contact persons or roles. 10 ccTLDs and 18 gTLDs support queries by
queries by nameserver. Four ccTLDs and 18 gTLDs support registrar nameserver. Four ccTLDs and 18 gTLDs support registrar queries.
queries. Domain WHOIS data contain 68 data elements that use a total Domain WHOIS data contain 68 data elements that use a total of 550
of 550 labels. There is a total of 392 other objects for domain labels. There is a total of 392 other objects for domain WHOIS data.
WHOIS data. The raw data can be accessed at WHOIS Statistics Data
File [Stat-Data-File].
5.2. Public Objects 5.2. Public Objects
As mentioned above, public objects are those data elements selected As mentioned above, public objects are those data elements selected
according to the new gTLD applicant guide book and EPP protocols. according to the new gTLD applicant guidebook and EPP. They are
They are generally classified into four categories: domain, contact, generally classified into four categories by whether they are related
nameserver and registrar related information. to the domain, contact, nameserver, or registrar.
5.2.1. WHOIS Data for Domains 5.2.1. WHOIS Data for Domains
WHOIS replies about domains include "Domain Name", "Creation Date", WHOIS replies about domains include "Domain Name", "Creation Date",
"Domain Status", "Expiration Date", "Updated Date", "Domain ID", "Domain Status", "Expiration Date", "Updated Date", "Domain ID",
"DNSSEC" and "Last Transferred Date". The table 6 gives the element "DNSSEC", and "Last Transferred Date". Table 6 gives the element
name, most popular label and corresponding numbers of TLDs and name, most popular label, and the corresponding numbers of TLDs and
labels. labels.
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| Data Element | Most Popular | No. of | No. of | | Data Element | Most Popular | No. of | No. of |
| | Label | TLDs | Labels | | | Label | TLDs | Labels |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| Domain Name | Domain Name | 118 | 6 | | Domain Name | Domain Name | 118 | 6 |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| Creation Date | Created | 106 | 24 | | Creation Date | Created | 106 | 24 |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| Domain Status | Status | 95 | 8 | | Domain Status | Status | 95 | 8 |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| Expiration Date | Expiration Date | 81 | 21 | | Expiration Date | Expiration Date | 81 | 21 |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| Updated Date | Modified | 70 | 20 | | Updated Date | Modified | 70 | 20 |
skipping to change at page 14, line 29 skipping to change at page 15, line 37
| Domain ID | Domain ID | 34 | 5 | | Domain ID | Domain ID | 34 | 5 |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| DNSSEC | DNSSEC | 14 | 4 | | DNSSEC | DNSSEC | 14 | 4 |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| Last Transferred | Last Transferred | 4 | 3 | | Last Transferred | Last Transferred | 4 | 3 |
| Date | Date | | | | Date | Date | | |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
Table 6. WHOIS Data for Domains Table 6. WHOIS Data for Domains
Several statistical conclusion that obtained from above data include: Several statistical conclusions obtained from above data are:
o About 95.16% of the 124 registries support a "Domain Name" data o 95.16% of the 124 registries support a "Domain Name" data element.
element.
o Nearly 85.48% of the 124 registries support a "Creation Date" data o 85.48% of the 124 registries support a "Creation Date" data
element. element.
o Almost 76.61% of the 124 registries support a "Domain Status" data o 76.61% of the 124 registries support a "Domain Status" data
element element.
o On the other hand, some elements such as "DNSSEC" and "Last o On the other hand, some elements such as "DNSSEC" and "Last
Transferred Date" are only supported by 11.29% and 3.23% of all Transferred Date" are only supported by 11.29% and 3.23% of the
the registries seperately. registries, respectively.
5.2.2. WHOIS Data for Contacts 5.2.2. WHOIS Data for Contacts
In the domain name space, contacts are typically divided into In the domain name space, contacts are typically divided into
registrant, administrative contact, technical contact and billing registrant, administrative contact, technical contact, and billing
contact. contact.
5.2.2.1. Registrant 5.2.2.1. Registrant
The table 7 shows all the contact information for a registrant. 14 Table 7 shows all the contact information for a registrant. 14 data
data elements are listed below. elements are listed below.
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
| Registrant Name | Name | 65 | 7 | | Registrant Name | Name | 65 | 7 |
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
| Registrant Email | Registrant Email | 59 | 7 | | Registrant Email | Registrant Email | 59 | 7 |
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
| Registrant ID | Registrant ID | 50 | 12 | | Registrant ID | Registrant ID | 50 | 12 |
skipping to change at page 15, line 51 skipping to change at page 17, line 11
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
| Registrant Phone | Registrant Phone | 18 | 2 | | Registrant Phone | Registrant Phone | 18 | 2 |
| Ext. | Ext. | | | | Ext. | Ext. | | |
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
| Registrant Fax Ext | Registrant Fax Ext | 17 | 2 | | Registrant Fax Ext | Registrant Fax Ext | 17 | 2 |
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
Table 7. Registrant Table 7. Registrant
Among all the data elements, only "Registrant Name" is supported by Among all the data elements, only "Registrant Name" is supported by
more than one half of registries and those supported by more than one more than one half of registries. Those supported by more than one
third of registries are: "Registrant Name", "Registrant Email", third of registries are: "Registrant Name", "Registrant Email",
"Registrant ID", "Registrant Phone", "Registrant Fax", "Registrant "Registrant ID", "Registrant Phone", "Registrant Fax", "Registrant
Organization" and "Registrant Country Code". Organization", and "Registrant Country Code".
5.2.2.2. Admin Contact 5.2.2.2. Admin Contact
The table 8 shows all the contact information for an administrative Table 8 shows all the contact information for an administrative
contact. 14 data elements are listed below. contact. 14 data elements are listed below.
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Admin Street | Address | 64 | 19 | | Admin Street | Address | 64 | 19 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Admin Name | Admin Name | 60 | 9 | | Admin Name | Admin Name | 60 | 9 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
skipping to change at page 16, line 49 skipping to change at page 18, line 47
| Admin Country | Admin Country | 17 | 5 | | Admin Country | Admin Country | 17 | 5 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Admin Phone Ext. | Admin Phone Ext. | 17 | 3 | | Admin Phone Ext. | Admin Phone Ext. | 17 | 3 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Admin Fax Ext. | Admin Fax Ext. | 17 | 3 | | Admin Fax Ext. | Admin Fax Ext. | 17 | 3 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
Table 8. Admin Contact Table 8. Admin Contact
Among all the data elements, only "Admin Street" is supported by more Among all the data elements, only "Admin Street" is supported by more
than one half of registries and those supported by more than one than one half of registries. Those supported by more than one third
third of registries are: "Admin Street", "Admin Name", "Admin Email", of registries are: "Admin Street", "Admin Name", "Admin Email",
"Admin ID", "Admin Fax", "Admin Phone", "Admin Organization" and "Admin ID", "Admin Fax", "Admin Phone", "Admin Organization", and
"Admin Country Code". "Admin Country Code".
5.2.2.3. Tech Contact 5.2.2.3. Tech Contact
The table 9 shows all the information for a domain name technical Table 9 shows all the information for a domain name technical
contact. 14 data elements are listed below. contact. 14 data elements are listed below.
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Tech Email | Tech Email | 59 | 9 | | Tech Email | Tech Email | 59 | 9 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Tech ID | Tech ID | 55 | 16 | | Tech ID | Tech ID | 55 | 16 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
skipping to change at page 17, line 49 skipping to change at page 19, line 47
| Tech Country | Tech Country | 18 | 5 | | Tech Country | Tech Country | 18 | 5 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Tech Fax Ext | Tech Fax Ext | 18 | 3 | | Tech Fax Ext | Tech Fax Ext | 18 | 3 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Tech Phone Ext. | Tech Phone Ext. | 13 | 3 | | Tech Phone Ext. | Tech Phone Ext. | 13 | 3 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
Table 9. Tech Contact Table 9. Tech Contact
Among all the data elements, there are no elements supported by more Among all the data elements, there are no elements supported by more
than one half of registries and those supported by more than one than one half of registries. Those supported by more than one third
third of registries are: "Tech Email", "Tech ID", "Tech Name","Tech of registries are: "Tech Email", "Tech ID", "Tech Name", "Tech Fax",
Fax","Tech Phone" and "Tech Country Code". "Tech Phone", and "Tech Country Code".
5.2.2.4. Billing Contact 5.2.2.4. Billing Contact
The table 10 shows all the information for a domain name billing Table 10 shows all the information for a domain name billing contact.
contact. 14 data elements are listed below. 14 data elements are listed below.
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Billing Name | Name | 47 | 5 | | Billing Name | Name | 47 | 5 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Billing Fax | Fax | 43 | 6 | | Billing Fax | Fax | 43 | 6 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Billing Email | Email Address | 42 | 7 | | Billing Email | Email Address | 42 | 7 |
skipping to change at page 18, line 50 skipping to change at page 20, line 50
| Billing Country | Billing Country | 13 | 5 | | Billing Country | Billing Country | 13 | 5 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Billing Phone Ext. | Billing Phone Ext. | 10 | 2 | | Billing Phone Ext. | Billing Phone Ext. | 10 | 2 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Billing Fax Ext | Billing Fax Ext | 10 | 2 | | Billing Fax Ext | Billing Fax Ext | 10 | 2 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
Table 10. Billing Contact Table 10. Billing Contact
Among all the data elements, there are no elements supported by more Among all the data elements, there are no elements supported by more
than one half of registries and those supported by more than one than one half of registries. Those supported by more than one third
third of registries are "Billing Name", "Billing Fax" and "Billing of registries are "Billing Name", "Billing Fax", and "Billing Email".
Email".
5.2.3. WHOIS Data for Nameservers 5.2.3. WHOIS Data for Nameservers
114 registries (about 92% of all the 124 registries) have the 114 registries (about 92% of the 124 registries) have the
"nameserver" data element in their WHOIS responses. However, there "nameserver" data element in their WHOIS responses. However, there
are 63 different labels for this element, just as shown in table 11. are 63 different labels for this element, as shown in Table 11. The
The top three labels for this element are "Name Server" which is top three labels for this element are "Name Server" (which is
supported by 25% of all the registries, "Name Servers" which is supported by 25% of the registries), "Name Servers" (which is
supported by 16% of all the registries and "nserver" which is supported by 16% of the registries), and "nserver" (which is
supported by 12% of all the registries. supported by 12% of the registries).
+--------------+--------------------+-------------+---------------+ +--------------+--------------------+-------------+---------------+
| Data Element | Most Popular Label | No. of TLDs | No. of Labels | | Data Element | Most Popular Label | No. of TLDs | No. of Labels |
+--------------+--------------------+-------------+---------------+ +--------------+--------------------+-------------+---------------+
| NameServer | Name Server | 114 | 63 | | NameServer | Name Server | 114 | 63 |
+--------------+--------------------+-------------+---------------+ +--------------+--------------------+-------------+---------------+
Table 11. WHOIS Data for Nameservers Table 11. WHOIS Data for Nameservers
Some registries have nameserver elements such like "nameserver 1", Some registries have nameserver elements such like "nameserver 1",
skipping to change at page 19, line 48 skipping to change at page 21, line 48
| Created by | Created by | 14 | 3 | | Created by | Created by | 14 | 3 |
| Registrar | | | | | Registrar | | | |
+-------------------+---------------------+-----------+-------------+ +-------------------+---------------------+-----------+-------------+
| Updated by | Last Updated by | 11 | 3 | | Updated by | Last Updated by | 11 | 3 |
| Registrar | Registrar | | | | Registrar | Registrar | | |
+-------------------+---------------------+-----------+-------------+ +-------------------+---------------------+-----------+-------------+
Table 12. WHOIS Data for Registrars Table 12. WHOIS Data for Registrars
67.7% of the registries have the "Sponsoring Registrar" data element. 67.7% of the registries have the "Sponsoring Registrar" data element.
Elements such as "Created by Registrar" and "Updated by Registrar" The elements "Created by Registrar" and "Updated by Registrar" are
are supported by 11.3% and 8.9% of the registries. supported by 11.3% and 8.9% of the registries, respectively.
5.3. Other Objects 5.3. Other Objects
So-called "other objects" are those data elements that are privately So-called "other objects" are those data elements that are privately
specified or are difficult to be classified. There are 392 other specified or are difficult to be classified. There are 392 other
objects altogether. The table 13 lists the top 50 other objects objects altogether. Table 13 lists the top 50 other objects found
according to the data collection result. during data collection.
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Data Element | No. of TLDs | | Data Element | No. of TLDs |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Registrant | 41 | | Registrant | 41 |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Phone | 32 | | Phone | 32 |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Technical contact | 26 | | Technical contact | 26 |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
skipping to change at page 22, line 29 skipping to change at page 24, line 30
Table 13. The Top 50 Other Objects Table 13. The Top 50 Other Objects
Some registries returned things that looked like labels, but were Some registries returned things that looked like labels, but were
not. For example, in this reply: not. For example, in this reply:
Registrant: Registrant:
Name: Name:
Email: Email:
... ...
"Name" and "Email" appeared to be data elements, but "Registrant" was "Name" and "Email" appeared to be data elements, but "Registrant" did
not. The inventory work proceeded on that assumption, i.e., there not. The inventory work proceeded on that assumption, i.e., there
were two data elements to be recorded in this example. were two data elements to be recorded in this example.
Some other data elements, like "Remarks", "anniversary" and "Customer Some other data elements, like "Remarks", "anniversary", and
service Contact" etc., are designed particularly for their own "Customer service Contact", are designed particularly for their own
purpose by different registries. purpose by different registries.
5.4. Conclusion 5.4. Conclusion
5.4.1. Preliminary Statistics 5.4.1. Preliminary Statistics
Some preliminary conclusions could be drawn from the raw data. Some preliminary conclusions could be drawn from the raw data.
o All of the 124 domain registries have the object names in their o All of the 124 domain registries have the object names in their
responses although they are in various formats. responses, although they are in various formats.
o Of the 118 WHOIS services contacted, 65 registries show their o Of the 118 WHOIS services contacted, 65 registries show their
registrant contact. About half of the registries (60 registries) registrant contact. About half of the registries (60 registries)
support admin contact information. There are 47 registries, which support admin contact information. There are 47 registries, which
is about one third of the total number, have technical and billing is about one third of the total number, that have technical and
contact information. Only seven of all the 124 registries give billing contact information. Only seven of the 124 registries
their abuse email in a "remarks" section. No explicit abuse give their abuse email in a "remarks" section. No explicit abuse
contact information is provided. contact information is provided.
o There are mainly two presentation formats. One is key:value, the o There are mainly two presentation formats. One is key-value; the
other is data block format. Example of key-value format: other is data block format. Example of key-value format:
Domain Information Domain Information
Query: nic.example.com Query: nic.example.com
Status: Delegated Status: Delegated
Created: 17 Apr 2004 Created: 17 Apr 2004
Modified: 14 Nov 2010 Modified: 14 Nov 2010
Expires: 31 Dec 9999 Expires: 31 Dec 9999
Name Servers: ns.example.net Name Servers: ns.example.net
ns1.na.example.net ns1.na.example.net
skipping to change at page 24, line 44 skipping to change at page 26, line 20
Titular: Titular:
John (nic.example.org) john@nic.example.org John (nic.example.org) john@nic.example.org
NIC Example NIC Example
Av. Veracruz con calle Cali, Edif Aguila, Urb. Las Mercedes Av. Veracruz con calle Cali, Edif Aguila, Urb. Las Mercedes
Caracas, Distrito Capital VE Caracas, Distrito Capital VE
0212-1234567 (FAX) +582123456789 0212-1234567 (FAX) +582123456789
o 11 registries give local script responses. The WHOIS information o 11 registries give local script responses. The WHOIS information
of other registries are all represented in English. of other registries are all represented in English.
5.4.2. Data Elements Analysis 5.4.2. Data Element Analysis
The top 10 data elements are listed in table 14: The top 10 data elements are listed in Table 14.
+----------------------+-------------+ +----------------------+-------------+
| Data Element | No. of TLDs | | Data Element | No. of TLDs |
+----------------------+-------------+ +----------------------+-------------+
| Domain Name | 118 | | Domain Name | 118 |
+----------------------+-------------+ +----------------------+-------------+
| Name Server | 114 | | Name Server | 114 |
+----------------------+-------------+ +----------------------+-------------+
| Creation Date | 106 | | Creation Date | 106 |
+----------------------+-------------+ +----------------------+-------------+
skipping to change at page 25, line 31 skipping to change at page 27, line 5
+----------------------+-------------+ +----------------------+-------------+
| Registrant Name | 65 | | Registrant Name | 65 |
+----------------------+-------------+ +----------------------+-------------+
| Admin Street | 64 | | Admin Street | 64 |
+----------------------+-------------+ +----------------------+-------------+
| Admin Name | 60 | | Admin Name | 60 |
+----------------------+-------------+ +----------------------+-------------+
Table 14. The Top 10 Data Elements Table 14. The Top 10 Data Elements
Most of the domain related WHOIS information is included in the top Most of the domain-related WHOIS information is included in the top
10 data elements. Other information like name server and registrar 10 data elements. Other information like name server and registrar
name are also supported by most registries. name is also supported by most registries.
A cumulative distribution analysis of all the data elements was done. A cumulative distribution analysis of all the data elements was done.
(1) About 5% of the data elements discovered by the inventory work (1) About 5% of the data elements discovered by the inventory work
are supported by over 111 (90%) registries. are supported by 111 registries (i.e., 90%).
(2) About 30% of the data elements discovered by the inventory work (2) About 30% of the data elements discovered by the inventory work
are supported by over 44 (35%) registries. are supported by 44 registries (i.e., 35%).
(3) About 60% of the data elements discovered by the inventory work (3) About 60% of the data elements discovered by the inventory work
are supported by over 32 (26%) registries. are supported by 32 registries (i.e., 26%).
(4) About 90% of the data elements discovered by the inventory work (4) About 90% of the data elements discovered by the inventory work
are supported by over 14 (11%) registries. are supported by 14 registries (i.e., 11%).
From the above result, it is clear that only a few registries support 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 all the public objects, most of the registries support just some of
all the objects. the objects.
5.4.3. Labels Analysis 5.4.3. Label Analysis
The top 10 labels of different data elements include: The top 10 labels of different data elements are listed in Table 15.
+-------------------+---------------+ +-------------------+---------------+
| Labels | No. of Labels | | Labels | No. of Labels |
+-------------------+---------------+ +-------------------+---------------+
| Name Server | 63 | | Name Server | 63 |
+-------------------+---------------+ +-------------------+---------------+
| Creation Date | 24 | | Creation Date | 24 |
+-------------------+---------------+ +-------------------+---------------+
| Expiration Date | 21 | | Expiration Date | 21 |
+-------------------+---------------+ +-------------------+---------------+
skipping to change at page 26, line 35 skipping to change at page 28, line 35
+-------------------+---------------+ +-------------------+---------------+
| Admin ID | 16 | | Admin ID | 16 |
+-------------------+---------------+ +-------------------+---------------+
| Tech Street | 16 | | Tech Street | 16 |
+-------------------+---------------+ +-------------------+---------------+
| Billing Street | 13 | | Billing Street | 13 |
+-------------------+---------------+ +-------------------+---------------+
Table 15. The Top 10 Labels Table 15. The Top 10 Labels
As explained above, the "Name Server" label is a unique example that As explained above, the "Name Server" label is a unique example
many registries define the name server elements from "nameserver 1" because many registries define the name server elements from
till "nameserver n". Thus, the count of labels for name servers is "nameserver 1" through "nameserver n". Thus, the count of labels for
much higher than other elements. Data elements representing dates name servers is much higher than other elements. Data elements
and street addresses were also common. representing dates and street addresses were also common.
A cumulative distribution analysis of label numbers was done. About A cumulative distribution analysis of label numbers was done. About
90% of data elements have more than two labels. It is therefore 90% of data elements have more than two labels. It is therefore
necessary to specify a standard and unified format for object names necessary to specify a standard and unified format for object names
in a WHOIS response. in a WHOIS response.
5.4.4. Other Objects Analysis 5.4.4. Analysis of Other Objects
The results indicate that there are 392 other data objects in total The results indicate that there are 392 other data objects in total
that are not easy to be classified or are privately defined by that are not easy to be classified or are privately defined by
various registries. The top 50 other objects are listed in the table various registries. The top 50 other objects are listed in Table 13
in section 4.3. It is clear that various different objects are in Section 5.3. It is clear that various different objects are
designed for some particular purpose. In order to ensure uniqueness designed for some particular purpose. In order to ensure uniqueness
of JSON names used in the RDAP service, establishment of an IANA of JSON names used in the RDAP service, establishment of an IANA
registry is advised. registry is advised.
5.5. Limitations 5.5. Limitations
This section enumerates limitations of the survey and some This section lists the limitations of the survey and some assumptions
assumptions that were made in the execution of this work. that were made in the execution of this work.
o The input "nic.ccTLD" maybe is not a good choice, for the term o The input "nic.ccTLD" may not be a good choice, for the term "nic"
"nic" is often specially used by the corresponding ccTLD so the is often specially used by the corresponding ccTLD, so the
collected WHOIS data may be customized and different from the collected WHOIS data may be customized and different from the
common data. common data.
o Since the programming script queried the "nic.ccTLD" in an o Since the programming script queried the "nic.ccTLD" in an
anonymous way, only the public WHOIS data from WHOIS servers anonymous way, only the public WHOIS data from WHOIS servers
having nic.ccTLD were collected. So the private WHOIS data were having nic.ccTLD were collected. So, the private WHOIS data were
not covered by this document. not covered by this document.
o 11 registries did not provide responses in English. The o 11 registries did not provide responses in English. The
classification of data elements within their responses may not be classification of data elements within their responses may not be
accurate. accurate.
o The extension data elements are used randomly by different o The extension data elements are used randomly by different
registries. It is difficult to do statistical analysis. registries. It is difficult to do statistical analysis.
o Sample sizes of contact, name server and registrar queries are o Sample sizes of contact, name server, and registrar queries are
small. small.
* Only WHOIS queries for contact ID, nameserver and registrar * Only WHOIS queries for contact ID, nameserver, and registrar
were used. were used.
* Some registries may not support contact, name server or * Some registries may not support contact, name server, or
registrar queries. registrar queries.
* Some may not support query contact by ID. * Some may not support query contact by ID.
* Contact information of some registries may be protected. * Contact information of some registries may be protected.
6. Reference Extension Objects 6. Reference Extension Objects
There are some objects that are included in the existing WHOIS system There are some objects that are included in the existing WHOIS system
but not mentioned in [I-D.ietf-weirds-json-response]. This document but not mentioned in [RFC7483]. This document is intended to give a
is intended to give a list of reference extension objects for list of reference extension objects for discussion.
discussion.
6.1. RIR Reference Extension Objects 6.1. RIR Reference Extension Objects
o company -- the company name registered by the registrant. o company - the company name registered by the registrant.
o maintainer -- authentication information that identifies who can o maintainer - authentication information that identifies who can
modify the contents of this object. modify the contents of this object.
o list of resources -- a list of IPv4 addresses, IPv6 addresses and o list of resources - a list of IPv4 addresses, IPv6 addresses, and
Autonomous System numbers. Autonomous System numbers.
o referral NOC contact -- the Network Operation Center contact. o referral NOC contact - the Network Operations Center contact.
6.2. DNR Reference Extension Objects 6.2. DNR Reference Extension Objects
The following objects are selected from the top 50 other objects in The following objects are selected from the top 50 other objects in
section 5.3 that are supported by more than five registries. These Section 5.3 that are supported by more than five registries. These
objects are considered as possible extension objects. objects are considered as possible extension objects.
o zone-c -- The identifier of a 'role' object with authority over a o zone-c - The identifier of a 'role' object with authority over a
zone. zone.
o maintainer -- authentication information that identifies who can o maintainer - authentication information that identifies who can
modify the contents of this object. modify the contents of this object.
o Registration URL -- typically the website address of a registry. o Registration URL - typically the website address of a registry.
o anonymous -- whether the registration information is anonymous or o anonymous - whether the registration information is anonymous or
not. not.
o hold -- whether the domain is "on hold" or not. o hold - whether the domain is "on hold" or not.
o nsl-id -- nameserver list ID.
o obsoleted -- whether a domain is obsoleted or not.
o Customer Service Contact -- a kind of contact.
7. IANA Considerations
This document does not specify any IANA actions. [RFC Editor: Please
delete this section prior to publication.]
8. Security considerations
This document does not provide any other security services or
introduce any additional considerations.
9. Acknowledgements
This document is the work product of the IETF's WEIRDS working group,
of which Olaf Kolkman and Murray Kucherawy were chairs.
The authors especially thank the following individuals who gave their o nsl-id - nameserver list ID.
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.
10. Informative References o obsoleted - whether a domain is obsoleted or not.
[I-D.ietf-weirds-bootstrap] o Customer Service Contact - a kind of contact.
Blanchet, M., "Finding the Authoritative Registration Data
(RDAP) Service", draft-ietf-weirds-bootstrap-09 (work in
progress), October 2014.
[I-D.ietf-weirds-json-response] 7. Security Considerations
Newton, A. and S. Hollenbeck, "JSON Responses for the
Registration Data Access Protocol (RDAP)", draft-ietf-
weirds-json-response-10 (work in progress), October 2014.
[I-D.ietf-weirds-rdap-query] This document does not provide any security services or introduce
Newton, A. and S. Hollenbeck, "Registration Data Access additional considerations to those discussed in [RFC7481].
Protocol Query Format", draft-ietf-weirds-rdap-query-15
(work in progress), October 2014.
[I-D.ietf-weirds-using-http] 8. Informative References
Newton, A., Ellacott, B., and N. Kong, "HTTP usage in the
Registration Data Access Protocol (RDAP)", draft-ietf-
weirds-using-http-13 (work in progress), October 2014.
[ICANN.AGB-201206] [ICANN.AGB-201206]
ICANN, "gTLD Applicant Guidebook", June 2012, ICANN, "gTLD Applicant Guidebook", June 2012,
<http://newgtlds.icann.org/en/applicants/agb/ <http://newgtlds.icann.org/en/applicants/agb/
guidebook-full-04jun12-en.pdf>. guidebook-full-04jun12-en.pdf>.
[RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D., [RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D.,
Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra, Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra,
"Routing Policy Specification Language (RPSL)", RFC 2622, "Routing Policy Specification Language (RPSL)", RFC 2622,
June 1999. June 1999, <http://www.rfc-editor.org/info/rfc2622>.
[RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912,
September 2004. September 2004, <http://www.rfc-editor.org/info/rfc3912>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, August 2009. STD 69, RFC 5730, August 2009,
<http://www.rfc-editor.org/info/rfc5730>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, August 2009. Domain Name Mapping", STD 69, RFC 5731, August 2009,
<http://www.rfc-editor.org/info/rfc5731>.
[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Host Mapping", STD 69, RFC 5732, August 2009. Host Mapping", STD 69, RFC 5732, August 2009,
<http://www.rfc-editor.org/info/rfc5732>.
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Contact Mapping", STD 69, RFC 5733, August 2009. Contact Mapping", STD 69, RFC 5733, August 2009,
<http://www.rfc-editor.org/info/rfc5733>.
[RFC5890] Klensin, J., "Internationalized Domain Names for [RFC5890] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework", Applications (IDNA): Definitions and Document Framework",
RFC 5890, August 2010. RFC 5890, August 2010,
<http://www.rfc-editor.org/info/rfc5890>.
[Stat-Data-File]
Kong, N., Zhou, L., and G. Deng, "WHOIS Statistics Data
File", July 2012, <https://docs.google.com/
open?id=0B96TtoK8a--MTTRuVUt3UHZMdEk>.
Appendix A. Change Log
Initial -00: Adopted as working group document.
-01:
* Added Change Log section.
* Added RIR data objects.
* Exchanged section 2 and section 3.
-02:
* Modified some object names in the section of RIR Objects
Analysis.
* Added reference extension objects.
-03: [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>.
* Updated to the keep-alive version. Changed the expiry dates [RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the
and the draft number. Registration Data Access Protocol (RDAP)", RFC 7481, March
2015, <http://www.rfc-editor.org/info/rfc7481>.
-04: [RFC7482] Newton, A. and S. Hollenbeck, "Registration Data Access
Protocol (RDAP) Query Format", RFC 7482, March 2015,
<http://www.rfc-editor.org/info/rfc7482>.
* Updated based on Murray's and Edward's comments during the WG [RFC7483] Newton, A. and S. Hollenbeck, "JSON Responses for the
last call. Registration Data Access Protocol (RDAP)", RFC 7483, March
2015, <http://www.rfc-editor.org/info/rfc7483>.
-05: [RFC7484] Blanchet, M., "Finding the Authoritative Registration Data
(RDAP) Service", RFC 7484, March 2015,
<http://www.rfc-editor.org/info/rfc7484>.
* Addressed AD feedback. Acknowledgements
-06: This document is the work product of the IETF's WEIRDS working group,
of which Olaf Kolkman and Murray Kucherawy were chairs.
* Addressed IETF Last Call comments. 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 Authors' Addresses
Linlin Zhou Linlin Zhou
CNNIC CNNIC
4 South 4th Street, Zhongguancun, Haidian District 4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190 Beijing 100190
China China
Phone: +86 10 5881 2677 Phone: +86 10 5881 2677
Email: zhoulinlin@cnnic.cn EMail: zhoulinlin@cnnic.cn
Ning Kong Ning Kong
CNNIC CNNIC
4 South 4th Street, Zhongguancun, Haidian District 4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190 Beijing 100190
China China
Phone: +86 10 5881 3147 Phone: +86 10 5881 3147
Email: nkong@cnnic.cn EMail: nkong@cnnic.cn
Sean Shen Sean Shen
CNNIC CNNIC
4 South 4th Street, Zhongguancun, Haidian District 4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190 Beijing 100190
China China
Phone: +86 10 5881 3038 Phone: +86 10 5881 3038
Email: shenshuo@cnnic.cn EMail: shenshuo@cnnic.cn
Steve Sheng Steve Sheng
ICANN ICANN
12025 Waterfront Drive, Suite 300 12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536 Los Angeles, CA 90094-2536
USA United States
Phone: +1 310 301 5800 Phone: +1 310 301 5800
Email: steve.sheng@icann.org EMail: steve.sheng@icann.org
Arturo Servin Arturo Servin
LACNIC LACNIC
Rambla Mexico 6125 Rambla Mexico 6125
Montevideo, Montevideo 11400 Montevideo 11400
Uruguay Uruguay
Phone: +598-2604-2222 Phone: +598-2604-2222
Email: aservin@lacnic.net EMail: arturo.servin@gmail.com
 End of changes. 140 change blocks. 
339 lines changed or deleted 291 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/