draft-ietf-weirds-object-inventory-04.txt   draft-ietf-weirds-object-inventory-05.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: March 24, 2015 CNNIC Expires: April 12, 2015 CNNIC
S. Sheng S. Sheng
ICANN ICANN
A. Servin A. Servin
LACNIC LACNIC
September 20, 2014 October 9, 2014
Registration Data Access Protocol Object Inventory Analysis Registration Data Access Protocol Object Inventory Analysis
draft-ietf-weirds-object-inventory-04 draft-ietf-weirds-object-inventory-05
Abstract Abstract
WHOIS output objects from registries (including both Regional WHOIS output objects from registries (including both Regional
Internet Registries (RIRs) and Domain Name Registries (DNRs)) were Internet Registries (RIRs) and Domain Name Registries (DNRs)) were
collected and analyzed. This document describes the statistical collected and analyzed. This document describes the statistical
analysis process and result of existing WHOIS information. The analysis process and result of existing WHOIS information. The
purpose of this document is to build an object inventory to purpose of this document is to build an object inventory to
facilitate discussions of data objects included in Registration Data facilitate discussions of data objects included in Registration Data
Access Protocol (RDAP) responses. Access Protocol (RDAP) responses.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 24, 2015. This Internet-Draft will expire on April 12, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. RIR Objects Analysis . . . . . . . . . . . . . . . . . . . . 5 4. RIR Objects Analysis . . . . . . . . . . . . . . . . . . . . 5
4.1. WHOIS Data for Organizations Holding a Resource . . . . . 5 4.1. WHOIS Data for Organizations Holding a Resource . . . . . 5
4.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . . . 7 4.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . . . 7
4.3. WHOIS data for IP Addresses . . . . . . . . . . . . . . . 9 4.3. WHOIS data for IP Addresses . . . . . . . . . . . . . . . 9
4.4. WHOIS data for ASNs . . . . . . . . . . . . . . . . . . . 10 4.4. WHOIS data for ASNs . . . . . . . . . . . . . . . . . . . 11
4.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 12 4.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 13
5. DNR Objects Analysis . . . . . . . . . . . . . . . . . . . . 12 5. DNR Objects Analysis . . . . . . . . . . . . . . . . . . . . 13
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 12 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 13
5.2. Public Objects . . . . . . . . . . . . . . . . . . . . . 12 5.2. Public Objects . . . . . . . . . . . . . . . . . . . . . 13
5.2.1. WHOIS Data for Domains . . . . . . . . . . . . . . . 12 5.2.1. WHOIS Data for Domains . . . . . . . . . . . . . . . 13
5.2.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . 13 5.2.2. WHOIS Data for Contacts . . . . . . . . . . . . . . . 14
5.2.2.1. Registrant . . . . . . . . . . . . . . . . . . . 14 5.2.2.1. Registrant . . . . . . . . . . . . . . . . . . . 15
5.2.2.2. Admin Contact . . . . . . . . . . . . . . . . . . 15 5.2.2.2. Admin Contact . . . . . . . . . . . . . . . . . . 16
5.2.2.3. Tech Contact . . . . . . . . . . . . . . . . . . 16 5.2.2.3. Tech Contact . . . . . . . . . . . . . . . . . . 17
5.2.2.4. Billing Contact . . . . . . . . . . . . . . . . . 17 5.2.2.4. Billing Contact . . . . . . . . . . . . . . . . . 18
5.2.3. WHOIS Data for Nameservers . . . . . . . . . . . . . 18 5.2.3. WHOIS Data for Nameservers . . . . . . . . . . . . . 19
5.2.4. WHOIS Data for Registrars . . . . . . . . . . . . . . 18 5.2.4. WHOIS Data for Registrars . . . . . . . . . . . . . . 19
5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 19 5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 20
5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 21 5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 21 5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 22
5.4.2. Data Elements Analysis . . . . . . . . . . . . . . . 23 5.4.2. Data Elements Analysis . . . . . . . . . . . . . . . 24
5.4.3. Labels Analysis . . . . . . . . . . . . . . . . . . . 25 5.4.3. Labels Analysis . . . . . . . . . . . . . . . . . . . 26
5.4.4. Other Objects Analysis . . . . . . . . . . . . . . . 25 5.4.4. Other Objects Analysis . . . . . . . . . . . . . . . 26
5.5. Limitations . . . . . . . . . . . . . . . . . . . . . . . 27
5.5. Limitations . . . . . . . . . . . . . . . . . . . . . . . 26 6. Reference Extension Objects . . . . . . . . . . . . . . . . . 27
6. Reference Extension Objects . . . . . . . . . . . . . . . . . 26 6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 27
6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 26 6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 28
6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 27 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 8. Security considerations . . . . . . . . . . . . . . . . . . . 28
8. Security considerations . . . . . . . . . . . . . . . . . . . 27 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27 10. Informative References . . . . . . . . . . . . . . . . . . . 29
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 29
10.1. Normative References . . . . . . . . . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
10.2. Informative References . . . . . . . . . . . . . . . . . 28
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
1. Introduction 1. Introduction
RIRs and DNRs have historically maintained a lookup service to permit RIRs and DNRs have historically maintained a lookup service to permit
public access to some portion of the registry database. Most public access to some portion of the registry database. Most
registries offer the service via the WHOIS protocol [RFC3912], with registries offer the service via the WHOIS protocol [RFC3912], with
additional services being offered via world wide web pages, bulk additional services being offered via world wide web pages, bulk
downloads, and other services, such as Routing Policy Specification downloads, and other services, such as Routing Policy Specification
Language (RPSL) [RFC2622]. Language (RPSL) [RFC2622].
skipping to change at page 9, line 9 skipping to change at page 9, line 9
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| Reference | NA | NA | Ref | NA | NA | | Reference | NA | NA | Ref | NA | NA |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
WHOIS Data for Contacts 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 following table shows the IP address objects of five RIRs.
+--------------+---------+----------+--------------+--------+-------------+ Note: Because the length limit of each line is 72 characters, too
| RIR | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC | long strings in some table unites are split into two or more parts,
| Objects | | | | | | which are orderly placed in different lines of the same table unit.
+--------------+---------+----------+--------------+--------+-------------+ Every hyphen as the suffix of each string indicates this string and
| IP | inetnum | inetnum | NetRange | NA | inetnum | the one in the next line of the same table unit are divided because
| address | | | | | | of the length limit.
| range | | | | | |
+--------------+---------+----------+--------------+--------+-------------+ +----------+----------+----------+
| IPV6 | inet6num|inet6num/ | CIDR |inetnum | inet6num/ | | Adminis- | | abuse-- |
| address | | inetnum | | | inetnum | | trative | admin-c | mailbox |
| range | | | | | | | contact | | |
+--------------+---------+----------+--------------+--------+-------------+ +----------+----------+----------+
| Description | descr | descr | NetName | NA | descr |
| | | | | | | Example of String Splitting
+--------------+---------+----------+--------------+--------+-------------+
| Remarks | remarks | remarks | NA | NA | remarks | For instance, the original strings in the above table units are
| | | | | | | "Administrative contact", "admin-c" and "abuse-mailbox",
+--------------+---------+----------+--------------+--------+-------------+ respectively.
| Origin AS | NA |origin (on| OriginAS |OriginAS| origin (on |
| | | route/6) | |(future)| route/6) | +------------+--------+----------+--------------+--------+-------------+
+--------------+---------+----------+--------------+--------+-------------+ | RIR | AFRINIC| APNIC | ARIN | LACNIC | RIPE NCC |
| Network | netname | netname | NetHandle |inetrev | netname | | Objects | | | | | |
| name/ID | | | | | | +------------+--------+----------+--------------+--------+-------------+
+--------------+---------+----------+--------------+--------+-------------+ | IP | inetnum| inetnum | NetRange | NA | inetnum |
| Maintainer | mnt-by | NA | NA | NA | mnt-by | | address | | | | | |
+--------------+---------+----------+--------------+--------+-------------+ | range | | | | | |
| Maintainer |mnt-lower| NA | NA | NA | NA | +------------+--------+----------+--------------+--------+-------------+
| | | | | | | | IPV6 |inet6num|inet6num/ | CIDR |inetnum | inet6num/ |
+--------------+---------+----------+--------------+--------+-------------+ | address | | inetnum | | | inetnum |
|Administrative| admin-c | admin-c | OrgId | ownerid| admin-c | | range | | | | | |
| contact | | | | | | +------------+--------+----------+--------------+--------+-------------+
+--------------+---------+----------+--------------+--------+-------------+ | Description| descr | descr | NetName | NA | descr |
| Parent | parent | NA | Parent | NA | NA | | | | | | | |
| range | | | | | | +------------+--------+----------+--------------+--------+-------------+
+--------------+---------+----------+--------------+--------+-------------+ | Remarks | remarks| remarks | NA | NA | remarks |
| Status | status | status | NetType | status | status | | | | | | | |
+--------------+---------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Registration | changed | NA | RegDate | created| changed | | Origin AS | NA |origin (on| OriginAS |OriginAS| origin (on |
| Date | | | | | | | | | route/6) | |(future)| route/6) |
+--------------+---------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Registration | changed | changed | Updated | changed| changed | | Network | netname| netname | NetHandle |inetrev | netname |
| update | |(multiple)| | | | | name/ID | | | | | |
+--------------+---------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Reference | NA | NA | Ref | NA | NA | | Maintainer | mnt-by | NA | NA | NA | mnt-by |
+--------------+---------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| ID | org | NA | OrgId | owner |organisation | | Maintainer | mnt-- | NA | NA | NA | NA |
| organization | | | | | | | | lower | | | | |
| holding the | | | | | | +------------+--------+----------+--------------+--------+-------------+
| resource | | | | | | | Adminis- | admin-c| admin-c | OrgId | ownerid| admin-c |
+--------------+---------+----------+--------------+--------+-------------+ | trative | | | | | |
| Referral | NA | NA |ReferralServer| NA | NA | | contact | | | | | |
| server | | | | | | +------------+--------+----------+--------------+--------+-------------+
+--------------+---------+----------+--------------+--------+-------------+ | Parent | parent | NA | Parent | NA | NA |
| Technical | tech-c | tech-c |OrgTechHandle | tech-c | tech-c | | range | | | | | |
| contact | | | | | (multiple) | +------------+--------+----------+--------------+--------+-------------+
+--------------+---------+----------+--------------+--------+-------------+ | Status | status | status | NetType | status | status |
| Abuse | NA | NA |OrgAbuseHandle| abuse-c|abuse-mailbox| +------------+--------+----------+--------------+--------+-------------+
| contact | | | | | | |Registration| changed| NA | RegDate | created| changed |
+--------------+---------+----------+--------------+--------+-------------+ | Date | | | | | |
| Referral | NA | NA | RTechHandle | NA | NA | +------------+--------+----------+--------------+--------+-------------+
| technical | | | | | | |Registration| changed| changed | Updated | changed| changed |
| contact | | | | | | | update | |(multiple)| | | |
+--------------+---------+----------+--------------+--------+-------------+ +------------+--------+----------+--------------+--------+-------------+
| Referral | mnt-irt | mnt-irt | RAbuseHandle | NA | NA | | Reference | NA | NA | Ref | NA | NA |
| abuse | | | | | | +------------+--------+----------+--------------+--------+-------------+
| contact | | | | | | | ID | org | NA | OrgId | owner |organisation |
+--------------+---------+----------+--------------+--------+-------------+ |organization| | | | | |
| Referral | NA | NA | RNOCHandle | NA | NA | |holding the | | | | | |
| NOC | | | | | | | resource | | | | | |
| contact | | | | | | +------------+--------+----------+--------------+--------+-------------+
+--------------+---------+----------+--------------+--------+-------------+ | Referral | NA | NA |ReferralServer| NA | NA |
| Name | NA | NA | NA | nserver| NA | | server | | | | | |
| server | | | | | | +------------+--------+----------+--------------+--------+-------------+
+--------------+---------+----------+--------------+--------+-------------+ | Technical | tech-c | tech-c |OrgTechHandle | tech-c | tech-c |
| contact | | | | | (multiple) |
+------------+--------+----------+--------------+--------+-------------+
| Abuse | NA | NA |OrgAbuseHandle| abuse-c|abuse-mailbox|
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Referral | NA | NA | RTechHandle | NA | NA |
| technical | | | | | |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Referral | mnt-irt| mnt-irt | RAbuseHandle | NA | NA |
| abuse | | | | | |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Referral | NA | NA | RNOCHandle | NA | NA |
| NOC | | | | | |
| contact | | | | | |
+------------+--------+----------+--------------+--------+-------------+
| Name | NA | NA | NA | nserver| NA |
| server | | | | | |
+------------+--------+----------+--------------+--------+-------------+
WHOIS Data for IP Addresses WHOIS Data for IP Addresses
4.4. WHOIS data for ASNs 4.4. WHOIS data for ASNs
+--------------+---------+----------+-------------+---------+------------+ +--------------+---------+----------+-------------+---------+----------+
| RIR | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC | | RIR | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC |
| Objects | | | | | | | Objects | | | | | |
+--------------+---------+----------+-------------+---------+------------+ +--------------+---------+----------+-------------+---------+----------+
| 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 | | | | |(multiple)|
+--------------+---------+----------+-------------+---------+------------+ +--------------+---------+----------+-------------+---------+----------+
| Organization | NA | nic-hdl | NA | owner-c |organisation| | Organization | NA | nic-hdl | NA | owner-c | organi- |
| ID | | | | | | | 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 | |(multiple)| | | |
+--------------+---------+----------+-------------+---------+------------+ +--------------+---------+----------+-------------+---------+----------+
| Source | source | source | NA | NA | source | | Source | source | source | NA | NA | source |
+--------------+---------+----------+-------------+---------+------------+ +--------------+---------+----------+-------------+---------+----------+
WHOIS Data for ASNs WHOIS Data for ASNs
4.5. Conclusion 4.5. Conclusion
As it can be observed, for each object (Organization, Contact Person, As it can be observed, for each object (Organization, Contact Person,
Net-num and ASN) there are fields that are unique to only one or a Net-num and ASN) there are fields that are unique to only one or a
set of RIRs and there are fields that have the same meaning but are set of RIRs and there are fields that have the same meaning but are
labeled differently for each RIR. In order to construct a single labeled differently for each RIR. In order to construct a single
data model for each object, a selection of the most common and useful data model for each object, a selection of the most common and useful
skipping to change at page 14, line 50 skipping to change at page 15, line 50
| Registrant Country | Registrant Country | 19 | 4 | | Registrant Country | Registrant Country | 19 | 4 |
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
| Registrant Phone | Registrant Phone | 18 | 2 | | Registrant Phone | Registrant Phone | 18 | 2 |
| Ext. | Ext. | | | | Ext. | Ext. | | |
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
| Registrant Fax Ext | Registrant Fax Ext | 17 | 2 | | Registrant Fax Ext | Registrant Fax Ext | 17 | 2 |
+--------------------+---------------------+-----------+------------+ +--------------------+---------------------+-----------+------------+
Registrant Registrant
Among all the data elements, "Registrant Name", "Registrant Email" Among all the data elements, only "Registrant Name" is supported by
and "Registrant ID" are the top three data elements. more than one half of registries and those supported by more than one
third of registries are: "Registrant Name", "Registrant Email",
"Registrant ID", "Registrant Phone", "Registrant Fax", "Registrant
Organization" and "Registrant Country Code".
5.2.2.2. Admin Contact 5.2.2.2. Admin Contact
The following table shows all the contact information for an The following table shows all the contact information for an
administrative contact. 14 data elements are listed below. administrative contact. 14 data elements are listed below.
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
skipping to change at page 15, line 46 skipping to change at page 16, line 48
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Admin Country | Admin Country | 17 | 5 | | Admin Country | Admin Country | 17 | 5 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Admin Phone Ext. | Admin Phone Ext. | 17 | 3 | | Admin Phone Ext. | Admin Phone Ext. | 17 | 3 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Admin Fax Ext. | Admin Fax Ext. | 17 | 3 | | Admin Fax Ext. | Admin Fax Ext. | 17 | 3 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
Admin Contact Admin Contact
Among all the data elements, "Admin Street", "Admin Name" and "Admin Among all the data elements, only "Admin Street" is supported by more
Email" are the top three data elements. than one half of registries and those supported by more than one
third of registries are: "Admin Street", "Admin Name", "Admin Email",
"Admin ID", "Admin Fax", "Admin Phone", "Admin Organization" and
"Admin Country Code".
5.2.2.3. Tech Contact 5.2.2.3. Tech Contact
The following table shows all the information for a domain name The following table shows all the information for a domain name
technical contact. 14 data elements are listed below. technical contact. 14 data elements are listed below.
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
skipping to change at page 16, line 46 skipping to change at page 17, line 48
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Tech Country | Tech Country | 18 | 5 | | Tech Country | Tech Country | 18 | 5 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Tech Fax Ext | Tech Fax Ext | 18 | 3 | | Tech Fax Ext | Tech Fax Ext | 18 | 3 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Tech Phone Ext. | Tech Phone Ext. | 13 | 3 | | Tech Phone Ext. | Tech Phone Ext. | 13 | 3 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
Tech Contact Tech Contact
Among all the data elements, "Tech Email", "Tech ID" and "Tech Name" Among all the data elements, there are no elements supported by more
are the top three data elements. 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".
5.2.2.4. Billing Contact 5.2.2.4. Billing Contact
The following table shows all the information for a domain name The following table shows all the information for a domain name
billing contact. 14 data elements are listed below. billing contact. 14 data elements are listed below.
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
skipping to change at page 17, line 49 skipping to change at page 18, line 49
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Billing Country | Billing Country | 13 | 5 | | Billing Country | Billing Country | 13 | 5 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Billing Phone Ext. | Billing Phone Ext. | 10 | 2 | | Billing Phone Ext. | Billing Phone Ext. | 10 | 2 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
| Billing Fax Ext | Billing Fax Ext | 10 | 2 | | Billing Fax Ext | Billing Fax Ext | 10 | 2 |
+--------------------+--------------------+-----------+-------------+ +--------------------+--------------------+-----------+-------------+
Billing Contact Billing Contact
Among all the data elements, "Billing Name", "Tech Fax" and "Billing Among all the data elements, there are no elements supported by more
Email" are the top three data elements. than one half of registries and those supported by more than one
third of registries are "Billing Name", "Billing Fax" and "Billing
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. The top three labels for
this element are "Name Server" which is supported by 25% of all the 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, "Name Servers" which is supported by 16% of all the
registries and "nserver" which is supported by 12% of all the registries and "nserver" which is supported by 12% of all the
registries. registries.
skipping to change at page 22, line 12 skipping to change at page 23, line 12
support admin contact information. There are 47 registries, which support admin contact information. There are 47 registries, which
is about one third of the total number, have technical and billing is about one third of the total number, have technical and billing
contact information. Only seven of all the 124 registries give contact information. Only seven of all the 124 registries give
their abuse email in a "remarks" section. No explicit abuse their abuse email in a "remarks" section. No explicit abuse
contact information is provided. contact information is provided.
o There are mainly two presentation formats. One is key:value, the o There are mainly two presentation formats. One is key:value, the
other is data block format. Example of key-value format: other is data block format. Example of key-value format:
Domain Information Domain Information
Query: na-nic.com.na Query: nic.example.com
Status: Delegated Status: Delegated
Created: 17 Apr 2004 Created: 17 Apr 2004
Modified: 14 Nov 2010 Modified: 14 Nov 2010
Expires: 31 Dec 9999 Expires: 31 Dec 9999
Name Servers: oshikoko.omadhina.net Name Servers: ns.example.net
ns1.na.afrisp.net ns1.na.example.net
ns2.na.afrisp.net ns2.na.example.net
... ...
Example of data block format: Example of data block format:
WHOIS database WHOIS database
domain nic.vg domain nic.example.org
Domain Name nic.vg Domain Name nic.example.org
Registered 1998-09-02 Registered 1998-09-02
Expiry 2012-09-02 Expiry 2012-09-02
Resource Records Resource Records
a 195.153.6.27 a 198.51.100.1
mx 10 terpsichore.william.org mx 10 test.example.net
www a 195.153.6.27 www a 198.51.100.10
Contact details Contact details
Registrant, Registrant,
Technical Contact, Technical Contact,
Billing Contact, Billing Contact,
Admin. Contact AdamsNames Reserved Domains (i) Admin. Contact AdamsNames Reserved Domains (i)
These domains are not available for registration These domains are not available for registration
United Kingdom United Kingdom
Identifier: neams048s Identifier: test123
Servidor WHOIS de NIC-Venezuela (.VE) Servidor WHOIS de NIC-Example
Este servidor contiene informacion autoritativa exclusivamente Este servidor contiene informacion autoritativa exclusivamente de
de dominios .VE Cualquier consulta sobre este servicio, puede dominios nic.example.org Cualquier consulta sobre este servicio, puede
hacerla al correo electronico whois@nic.ve hacerla al correo electronico whois@nic.example.org
Titular: Titular:
Jhonny Valera (nic.ve-dom) jhovalera@conatel.gob.ve John (nic.example.org) john@nic.example.org
Comision Nacional de Telecomunicaciones 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-9090493 (FAX) +582127718599 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 as follows:
+----------------------+-------------+ +----------------------+-------------+
| Data Element | No. of TLDs | | Data Element | No. of TLDs |
skipping to change at page 26, line 48 skipping to change at page 27, line 48
is intended to give a list of reference extension objects for is intended to give a list of reference extension objects for
discussion. discussion.
6.1. RIR Reference Extension Objects 6.1. RIR Reference Extension Objects
o company -- the company name registered by the registrant. o company -- the company name registered by the registrant.
o maintainer -- authentication information that identifies who can o maintainer -- authentication information that identifies who can
modify the contents of this object. modify the contents of this object.
o list of resources -- include a list of all the Internet resources o list of resources -- a list of IPv4 addresses, IPv6 addresses and
assigned to this organization. Autonomous System numbers.
o referral NOC contact -- the Network Operation Center contact. o referral NOC contact -- the Network Operation Center contact.
6.2. DNR Reference Extension Objects 6.2. DNR Reference Extension Objects
The following objects are selected from the top 50 other objects in The following objects are selected from the top 50 other objects in
section 5.3 that are supported by more than five registries. These section 5.3 that are supported by more than five registries. These
objects are considered as possible extension objects. objects are considered as possible extension objects.
o zone-c -- The handle of a 'role' object with authority over a o zone-c -- The identifier of a 'role' object with authority over a
zone. zone.
o maintainer -- authentication information that identifies who can o maintainer -- authentication information that identifies who can
modify the contents of this object. modify the contents of this object.
o Registration URL -- typically the website address of a registry. o Registration URL -- typically the website address of a registry.
o anonymous -- whether the registration information is anonymous or o anonymous -- whether the registration information is anonymous or
not. not.
skipping to change at page 27, line 42 skipping to change at page 28, line 42
This document does not specify any IANA actions. [RFC Editor: Please This document does not specify any IANA actions. [RFC Editor: Please
delete this section prior to publication.] delete this section prior to publication.]
8. Security considerations 8. Security considerations
This document does not provide any other security services or This document does not provide any other security services or
introduce any additional considerations. introduce any additional considerations.
9. Acknowledgements 9. Acknowledgements
This document has been reviewed and improved by the WEIRDS working This document is the work product of the IETF's WEIRDS working group,
group. The authors especially thank the following individuals who of which Olaf Kolkman and Murray Kucherawy were chairs.
gave their suggestions and contributions to this document: Guangqing
Deng, Frederico A C Neves, Ray Bellis, Edward Shryane, Kaveh Ranjbar,
Murray Kucherawy and Edward Lewis.
10. References The authors especially thank the following individuals who gave their
10.1. Normative References suggestions and contributions to this document: Guangqing Deng,
Frederico A C Neves, Ray Bellis, Edward Shryane, Kaveh Ranjbar,
Murray Kucherawy, Edward Lewis and Pete Resnick.
10. Informative References
[I-D.ietf-weirds-json-response] [I-D.ietf-weirds-json-response]
Newton, A. and S. Hollenbeck, "JSON Responses for the Newton, A. and S. Hollenbeck, "JSON Responses for the
Registration Data Access Protocol (RDAP)", draft-ietf- Registration Data Access Protocol (RDAP)", draft-ietf-
weirds-json-response-08 (work in progress), August 2014. weirds-json-response-09 (work in progress), September
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., [RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D.,
Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra, Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra,
"Routing Policy Specification Language (RPSL)", RFC 2622, "Routing Policy Specification Language (RPSL)", RFC 2622,
June 1999. June 1999.
[RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912,
September 2004. September 2004.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
skipping to change at page 28, line 35 skipping to change at page 29, line 42
[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Host Mapping", STD 69, RFC 5732, August 2009. Host Mapping", STD 69, RFC 5732, August 2009.
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Contact Mapping", STD 69, RFC 5733, August 2009. Contact Mapping", STD 69, RFC 5733, August 2009.
[RFC5890] Klensin, J., "Internationalized Domain Names for [RFC5890] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework", Applications (IDNA): Definitions and Document Framework",
RFC 5890, August 2010. RFC 5890, August 2010.
10.2. Informative References
[ICANN.AGB-201206]
ICANN, "gTLD Applicant Guidebook", June 2012,
<http://newgtlds.icann.org/en/applicants/agb/
guidebook-full-04jun12-en.pdf>.
[Stat-Data-File] [Stat-Data-File]
Kong, N., Zhou, L., and G. Deng, "WHOIS Statistics Data Kong, N., Zhou, L., and G. Deng, "WHOIS Statistics Data
File", July 2012, <https://docs.google.com/ File", July 2012, <https://docs.google.com/
open?id=0B96TtoK8a--MTTRuVUt3UHZMdEk>. open?id=0B96TtoK8a--MTTRuVUt3UHZMdEk>.
Appendix A. Change Log Appendix A. Change Log
Initial -00: Adopted as working group document. Initial -00: Adopted as working group document.
-01: -01:
skipping to change at page 29, line 28 skipping to change at page 30, line 28
-03: -03:
* Updated to the keep-alive version. Changed the expiry dates * Updated to the keep-alive version. Changed the expiry dates
and the draft number. and the draft number.
-04: -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:
* Addressed AD feedback.
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. 30 change blocks. 
223 lines changed or deleted 242 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/