draft-ietf-weirds-object-inventory-05.txt   draft-ietf-weirds-object-inventory-06.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: April 12, 2015 CNNIC Expires: April 30, 2015 CNNIC
S. Sheng S. Sheng
ICANN ICANN
A. Servin A. Servin
LACNIC LACNIC
October 9, 2014 October 27, 2014
Registration Data Access Protocol Object Inventory Analysis Registration Data Access Protocol Object Inventory Analysis
draft-ietf-weirds-object-inventory-05 draft-ietf-weirds-object-inventory-06
Abstract Abstract
WHOIS output objects from registries (including both Regional WHOIS output objects from registries (including both Regional
Internet Registries (RIRs) and Domain Name Registries (DNRs)) were Internet Registries (RIRs) and Domain Name Registries (DNRs)) were
collected and analyzed. This document describes the statistical collected and analyzed. This document describes the statistical
analysis process and result of existing WHOIS information. The analysis process and results of the analysis of existing WHOIS
purpose of this document is to build an object inventory to information. The purpose of this document is to build an object
facilitate discussions of data objects included in Registration Data inventory to facilitate discussions of data objects included in
Access Protocol (RDAP) responses. Registration Data Access Protocol (RDAP) responses.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 April 12, 2015. This Internet-Draft will expire on April 30, 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 42 skipping to change at page 2, line 42
5.2.3. WHOIS Data for Nameservers . . . . . . . . . . . . . 19 5.2.3. WHOIS Data for Nameservers . . . . . . . . . . . . . 19
5.2.4. WHOIS Data for Registrars . . . . . . . . . . . . . . 19 5.2.4. WHOIS Data for Registrars . . . . . . . . . . . . . . 19
5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 20 5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 20
5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 22 5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 22 5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 22
5.4.2. Data Elements Analysis . . . . . . . . . . . . . . . 24 5.4.2. Data Elements Analysis . . . . . . . . . . . . . . . 24
5.4.3. Labels Analysis . . . . . . . . . . . . . . . . . . . 26 5.4.3. Labels Analysis . . . . . . . . . . . . . . . . . . . 26
5.4.4. Other Objects Analysis . . . . . . . . . . . . . . . 26 5.4.4. Other Objects Analysis . . . . . . . . . . . . . . . 26
5.5. Limitations . . . . . . . . . . . . . . . . . . . . . . . 27 5.5. Limitations . . . . . . . . . . . . . . . . . . . . . . . 27
6. Reference Extension Objects . . . . . . . . . . . . . . . . . 27 6. Reference Extension Objects . . . . . . . . . . . . . . . . . 27
6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 27 6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 28
6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 28 6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 28
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
8. Security considerations . . . . . . . . . . . . . . . . . . . 28 8. Security considerations . . . . . . . . . . . . . . . . . . . 28
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29
10. Informative References . . . . . . . . . . . . . . . . . . . 29 10. Informative References . . . . . . . . . . . . . . . . . . . 29
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 29 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
RIRs and DNRs have historically maintained a lookup service to permit Regional Internet Registries (RIRs) and Domain Name Registries (DNRs)
public access to some portion of the registry database. Most have historically maintained a lookup service to permit public access
registries offer the service via the WHOIS protocol [RFC3912], with to some portion of the registry database. Most registries offer the
additional services being offered via world wide web pages, bulk service via the WHOIS protocol [RFC3912], with additional services
downloads, and other services, such as Routing Policy Specification being offered via world wide web pages, bulk downloads, and other
Language (RPSL) [RFC2622]. services, such as Routing Policy Specification Language (RPSL)
[RFC2622].
Although the WHOIS protocol is widely adopted and supported, it has Although the WHOIS protocol is widely adopted and supported, it has
several shortcomings that limit its usefulness to the evolving needs several shortcomings that limit its usefulness to the evolving needs
of the Internet community. Specifically, of the Internet community. Specifically,
o It has no query and response format. o It has no query and response format.
o It does not support user authentication, access control for o It does not support user authentication and access control for
differentiated access. differentiated access.
o It has not been internationalized and thus does not consistently o It has not been internationalized and thus does not consistently
support Internationalized Domain Names (IDNs, described in support Internationalized Domain Names (IDNs, described in
[RFC5890]). [RFC5890]).
This document records an inventory of registry data objects to This document records an inventory of registry data objects to
facilitate discussions of registration data objects. The facilitate discussions of registration data objects. The
Registration Data Access Protocol (RDAP) was developed using this Registration Data Access Protocol (RDAP)
inventory as input. ([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 number space, there are altogether five RIRs. Although all RIRs In the number space, there were altogether five RIRs. Although all
provide information about IP addresses, Autonomous System Number RIRs provided information about IP addresses, Autonomous System
(ASNs) and contacts, the data model used is different for each RIR. Numbers (ASNs) and contacts, the data model used was different for
In domain name space, there are over 200 country code Top-Level each RIR. In the domain name space, there were over 200 country code
Domains (ccTLDs) and over 400 generic Top-Level Domains (gTLDs) when Top-Level Domains (ccTLDs) and over 400 generic Top-Level Domains
the document is published. Different domain name registries may have (gTLDs) when the document was published. Different domain name
different WHOIS response objects and formats. A common understanding registries may have different WHOIS response objects and formats. A
of all these data formats is critical. 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 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 five 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 by the five RIRs into IP address, ASN, person
the organization that held the resource. The DNR data objects are or contact and the organization that held the resource. According to
classified into domain, contact, nameserver and registrar related the SPECIFICATION 4 (SPECIFICATION FOR REGISTRATION DATA PUBLICATION
objects. Other objects that do not belong to above categories are SERVICES) of new gTLD applicant guide book [ICANN.AGB-201206] and the
viewed as private designed objects. In this document, there is no Extensible Provisioning Protocol (EPP) ([RFC5730], [RFC5731],
intent to analyze all the query and response types existed in RIRs
and DNRs. The most common query objects are discussed, but other [RFC5732] and [RFC5733]), the DNR data objects are classified into
objects such as RPSL data structures used by Internet Routing domain, contact, nameserver and registrar related objects. Other
Registries (IRRs) can be documented later if the community feels it objects that do not belong to above categories are viewed as private
is necessary. 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 2. Terminology
o Data element -- The name of specific response object. o Data element -- The name of specific response object.
o Label -- The name given to a particular data element, which may o Label -- The name given to a particular data element, which may
vary between registries. vary between registries.
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,
was collected following the procedures described below. was collected between July 9th, 2012 and July 20th, 2012 following
the procedures described below.
RIR objects collection process:
(1) The process of RIR data collection was relatively easy. There (1) First, find the RIR WHOIS servers of five RIRs which are
are altogether five RIRs which are AFRINIC, APNIC, ARIN, LACNIC AFRINIC, APNIC, ARIN, LACNIC and RIPE NCC. All the RIRs provide
and RIPE NCC. All the RIRs provide information of IPs, ASNs and information of IPs, ASNs and contacts.
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 five 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,
were grouped together. were grouped together.
DNR objects collections process: DNR objects collections process:
(1) A programming script was applied to collect port 43 response (1) A programming script was applied to collect port 43 response
data from 294 ccTLDs. "nic.ccTLD" is used as the query string, data from 294 ccTLDs. "nic.ccTLD" is used as the query string,
which is usually registered in a domain registry. Responses of which is usually registered in a domain registry. Responses for
106 ccTLDs were received. 18 gTLDs' port 43 response data was 106 ccTLDs were received. 18 gTLDs' port 43 response data was
collected from their contracts with ICANN. Thus, the sample collected from their contracts with ICANN. Thus, the sample
size of port 43 WHOIS response data is 124 registries in total. size of port 43 WHOIS response data is 124 registries in total.
(2) WHOIS data from web was collected manually from the 124 (2) WHOIS data from web was collected manually from the 124
registries that have port 43 WHOIS responses. registries that send port 43 WHOIS responses.
(3) Some of the responses which were collected by program did not (3) Some of the responses which were collected by the program did
seem to be correct, so data of the top 10 ccTLD registries, like not seem to be correct, so data of the top 10 ccTLD registries,
.de, .eu and .uk etc., was re-verified by querying domain names like .de, .eu and .uk etc., was re-verified by querying domain
other than "nic.ccTLD". names 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 [ICANN.AGB-201206] and the Extensible Provisioning guide book [ICANN.AGB-201206] and the Extensible Provisioning
Protocol (EPP) ([RFC5730], [RFC5731], [RFC5732] and [RFC5733]), Protocol (EPP) ([RFC5730], [RFC5731], [RFC5732] and [RFC5733]),
the response data objects are classified into public and other the response data objects are classified into public and other
data objects. Public data objects are those which are defined data objects. Public data objects are those which are defined
in the above references. Other objects are those which are self in the above references. Other objects are those which are
designed data elements or objects in different registries. privately specified 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,
were grouped together. The numbers of registries that support were grouped together. The numbers of registries that support
the data elements are shown 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 for Organizations Holding a Resource 4.1. WHOIS Data for Organizations Holding a Resource
The following table shows the organization objects of five RIRs. The table 1 shows the organization objects of five RIRs.
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| RIR | AFRINIC |APNIC| ARIN | LACNIC | RIPE NCC | | RIR | AFRINIC |APNIC| ARIN | LACNIC | RIPE NCC |
| Objects | | | | | | | Objects | | | | | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Organization |organisation| NA | Name | Owner | org-name | | Organization |organisation| NA | Name | Owner | org-name |
| name | | | | | | | name | | | | | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Organization | org-name | NA | Handle | owner-id |organisation| | Organization | org-name | NA | Handle | owner-id |organisation|
| ID | | | | | | | ID | | | | | |
skipping to change at page 6, line 15 skipping to change at page 6, line 22
| State | NA | NA | StateProv| NA | address | | State | NA | NA | StateProv| NA | address |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Postal | NA | NA |PostalCode| NA | address | | Postal | NA | NA |PostalCode| NA | address |
| Code | | | | | | | Code | | | | | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Phone | phone | NA | NA | phone | phone | | Phone | phone | NA | NA | phone | phone |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Fax Number | fax-no | NA | NA | NA | fax-no | | Fax Number | fax-no | NA | NA | NA | fax-no |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| ID of | admin-c | NA | Admin | owner-c | admin-c | | ID of | admin-c | NA | Admin | owner-c | admin-c |
|administrative| | | POC | | (multiple) | |administrative| | | POC | | |
| contact | | | | | | | contact | | | | | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| ID of | tech-c | NA | Tech POC | tech-c | tech-c | | ID of | tech-c | NA | Tech POC | tech-c | tech-c |
| technical | | | | | (multiple) | | technical | | | | | |
| contact | | | | | | | contact | | | | | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Maintainer | mnt-ref | NA | NOC POC | NA | mnt-ref | | Maintainer | mnt-ref | NA | NOC POC | NA | mnt-ref |
| organization | | | | | | | organization | | | | | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Maintainer | mnt-by | NA | Abuse | NA | mnt-by | | Maintainer | mnt-by | NA | Abuse | NA | mnt-by |
| object | | | POC | | | | object | | | POC | | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Remarks | remarks | NA | NA | NA | remarks | | Remarks | remarks | NA | NA | NA | remarks |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
skipping to change at page 6, line 45 skipping to change at page 7, line 4
| record | | | | | | | record | | | | | |
| changed | | | | | | | changed | | | | | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| List of | NA | NA | NA | list of | NA | | List of | NA | NA | NA | list of | NA |
| resources | | | | resources | | | resources | | | | resources | |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Source | source | NA | NA | NA | source | | Source | source | NA | NA | NA | source |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
| Reference | NA | NA | Ref | NA | NA | | Reference | NA | NA | Ref | NA | NA |
+--------------+------------+-----+----------+-----------+------------+ +--------------+------------+-----+----------+-----------+------------+
Table 1. WHOIS Data for Organizations Holding a Resource
WHOIS Data for Organizations Holding a Resource
4.2. WHOIS Data for Contacts 4.2. WHOIS Data for Contacts
The following table shows the contact objects of five RIRs. The table 2 shows the contact objects of five RIRs.
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| RIR Objects | AFRINIC | APNIC | ARIN | LACNIC | RIPE | | Data Element | AFRINIC | APNIC | ARIN | LACNIC | RIPE |
| | | | | | NCC | | | | | | | NCC |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| Name | person | person | Name | person | person | | Name | person | person | Name | person | person |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| Company | NA | NA | Company | NA | NA | | Company | NA | NA | Company | NA | NA |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| Postal | address | address | Address | address | address | | Postal | address | address | Address | address | address |
| Address | | | | | | | Address | | | | | |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| City | NA | NA | City | NA | address | | City | NA | NA | City | NA | address |
skipping to change at page 8, line 50 skipping to change at page 8, line 50
| 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 for Contacts Table 2. WHOIS Data for Contacts
4.3. WHOIS data for IP Addresses 4.3. WHOIS data for IP Addresses
The following table shows the IP address objects of five RIRs. The table 4 shows the IP address objects of five RIRs.
Note: Because the length limit of each line is 72 characters, too 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, long strings in some table unites are split into two or more parts,
which are orderly placed in different lines of the same table unit. which are placed in order in different lines of the same table unit.
Every hyphen as the suffix of each string indicates this string and 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 the one in the next line of the same table unit are divided because
of the length limit. of the length limit.
+----------+----------+----------+ +----------+----------+----------+
| Adminis- | | abuse-- | | Adminis- | | abuse-- |
| trative | admin-c | mailbox | | trative | admin-c | mailbox |
| contact | | | | contact | | |
+----------+----------+----------+ +----------+----------+----------+
Example of String Splitting Table 3. Example of String Splitting
For instance, the original strings in the above table units are For instance, the original strings in the table units of table 3 are
"Administrative contact", "admin-c" and "abuse-mailbox", "Administrative contact", "admin-c" and "abuse-mailbox",
respectively. respectively.
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| RIR | AFRINIC| APNIC | ARIN | LACNIC | RIPE NCC | | Data | AFRINIC| APNIC | ARIN | LACNIC | RIPE NCC |
| Objects | | | | | | | Element | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| IP | inetnum| inetnum | NetRange | NA | inetnum | | IP | inetnum| inetnum | NetRange | NA | inetnum |
| address | | | | | | | address | | | | | |
| range | | | | | | | range | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| IPV6 |inet6num|inet6num/ | CIDR |inetnum | inet6num/ | | IPV6 |inet6num| inet6num | CIDR |inetnum | inet6num |
| address | | inetnum | | | inetnum | | address | | | | | |
| range | | | | | | | range | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Description| descr | descr | NetName | NA | descr | | Description| descr | descr | NetName | NA | descr |
| | | | | | | | | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Remarks | remarks| remarks | NA | NA | remarks | | Remarks | remarks| remarks | NA | NA | remarks |
| | | | | | | | | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Origin AS | NA |origin (on| OriginAS |OriginAS| origin (on | | Origin AS | NA | NA | OriginAS |OriginAS| NA |
| | | route/6) | |(future)| route/6) | | | | | |(future)| |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Network | netname| netname | NetHandle |inetrev | netname | | Network | netname| netname | NetHandle |inetrev | netname |
| name/ID | | | | | | | name/ID | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Maintainer | mnt-by | NA | NA | NA | mnt-by | | Maintainer | mnt-by | NA | NA | NA | mnt-by |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Maintainer | mnt-- | NA | NA | NA | NA | | Maintainer | mnt-- | NA | NA | NA | NA |
| | lower | | | | | | | lower | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Adminis- | admin-c| admin-c | OrgId | ownerid| admin-c | | Adminis- | admin-c| admin-c | OrgId | ownerid| admin-c |
skipping to change at page 10, line 21 skipping to change at page 10, line 21
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Parent | parent | NA | Parent | NA | NA | | Parent | parent | NA | Parent | NA | NA |
| range | | | | | | | range | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Status | status | status | NetType | status | status | | Status | status | status | NetType | status | status |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
|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 | |(multiple)| | | | | update | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Reference | NA | NA | Ref | NA | NA | | Reference | NA | NA | Ref | NA | NA |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| ID | org | NA | OrgId | owner |organisation | | ID | org | NA | OrgId | owner |organisation |
|organization| | | | | | |organization| | | | | |
|holding the | | | | | | |holding the | | | | | |
| resource | | | | | | | resource | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Referral | NA | NA |ReferralServer| NA | NA | | Referral | NA | NA |ReferralServer| NA | NA |
| server | | | | | | | server | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Technical | tech-c | tech-c |OrgTechHandle | tech-c | tech-c | | Technical | tech-c | tech-c |OrgTechHandle | tech-c | tech-c |
| contact | | | | | (multiple) | | contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Abuse | NA | NA |OrgAbuseHandle| abuse-c|abuse-mailbox| | Abuse | NA | NA |OrgAbuseHandle| abuse-c|abuse-mailbox|
| contact | | | | | | | contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Referral | NA | NA | RTechHandle | NA | NA | | Referral | NA | NA | RTechHandle | NA | NA |
| technical | | | | | | | technical | | | | | |
| contact | | | | | | | contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Referral | mnt-irt| mnt-irt | RAbuseHandle | NA | NA | | Referral | mnt-irt| mnt-irt | RAbuseHandle | NA | NA |
| abuse | | | | | | | abuse | | | | | |
| contact | | | | | | | contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Referral | NA | NA | RNOCHandle | NA | NA | | Referral | NA | NA | RNOCHandle | NA | NA |
| NOC | | | | | | | NOC | | | | | |
| contact | | | | | | | contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Name | NA | NA | NA | nserver| NA | | Name | NA | NA | NA | nserver| NA |
| server | | | | | | | server | | | | | |
+------------+--------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
WHOIS Data for IP Addresses Table 4. WHOIS Data for IP Addresses
4.4. WHOIS data for ASNs 4.4. WHOIS data for ASNs
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| RIR | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC | | Data | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC |
| Objects | | | | | | | Element | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| ID | aut-num | aut-num | ASNumber | aut-num | aut-num | | ID | aut-num | aut-num | ASNumber | aut-num | aut-num |
| | | | | | | | | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Description | descr | descr | NA | NA | descr | | Description | descr | descr | NA | NA | descr |
| | | | | | | | | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
|Organization | org | NA | OrgId | owner | org | |Organization | org | NA | OrgId | owner | org |
| | | | | | | | | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Comment | remarks | NA | Comment | NA | remarks | | Comment | remarks | NA | Comment | NA | remarks |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
|Administrative| admin-c | admin-c | ASHandle |owner-id | admin-c | |Administrative| admin-c | admin-c | ASHandle |owner-id | admin-c |
| contact ID | | | | | | | contact ID | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Technical | tech-c | tech-c |OrgTechHandle|routing-c| tech-c | | Technical | tech-c | tech-c |OrgTechHandle|routing-c| tech-c |
| contact ID | | | | |(multiple)| | contact ID | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Organization | NA | nic-hdl | NA | owner-c | organi- | | Organization | NA | nic-hdl | NA | owner-c | organi- |
| ID | | | | | sation | | ID | | | | | sation |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Notify | notify | notify | NA | NA | NA | | Notify | notify | notify | NA | NA | NA |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Abuse | NA | NA | OrgAbuse | abuse-c | NA | | Abuse | NA | NA | OrgAbuse | abuse-c | NA |
| contact | | | Handle | | | | contact | | | Handle | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Maintainer | mnt-by | mnt-by | NA | NA | mnt-by | | Maintainer | mnt-by | mnt-by | NA | NA | mnt-by |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Maintainer |mnt-lower| mnt-lower| NA | NA |mnt-lower | | Maintainer |mnt-lower| mnt-lower| NA | NA |mnt-lower |
| | | | | | | | | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Maintainer | NA | NA | NA | NA | mnt-ref | | Maintainer | NA | NA | NA | NA | mnt-ref |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
|Registration | changed | NA | RegDate | created | NA | |Registration | changed | NA | RegDate | created | NA |
| Date | | | | | | | Date | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
|Registration | changed | changed | Updated | changed | NA | |Registration | changed | changed | Updated | changed | NA |
| update | |(multiple)| | | | | update | | | | | |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
| Source | source | source | NA | NA | source | | Source | source | source | NA | NA | source |
+--------------+---------+----------+-------------+---------+----------+ +--------------+---------+----------+-------------+---------+----------+
WHOIS Data for ASNs Table 5. WHOIS Data for ASNs
4.5. Conclusion 4.5. Conclusion
As it can be observed, for each object (Organization, Contact Person, As it could be observed, some data elements were not supported by all
Net-num and ASN) there are fields that are unique to only one or a RIRs and some ones were named as different labels by different RIRs.
set of RIRs and there are fields that have the same meaning but are There were identical labels used for different data elements by
labeled differently for each RIR. In order to construct a single different RIRs. In order to construct a single data model for each
data model for each object, a selection of the most common and useful object, a selection of the most common and useful fields was made.
fields was made. That initial selection was the starting point for That initial selection was the starting point for
[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 was collected from 124 registries, including 106 ccTLDs WHOIS data was collected from 124 registries, including 106 ccTLDs
and 18 gTLDs. All the 124 registries support domain queries. Among and 18 gTLDs. All the 124 registries support domain queries. Among
124 registries, eight ccTLDs and 15 gTLDs support queries for 124 registries, eight ccTLDs and 15 gTLDs support queries for
specific contact persons or roles. 10 ccTLDs and 18 gTLDs support specific contact persons or roles. 10 ccTLDs and 18 gTLDs support
queries by nameserver. four ccTLDs and 18 gTLDs support registrar queries by nameserver. Four ccTLDs and 18 gTLDs support registrar
queries. Domain WHOIS data contain 68 data elements that use a total 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 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 WHOIS data. The raw data can be accessed at WHOIS Statistics Data
File [Stat-Data-File]. File [Stat-Data-File].
5.2. Public Objects 5.2. Public Objects
As mentioned above, public objects are those data elements selected As mentioned above, public objects are those data elements selected
according to the new gTLD applicant guide book and EPP protocols. according to the new gTLD applicant guide book and EPP protocols.
They are generally classified into four categories: domain, contact, They are generally classified into four categories: domain, contact,
nameserver and registrar related information. nameserver and registrar related information.
5.2.1. WHOIS Data for Domains 5.2.1. WHOIS Data for Domains
WHOIS replies about domains include "Domain Name", "Creation Date", WHOIS replies about domains include "Domain Name", "Creation Date",
"Domain Status", "Expiration Date", "Updated Date", "Domain ID", "Domain Status", "Expiration Date", "Updated Date", "Domain ID",
"DNSSEC" and "Last Transferred Date". The following table gives the "DNSSEC" and "Last Transferred Date". The table 6 gives the element
element name, most popular label and corresponding numbers of TLDs name, most popular label and corresponding numbers of TLDs and
and labels. labels.
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| Data Element | Most Popular | No. of | No. of | | Data Element | Most Popular | No. of | No. of |
| | Label | TLDs | Labels | | | Label | TLDs | Labels |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| Domain Name | Domain Name | 118 | 6 | | Domain Name | Domain Name | 118 | 6 |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| Creation Date | Created | 106 | 24 | | Creation Date | Created | 106 | 24 |
+-------------------+-------------------+------------+--------------+ +-------------------+-------------------+------------+--------------+
| Domain Status | Status | 95 | 8 | | Domain Status | Status | 95 | 8 |
skipping to change at page 14, line 27 skipping to change at page 14, line 27
| 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 for Domains Table 6. WHOIS Data for Domains
Several statistical conclusion that obtained from above data include: Several statistical conclusion that obtained from above data include:
o About 95.16% of the 124 registries support a "Domain Name" data o About 95.16% of the 124 registries support a "Domain Name" data
element. element.
o Nearly 85.48% of the 124 registries support a "Creation Date" data o Nearly 85.48% of the 124 registries support a "Creation Date" data
element. element.
o Almost 76.61% of the 124 registries support a "Domain Status" data o Almost 76.61% of the 124 registries support a "Domain Status" data
element element
o On the other hand, some elements such as "DNSSEC" and "Last o On the other hand, some elements such as "DNSSEC" and "Last
Transferred Date" are only supported by 11.29% and 3.23% of all Transferred Date" are only supported by 11.29% and 3.23% of all
the registries seperately. the registries seperately.
5.2.2. WHOIS Data for Contacts 5.2.2. WHOIS Data for Contacts
In domain name space, contacts are typically divided into registrant, In the domain name space, contacts are typically divided into
administrative contact, technical contact and billing contact. registrant, 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 for a The table 7 shows all the contact information for a registrant. 14
registrant. 14 data elements are listed below. 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 |
skipping to change at page 15, line 48 skipping to change at page 15, line 48
| 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 Table 7. Registrant
Among all the data elements, only "Registrant Name" is supported by Among all the data elements, only "Registrant Name" is supported by
more than one half of registries and those supported by more than one more than one half of registries and those supported by more than one
third of registries are: "Registrant Name", "Registrant Email", third of registries are: "Registrant Name", "Registrant Email",
"Registrant ID", "Registrant Phone", "Registrant Fax", "Registrant "Registrant ID", "Registrant Phone", "Registrant Fax", "Registrant
Organization" and "Registrant Country Code". Organization" and "Registrant Country Code".
5.2.2.2. Admin Contact 5.2.2.2. Admin Contact
The following table shows all the contact information for an The table 8 shows all the contact information for an administrative
administrative contact. 14 data elements are listed below. contact. 14 data elements are listed below.
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Admin Street | Address | 64 | 19 | | Admin Street | Address | 64 | 19 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Admin Name | Admin Name | 60 | 9 | | Admin Name | Admin Name | 60 | 9 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Admin Email | Admin Email | 54 | 12 | | Admin Email | Admin Email | 54 | 12 |
skipping to change at page 16, line 46 skipping to change at page 16, line 46
| 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 Table 8. Admin Contact
Among all the data elements, only "Admin Street" is supported by more Among all the data elements, only "Admin Street" is supported by more
than one half of registries and those supported by more than one than one half of registries and those supported by more than one
third of registries are: "Admin Street", "Admin Name", "Admin Email", third of registries are: "Admin Street", "Admin Name", "Admin Email",
"Admin ID", "Admin Fax", "Admin Phone", "Admin Organization" and "Admin ID", "Admin Fax", "Admin Phone", "Admin Organization" and
"Admin Country Code". "Admin Country Code".
5.2.2.3. Tech Contact 5.2.2.3. Tech Contact
The following table shows all the information for a domain name The table 9 shows all the information for a domain name technical
technical contact. 14 data elements are listed below. contact. 14 data elements are listed below.
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Tech Email | Tech Email | 59 | 9 | | Tech Email | Tech Email | 59 | 9 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Tech ID | Tech ID | 55 | 16 | | Tech ID | Tech ID | 55 | 16 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Tech Name | Tech Name | 47 | 6 | | Tech Name | Tech Name | 47 | 6 |
skipping to change at page 17, line 46 skipping to change at page 17, line 46
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| 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 Table 9. Tech Contact
Among all the data elements, there are no elements supported by more Among all the data elements, there are no elements supported by more
than one half of registries and those supported by more than one than one half of registries and those supported by more than one
third of registries are: "Tech Email", "Tech ID", "Tech Name","Tech third of registries are: "Tech Email", "Tech ID", "Tech Name","Tech
Fax","Tech Phone" and "Tech Country Code". Fax","Tech Phone" and "Tech Country Code".
5.2.2.4. Billing Contact 5.2.2.4. Billing Contact
The following table shows all the information for a domain name The table 10 shows all the information for a domain name billing
billing contact. 14 data elements are listed below. contact. 14 data elements are listed below.
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Billing Name | Name | 47 | 5 | | Billing Name | Name | 47 | 5 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Billing Fax | Fax | 43 | 6 | | Billing Fax | Fax | 43 | 6 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Billing Email | Email Address | 42 | 7 | | Billing Email | Email Address | 42 | 7 |
skipping to change at page 18, line 47 skipping to change at page 18, line 47
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| 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 Table 10. Billing Contact
Among all the data elements, there are no elements supported by more Among all the data elements, there are no elements supported by more
than one half of registries and those supported by more than one than one half of registries and those supported by more than one
third of registries are "Billing Name", "Billing Fax" and "Billing third of registries are "Billing Name", "Billing Fax" and "Billing
Email". Email".
5.2.3. WHOIS Data for Nameservers 5.2.3. WHOIS Data for Nameservers
114 registries (about 92% of all the 124 registries) have the 114 registries (about 92% of all the 124 registries) have the
"nameserver" data element in their WHOIS responses. However, there "nameserver" data element in their WHOIS responses. However, there
are 63 different labels for this element. The top three labels for are 63 different labels for this element, just as shown in table 11.
this element are "Name Server" which is supported by 25% of all the The top three labels for this element are "Name Server" which is
registries, "Name Servers" which is supported by 16% of all the supported by 25% of all the registries, "Name Servers" which is
registries and "nserver" which is supported by 12% of all the supported by 16% of all the registries and "nserver" which is
registries. 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 | Name Server | 114 | 63 | | NameServer | Name Server | 114 | 63 |
+--------------+--------------------+-------------+---------------+ +--------------+--------------------+-------------+---------------+
WHOIS Data for Nameservers Table 11. WHOIS Data for Nameservers
Some registries have nameserver elements such like "nameserver 1", Some registries have nameserver elements such like "nameserver 1",
"nameserver 2" till "nameserver n". Thus, there are more labels than "nameserver 2" till "nameserver n". Thus, there are more labels than
of other data elements. of other data elements.
5.2.4. WHOIS Data for Registrars 5.2.4. WHOIS Data for Registrars
There are three data elements about registrar information. There are three data elements about registrar information.
+-------------------+---------------------+-----------+-------------+ +-------------------+---------------------+-----------+-------------+
skipping to change at page 19, line 45 skipping to change at page 19, line 45
| 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 for Registrars Table 12. WHOIS Data for Registrars
67.7% of the registries have "Sponsoring Registrar" data element. 67.7% of the registries have the "Sponsoring Registrar" data element.
Elements such as "Created by Registrar" and "Updated by Registrar" 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 privately
designed or are difficult to be classified. There are 392 other specified or are difficult to be classified. There are 392 other
objects altogether. The following tables lists the top 50 other objects altogether. The table 13 lists the top 50 other objects
objects according to the data collection result. according to the data collection result.
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Data Element | No. of TLDs | | Data Element | No. of TLDs |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Registrant | 41 | | Registrant | 41 |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Phone | 32 | | Phone | 32 |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Technical contact | 26 | | Technical contact | 26 |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
skipping to change at page 22, line 19 skipping to change at page 22, line 19
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Record maintained by | 2 | | Record maintained by | 2 |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Registration Service Provider | 2 | | Registration Service Provider | 2 |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Registration Service Provided By | 2 | | Registration Service Provided By | 2 |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
| Registrar URL (registration services) | 2 | | Registrar URL (registration services) | 2 |
+----------------------------------------+-------------+ +----------------------------------------+-------------+
The Top 50 Other Objects Table 13. The Top 50 Other Objects
Some registries returned things that looked like labels, but were Some registries returned things that looked like labels, but were
not. For example, in this reply: not. For example, in this reply:
Registrant: Registrant:
Name: Name:
Email: Email:
... ...
"Name" and "Email" appeared to be data elements, but "Registrant" was "Name" and "Email" appeared to be data elements, but "Registrant" was
skipping to change at page 24, line 46 skipping to change at page 24, line 46
NIC Example NIC Example
Av. Veracruz con calle Cali, Edif Aguila, Urb. Las Mercedes Av. Veracruz con calle Cali, Edif Aguila, Urb. Las Mercedes
Caracas, Distrito Capital VE Caracas, Distrito Capital VE
0212-1234567 (FAX) +582123456789 0212-1234567 (FAX) +582123456789
o 11 registries give local script responses. The WHOIS information o 11 registries give local script responses. The WHOIS information
of other registries are all represented in English. of other registries are all represented in English.
5.4.2. Data Elements Analysis 5.4.2. Data Elements Analysis
The top 10 data elements are as follows: The top 10 data elements are listed in table 14:
+----------------------+-------------+ +----------------------+-------------+
| Data Element | No. of TLDs | | Data Element | No. of TLDs |
+----------------------+-------------+ +----------------------+-------------+
| Domain Name | 118 | | Domain Name | 118 |
+----------------------+-------------+ +----------------------+-------------+
| Name Server | 114 | | Name Server | 114 |
+----------------------+-------------+ +----------------------+-------------+
| Creation Date | 106 | | Creation Date | 106 |
+----------------------+-------------+ +----------------------+-------------+
skipping to change at page 25, line 29 skipping to change at page 25, line 29
+----------------------+-------------+ +----------------------+-------------+
| Updated Date | 70 | | Updated Date | 70 |
+----------------------+-------------+ +----------------------+-------------+
| Registrant Name | 65 | | Registrant Name | 65 |
+----------------------+-------------+ +----------------------+-------------+
| Admin Street | 64 | | Admin Street | 64 |
+----------------------+-------------+ +----------------------+-------------+
| Admin Name | 60 | | Admin Name | 60 |
+----------------------+-------------+ +----------------------+-------------+
The Top 10 Data Elements Table 14. The Top 10 Data Elements
Most of the domain related WHOIS information is included in the top Most of the domain related WHOIS information is included in the top
10 data elements. Other information like name server and registrar 10 data elements. Other information like name server and registrar
name are also supported by most registries. name are also supported by most registries.
A cumulative distribution analysis of all the data elements was done. A cumulative distribution analysis of all the data elements was done.
(1) About 5% of the data elements discovered by the inventory work (1) About 5% of the data elements discovered by the inventory work
are supported by over 111 (90%) registries. are supported by over 111 (90%) registries.
(2) About 30% of the data elements discovered by the inventory work (2) About 30% of the data elements discovered by the inventory work
are supported by over 44 (35%) registries. are supported by over 44 (35%) registries.
(3) About 60% of the data elements discovered by the inventory work (3) About 60% of the data elements discovered by the inventory work
are supported by over 32 (26%) registries. are supported by over 32 (26%) registries.
(4) About 90% of the data elements discovered by the inventory work (4) About 90% of the data elements discovered by the inventory work
are supported by over 14 (11%) registries. are supported by over 14 (11%) registries.
From the above result, it is clear that only a few registries support From the above result, it is clear that only a few registries support
all the public objects, most of the registries support just parts of all the public objects, most of the registries support just some 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 |
skipping to change at page 26, line 33 skipping to change at page 26, line 33
+-------------------+---------------+ +-------------------+---------------+
| Registrant Street | 16 | | Registrant Street | 16 |
+-------------------+---------------+ +-------------------+---------------+
| Admin ID | 16 | | Admin ID | 16 |
+-------------------+---------------+ +-------------------+---------------+
| Tech Street | 16 | | Tech Street | 16 |
+-------------------+---------------+ +-------------------+---------------+
| Billing Street | 13 | | Billing Street | 13 |
+-------------------+---------------+ +-------------------+---------------+
The Top 10 Labels Table 15. The Top 10 Labels
As explained above, the "Name Server" label is a unique example that As explained above, the "Name Server" label is a unique example that
many registries define the name server elements from "nameserver 1" many registries define the name server elements from "nameserver 1"
till "nameserver n". Thus, the count of labels for name servers is till "nameserver n". Thus, the count of labels for name servers is
much higher than other elements. Data elements representing dates much higher than other elements. Data elements representing dates
and street addresses were also common. and street addresses were also common.
A cumulative distribution analysis of label numbers was done. About A cumulative distribution analysis of label numbers was done. About
90% of data elements have more than two labels. It is therefore 90% of data elements have more than two labels. It is therefore
necessary to specify a standard and unified format for object names necessary to specify a standard and unified format for object names
skipping to change at page 27, line 12 skipping to change at page 27, line 12
in section 4.3. It is clear that various different objects are in section 4.3. It is clear that various different objects are
designed for some particular purpose. In order to ensure uniqueness designed for some particular purpose. In order to ensure uniqueness
of JSON names used in the RDAP service, establishment of an IANA of JSON names used in the RDAP service, establishment of an IANA
registry is advised. registry is advised.
5.5. Limitations 5.5. Limitations
This section enumerates limitations of the survey and some This section enumerates limitations of the survey and some
assumptions that were made in the execution of this work. 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, 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 o 11 registries did not provide responses in English. The
classification of data elements within their responses may not be classification of data elements within their responses may not be
accurate. accurate.
o The extension data elements are used randomly by different o The extension data elements are used randomly by different
registries. It is difficult to do statistical analysis. registries. It is difficult to do statistical analysis.
o Sample sizes of contact, name server and registrar queries are o Sample sizes of contact, name server and registrar queries are
small. small.
skipping to change at page 28, line 48 skipping to change at page 29, line 13
introduce any additional considerations. introduce any additional considerations.
9. Acknowledgements 9. Acknowledgements
This document is the work product of the IETF's WEIRDS working group, This document is the work product of the IETF's WEIRDS working group,
of which Olaf Kolkman and Murray Kucherawy were chairs. of which Olaf Kolkman and Murray Kucherawy were chairs.
The authors especially thank the following individuals who gave their The authors especially thank the following individuals who gave their
suggestions and contributions to this document: Guangqing Deng, suggestions and contributions to this document: Guangqing Deng,
Frederico A C Neves, Ray Bellis, Edward Shryane, Kaveh Ranjbar, Frederico A C Neves, Ray Bellis, Edward Shryane, Kaveh Ranjbar,
Murray Kucherawy, Edward Lewis and Pete Resnick. Murray Kucherawy, Edward Lewis, Pete Resnick, Juergen Schoenwaelder,
Ben Campbell and Claudio Allocchio.
10. Informative References 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] [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-09 (work in progress), September weirds-json-response-10 (work in progress), October 2014.
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.AGB-201206]
ICANN, "gTLD Applicant Guidebook", June 2012, ICANN, "gTLD Applicant Guidebook", June 2012,
<http://newgtlds.icann.org/en/applicants/agb/ <http://newgtlds.icann.org/en/applicants/agb/
guidebook-full-04jun12-en.pdf>. guidebook-full-04jun12-en.pdf>.
[RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D., [RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D.,
Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra, Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra,
"Routing Policy Specification Language (RPSL)", RFC 2622, "Routing Policy Specification Language (RPSL)", RFC 2622,
June 1999. June 1999.
skipping to change at page 30, line 32 skipping to change at page 31, line 7
-04: -04:
* Updated based on Murray's and Edward's comments during the WG * Updated based on Murray's and Edward's comments during the WG
last call. last call.
-05: -05:
* Addressed AD feedback. * Addressed AD feedback.
-06:
* Addressed IETF Last Call comments.
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
 End of changes. 69 change blocks. 
128 lines changed or deleted 162 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/