draft-ietf-weirds-object-inventory-01.txt   draft-ietf-weirds-object-inventory-02.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 15, 2014 CNNIC Expires: July 24, 2014 CNNIC
S. Sheng S. Sheng
ICANN ICANN
A. Servin A. Servin
LACNIC LACNIC
Oct 2013 January 20, 2014
Registration Data Access Protocol Object Inventory Analysis Registration Data Access Protocol Object Inventory Analysis
draft-ietf-weirds-object-inventory-01 draft-ietf-weirds-object-inventory-02
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 July 24, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
skipping to change at page 2, line 31 skipping to change at page 2, line 33
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. RIR Objects Analysis . . . . . . . . . . . . . . . . . . . . 5 4. RIR Objects Analysis . . . . . . . . . . . . . . . . . . . . 5
4.1. WHOIS Data of Organizations Holding a Resource . . . . . 5 4.1. WHOIS Data of Organizations Holding a Resource . . . . . 5
4.2. WHOIS Data of Contact . . . . . . . . . . . . . . . . . . 6 4.2. WHOIS Data of Contact . . . . . . . . . . . . . . . . . . 6
4.3. WHOIS Data of IP . . . . . . . . . . . . . . . . . . . . 7 4.3. WHOIS Data of IP . . . . . . . . . . . . . . . . . . . . 7
4.4. WHOIS Data of ASN . . . . . . . . . . . . . . . . . . . . 8 4.4. WHOIS Data of ASN . . . . . . . . . . . . . . . . . . . . 9
4.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 9 4.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 9
5. DNR Objects Analysis . . . . . . . . . . . . . . . . . . . . 9 5. DNR Objects Analysis . . . . . . . . . . . . . . . . . . . . 10
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 9 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2. Public Objects . . . . . . . . . . . . . . . . . . . . . 10 5.2. Public Objects . . . . . . . . . . . . . . . . . . . . . 10
5.2.1. WHOIS Data of Domain . . . . . . . . . . . . . . . . 10 5.2.1. WHOIS Data of Domain . . . . . . . . . . . . . . . . 10
5.2.2. WHOIS Data of Contact . . . . . . . . . . . . . . . . 10 5.2.2. WHOIS Data of Contact . . . . . . . . . . . . . . . . 11
5.2.2.1. Registrant . . . . . . . . . . . . . . . . . . . 10 5.2.2.1. Registrant . . . . . . . . . . . . . . . . . . . 11
5.2.2.2. Admin Contact . . . . . . . . . . . . . . . . . . 11 5.2.2.2. Admin Contact . . . . . . . . . . . . . . . . . . 12
5.2.2.3. Tech Contact . . . . . . . . . . . . . . . . . . 12 5.2.2.3. Tech Contact . . . . . . . . . . . . . . . . . . 12
5.2.2.4. Billing Contact . . . . . . . . . . . . . . . . . 12 5.2.2.4. Billing Contact . . . . . . . . . . . . . . . . . 13
5.2.3. WHOIS Data of Nameserver . . . . . . . . . . . . . . 13 5.2.3. WHOIS Data of Nameserver . . . . . . . . . . . . . . 14
5.2.4. WHOIS Data of Registrar . . . . . . . . . . . . . . . 14 5.2.4. WHOIS Data of Registrar . . . . . . . . . . . . . . . 15
5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 14 5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 15
5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 16 5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 17
5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 16 5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 17
5.4.2. Data Elements Analysis . . . . . . . . . . . . . . . 17 5.4.2. Data Elements Analysis . . . . . . . . . . . . . . . 18
5.4.3. Labels Analysis . . . . . . . . . . . . . . . . . . . 18 5.4.3. Labels Analysis . . . . . . . . . . . . . . . . . . . 19
5.4.4. Other Objects Analysis . . . . . . . . . . . . . . . 19 5.4.4. Other Objects Analysis . . . . . . . . . . . . . . . 20
5.5. Limitation . . . . . . . . . . . . . . . . . . . . . . . 19
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 5.5. Limitation . . . . . . . . . . . . . . . . . . . . . . . 20
7. Security considerations . . . . . . . . . . . . . . . . . . . 20 6. Reference Extension Objects . . . . . . . . . . . . . . . . . 21
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 21
9. Normative References . . . . . . . . . . . . . . . . . . . . 20 6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 21
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 21 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 8. Security considerations . . . . . . . . . . . . . . . . . . . 22
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
10. Normative References . . . . . . . . . . . . . . . . . . . . 22
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
RIRs and DNRs have historically maintained a lookup service to permit RIRs and DNRs have historically maintained a lookup service to permit
public access to some portion of the registry database. Most public access to some portion of the registry database. Most
registries offer the service via the WHOIS protocol [RFC3912], with registries offer the service via the WHOIS protocol [RFC3912], with
additional services being offered via world wide web pages, bulk additional services being offered via world wide web pages, bulk
downloads, and other services, such as RPSL [RFC2622]. downloads, and other services, such as RPSL [RFC2622].
Although the WHOIS protocol specified in [RFC3912] is widely adopted Although the WHOIS protocol specified in [RFC3912] is widely adopted
skipping to change at page 4, line 32 skipping to change at page 4, line 37
data element. data element.
3. Methodology 3. Methodology
WHOIS information, including port 43 response and web response data, WHOIS information, including port 43 response and web response data,
is collected following the procedures described below. is collected following the procedures described below.
RIR objects collection process: RIR objects collection process:
(1) The process of RIR data collection is relatively easy. There (1) The process of RIR data collection is relatively easy. There
are altogether 5 RIRs which are AFRINIC, APNIC, ARIN, LACNIC and are altogether 5 RIRs which are AFRINIC, APNIC, ARIN, LACNIC and
RIPE NCC. All the RIRs provide information of IPs, ASNs and RIPE NCC. All the RIRs provide information of IPs, ASNs and
contacts. Find the 5 RIR WHOIS servers firstly. contacts. Find the 5 RIR WHOIS servers firstly.
(2) Query the corresponding IPs, ASNs, contacts and organizations (2) Query the corresponding IPs, ASNs, contacts and organizations
registered in 5 RIRs and make a comparative analysis of the registered in 5 RIRs and make a comparative analysis of the
responses data. responses data.
(3) Data elements with the same meaning, but using different labels, (3) Data elements with the same meaning, but using different labels,
are grouped together. are grouped together.
DNR objects collections process: DNR objects collections process:
(1) A programming script is applied to collect port 43 response data (1) A programming script is applied to collect port 43 response data
from 294 ccTLDs. "nic.ccTLD" is used as the query string which is from 294 ccTLDs. "nic.ccTLD" is used as the query string which
usually registered in a domain registry. Responses of 106 ccTLDs is usually registered in a domain registry. Responses of 106
were received. 18 gTLDs' port 43 response data is collected from ccTLDs were received. 18 gTLDs' port 43 response data is
their contracts with ICANN. So the sample size of port 43 WHOIS collected from their contracts with ICANN. So the sample size
response data is 124 registries in total. of port 43 WHOIS response data is 124 registries in total.
(2) WHOIS data from web is collected manually from the 124 (2) WHOIS data from web is collected manually from the 124
registries that have port 43 WHOIS responses. registries that have port 43 WHOIS responses.
(3) Some of the responses which are collected by program may not (3) Some of the responses which are collected by program may not
seem to be correct. So data of top 10 ccTLD registries, like .de, seem to be correct. So data of top 10 ccTLD registries, like
.eu and .uk etc., was re-verified by querying domain names other .de, .eu and .uk etc., was re-verified by querying domain names
than "nic.ccTLD". other than "nic.ccTLD".
(4) In accordance with the specification 4 of new gTLD applicant (4) In accordance with the specification 4 of new gTLD applicant
guide book, [RFC5730], [RFC5731], [RFC5732] and [RFC5733], the guide book, [RFC5730], [RFC5731], [RFC5732] and [RFC5733], the
response data objects are classified into public and other data response data objects are classified into public and other data
objects. Public data objects are those which are defined in the objects. Public data objects are those which are defined in the
above two documents. Other objects are those which are self above two documents. Other objects are those which are self
designed data elements or objects in different registries. designed data elements or objects in different registries.
(5) Data elements with the same meaning, but using different labels, (5) Data elements with the same meaning, but using different labels,
are grouped together. The numbers of registries that support the are grouped together. The numbers of registries that support
data elements is calculated in the total count column. the data elements is calculated in the total count column.
4. RIR Objects Analysis 4. RIR Objects Analysis
4.1. WHOIS Data of Organizations Holding a Resource 4.1. WHOIS Data of Organizations Holding a Resource
The following table shows the organization objects of 5 RIRs. The following table shows the organization objects of 5 RIRs.
+------------+----------+----------+----------+----------+----------+ +------------+-----------+------+----------+-----------+------------+
| RIR | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC | | RIR | AFRINIC | APNI | ARIN | LACNIC | RIPE NCC |
| Objects | | | | | | | Objects | | C | | | |
+------------+----------+----------+----------+----------+----------+ +------------+-----------+------+----------+-----------+------------+
| Organizati | Organisa | role | Name | Owner | org-name | | Organizati | organisat | NA | Name | Owner | org-name |
| on name | tion | | | | | | on name | ion | | | | |
| Organizati | org-name | nic-hdl | Handle | owner-id | organisa | | Organizati | org-name | NA | Handle | owner-id | organisati |
| on ID | | | | | tion | | on ID | | | | | on |
| Company | NA | NA | Company | NA | NA | | Company | NA | NA | Company | NA | NA |
| Name of | NA | NA | NA | responsi | NA | | Name of | NA | NA | NA | responsib | NA |
| person res | | | | ble | | | person res | | | | le | |
| ponsible | | | | | | | ponsible | | | | | |
| Type of or | org-type | NA | NA | NA | org-type | | Type of or | org-type | NA | NA | NA | org-type |
| ganization | | | | | | | ganization | | | | | |
| Country | country | country | country | country | NA | | Country | country | NA | country | country | country |
| Postal | address | address | address | address | address | | Postal | address | NA | address | address | address |
| Address | | | | | | | Address | | | | | |
| City | NA | NA | city | NA | NA | | City | NA | NA | city | NA | address |
| State | NA | NA | StatePro | NA | NA | | State | NA | NA | StatePro | NA | address |
| | | | v | | | | | | | v | | |
| Postal | NA | NA | PostalCo | NA | NA | | Postal | NA | NA | PostalCo | NA | address |
| Code | | | de | | | | Code | | | de | | |
| Phone | phone | phone | phone | phone | phone | | Phone | phone | NA | NA | phone | phone |
| Fax Number | fax-no | fax-no | NA | NA | fax-no | | Fax Number | fax-no | NA | NA | NA | fax-no |
| ID of admi | admin-c | admin-c | NA | owner-c | admin-c | | ID of admi | admin-c | NA | Admin | owner-c | admin-c |
| nistrative | | | | | (multipl | | nistrative | | | POC | | (multiple) |
| contact | | | | | e) | | contact | | | | | |
| ID of | tech-c | tech-c | NA | tech-c | tech-c ( | | ID of | tech-c | NA | Tech POC | tech-c | tech-c |
| technical | | | | | multiple | | technical | | | | | (multiple) |
| contact | | | | | ) | | contact | | | | | |
| Reference | mnt-ref | NA | NA | NA | mnt-ref | | Reference | mnt-ref | NA | NOC POC | NA | mnt-ref |
| of | | | | | | | of | | | | | |
| maintainer | | | | | | | maintainer | | | | | |
| Reference | mnt-by | mnt-by | NA | NA | mnt-by | | Reference | mnt-by | NA | Abuse | NA | mnt-by |
| of | | | | | | | of | | | POC | | |
| maintainer | | | | | | | maintainer | | | | | |
| Remarks | remarks | remarks | NA | NA | remarks | | Remarks | remarks | NA | NA | NA | remarks |
| Date of | NA | NA | RegDate | created | NA | | Date of | Changed | NA | RegDate | created | Changed |
| record | | | | | | | record | | | | | |
| creation | | | | | | | creation | | | | | |
| Date of | NA | changed | Updated | changed | NA | | Date of | changed | NA | Updated | changed | changed |
| record | | (multipl | | | | | record | | | | | |
| changed | | e) | | | | | changed | | | | | |
| List of | NA | NA | NA | list of | NA | | List of | NA | NA | NA | list of | NA |
| resources | | | | resource | | | resources | | | | resources | |
| | | | | s | | | Source | source | NA | NA | NA | source |
| Source | source | source | NA | NA | source | | Reference | NA | NA | Ref | NA | NA |
| Reference | NA | NA | Ref | NA | NA | +------------+-----------+------+----------+-----------+------------+
+------------+----------+----------+----------+----------+----------+
WHOIS Data of Organizations Holding a Resource WHOIS Data of Organizations Holding a Resource
4.2. WHOIS Data of Contact 4.2. WHOIS Data of Contact
The following table shows the contact objects of 5 RIRs. The following table shows the contact objects of 5 RIRs.
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| RIR Objects | AFRINIC | APNIC | ARIN | LACNIC | RIPE | | RIR Objects | AFRINIC | APNIC | ARIN | LACNIC | RIPE |
| | | | | | NCC | | | | | | | NCC |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
| Name | person | person | Name | person | person | | Name | person | person | Name | person | person |
| Company | NA | NA | Company | NA | NA | | Company | NA | NA | Company | NA | NA |
| Postal | address | address | Address | address | address | | Postal | address | address | Address | address | address |
| Address | | | | | | | Address | | | | | |
| City | NA | NA | City | NA | NA | | City | NA | NA | City | NA | address |
| State | NA | NA | StateProv | NA | NA | | State | NA | NA | StateProv | NA | address |
| Postal Code | NA | NA | PostalCode | NA | NA | | Postal Code | NA | NA | PostalCode | NA | address |
| Country | NA | country | Country | country | NA | | Country | NA | country | Country | country | NA |
| Phone | phone | phone | Phone | phone | phone | | Phone | phone | phone | Mobile | phone | phone |
| Fax Number | fax-no | fax-no | NA | NA | fax-no | | Fax Number | fax-no | fax-no | Fax | NA | fax-no |
| Email | e-mail | e-mail | Email | e-mail | NA | | Email | e-mail | e-mail | Email | e-mail | NA |
| ID | nic-hdl | nic-hdl | Handle | nic-hdl | nic-hdl | | ID | nic-hdl | nic-hdl | Handle | nic-hdl | nic-hdl |
| Remarks | NA | remarks | NA | NA | remarks | | Remarks | remarks | remarks | Remarks | NA | remarks |
| Notify | NA | notify | NA | NA | NA | | Notify | notify | notify | NA | NA | notify |
| ID of | mnt-by | mnt-by | NA | NA | mnt-by | | ID of | mnt-by | mnt-by | NA | NA | mnt-by |
| maintainer | | | | | | | maintainer | | | | | |
| Registration | NA | NA | RegDate | created | NA | | Registration | changed | NA | RegDate | created | changed |
| Date | | | | | | | Date | | | | | |
| Registration | NA | changed | Updated | changed | NA | | Registration | changed | changed | Updated | changed | changed |
| update | | | | | | | update | | | | | |
| Source | source | source | NA | NA | source | | Source | source | source | NA | NA | source |
| Reference | NA | NA | Ref | NA | NA | | Reference | NA | NA | Ref | NA | NA |
+--------------+---------+---------+------------+---------+---------+ +--------------+---------+---------+------------+---------+---------+
WHOIS Data of Contact WHOIS Data of Contact
4.3. WHOIS Data of IP 4.3. WHOIS Data of IP
The following table shows the IP address objects of 5 RIRs. The following table shows the IP address objects of 5 RIRs.
+----------+------------+------------+----------+------+------------+ +-----------+-------+------------+-----------+--------+-------------+
| RIR | AFRINIC | APNIC | ARIN | LACN | RIPE NCC | | RIR | AFRIN | APNIC | ARIN | LACNIC | RIPE NCC |
| Objects | | | | IC | | | Objects | IC | | | | |
+----------+------------+------------+----------+------+------------+ +-----------+-------+------------+-----------+--------+-------------+
| IP | inetnum | inetnum | NetRange | NA | inetnum | | IP | inetn | inetnum | NetRange | NA | inetnum |
| address | | | | | | | address | um | | | | |
| range | | | | | | | range | | | | | |
| IPV6 | inet6num/i | inet6num/i | CIDR | inet | inet6num/i | | IPV6 | inet6 | inet6num/i | CIDR | inetnu | inet6num/in |
| address | netnum | netnum | | num | netnum | | address | num | netnum | | m | etnum |
| range | | | | | | | range | | | | | |
| Descript | descr | descr | NA | NA | descr | | Descripti | descr | descr | NetName | NA | descr |
| ion | | | | | | | on | | | | | |
| Remarks | NA | NA | NA | NA | remarks | | Remarks | remar | remarks | NA | NA | remarks |
| Origin | NA | origin (on | OriginAS | Orig | origin (on | | | ks | | | | |
| AS | | route/6) | | inAS | route/6) | | Origin AS | NA | origin (on | OriginAS | Origin | origin (on |
| | | | | (fut | | | | | route/6) | | AS (fu | route/6) |
| | | | | ure) | | | | | | | ture) | |
| Network | netname | netname | NetName | inet | netname | | Network | netna | netname | NetHandle | inetre | netname |
| name/ID | | | NetHandl | rev | | | name/ID | me | | | v | |
| | | | e | | | | Maintaine | mnt- | NA | NA | NA | mnt-by |
| Maintain | NA | mnt-irt | NA | NA | NA | | r | by | | | | |
| er | | | | | | | Maintaine | mnt- | NA | NA | NA | NA |
| Maintain | mnt-ref | NA | NA | NA | NA | | r | lower | | | | |
| er | | | | | | | Administr | admin | admin-c | OrgId | owneri | admin-c |
| Administ | admin-c | admin-c | OrgId | owne | admin-c | | ative | -c | | | d | |
| rative | | | | rid | | | contact | | | | | |
| contact | | | | | | | Parent | paren | NA | Parent | NA | NA |
| Parent | parent | NA | Parent | NA | NA | | range | t | | | | |
| range | | | | | | | Status | statu | status | NetType | status | status |
| Status | status | status | NetType | stat | status | | | s | | | | |
| | | | | us | | | Registrat | chang | NA | RegDate | create | changed |
| Registra | NA | NA | RegDate | crea | NA | | ion Date | ed | | | d | |
| tion | | | | ted | | | Registrat | chang | changed | Updated | change | changed |
| Date | | | | | | | ion | ed | (multiple) | | d | |
| Registra | NA | changed | Updated | chan | NA | | update | | | | | |
| tion | | (multiple) | | ged | | | Reference | NA | NA | Ref | NA | NA |
| update | | | | | | | ID organi | org | NA | OrgId | owner | organisatio |
| Referenc | NA | NA | Ref | NA | NA | | zation | | | | | n |
| e | | | | | | | holding | | | | | |
| ID organ | org | NA | OrgId | owne | organisati | | the | | | | | |
| ization | | | | r | on | | resource | | | | | |
| holding | | | | | | | Referral | NA | NA | ReferralS | NA | NA |
| the | | | | | | | server | | | erver | | |
| resource | | | | | | | Technical | tech- | tech-c | OrgTechHa | tech-c | tech-c |
| Referral | NA | NA | Referral | NA | NA | | contact | c | | ndle | | (multiple) |
| server | | | Server | | | | Abuse | NA | NA | OrgAbuseH | abuse- | abuse- |
| Technica | tech-c | tech-c | OrgTechH | tech | tech-c | | contact | | | andle | c | mailbox |
| l | | | andle | -c | (multiple) | | Referral | NA | NA | RTechHand | NA | NA |
| contact | | | | | | | technical | | | le | | |
| Abuse | NA | NA | OrgAbuse | abus | abuse- | | contact | | | | | |
| contact | | | Handle | e-c | mailbox | | Referral | mnt- | mnt-irt | RAbuseHan | NA | NA |
| Referral | NA | NA | RTechHan | NA | NA | | abuse | irt | | dle | | |
| technica | | | dle | | | | contact | | | | | |
| l | | | | | | | Referral | NA | NA | RNOCHandl | NA | NA |
| contact | | | | | | | NOC | | | e | | |
| Referral | NA | NA | RAbuseHa | NA | NA | | contact | | | | | |
| abuse | | | ndle | | | | Name | NA | NA | NA | nserve | NA |
| contact | | | | | | | server | | | | r | |
| Referral | NA | NA | RNOCHand | NA | NA | +-----------+-------+------------+-----------+--------+-------------+
| NOC | | | le | | |
| contact | | | | | |
| Name | NA | NA | NA | nser | NA |
| server | | | | ver | |
+----------+------------+------------+----------+------+------------+
WHOIS Data of IP WHOIS Data of IP
4.4. WHOIS Data of ASN 4.4. WHOIS Data of ASN
+------------+----------+----------+------------+--------+----------+ +------------+--------+---------+-------------+---------+-----------+
| RIR | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC | | RIR | AFRINI | APNIC | ARIN | LACNIC | RIPE NCC |
| Objects | | | | | | | Objects | C | | | | |
+------------+----------+----------+------------+--------+----------+ +------------+--------+---------+-------------+---------+-----------+
| Descriptio | descr | descr | NA | NA | descr | | ID | aut- | aut-num | ASNumber | aut-num | aut-num |
| n | | | | | | | | num | | | | |
| Organizati | organisa | NA | OrgId | owner | org | | Descriptio | descr | descr | NA | NA | descr |
| on | tion | | | | | | n | | | | | |
| Comment | NA | NA | Comment | NA | remarks | | Organizati | org | NA | OrgId | owner | org |
| Administra | admin-c | admin-c | ASHandle | owner- | admin-c | | on | | | | | |
| tive | | | | id | | | Comment | remark | NA | Comment | NA | remarks |
| contact ID | | | | | | | | s | | | | |
| Technical | tech-c | tech-c | OrgTechHan | routin | tech-c ( | | Administra | admin- | admin-c | ASHandle | owner- | admin-c |
| contact ID | | | dle | g-c | multiple | | tive | c | | | id | |
| | | | | | ) | | contact ID | | | | | |
| Organizati | NA | nic-hdl | NA | owner- | organisa | | Technical | tech-c | tech-c | OrgTechHand | routing | tech-c (m |
| on ID | | | | c | tion | | contact ID | | | le | -c | ultiple) |
| Notify | NA | notify | NA | NA | NA | | Organizati | NA | nic-hdl | NA | owner-c | organisat |
| Abuse | NA | NA | OrgAbuseHa | abuse- | NA | | on ID | | | | | ion |
| contact | | | ndle | c | | | Notify | notify | notify | NA | NA | NA |
| Maintainer | mnt-by | mnt-by | NA | NA | mnt-by | | Abuse | NA | NA | OrgAbuseHan | abuse-c | NA |
| Maintainer | mnt- | NA | NA | NA | mnt- | | contact | | | dle | | |
| | lower | | | | lower | | Maintainer | mnt-by | mnt-by | NA | NA | mnt-by |
| Maintainer | NA | NA | NA | NA | mnt-ref | | Maintainer | mnt- | mnt- | NA | NA | mnt-lower |
| Registrati | NA | NA | RegDate | create | NA | | | lower | lower | | | |
| on Date | | | | d | | | Maintainer | NA | NA | NA | NA | mnt-ref |
| Registrati | NA | changed | Updated | change | NA | | Registrati | change | NA | RegDate | created | NA |
| on update | | (multipl | | d | | | on Date | d | | | | |
| | | e) | | | | | Registrati | change | changed | Updated | changed | NA |
| Source | source | source | NA | NA | source | | on update | d | (multip | | | |
+------------+----------+----------+------------+--------+----------+ | | | le) | | | |
| Source | source | source | NA | NA | source |
+------------+--------+---------+-------------+---------+-----------+
WHOIS Data of ASN WHOIS Data of ASN
4.5. Conclusion 4.5. Conclusion
As it can be observed, for each object (Organization, Contact Person, As it can be observed, for each object (Organization, Contact Person,
Net-num and ASN) there are fields that are unique to only one or a Net-num and ASN) there are fields that are unique to only one or a
set of RIRs and there are fields that have the same meaning but are set of RIRs and there are fields that have the same meaning but are
referred different for each RIR. In order to construct a single data referred different for each RIR. In order to construct a single data
model for each object a selection of the most common and useful model for each object a selection of the most common and useful
skipping to change at page 10, line 20 skipping to change at page 10, line 33
categories: domain, contact, nameserver and registrar related categories: domain, contact, nameserver and registrar related
information. information.
5.2.1. WHOIS Data of Domain 5.2.1. WHOIS Data of Domain
WHOIS data of domain includes "Domain Name", "Creation Date", "Domain WHOIS data of domain includes "Domain Name", "Creation Date", "Domain
Status", "Expiration Date", "Updated Date", "Domain ID", "DNSSEC" and Status", "Expiration Date", "Updated Date", "Domain ID", "DNSSEC" and
"Last Transferred Date". The following table gives the element name, "Last Transferred Date". The following table gives the element name,
most popular label and corresponding numbers of TLDs and labels. most popular label and corresponding numbers of TLDs and labels.
+---------------------+---------------------+----------+------------+ +-------------------+-------------------+------------+--------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular | No. of | No. of |
| | | TLDs | Labels | | | Label | TLDs | Labels |
+---------------------+---------------------+----------+------------+ +-------------------+-------------------+------------+--------------+
| Domain Name | Domain Name | 118 | 6 | | Domain Name | Domain Name | 118 | 6 |
| Creation Date | Created | 106 | 24 | | Creation Date | Created | 106 | 24 |
| Domain Status | Status | 95 | 8 | | Domain Status | Status | 95 | 8 |
| Expiration Date | Expiration Date | 81 | 21 | | Expiration Date | Expiration Date | 81 | 21 |
| Updated Date | Modified | 70 | 20 | | Updated Date | Modified | 70 | 20 |
| Domain ID | Domain ID | 34 | 5 | | Domain ID | Domain ID | 34 | 5 |
| DNSSEC | DNSSEC | 14 | 4 | | DNSSEC | DNSSEC | 14 | 4 |
| Last Transferred | Last Transferred | 4 | 3 | | Last Transferred | Last Transferred | 4 | 3 |
| Date | Date | | | | Date | Date | | |
+---------------------+---------------------+----------+------------+ +-------------------+-------------------+------------+--------------+
WHOIS Data of Domain WHOIS Data of Domain
Analyzing the above data, about 95.16% of the 124 registries support Analyzing the above data, about 95.16% of the 124 registries support
"Domain Name" data element; 85.48% of the 124 registries support "Domain Name" data element; 85.48% of the 124 registries support
"Creation Date" data element; 76.61% of the 124 registries support "Creation Date" data element; 76.61% of the 124 registries support
"Domain Status" data element. On the other hand, some elements such "Domain Status" data element. On the other hand, some elements such
as "DNSSEC" and "Last Transferred Date" are only supported by 11.29% as "DNSSEC" and "Last Transferred Date" are only supported by 11.29%
and 3.23% of all the registries seperately. and 3.23% of all the registries seperately.
5.2.2. WHOIS Data of Contact 5.2.2. WHOIS Data of Contact
In domain name space, contacts are typically divided into registrant, In domain name space, contacts are typically divided into registrant,
administrative contact, technical contact and billing contact. administrative contact, technical contact and billing contact.
5.2.2.1. Registrant 5.2.2.1. Registrant
The following table shows all the contact information of registrant. The following table shows all the contact information of registrant.
14 data elements are listed below. 14 data elements are listed below.
+----------------------+----------------------+--------+------------+ +--------------------+---------------------+-----------+------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+----------------------+----------------------+--------+------------+ +--------------------+---------------------+-----------+------------+
| Registrant Name | Name | 65 | 7 | | Registrant Name | Name | 65 | 7 |
| Registrant Email | Registrant Email | 59 | 7 | | Registrant Email | Registrant Email | 59 | 7 |
| Registrant ID | Registrant ID | 50 | 12 | | Registrant ID | Registrant ID | 50 | 12 |
| Registrant Phone | Registrant Phone | 48 | 6 | | Registrant Phone | Registrant Phone | 48 | 6 |
| Registrant Fax | Registrant Fax | 44 | 6 | | Registrant Fax | Registrant Fax | 44 | 6 |
| Registrant | Registrant | 42 | 4 | | Registrant | Registrant | 42 | 4 |
| Organization | Organization | | | | Organization | Organization | | |
| Registrant Country | Country | 42 | 6 | | Registrant Country | Country | 42 | 6 |
| Code | | | | | Code | | | |
| Registrant City | Registrant City | 38 | 4 | | Registrant City | Registrant City | 38 | 4 |
| Registrant Postal | Registrant Postal | 37 | 5 | | Registrant Postal | Registrant Postal | 37 | 5 |
| Code | Code | | | | Code | Code | | |
| Registrant | Registrant | 32 | 4 | | Registrant | Registrant | 32 | 4 |
| State/Province | State/Province | | | | State/Province | State/Province | | |
| Registrant Street | Registrant Street1 | 31 | 16 | | Registrant Street | Registrant Street1 | 31 | 16 |
| Registrant Country | Registrant Country | 19 | 4 | | Registrant Country | Registrant Country | 19 | 4 |
| Registrant Phone | Registrant Phone | 18 | 2 | | Registrant Phone | Registrant Phone | 18 | 2 |
| Ext. | Ext. | | | | Ext. | Ext. | | |
| Registrant Fax Ext | Registrant Fax Ext | 17 | 2 | | Registrant Fax Ext | Registrant Fax Ext | 17 | 2 |
+----------------------+----------------------+--------+------------+ +--------------------+---------------------+-----------+------------+
Registrant Registrant
Among all the data elements, "Registrant Name", "Registrant Email" Among all the data elements, "Registrant Name", "Registrant Email"
and "Registrant ID" are the top 3 data elements. and "Registrant ID" are the top 3 data elements.
5.2.2.2. Admin Contact 5.2.2.2. Admin Contact
The following table shows all the contact information of The following table shows all the contact information of
administrative contact. 14 data elements are listed below. administrative contact. 14 data elements are listed below.
+----------------------+----------------------+---------+-----------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+----------------------+----------------------+---------+-----------+ +--------------------+--------------------+-----------+-------------+
| Admin Street | Address | 64 | 19 | | Admin Street | Address | 64 | 19 |
| Admin Name | Admin Name | 60 | 9 | | Admin Name | Admin Name | 60 | 9 |
| Admin Email | Admin Email | 54 | 12 | | Admin Email | Admin Email | 54 | 12 |
| Admin ID | Admin ID | 52 | 16 | | Admin ID | Admin ID | 52 | 16 |
| Admin Fax | Admin Fax | 44 | 8 | | Admin Fax | Admin Fax | 44 | 8 |
| Admin Phone | Admin Phone | 43 | 9 | | Admin Phone | Admin Phone | 43 | 9 |
| Admin Organization | Admin Organization | 42 | 9 | | Admin Organization | Admin Organization | 42 | 9 |
| Admin Country Code | Country | 42 | 7 | | Admin Country Code | Country | 42 | 7 |
| Admin City | Admin City | 35 | 5 | | Admin City | Admin City | 35 | 5 |
| Admin Postal Code | Admin Postal Code | 35 | 7 | | Admin Postal Code | Admin Postal Code | 35 | 7 |
| Admin State/Province | Admin State/Province | 28 | 5 | | Admin | Admin | 28 | 5 |
| Admin Country | Admin Country | 17 | 5 | | State/Province | State/Province | | |
| Admin Phone Ext. | Admin Phone Ext. | 17 | 3 | | Admin Country | Admin Country | 17 | 5 |
| Admin Fax Ext. | Admin Fax Ext. | 17 | 3 | | Admin Phone Ext. | Admin Phone Ext. | 17 | 3 |
+----------------------+----------------------+---------+-----------+ | Admin Fax Ext. | Admin Fax Ext. | 17 | 3 |
+--------------------+--------------------+-----------+-------------+
Admin Contact Admin Contact
Among all the data elements, "Admin Street", "Admin Name" and "Admin Among all the data elements, "Admin Street", "Admin Name" and "Admin
Email" are the top 3 data elements. Email" are the top 3 data elements.
5.2.2.3. Tech Contact 5.2.2.3. Tech Contact
The following table shows all the information about domain name The following table shows all the information about domain name
technical contact. 14 data elements are listed below. technical contact. 14 data elements are listed below.
+----------------------+----------------------+---------+-----------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+----------------------+----------------------+---------+-----------+ +--------------------+--------------------+-----------+-------------+
| Tech Email | Tech Email | 59 | 9 | | Tech Email | Tech Email | 59 | 9 |
| Tech ID | Tech ID | 55 | 16 | | Tech ID | Tech ID | 55 | 16 |
| Tech Name | Tech Name | 47 | 6 | | Tech Name | Tech Name | 47 | 6 |
| Tech Fax | Tech Fax | 45 | 9 | | Tech Fax | Tech Fax | 45 | 9 |
| Tech Phone | Tech Phone | 45 | 10 | | Tech Phone | Tech Phone | 45 | 10 |
| Tech Country Code | Country | 43 | 9 | | Tech Country Code | Country | 43 | 9 |
| Tech Organization | Tech Organization | 39 | 7 | | Tech Organization | Tech Organization | 39 | 7 |
| Tech City | Tech City | 36 | 4 | | Tech City | Tech City | 36 | 4 |
| Tech Postal Code | Tech Postal Code | 36 | 7 | | Tech Postal Code | Tech Postal Code | 36 | 7 |
| Tech State/Province | Tech State/Province | 30 | 4 | | Tech | Tech | 30 | 4 |
| Tech Street | Tech Street1 | 27 | 16 | | State/Province | State/Province | | |
| Tech Country | Tech Country | 18 | 5 | | Tech Street | Tech Street1 | 27 | 16 |
| Tech Fax Ext | Tech Fax Ext | 18 | 3 | | Tech Country | Tech Country | 18 | 5 |
| Tech Phone Ext. | Tech Phone Ext. | 13 | 3 | | Tech Fax Ext | Tech Fax Ext | 18 | 3 |
+----------------------+----------------------+---------+-----------+ | Tech Phone Ext. | Tech Phone Ext. | 13 | 3 |
+--------------------+--------------------+-----------+-------------+
Tech Contact Tech Contact
Among all the data elements, "Tech Email", "Tech ID" and "Tech Name" Among all the data elements, "Tech Email", "Tech ID" and "Tech Name"
are the top 3 data elements. are the top 3 data elements.
5.2.2.4. Billing Contact 5.2.2.4. Billing Contact
The following table shows all the information about domain name The following table shows all the information about domain name
billing contact. 14 data elements are listed below. billing contact. 14 data elements are listed below.
+----------------------+----------------------+--------+------------+ +--------------------+--------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+----------------------+----------------------+--------+------------+ +--------------------+--------------------+-----------+-------------+
| Billing Name | Name | 47 | 5 | | Billing Name | Name | 47 | 5 |
| Billing Fax | Fax | 43 | 6 | | Billing Fax | Fax | 43 | 6 |
| Billing Email | Email Address | 42 | 7 | | Billing Email | Email Address | 42 | 7 |
| Billing Country Code | Country | 38 | 4 | | Billing Country | Country | 38 | 4 |
| Billing Phone | Phone Number | 34 | 6 | | Code | | | |
| Billing ID | Billing ID | 28 | 9 | | Billing Phone | Phone Number | 34 | 6 |
| Billing City | Billing City | 28 | 4 | | Billing ID | Billing ID | 28 | 9 |
| Billing Organization | Billing Organization | 28 | 5 | | Billing City | Billing City | 28 | 4 |
| Billing Postal Code | Billing Postal Code | 27 | 4 | | Billing | Billing | 28 | 5 |
| Billing | Billing | 21 | 4 | | Organization | Organization | | |
| State/Province | State/Province | | | | Billing Postal | Billing Postal | 27 | 4 |
| Billing Street | Billing Street1 | 19 | 13 | | Code | Code | | |
| Billing Country | Billing Country | 13 | 5 | | Billing | Billing | 21 | 4 |
| Billing Phone Ext. | Billing Phone Ext. | 10 | 2 | | State/Province | State/Province | | |
| Billing Fax Ext | Billing Fax Ext | 10 | 2 | | Billing Street | Billing Street1 | 19 | 13 |
+----------------------+----------------------+--------+------------+ | Billing Country | Billing Country | 13 | 5 |
| Billing Phone Ext. | Billing Phone Ext. | 10 | 2 |
| Billing Fax Ext | Billing Fax Ext | 10 | 2 |
+--------------------+--------------------+-----------+-------------+
Billing Contact Billing Contact
Among all the data elements, "Billing Name", "Tech Fax" and "Billing Among all the data elements, "Billing Name", "Tech Fax" and "Billing
Email" are the top 3 data elements. Email" are the top 3 data elements.
5.2.3. WHOIS Data of Nameserver 5.2.3. WHOIS Data of Nameserver
114 registries (about 92% of all the 124 registries) have the 114 registries (about 92% of all the 124 registries) have the
nameserver data element in their WHOIS response. But there are 63 nameserver data element in their WHOIS response. But there are 63
skipping to change at page 14, line 9 skipping to change at page 15, line 13
WHOIS Data of Nameserver WHOIS Data of Nameserver
Some registries have nameserver elements such like "nameserver 1", Some registries have nameserver elements such like "nameserver 1",
"nameserver 2" till "nameserver n". So there are more labels than of "nameserver 2" till "nameserver n". So there are more labels than of
other data elements. other data elements.
5.2.4. WHOIS Data of Registrar 5.2.4. WHOIS Data of Registrar
There are three data elements about registrar information. There are three data elements about registrar information.
+--------------------+---------------------+----------+-------------+ +-------------------+---------------------+-----------+-------------+
| Data Element | Most Popular Label | No. of | No. of | | Data Element | Most Popular Label | No. of | No. of |
| | | TLDs | Labels | | | | TLDs | Labels |
+--------------------+---------------------+----------+-------------+ +-------------------+---------------------+-----------+-------------+
| Sponsoring | Registrar | 84 | 6 | | Sponsoring | Registrar | 84 | 6 |
| Registrar | | | | | Registrar | | | |
| Created by | Created by | 14 | 3 | | Created by | Created by | 14 | 3 |
| Registrar | | | | | Registrar | | | |
| Updated by | Last Updated by | 11 | 3 | | Updated by | Last Updated by | 11 | 3 |
| Registrar | Registrar | | | | Registrar | Registrar | | |
+--------------------+---------------------+----------+-------------+ +-------------------+---------------------+-----------+-------------+
WHOIS Data of Registrar WHOIS Data of Registrar
67.7% of the registries have sponsoring registrar data element. 67.7% of the registries have sponsoring registrar data element.
Elements such as "Created by Registrar" and "Updated by Registrar" Elements such as "Created by Registrar" and "Updated by Registrar"
are supported by 11.3% and 8.9% of the registries. are supported by 11.3% and 8.9% of the registries.
5.3. Other Objects 5.3. Other Objects
So called other objects are those data elements that are self- So called other objects are those data elements that are self-
skipping to change at page 18, line 29 skipping to change at page 19, line 29
Top 10 Data Elements Top 10 Data Elements
Most of the domain related WHOIS information is included in the top Most of the domain related WHOIS information is included in the top
10 data elements. Other information like name server and registrar 10 data elements. Other information like name server and registrar
name are also supported by most registries. name are also supported by most registries.
We did a cumulative distribution analysis of all the data elements. We did a cumulative distribution analysis of all the data elements.
(1) About 5% of data elements are supported by over 111 (90%) (1) About 5% of data elements are supported by over 111 (90%)
registries. registries.
(2) About 30% of data elements are supported by over 44 (35%) (2) About 30% of data elements are supported by over 44 (35%)
registries. registries.
(3) About 60% of data elements are supported by over 32 (26%) (3) About 60% of data elements are supported by over 32 (26%)
registries. registries.
(4) About 90% of data elements are supported by over 14 (11%) (4) About 90% of data elements are supported by over 14 (11%)
registries. registries.
From the above result, we can conclude that only a few registries From the above result, we can conclude that only a few registries
support all the public objects, most of the registries support just support all the public objects, most of the registries support just
parts of all the objects. parts of 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:
+-------------------+---------------+ +-------------------+---------------+
skipping to change at page 20, line 12 skipping to change at page 21, line 18
* We only use "Whois contactID/nameserver/registrar" as the query * We only use "Whois contactID/nameserver/registrar" as the query
commands to check. commands to check.
* Some registries may not support contact, name server or * Some registries may not support contact, name server or
registrar queries. registrar queries.
* Some may not support query contact by ID. * Some may not support query contact by ID.
* Contact information of some registries may be protected. * Contact information of some registries may be protected.
6. IANA Considerations 6. Reference Extension Objects
There are some objects that are included in the existed WHOIS system
but not mentioned in the document of [I-D.ietf-weirds-json-response].
This document is intended to give a list of reference extension
ogjects for discussion.
6.1. RIR Reference Extension Objects
o company -- the company name registered by the registrant.
o maintainer -- authentication information that identifies who can
modify the contents of this object.
o list of resources -- include a list of all the Internet resources
assigned to this organization.
o referral NOC contact -- the Network Operation Center contact.
6.2. DNR Reference Extension Objects
The following objects are selected from the Top 50 other objects in
section 5.3 that are supported by over 5 registries. These objects
are considered as possible extension objects.
o zone-c -- The handle of a 'role' object with authority over a
zone.
o maintainer -- authentication information that identifies who can
modify the contents of this object.
o Registration URL -- it is usually the website address of a
registry.
o anonymous -- whether the registration information is anonymous or
not.
o hold -- whethe the domain is hold or not.
o nsl-id -- nameserver list ID.
o obsoleted -- whether a domain is obsoleted or not.
o Customer Service Contact -- a kind of contact.
7. IANA Considerations
This document does not specify any IANA actions. This document does not specify any IANA actions.
7. 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.
8. Acknowledgements 9. Acknowledgements
This document has been reviewed and improved by the design team. The This document has been reviewed and improved by the Weirds working
authors especially thank the following individuals who gave their group. The authors especially thank the following individuals who
suggestions and contributions to this document: Guangqing Deng, gave their suggestions and contributions to this document: Guangqing
Frederico A C Neves and Ray Bellis. Deng, Frederico A C Neves, Ray Bellis, Edward Shryane and Kaveh
Ranjbar.
9. Normative References 10. Normative References
[I-D.ietf-weirds-json-response] [I-D.ietf-weirds-json-response]
Newton, A. and S. Hollenbeck, "JSON Responses for the Newton, A. and S. Hollenbeck, "JSON Responses for the
Registration Data Access Protocol (RDAP)", draft-ietf- Registration Data Access Protocol (RDAP)", draft-ietf-
weirds-json-response-06 (work in progress), October 2013. weirds-json-response-06 (work in progress), October 2013.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D., [RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D.,
skipping to change at page 21, line 17 skipping to change at page 23, line 20
[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.
[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:
* Added Change Log section. * Added Change Log section.
* Added RIR data objects. * Added RIR data objects.
* Exchanged section 2 and section 3. * Exchanged section 2 and section 3.
-02:
* Modified some object names in the section of RIR Objects
Analysis.
* Added reference extension objects.
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. 42 change blocks. 
321 lines changed or deleted 381 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/