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