draft-ietf-weirds-object-inventory-03.txt   draft-ietf-weirds-object-inventory-04.txt 
Internet Engineering Task Force L. Zhou Internet Engineering Task Force L. Zhou
Internet-Draft N. Kong Internet-Draft N. Kong
Intended status: Informational S. Shen Intended status: Informational S. Shen
Expires: January 24, 2015 CNNIC Expires: March 24, 2015 CNNIC
S. Sheng S. Sheng
ICANN ICANN
A. Servin A. Servin
LACNIC LACNIC
July 23, 2014 September 20, 2014
Registration Data Access Protocol Object Inventory Analysis Registration Data Access Protocol Object Inventory Analysis
draft-ietf-weirds-object-inventory-03 draft-ietf-weirds-object-inventory-04
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 statistical
analysis process and result of existing WHOIS information. The analysis process and result of existing WHOIS information. The
purpose of this document is to build an object inventory to purpose of this document is to build an object inventory to
facilitate discussions of data objects included in Registration Data facilitate discussions of data objects included in Registration Data
Access Protocol (RDAP) responses. Access Protocol (RDAP) responses.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 24, 2015. This Internet-Draft will expire on March 24, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 2, line 30 skipping to change at page 2, line 30
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. RIR Objects Analysis . . . . . . . . . . . . . . . . . . . . 5 4. RIR Objects Analysis . . . . . . . . . . . . . . . . . . . . 5
4.1. WHOIS Data of Organizations Holding a Resource . . . . . 5 4.1. WHOIS Data for Organizations Holding a Resource . . . . . 5
4.2. WHOIS Data of Contact . . . . . . . . . . . . . . . . . . 6 4.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . . . 7
4.3. WHOIS Data of IP . . . . . . . . . . . . . . . . . . . . 7 4.3. WHOIS data for IP Addresses . . . . . . . . . . . . . . . 9
4.4. WHOIS Data of ASN . . . . . . . . . . . . . . . . . . . . 9 4.4. WHOIS data for ASNs . . . . . . . . . . . . . . . . . . . 10
4.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 9 4.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 12
5. DNR Objects Analysis . . . . . . . . . . . . . . . . . . . . 10 5. DNR Objects Analysis . . . . . . . . . . . . . . . . . . . . 12
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 10 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2. Public Objects . . . . . . . . . . . . . . . . . . . . . 10 5.2. Public Objects . . . . . . . . . . . . . . . . . . . . . 12
5.2.1. WHOIS Data of Domain . . . . . . . . . . . . . . . . 10 5.2.1. WHOIS Data for Domains . . . . . . . . . . . . . . . 12
5.2.2. WHOIS Data of Contact . . . . . . . . . . . . . . . . 11 5.2.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . 13
5.2.2.1. Registrant . . . . . . . . . . . . . . . . . . . 11 5.2.2.1. Registrant . . . . . . . . . . . . . . . . . . . 14
5.2.2.2. Admin Contact . . . . . . . . . . . . . . . . . . 12 5.2.2.2. Admin Contact . . . . . . . . . . . . . . . . . . 15
5.2.2.3. Tech Contact . . . . . . . . . . . . . . . . . . 12 5.2.2.3. Tech Contact . . . . . . . . . . . . . . . . . . 16
5.2.2.4. Billing Contact . . . . . . . . . . . . . . . . . 13 5.2.2.4. Billing Contact . . . . . . . . . . . . . . . . . 17
5.2.3. WHOIS Data of Nameserver . . . . . . . . . . . . . . 14 5.2.3. WHOIS Data for Nameservers . . . . . . . . . . . . . 18
5.2.4. WHOIS Data of Registrar . . . . . . . . . . . . . . . 15 5.2.4. WHOIS Data for Registrars . . . . . . . . . . . . . . 18
5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 15 5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 19
5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 17 5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 17 5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 21
5.4.2. Data Elements Analysis . . . . . . . . . . . . . . . 18 5.4.2. Data Elements Analysis . . . . . . . . . . . . . . . 23
5.4.3. Labels Analysis . . . . . . . . . . . . . . . . . . . 19 5.4.3. Labels Analysis . . . . . . . . . . . . . . . . . . . 25
5.4.4. Other Objects Analysis . . . . . . . . . . . . . . . 20 5.4.4. Other Objects Analysis . . . . . . . . . . . . . . . 25
5.5. Limitation . . . . . . . . . . . . . . . . . . . . . . . 20 5.5. Limitations . . . . . . . . . . . . . . . . . . . . . . . 26
6. Reference Extension Objects . . . . . . . . . . . . . . . . . 21 6. Reference Extension Objects . . . . . . . . . . . . . . . . . 26
6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 21 6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 26
6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 21 6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 27
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
8. Security considerations . . . . . . . . . . . . . . . . . . . 22 8. Security considerations . . . . . . . . . . . . . . . . . . . 27
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27
10. Normative References . . . . . . . . . . . . . . . . . . . . 22 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 27
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 23 10.1. Normative References . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 10.2. Informative References . . . . . . . . . . . . . . . . . 28
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
1. Introduction 1. Introduction
RIRs and DNRs have historically maintained a lookup service to permit RIRs and DNRs have historically maintained a lookup service to permit
public access to some portion of the registry database. Most public access to some portion of the registry database. Most
registries offer the service via the WHOIS protocol [RFC3912], with registries offer the service via the WHOIS protocol [RFC3912], with
additional services being offered via world wide web pages, bulk additional services being offered via world wide web pages, bulk
downloads, and other services, such as RPSL [RFC2622]. downloads, and other services, such as Routing Policy Specification
Language (RPSL) [RFC2622].
Although the WHOIS protocol specified in [RFC3912] is widely adopted Although the WHOIS protocol is widely adopted and supported, it has
and supported, it has several shortcomings that limits its usefulness several shortcomings that limit its usefulness to the evolving needs
to the evolving needs of the Internet community. For example, the of the Internet community. Specifically,
WHOIS protocol has not been Internationalized, it does not
consistently support Internationalized Domain Name (IDN, described in
[RFC5890]); WHOIS has no query and response format; and WHOIS
protocol does not support user authentication, access control for
differentiated access.
This document is aimed to build an object inventory to facilitate o It has no query and response format.
discussions of registration data objects. Based on this statistics
result, it may help to form and specify the RDAP response format.
In number space, there are altogether 5 RIRs. All RIRs provide o It does not support user authentication, access control for
information about IP addresses, Autonomous System Number (ASNs) and differentiated access.
contacts, the data model used is different for each RIR. In domain
name space, there are now over 200 ccTLDs and 21 gTLDs. Different o It has not been internationalized and thus does not consistently
domain name registries may have different WHOIS response objects and support Internationalized Domain Names (IDNs, described in
formats. A common understanding of all these data formats is [RFC5890]).
critical.
This document records an inventory of registry data objects to
facilitate discussions of registration data objects. The
Registration Data Access Protocol (RDAP) was developed using this
inventory as input.
In number space, there are altogether five RIRs. Although all RIRs
provide information about IP addresses, Autonomous System Number
(ASNs) and contacts, the data model used is different for each RIR.
In domain name space, there are over 200 country code Top-Level
Domains (ccTLDs) and over 400 generic Top-Level Domains (gTLDs) when
the document is published. Different domain name registries may have
different WHOIS response objects and formats. A common understanding
of all these data formats is critical.
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 a data object inventory analysis based on the collected data
from 5 RIRs and 106 ccTLDs and 18 gTLDs from DNRs. The RIR data from five RIRs and 106 ccTLDs and 18 gTLDs from DNRs. The RIR data
objects are classified into IP address, ASN, person or contact and objects are classified into IP address, ASN, person or contact and
the organization that held the resource. The DNR data objects are the organization that held the resource. The DNR data objects are
classified into domain, contact, nameserver and registrar related classified into domain, contact, nameserver and registrar related
objects. Other objects that do not belong to above categories are objects. Other objects that do not belong to above categories are
viewed as private designed objects. In this document, we are not viewed as private designed objects. In this document, there is no
intended to analyze all the query and response types existed in RIRs intent to analyze all the query and response types existed in RIRs
and DNRs. The most common query objects will be discussed, other and DNRs. The most common query objects are discussed, but other
objects such as RPSL data structure used by Internet Routing objects such as RPSL data structures used by Internet Routing
Registries (IRRs) will be added at a later time if the community Registries (IRRs) can be documented later if the community feels it
feels it is necessary. is necessary.
Since this is a document with statistics analysis and there are no
protocol specifications, the [RFC2119] language does not apply.
2. Terminology 2. Terminology
o Data element -- The name of specific response object. o Data element -- The name of specific response object.
o Label -- Different registries may have different naming ways for o Label -- The name given to a particular data element, which may
the same data element. So there may be several labels with the vary between registries.
same meaning and belong to one group of data element.
o Most popular label -- The label which is most supported by the o Most popular label -- The label which 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 Total count -- The number of registries that support a certain
data element. data 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,
is collected following the procedures described below. was collected following the procedures described below.
RIR objects collection process: RIR objects collection process:
(1) The process of RIR data collection is relatively easy. There (1) The process of RIR data collection was relatively easy. There
are altogether 5 RIRs which are AFRINIC, APNIC, ARIN, LACNIC and are altogether five RIRs which are AFRINIC, APNIC, ARIN, LACNIC
RIPE NCC. All the RIRs provide information of IPs, ASNs and and RIPE NCC. All the RIRs provide information of IPs, ASNs and
contacts. Find the 5 RIR WHOIS servers firstly. contacts. First, find the five RIR WHOIS servers.
(2) Query the corresponding IPs, ASNs, contacts and organizations (2) Query the corresponding IPs, ASNs, contacts and organizations
registered in 5 RIRs and make a comparative analysis of the registered in five RIRs and make a comparative analysis of the
responses data. responses data.
(3) Data elements with the same meaning, but using different labels, (3) Data elements with the same meaning, but using different labels,
are grouped together. were grouped together.
DNR objects collections process: DNR objects collections process:
(1) A programming script is applied to collect port 43 response data (1) A programming script was applied to collect port 43 response
from 294 ccTLDs. "nic.ccTLD" is used as the query string which data from 294 ccTLDs. "nic.ccTLD" is used as the query string,
is usually registered in a domain registry. Responses of 106 which is usually registered in a domain registry. Responses of
ccTLDs were received. 18 gTLDs' port 43 response data is 106 ccTLDs were received. 18 gTLDs' port 43 response data was
collected from their contracts with ICANN. So the sample size collected from their contracts with ICANN. Thus, the sample
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 is collected manually from the 124 (2) WHOIS data from web was collected manually from the 124
registries that have port 43 WHOIS responses. registries that have port 43 WHOIS responses.
(3) Some of the responses which are collected by program may not (3) Some of the responses which were collected by program did not
seem to be correct. So data of top 10 ccTLD registries, like seem to be correct, so data of the top 10 ccTLD registries, like
.de, .eu and .uk etc., was re-verified by querying domain names .de, .eu and .uk etc., was re-verified by querying domain names
other than "nic.ccTLD". other than "nic.ccTLD".
(4) In accordance with the specification 4 of new gTLD applicant (4) In accordance with the specification 4 of new gTLD applicant
guide book, [RFC5730], [RFC5731], [RFC5732] and [RFC5733], the guide book [ICANN.AGB-201206] and the Extensible Provisioning
response data objects are classified into public and other data Protocol (EPP) ([RFC5730], [RFC5731], [RFC5732] and [RFC5733]),
objects. Public data objects are those which are defined in the the response data objects are classified into public and other
above two documents. Other objects are those which are self data objects. Public data objects are those which are defined
in the above references. Other objects are those which are self
designed data elements or objects in different registries. designed data elements or objects in different registries.
(5) Data elements with the same meaning, but using different labels, (5) Data elements with the same meaning, but using different labels,
are grouped together. The numbers of registries that support were grouped together. The numbers of registries that support
the data elements is calculated in the total count column. the data elements are shown in the total count column.
4. RIR Objects Analysis 4. RIR Objects Analysis
4.1. WHOIS Data of Organizations Holding a Resource 4.1. WHOIS Data for Organizations Holding a Resource
The following table shows the organization objects of 5 RIRs. The following table shows the organization objects of five RIRs.
+------------+-----------+------+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| RIR | AFRINIC | APNI | ARIN | LACNIC | RIPE NCC | | RIR | AFRINIC |APNIC| ARIN | LACNIC | RIPE NCC |
| Objects | | C | | | | | Objects | | | | | |
+------------+-----------+------+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Organizati | organisat | NA | Name | Owner | org-name | | Organization |organisation| NA | Name | Owner | org-name |
| on name | ion | | | | | | name | | | | | |
| Organizati | org-name | NA | Handle | owner-id | organisati | +--------------+------------+-----+----------+-----------+------------+
| on ID | | | | | on | | Organization | org-name | NA | Handle | owner-id |organisation|
| Company | NA | NA | Company | NA | NA | | ID | | | | | |
| Name of | NA | NA | NA | responsib | NA | +--------------+------------+-----+----------+-----------+------------+
| person res | | | | le | | | Company | NA | NA | Company | NA | NA |
| ponsible | | | | | | +--------------+------------+-----+----------+-----------+------------+
| Type of or | org-type | NA | NA | NA | org-type | | Name of | NA | NA | NA |responsible| NA |
| ganization | | | | | | | person | | | | | |
| Country | country | NA | country | country | country | | responsible | | | | | |
| Postal | address | NA | address | address | address | +--------------+------------+-----+----------+-----------+------------+
| Address | | | | | | | Type of | org-type | NA | NA | NA | org-type |
| City | NA | NA | city | NA | address | | organization | | | | | |
| State | NA | NA | StatePro | NA | address | +--------------+------------+-----+----------+-----------+------------+
| | | | v | | | | Country | country | NA | country | country | country |
| Postal | NA | NA | PostalCo | NA | address | +--------------+------------+-----+----------+-----------+------------+
| Code | | | de | | | | Postal | address | NA | address | address | address |
| Phone | phone | NA | NA | phone | phone | | Address | | | | | |
| Fax Number | fax-no | NA | NA | NA | fax-no | +--------------+------------+-----+----------+-----------+------------+
| ID of admi | admin-c | NA | Admin | owner-c | admin-c | | City | NA | NA | city | NA | address |
| nistrative | | | POC | | (multiple) | +--------------+------------+-----+----------+-----------+------------+
| contact | | | | | | | State | NA | NA | StateProv| NA | address |
| ID of | tech-c | NA | Tech POC | tech-c | tech-c | +--------------+------------+-----+----------+-----------+------------+
| technical | | | | | (multiple) | | Postal | NA | NA |PostalCode| NA | address |
| contact | | | | | | | Code | | | | | |
| Reference | mnt-ref | NA | NOC POC | NA | mnt-ref | +--------------+------------+-----+----------+-----------+------------+
| of | | | | | | | Phone | phone | NA | NA | phone | phone |
| maintainer | | | | | | +--------------+------------+-----+----------+-----------+------------+
| Reference | mnt-by | NA | Abuse | NA | mnt-by | | Fax Number | fax-no | NA | NA | NA | fax-no |
| of | | | POC | | | +--------------+------------+-----+----------+-----------+------------+
| maintainer | | | | | | | ID of | admin-c | NA | Admin | owner-c | admin-c |
| Remarks | remarks | NA | NA | NA | remarks | |administrative| | | POC | | (multiple) |
| Date of | Changed | NA | RegDate | created | Changed | | contact | | | | | |
| record | | | | | | +--------------+------------+-----+----------+-----------+------------+
| creation | | | | | | | ID of | tech-c | NA | Tech POC | tech-c | tech-c |
| Date of | changed | NA | Updated | changed | changed | | technical | | | | | (multiple) |
| record | | | | | | | contact | | | | | |
| changed | | | | | | +--------------+------------+-----+----------+-----------+------------+
| List of | NA | NA | NA | list of | NA | | Maintainer | mnt-ref | NA | NOC POC | NA | mnt-ref |
| resources | | | | resources | | | organization | | | | | |
| Source | source | NA | NA | NA | source | +--------------+------------+-----+----------+-----------+------------+
| Reference | NA | NA | Ref | NA | NA | | 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 |
+--------------+------------+-----+----------+-----------+------------+
WHOIS Data of Organizations Holding a Resource WHOIS Data for Organizations Holding a Resource
4.2. WHOIS Data of Contact 4.2. WHOIS Data for Contacts
The following table shows the contact objects of 5 RIRs. The following table shows the contact objects of five RIRs.
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| RIR Objects | AFRINIC | APNIC | ARIN | LACNIC | RIPE | | RIR Objects | 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 |
| Address | | | | | | | Address | | | | | |
+--------------+---------+---------+------------+---------+---------+
| City | NA | NA | City | NA | address | | City | NA | NA | City | NA | address |
+--------------+---------+---------+------------+---------+---------+
| State | NA | NA | StateProv | NA | address | | State | NA | NA | StateProv | NA | address |
+--------------+---------+---------+------------+---------+---------+
| Postal Code | NA | NA | PostalCode | NA | address | | Postal Code | NA | NA | PostalCode | NA | address |
+--------------+---------+---------+------------+---------+---------+
| Country | NA | country | Country | country | NA | | Country | NA | country | Country | country | NA |
+--------------+---------+---------+------------+---------+---------+
| Phone | phone | phone | Mobile | phone | phone | | Phone | phone | phone | Mobile | phone | phone |
+--------------+---------+---------+------------+---------+---------+
| Fax Number | fax-no | fax-no | Fax | NA | fax-no | | Fax Number | fax-no | fax-no | Fax | NA | fax-no |
+--------------+---------+---------+------------+---------+---------+
| Email | e-mail | e-mail | Email | e-mail | NA | | Email | e-mail | e-mail | Email | e-mail | NA |
+--------------+---------+---------+------------+---------+---------+
| ID | nic-hdl | nic-hdl | Handle | nic-hdl | nic-hdl | | ID | nic-hdl | nic-hdl | Handle | nic-hdl | nic-hdl |
+--------------+---------+---------+------------+---------+---------+
| Remarks | remarks | remarks | Remarks | NA | remarks | | Remarks | remarks | remarks | Remarks | NA | remarks |
+--------------+---------+---------+------------+---------+---------+
| Notify | notify | notify | NA | NA | notify | | Notify | notify | notify | NA | NA | notify |
+--------------+---------+---------+------------+---------+---------+
| ID of | mnt-by | mnt-by | NA | NA | mnt-by | | ID of | mnt-by | mnt-by | NA | NA | mnt-by |
| maintainer | | | | | | | maintainer | | | | | |
+--------------+---------+---------+------------+---------+---------+
| Registration | changed | NA | RegDate | created | changed | | Registration | changed | NA | RegDate | created | changed |
| Date | | | | | | | Date | | | | | |
+--------------+---------+---------+------------+---------+---------+
| 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 |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
WHOIS Data of Contact WHOIS Data for Contacts
4.3. WHOIS Data of IP
The following table shows the IP address objects of 5 RIRs. 4.3. WHOIS data for IP Addresses
+-----------+-------+------------+-----------+--------+-------------+ The following table shows the IP address objects of five RIRs.
| RIR | AFRIN | APNIC | ARIN | LACNIC | RIPE NCC |
| Objects | IC | | | | |
+-----------+-------+------------+-----------+--------+-------------+
| IP | inetn | inetnum | NetRange | NA | inetnum |
| address | um | | | | |
| range | | | | | |
| IPV6 | inet6 | inet6num/i | CIDR | inetnu | inet6num/in |
| address | num | netnum | | m | etnum |
| range | | | | | |
| Descripti | descr | descr | NetName | NA | descr |
| on | | | | | |
| Remarks | remar | remarks | NA | NA | remarks |
| | ks | | | | |
| Origin AS | NA | origin (on | OriginAS | Origin | origin (on |
| | | route/6) | | AS (fu | route/6) |
| | | | | ture) | |
| Network | netna | netname | NetHandle | inetre | netname |
| name/ID | me | | | v | |
| Maintaine | mnt- | NA | NA | NA | mnt-by |
| r | by | | | | |
| Maintaine | mnt- | NA | NA | NA | NA |
| r | lower | | | | |
| Administr | admin | admin-c | OrgId | owneri | admin-c |
| ative | -c | | | d | |
| contact | | | | | |
| Parent | paren | NA | Parent | NA | NA |
| range | t | | | | |
| Status | statu | status | NetType | status | status |
| | s | | | | |
| Registrat | chang | NA | RegDate | create | changed |
| ion Date | ed | | | d | |
| Registrat | chang | changed | Updated | change | changed |
| ion | ed | (multiple) | | d | |
| update | | | | | |
| Reference | NA | NA | Ref | NA | NA |
| ID organi | org | NA | OrgId | owner | organisatio |
| zation | | | | | n |
| holding | | | | | |
| the | | | | | |
| resource | | | | | |
| Referral | NA | NA | ReferralS | NA | NA |
| server | | | erver | | |
| Technical | tech- | tech-c | OrgTechHa | tech-c | tech-c |
| contact | c | | ndle | | (multiple) |
| Abuse | NA | NA | OrgAbuseH | abuse- | abuse- |
| contact | | | andle | c | mailbox |
| Referral | NA | NA | RTechHand | NA | NA |
| technical | | | le | | |
| contact | | | | | |
| Referral | mnt- | mnt-irt | RAbuseHan | NA | NA |
| abuse | irt | | dle | | |
| contact | | | | | |
| Referral | NA | NA | RNOCHandl | NA | NA |
| NOC | | | e | | |
| contact | | | | | |
| Name | NA | NA | NA | nserve | NA |
| server | | | | r | |
+-----------+-------+------------+-----------+--------+-------------+
WHOIS Data of IP +--------------+---------+----------+--------------+--------+-------------+
| RIR | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC |
| Objects | | | | | |
+--------------+---------+----------+--------------+--------+-------------+
| IP | inetnum | inetnum | NetRange | NA | inetnum |
| address | | | | | |
| range | | | | | |
+--------------+---------+----------+--------------+--------+-------------+
| IPV6 | inet6num|inet6num/ | CIDR |inetnum | inet6num/ |
| address | | inetnum | | | inetnum |
| range | | | | | |
+--------------+---------+----------+--------------+--------+-------------+
| Description | descr | descr | NetName | NA | descr |
| | | | | | |
+--------------+---------+----------+--------------+--------+-------------+
| Remarks | remarks | remarks | NA | NA | remarks |
| | | | | | |
+--------------+---------+----------+--------------+--------+-------------+
| Origin AS | NA |origin (on| OriginAS |OriginAS| origin (on |
| | | route/6) | |(future)| route/6) |
+--------------+---------+----------+--------------+--------+-------------+
| Network | netname | netname | NetHandle |inetrev | netname |
| name/ID | | | | | |
+--------------+---------+----------+--------------+--------+-------------+
| Maintainer | mnt-by | NA | NA | NA | mnt-by |
+--------------+---------+----------+--------------+--------+-------------+
| Maintainer |mnt-lower| NA | NA | NA | NA |
| | | | | | |
+--------------+---------+----------+--------------+--------+-------------+
|Administrative| admin-c | admin-c | OrgId | ownerid| admin-c |
| 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 | |(multiple)| | | |
+--------------+---------+----------+--------------+--------+-------------+
| 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 | | | | | (multiple) |
+--------------+---------+----------+--------------+--------+-------------+
| 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 | | | | | |
+--------------+---------+----------+--------------+--------+-------------+
4.4. WHOIS Data of ASN WHOIS Data for IP Addresses
+------------+--------+---------+-------------+---------+-----------+ 4.4. WHOIS data for ASNs
| RIR | AFRINI | APNIC | ARIN | LACNIC | RIPE NCC | +--------------+---------+----------+-------------+---------+------------+
| Objects | C | | | | | | RIR | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC |
+------------+--------+---------+-------------+---------+-----------+ | Objects | | | | | |
| ID | aut- | aut-num | ASNumber | aut-num | aut-num | +--------------+---------+----------+-------------+---------+------------+
| | num | | | | | | ID | aut-num | aut-num | ASNumber | aut-num | aut-num |
| Descriptio | descr | descr | NA | NA | descr | | | | | | | |
| n | | | | | | +--------------+---------+----------+-------------+---------+------------+
| Organizati | org | NA | OrgId | owner | org | | Description | descr | descr | NA | NA | descr |
| on | | | | | | | | | | | | |
| Comment | remark | NA | Comment | NA | remarks | +--------------+---------+----------+-------------+---------+------------+
| | s | | | | | |Organization | org | NA | OrgId | owner | org |
| Administra | admin- | admin-c | ASHandle | owner- | admin-c | | | | | | | |
| tive | c | | | id | | +--------------+---------+----------+-------------+---------+------------+
| contact ID | | | | | | | Comment | remarks | NA | Comment | NA | remarks |
| Technical | tech-c | tech-c | OrgTechHand | routing | tech-c (m | +--------------+---------+----------+-------------+---------+------------+
| contact ID | | | le | -c | ultiple) | |Administrative| admin-c | admin-c | ASHandle |owner-id | admin-c |
| Organizati | NA | nic-hdl | NA | owner-c | organisat | | contact ID | | | | | |
| on ID | | | | | ion | +--------------+---------+----------+-------------+---------+------------+
| Notify | notify | notify | NA | NA | NA | | Technical | tech-c | tech-c |OrgTechHandle|routing-c| tech-c |
| Abuse | NA | NA | OrgAbuseHan | abuse-c | NA | | contact ID | | | | | (multiple)|
| contact | | | dle | | | +--------------+---------+----------+-------------+---------+------------+
| Maintainer | mnt-by | mnt-by | NA | NA | mnt-by | | Organization | NA | nic-hdl | NA | owner-c |organisation|
| Maintainer | mnt- | mnt- | NA | NA | mnt-lower | | ID | | | | | |
| | lower | lower | | | | +--------------+---------+----------+-------------+---------+------------+
| Maintainer | NA | NA | NA | NA | mnt-ref | | Notify | notify | notify | NA | NA | NA |
| Registrati | change | NA | RegDate | created | NA | +--------------+---------+----------+-------------+---------+------------+
| on Date | d | | | | | | Abuse | NA | NA | OrgAbuse | abuse-c | NA |
| Registrati | change | changed | Updated | changed | NA | | contact | | | Handle | | |
| on update | d | (multip | | | | +--------------+---------+----------+-------------+---------+------------+
| | | le) | | | | | Maintainer | mnt-by | mnt-by | NA | NA | mnt-by |
| Source | source | source | NA | NA | source | +--------------+---------+----------+-------------+---------+------------+
+------------+--------+---------+-------------+---------+-----------+ | Maintainer |mnt-lower| mnt-lower| NA | NA | mnt-lower |
| | | | | | |
+--------------+---------+----------+-------------+---------+------------+
| Maintainer | NA | NA | NA | NA | mnt-ref |
+--------------+---------+----------+-------------+---------+------------+
|Registration | changed | NA | RegDate | created | NA |
| Date | | | | | |
+--------------+---------+----------+-------------+---------+------------+
|Registration | changed | changed | Updated | changed | NA |
| update | |(multiple)| | | |
+--------------+---------+----------+-------------+---------+------------+
| Source | source | source | NA | NA | source |
+--------------+---------+----------+-------------+---------+------------+
WHOIS Data of ASN WHOIS Data for ASNs
4.5. Conclusion 4.5. Conclusion
As it can be observed, for each object (Organization, Contact Person, As it can be observed, for each object (Organization, Contact Person,
Net-num and ASN) there are fields that are unique to only one or a Net-num and ASN) there are fields that are unique to only one or a
set of RIRs and there are fields that have the same meaning but are set of RIRs and there are fields that have the same meaning but are
referred different for each RIR. In order to construct a single data labeled differently for each RIR. In order to construct a single
model for each object a selection of the most common and useful data model for each object, a selection of the most common and useful
fields was made. That initial selection was the starting point of fields was made. That initial selection was the starting point for
the previous document of [I-D.ietf-weirds-json-response]. [I-D.ietf-weirds-json-response].
5. DNR Objects Analysis 5. DNR Objects Analysis
5.1. Overview 5.1. Overview
WHOIS data is collected from 124 registries, including 106 ccTLDs and WHOIS data was collected from 124 registries, including 106 ccTLDs
18 gTLDs. All the 124 registries support domain query. Among 124 and 18 gTLDs. All the 124 registries support domain queries. Among
registries, 8 ccTLDs and 15 gTLDs support contact query. 10 ccTLDs 124 registries, eight ccTLDs and 15 gTLDs support queries for
and 18 gTLDs support name server query. 4 ccTLDs and 18 gTLDs specific contact persons or roles. 10 ccTLDs and 18 gTLDs support
support registrar query. Domain WHOIS data contains 68 data elements queries by nameserver. four ccTLDs and 18 gTLDs support registrar
that use a total of 550 labels. There are total 392 other objects queries. Domain WHOIS data contain 68 data elements that use a total
for Domain WHOIS data. The raw data can be accessed with the of 550 labels. There is a total of 392 other objects for domain
following link: WHOIS Statistics Data File [Stat-Data-File] 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 new gTLD application guide book, [RFC5730], [RFC5731], according to the new gTLD applicant guide book and EPP protocols.
[RFC5732] and [RFC5733]. They are generally classified into four They are generally classified into four categories: domain, contact,
categories: domain, contact, nameserver and registrar related nameserver and registrar related information.
information.
5.2.1. WHOIS Data of Domain 5.2.1. WHOIS Data for Domains
WHOIS data of domain includes "Domain Name", "Creation Date", "Domain WHOIS replies about domains include "Domain Name", "Creation Date",
Status", "Expiration Date", "Updated Date", "Domain ID", "DNSSEC" and "Domain Status", "Expiration Date", "Updated Date", "Domain ID",
"Last Transferred Date". The following table gives the element name, "DNSSEC" and "Last Transferred Date". The following table gives the
most popular label and corresponding numbers of TLDs and labels. element name, most popular label and corresponding numbers of TLDs
and 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 |
+-------------------+-------------------+------------+--------------+
| 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 | | |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
WHOIS Data of Domain WHOIS Data for Domains
Analyzing the above data, about 95.16% of the 124 registries support Several statistical conclusion that obtained from above data include:
"Domain Name" data element; 85.48% of the 124 registries support
"Creation Date" data element; 76.61% of the 124 registries support
"Domain Status" data element. On the other hand, some elements such
as "DNSSEC" and "Last Transferred Date" are only supported by 11.29%
and 3.23% of all the registries seperately.
5.2.2. WHOIS Data of Contact o About 95.16% of the 124 registries support a "Domain Name" data
element.
o Nearly 85.48% of the 124 registries support a "Creation Date" data
element.
o Almost 76.61% of the 124 registries support a "Domain Status" data
element
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
the registries seperately.
5.2.2. WHOIS Data for Contacts
In domain name space, contacts are typically divided into registrant, In domain name space, contacts are typically divided into registrant,
administrative contact, technical contact and billing contact. administrative contact, technical contact and billing contact.
5.2.2.1. Registrant 5.2.2.1. Registrant
The following table shows all the contact information of registrant. The following table shows all the contact information for a
14 data elements are listed below. registrant. 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 |
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
| 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 |
+--------------------+---------------------+-----------+------------+
| Registrant Phone | Registrant Phone | 48 | 6 | | Registrant Phone | Registrant Phone | 48 | 6 |
+--------------------+---------------------+-----------+------------+
| Registrant Fax | Registrant Fax | 44 | 6 | | Registrant Fax | Registrant Fax | 44 | 6 |
+--------------------+---------------------+-----------+------------+
| Registrant | Registrant | 42 | 4 | | Registrant | Registrant | 42 | 4 |
| Organization | Organization | | | | Organization | Organization | | |
+--------------------+---------------------+-----------+------------+
| Registrant Country | Country | 42 | 6 | | Registrant Country | Country | 42 | 6 |
| Code | | | | | Code | | | |
+--------------------+---------------------+-----------+------------+
| Registrant City | Registrant City | 38 | 4 | | Registrant City | Registrant City | 38 | 4 |
+--------------------+---------------------+-----------+------------+
| Registrant Postal | Registrant Postal | 37 | 5 | | Registrant Postal | Registrant Postal | 37 | 5 |
| Code | Code | | | | Code | Code | | |
+--------------------+---------------------+-----------+------------+
| Registrant | Registrant | 32 | 4 | | Registrant | Registrant | 32 | 4 |
| State/Province | State/Province | | | | State/Province | State/Province | | |
+--------------------+---------------------+-----------+------------+
| Registrant Street | Registrant Street1 | 31 | 16 | | Registrant Street | Registrant Street1 | 31 | 16 |
+--------------------+---------------------+-----------+------------+
| Registrant Country | Registrant Country | 19 | 4 | | Registrant Country | Registrant Country | 19 | 4 |
+--------------------+---------------------+-----------+------------+
| 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 |
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
Registrant Registrant
Among all the data elements, "Registrant Name", "Registrant Email" Among all the data elements, "Registrant Name", "Registrant Email"
and "Registrant ID" are the top 3 data elements. and "Registrant ID" are the top three data elements.
5.2.2.2. Admin Contact 5.2.2.2. Admin Contact
The following table shows all the contact information of The following table shows all the contact information for an
administrative contact. 14 data elements are listed below. administrative 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 |
+--------------------+--------------------+-----------+-------------+
| Admin Email | Admin Email | 54 | 12 | | Admin Email | Admin Email | 54 | 12 |
+--------------------+--------------------+-----------+-------------+
| Admin ID | Admin ID | 52 | 16 | | Admin ID | Admin ID | 52 | 16 |
+--------------------+--------------------+-----------+-------------+
| Admin Fax | Admin Fax | 44 | 8 | | Admin Fax | Admin Fax | 44 | 8 |
+--------------------+--------------------+-----------+-------------+
| Admin Phone | Admin Phone | 43 | 9 | | Admin Phone | Admin Phone | 43 | 9 |
+--------------------+--------------------+-----------+-------------+
| Admin Organization | Admin Organization | 42 | 9 | | Admin Organization | Admin Organization | 42 | 9 |
+--------------------+--------------------+-----------+-------------+
| Admin Country Code | Country | 42 | 7 | | Admin Country Code | Country | 42 | 7 |
+--------------------+--------------------+-----------+-------------+
| Admin City | Admin City | 35 | 5 | | Admin City | Admin City | 35 | 5 |
+--------------------+--------------------+-----------+-------------+
| Admin Postal Code | Admin Postal Code | 35 | 7 | | Admin Postal Code | Admin Postal Code | 35 | 7 |
+--------------------+--------------------+-----------+-------------+
| Admin | Admin | 28 | 5 | | Admin | Admin | 28 | 5 |
| State/Province | State/Province | | | | State/Province | State/Province | | |
+--------------------+--------------------+-----------+-------------+
| 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 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
Admin Contact Admin Contact
Among all the data elements, "Admin Street", "Admin Name" and "Admin Among all the data elements, "Admin Street", "Admin Name" and "Admin
Email" are the top 3 data elements. Email" are the top three data elements.
5.2.2.3. Tech Contact 5.2.2.3. Tech Contact
The following table shows all the information about domain name The following table shows all the information for a domain name
technical contact. 14 data elements are listed below. technical 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 |
+--------------------+--------------------+-----------+-------------+
| Tech Name | Tech Name | 47 | 6 | | Tech Name | Tech Name | 47 | 6 |
+--------------------+--------------------+-----------+-------------+
| Tech Fax | Tech Fax | 45 | 9 | | Tech Fax | Tech Fax | 45 | 9 |
+--------------------+--------------------+-----------+-------------+
| Tech Phone | Tech Phone | 45 | 10 | | Tech Phone | Tech Phone | 45 | 10 |
+--------------------+--------------------+-----------+-------------+
| Tech Country Code | Country | 43 | 9 | | Tech Country Code | Country | 43 | 9 |
+--------------------+--------------------+-----------+-------------+
| Tech Organization | Tech Organization | 39 | 7 | | Tech Organization | Tech Organization | 39 | 7 |
+--------------------+--------------------+-----------+-------------+
| Tech City | Tech City | 36 | 4 | | Tech City | Tech City | 36 | 4 |
+--------------------+--------------------+-----------+-------------+
| Tech Postal Code | Tech Postal Code | 36 | 7 | | Tech Postal Code | Tech Postal Code | 36 | 7 |
+--------------------+--------------------+-----------+-------------+
| Tech | Tech | 30 | 4 | | Tech | Tech | 30 | 4 |
| State/Province | State/Province | | | | State/Province | State/Province | | |
+--------------------+--------------------+-----------+-------------+
| Tech Street | Tech Street1 | 27 | 16 | | Tech Street | Tech Street1 | 27 | 16 |
+--------------------+--------------------+-----------+-------------+
| 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 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
Tech Contact Tech Contact
Among all the data elements, "Tech Email", "Tech ID" and "Tech Name" Among all the data elements, "Tech Email", "Tech ID" and "Tech Name"
are the top 3 data elements. are the top three data elements.
5.2.2.4. Billing Contact 5.2.2.4. Billing Contact
The following table shows all the information about domain name The following table shows all the information for a domain name
billing contact. 14 data elements are listed below. billing 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 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| 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 |
+--------------------+--------------------+-----------+-------------+
| Billing Country | Country | 38 | 4 | | Billing Country | Country | 38 | 4 |
| Code | | | | | Code | | | |
+--------------------+--------------------+-----------+-------------+
| Billing Phone | Phone Number | 34 | 6 | | Billing Phone | Phone Number | 34 | 6 |
+--------------------+--------------------+-----------+-------------+
| Billing ID | Billing ID | 28 | 9 | | Billing ID | Billing ID | 28 | 9 |
+--------------------+--------------------+-----------+-------------+
| Billing City | Billing City | 28 | 4 | | Billing City | Billing City | 28 | 4 |
+--------------------+--------------------+-----------+-------------+
| Billing | Billing | 28 | 5 | | Billing | Billing | 28 | 5 |
| Organization | Organization | | | | Organization | Organization | | |
+--------------------+--------------------+-----------+-------------+
| Billing Postal | Billing Postal | 27 | 4 | | Billing Postal | Billing Postal | 27 | 4 |
| Code | Code | | | | Code | Code | | |
+--------------------+--------------------+-----------+-------------+
| Billing | Billing | 21 | 4 | | Billing | Billing | 21 | 4 |
| State/Province | State/Province | | | | State/Province | State/Province | | |
+--------------------+--------------------+-----------+-------------+
| Billing Street | Billing Street1 | 19 | 13 | | Billing Street | Billing Street1 | 19 | 13 |
+--------------------+--------------------+-----------+-------------+
| 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 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
Billing Contact Billing Contact
Among all the data elements, "Billing Name", "Tech Fax" and "Billing Among all the data elements, "Billing Name", "Tech Fax" and "Billing
Email" are the top 3 data elements. Email" are the top three data elements.
5.2.3. WHOIS Data of Nameserver 5.2.3. WHOIS Data for Nameservers
114 registries (about 92% of all the 124 registries) have the 114 registries (about 92% of all the 124 registries) have the
nameserver data element in their WHOIS response. But there are 63 "nameserver" data element in their WHOIS responses. However, there
different labels for this element. Top 3 labels for this element are are 63 different labels for this element. The top three labels for
Name Server which is supported by 25% of all the registries, Name this element are "Name Server" which is supported by 25% of all the
Servers which is supported by 16% of all the registries and nserver registries, "Name Servers" which is supported by 16% of all the
which is supported by 12% of all the registries. registries and "nserver" which is supported by 12% of all 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 | NameServer | 114 | 63 | | NameServer | Name Server | 114 | 63 |
+--------------+--------------------+-------------+---------------+ +--------------+--------------------+-------------+---------------+
WHOIS Data of Nameserver WHOIS Data for Nameservers
Some registries have nameserver elements such like "nameserver 1", Some registries have nameserver elements such like "nameserver 1",
"nameserver 2" till "nameserver n". So there are more labels than of "nameserver 2" till "nameserver n". Thus, there are more labels than
other data elements. of other data elements.
5.2.4. WHOIS Data of Registrar 5.2.4. WHOIS Data for Registrars
There are three data elements about registrar information. There are three data elements about registrar information.
+-------------------+---------------------+-----------+-------------+ +-------------------+---------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+-------------------+---------------------+-----------+-------------+ +-------------------+---------------------+-----------+-------------+
| Sponsoring | Registrar | 84 | 6 | | Sponsoring | Registrar | 84 | 6 |
| Registrar | | | | | Registrar | | | |
+-------------------+---------------------+-----------+-------------+
| 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 | | |
+-------------------+---------------------+-----------+-------------+ +-------------------+---------------------+-----------+-------------+
WHOIS Data of Registrar WHOIS Data for Registrars
67.7% of the registries have sponsoring registrar data element. 67.7% of the registries have "Sponsoring Registrar" data element.
Elements such as "Created by Registrar" and "Updated by Registrar" Elements such as "Created by Registrar" and "Updated by Registrar"
are supported by 11.3% and 8.9% of the registries. are supported by 11.3% and 8.9% of the registries.
5.3. Other Objects 5.3. Other Objects
So called other objects are those data elements that are self- So-called "other objects" are those data elements that are self-
designed or are difficult to be classified. There are 392 other designed or are difficult to be classified. There are 392 other
objects altogether. The following tables lists the top 50 other objects altogether. The following tables lists the top 50 other
objects according to the data collection result. objects according to the data collection result.
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Data Element | No. of TLDs | | Data Element | No. of TLDs |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Registrant | 41 | | Registrant | 41 |
| Phone | 32 | +----------------------------------------+-------------+
| Technical contact | 26 | | Phone | 32 |
| Administrative contact | 15 | +----------------------------------------+-------------+
| source | 14 | | Technical contact | 26 |
| fax-no | 13 | +----------------------------------------+-------------+
| nic-hdl | 13 | | Administrative contact | 15 |
| Billing Contact | 12 | +----------------------------------------+-------------+
| referral url | 11 | | source | 14 |
| e-mail | 10 | +----------------------------------------+-------------+
| WHOIS server | 9 | | fax-no | 13 |
| Admin Contact | 9 | +----------------------------------------+-------------+
| Type | 9 | | nic-hdl | 13 |
| Website | 9 | +----------------------------------------+-------------+
| zone-c | 8 | | Billing Contact | 12 |
| remarks | 7 | +----------------------------------------+-------------+
| Registration URL | 6 | | referral url | 11 |
| anonymous | 6 | +----------------------------------------+-------------+
| anniversary | 6 | | e-mail | 10 |
| hold | 6 | +----------------------------------------+-------------+
| nsl-id | 6 | | WHOIS server | 9 |
| obsoleted | 6 | +----------------------------------------+-------------+
| Customer Service Contact | 5 | | Admin Contact | 9 |
| Customer Service Email | 4 | +----------------------------------------+-------------+
| Registrar ID | 4 | | Type | 9 |
| org | 4 | +----------------------------------------+-------------+
| person | 4 | | Website | 9 |
| Maintainer | 4 | +----------------------------------------+-------------+
| Nombre | 3 | | zone-c | 8 |
| Sponsoring Registrar IANA ID | 3 | +----------------------------------------+-------------+
| Trademark Number | 3 | | remarks | 7 |
| Trademark Country | 3 | +----------------------------------------+-------------+
| descr | 3 | | Registration URL | 6 |
| url | 3 | +----------------------------------------+-------------+
| Postal address | 3 | | anonymous | 6 |
| Registrar URL | 3 | +----------------------------------------+-------------+
| International Name | 3 | | anniversary | 6 |
| International Address | 3 | +----------------------------------------+-------------+
| Admin Contacts | 2 | | hold | 6 |
| Contractual Language | 2 | +----------------------------------------+-------------+
| Date Trademark Registered | 2 | | nsl-id | 6 |
| Date Trademark Applied For | 2 | +----------------------------------------+-------------+
| IP Address | 2 | | obsoleted | 6 |
| Keys | 2 | +----------------------------------------+-------------+
| Language | 2 | | Customer Service Contact | 5 |
| NIC handle | 2 | +----------------------------------------+-------------+
| Record maintained by | 2 | | Customer Service Email | 4 |
| Registration Service Provider | 2 | +----------------------------------------+-------------+
| Registration Service Provided By | 2 | | Registrar ID | 4 |
| Registrar URL (registration services) | 2 | +----------------------------------------+-------------+
+----------------------------------------+-------------+ | 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 |
+----------------------------------------+-------------+
Top 50 Other Objects The Top 50 Other Objects
Some elements like "Registrant" are difficult to be classified into Some registries returned things that looked like labels, but were
any categories. A few registries have two levels of data elements, not. For example, in this reply:
for example:
Registrant: Registrant:
Name: Name:
Email: Email:
... ...
We do not think the first level of elements belong to any part. So "Name" and "Email" appeared to be data elements, but "Registrant" was
they are put into the scope of other objects. 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 Some other data elements, like "Remarks", "anniversary" and "Customer
service Contact" etc., are designed particularly for their own service Contact" etc., 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 statistics conclusion could be drawn from the raw Some preliminary conclusions could be drawn from the raw data.
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, that 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, have technical and billing
contact information. And only 7 of all the 124 registries give contact information. Only seven of all the 124 registries give
their abuse email in remarks part. No explicit abuse contact their abuse email in a "remarks" section. No explicit abuse
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: na-nic.com.na Query: na-nic.com.na
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: oshikoko.omadhina.net Name Servers: oshikoko.omadhina.net
ns1.na.afrisp.net ns1.na.afrisp.net
ns2.na.afrisp.net ns2.na.afrisp.net
... ...
Example of data block format: Example of data block format:
Whois database WHOIS database
domain nic.vg domain nic.vg
Domain Name nic.vg Domain Name nic.vg
Registered 1998-09-02 Registered 1998-09-02
Expiry 2012-09-02 Expiry 2012-09-02
Resource Records Resource Records
a 195.153.6.27 a 195.153.6.27
mx 10 terpsichore.william.org mx 10 terpsichore.william.org
skipping to change at page 18, line 28 skipping to change at page 23, line 28
Contact details Contact details
Registrant, Registrant,
Technical Contact, Technical Contact,
Billing Contact, Billing Contact,
Admin. Contact AdamsNames Reserved Domains (i) Admin. Contact AdamsNames Reserved Domains (i)
These domains are not available for registration These domains are not available for registration
United Kingdom United Kingdom
Identifier: neams048s Identifier: neams048s
Servidor Whois de NIC-Venezuela (.VE) Servidor WHOIS de NIC-Venezuela (.VE)
Este servidor contiene informacion autoritativa exclusivamente Este servidor contiene informacion autoritativa exclusivamente
de dominios .VE Cualquier consulta sobre este servicio, puede de dominios .VE Cualquier consulta sobre este servicio, puede
hacerla al correo electronico whois@nic.ve hacerla al correo electronico whois@nic.ve
Titular: Titular:
Jhonny Valera (nic.ve-dom) jhovalera@conatel.gob.ve Jhonny Valera (nic.ve-dom) jhovalera@conatel.gob.ve
Comision Nacional de Telecomunicaciones Comision Nacional de Telecomunicaciones
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-9090493 (FAX) +582127718599 0212-9090493 (FAX) +582127718599
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 Elements Analysis
Top 10 data elements are as follows: The top 10 data elements are as follows:
+----------------------+-------------+ +----------------------+-------------+
| Data Element | No. of TLDs | | Data Element | No. of TLDs |
+----------------------+-------------+ +----------------------+-------------+
| Domain Name | 118 | | Domain Name | 118 |
| Name Server | 114 | +----------------------+-------------+
| Creation Date | 106 | | Name Server | 114 |
| Domain Status | 95 | +----------------------+-------------+
| Sponsoring Registrar | 84 | | Creation Date | 106 |
| Expiration Date | 81 | +----------------------+-------------+
| Updated Date | 70 | | Domain Status | 95 |
| Registrant Name | 65 | +----------------------+-------------+
| Admin Street | 64 | | Sponsoring Registrar | 84 |
| Admin Name | 60 | +----------------------+-------------+
+----------------------+-------------+ | Expiration Date | 81 |
+----------------------+-------------+
| Updated Date | 70 |
+----------------------+-------------+
| Registrant Name | 65 |
+----------------------+-------------+
| Admin Street | 64 |
+----------------------+-------------+
| Admin Name | 60 |
+----------------------+-------------+
Top 10 Data Elements 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 are also supported by most registries.
We did a cumulative distribution analysis of all the data elements. A cumulative distribution analysis of all the data elements was done.
(1) About 5% of data elements are supported by over 111 (90%) (1) About 5% of the data elements discovered by the inventory work
registries. are supported by over 111 (90%) registries.
(2) About 30% of data elements are supported by over 44 (35%) (2) About 30% of the data elements discovered by the inventory work
registries. are supported by over 44 (35%) registries.
(3) About 60% of data elements are supported by over 32 (26%) (3) About 60% of the data elements discovered by the inventory work
registries. are supported by over 32 (26%) registries.
(4) About 90% of data elements are supported by over 14 (11%) (4) About 90% of the data elements discovered by the inventory work
registries. are supported by over 14 (11%) registries.
From the above result, we can conclude that only a few registries From the above result, it is clear that only a few registries support
support all the public objects, most of the registries support just all the public objects, most of the registries support just parts of
parts of all the objects. all the objects.
5.4.3. Labels Analysis 5.4.3. Labels Analysis
The top 10 labels of different data elements include: The top 10 labels of different data elements include:
+-------------------+---------------+ +-------------------+---------------+
| Labels | No. of Labels | | Labels | No. of Labels |
+-------------------+---------------+ +-------------------+---------------+
| Name Server | 63 | | Name Server | 63 |
| Creation Date | 24 | +-------------------+---------------+
| Expiration Date | 21 | | Creation Date | 24 |
| Updated Date | 20 | +-------------------+---------------+
| Admin Street | 19 | | Expiration Date | 21 |
| Tech ID | 18 | +-------------------+---------------+
| Registrant Street | 16 | | Updated Date | 20 |
| Admin ID | 16 | +-------------------+---------------+
| Tech Street | 16 | | Admin Street | 19 |
| Billing Street | 13 | +-------------------+---------------+
+-------------------+---------------+ | Tech ID | 18 |
+-------------------+---------------+
| Registrant Street | 16 |
+-------------------+---------------+
| Admin ID | 16 |
+-------------------+---------------+
| Tech Street | 16 |
+-------------------+---------------+
| Billing Street | 13 |
+-------------------+---------------+
Top 10 Labels The Top 10 Labels
As explained above, name server label is a unique example that many As explained above, the "Name Server" label is a unique example that
registries define the name server elements from "nameserver 1" till many registries define the name server elements from "nameserver 1"
"nameserver n". So label numbers of name server are much more than till "nameserver n". Thus, the count of labels for name servers is
other elements. Other elements about date, street name have more much higher than other elements. Data elements representing dates
labels. 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 2 Labels. So it is very 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
of WHOIS response. in a WHOIS response.
5.4.4. Other Objects Analysis 5.4.4. Other Objects Analysis
According to statistics result, there are 392 other data objects in The results indicate that there are 392 other data objects in total
total that are not easy to be classified or privately owned by that are not easy to be classified or are privately defined by
various registries. Top 50 other objects are listed in the table in various registries. The top 50 other objects are listed in the table
section 4.3. You can find that various different objects are in section 4.3. It is clear that various different objects are
designed for some particular purpose. So in order to ensure designed for some particular purpose. In order to ensure uniqueness
uniqueness of JSON names used in the Restful Whois service, of JSON names used in the RDAP service, establishment of an IANA
establishing an IANA registry is a necessary requirement. registry is advised.
5.5. Limitation 5.5. Limitations
This section enumerates limitations of the survey and some
assumptions that were made in the execution of this work.
o The input "nic.ccTLD" maybe is not a good choice. o The input "nic.ccTLD" maybe is not a good choice.
o The classification of local script data elements may not be o 11 registries did not provide responses in English. The
accurate. 11 registries give local script responses. classification of data elements within their responses may not be
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.
* We only use "Whois contactID/nameserver/registrar" as the query * Only WHOIS queries for contact ID, nameserver and registrar
commands to check. 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 existed WHOIS system There are some objects that are included in the existing WHOIS system
but not mentioned in the document of [I-D.ietf-weirds-json-response]. but not mentioned in [I-D.ietf-weirds-json-response]. This document
This document is intended to give a list of reference extension is intended to give a list of reference extension objects for
ogjects 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 -- include a list of all the Internet resources o list of resources -- include a list of all the Internet resources
assigned to this organization. assigned to this organization.
o referral NOC contact -- the Network Operation Center contact. o referral NOC contact -- the Network Operation 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 over 5 registries. These objects section 5.3 that are supported by more than five registries. These
are considered as possible extension objects. objects are considered as possible extension objects.
o zone-c -- The handle of a 'role' object with authority over a o zone-c -- The handle 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 -- it is usually the website address of a o Registration URL -- typically the website address of a registry.
registry.
o anonymous -- whether the registration information is anonymous or o anonymous -- whether the registration information is anonymous or
not. not.
o hold -- whethe the domain is hold or not. o hold -- whether the domain is "on hold" or not.
o nsl-id -- nameserver list ID. o nsl-id -- nameserver list ID.
o obsoleted -- whether a domain is obsoleted or not. o obsoleted -- whether a domain is obsoleted or not.
o Customer Service Contact -- a kind of contact. o Customer Service Contact -- a kind of contact.
7. IANA Considerations 7. IANA Considerations
This document does not specify any IANA actions. This document does not specify any IANA actions. [RFC Editor: Please
delete this section prior to publication.]
8. Security considerations 8. Security considerations
This document does not provide any other security services or This document does not provide any other security services or
introduce any additional considerations. introduce any additional considerations.
9. Acknowledgements 9. Acknowledgements
This document has been reviewed and improved by the Weirds working This document has been reviewed and improved by the WEIRDS working
group. The authors especially thank the following individuals who group. The authors especially thank the following individuals who
gave their suggestions and contributions to this document: Guangqing gave their suggestions and contributions to this document: Guangqing
Deng, Frederico A C Neves, Ray Bellis, Edward Shryane and Kaveh Deng, Frederico A C Neves, Ray Bellis, Edward Shryane, Kaveh Ranjbar,
Ranjbar. Murray Kucherawy and Edward Lewis.
10. Normative References 10. References
10.1. Normative References
[I-D.ietf-weirds-json-response] [I-D.ietf-weirds-json-response]
Newton, A. and S. Hollenbeck, "JSON Responses for the Newton, A. and S. Hollenbeck, "JSON Responses for the
Registration Data Access Protocol (RDAP)", draft-ietf- Registration Data Access Protocol (RDAP)", draft-ietf-
weirds-json-response-07 (work in progress), April 2014. weirds-json-response-08 (work in progress), August 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[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.
[RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912,
September 2004. September 2004.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
skipping to change at page 23, line 18 skipping to change at page 28, line 35
[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.
[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.
[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.
10.2. Informative References
[ICANN.AGB-201206]
ICANN, "gTLD Applicant Guidebook", June 2012,
<http://newgtlds.icann.org/en/applicants/agb/
guidebook-full-04jun12-en.pdf>.
[Stat-Data-File] [Stat-Data-File]
Kong, N., Zhou, L., and G. Deng, "WHOIS Statistics Data Kong, N., Zhou, L., and G. Deng, "WHOIS Statistics Data
File", July 2012, <https://docs.google.com/ File", July 2012, <https://docs.google.com/
open?id=0B96TtoK8a--MTTRuVUt3UHZMdEk>. open?id=0B96TtoK8a--MTTRuVUt3UHZMdEk>.
Appendix A. Change Log Appendix A. Change Log
Initial -00: Adopted as working group document. Initial -00: Adopted as working group document.
-01: -01:
skipping to change at page 23, line 47 skipping to change at page 29, line 23
* Modified some object names in the section of RIR Objects * Modified some object names in the section of RIR Objects
Analysis. Analysis.
* Added reference extension objects. * Added reference extension objects.
-03: -03:
* Updated to the keep-alive version. Changed the expiry dates * Updated to the keep-alive version. Changed the expiry dates
and the draft number. and the draft number.
-04:
* Updated based on Murray's and Edward's comments during the WG
last call.
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, 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
skipping to change at page 24, line 33 skipping to change at page 30, line 15
CNNIC CNNIC
4 South 4th Street, Zhongguancun, Haidian District 4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190 Beijing, 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
4676 Admiralty Way, Suite 330 12025 Waterfront Drive, Suite 300
Marina del Rey, CA 90292 Los Angeles, CA 90094-2536
United States of America USA
Phone: +1.310.823.9358 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, Montevideo 11400
Uruguay Uruguay
Phone: +598-2604-2222 Phone: +598-2604-2222
Email: aservin@lacnic.net Email: aservin@lacnic.net
 End of changes. 180 change blocks. 
448 lines changed or deleted 666 lines changed or added

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