idnits 2.17.1 draft-ietf-weirds-object-inventory-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 5 instances of lines with non-RFC2606-compliant FQDNs in the document. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 23, 2014) is 3537 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-14) exists of draft-ietf-weirds-json-response-07 Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force L. Zhou 3 Internet-Draft N. Kong 4 Intended status: Informational S. Shen 5 Expires: January 24, 2015 CNNIC 6 S. Sheng 7 ICANN 8 A. Servin 9 LACNIC 10 July 23, 2014 12 Registration Data Access Protocol Object Inventory Analysis 13 draft-ietf-weirds-object-inventory-03 15 Abstract 17 WHOIS output objects from registries (including both Regional 18 Internet Registries (RIRs) and Domain Name Registries (DNRs)) were 19 collected and analyzed. This document describes the statistical 20 analysis process and result of existing WHOIS information. The 21 purpose of this document is to build an object inventory to 22 facilitate discussions of data objects included in Registration Data 23 Access Protocol (RDAP) responses. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on January 24, 2015. 42 Copyright Notice 44 Copyright (c) 2014 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 This document may contain material from IETF Documents or IETF 58 Contributions published or made publicly available before November 59 10, 2008. The person(s) controlling the copyright in some of this 60 material may not have granted the IETF Trust the right to allow 61 modifications of such material outside the IETF Standards Process. 62 Without obtaining an adequate license from the person(s) controlling 63 the copyright in such materials, this document may not be modified 64 outside the IETF Standards Process, and derivative works of it may 65 not be created outside the IETF Standards Process, except to format 66 it for publication as an RFC or to translate it into languages other 67 than English. 69 Table of Contents 71 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 72 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 73 3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 4 74 4. RIR Objects Analysis . . . . . . . . . . . . . . . . . . . . 5 75 4.1. WHOIS Data of Organizations Holding a Resource . . . . . 5 76 4.2. WHOIS Data of Contact . . . . . . . . . . . . . . . . . . 6 77 4.3. WHOIS Data of IP . . . . . . . . . . . . . . . . . . . . 7 78 4.4. WHOIS Data of ASN . . . . . . . . . . . . . . . . . . . . 9 79 4.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 9 80 5. DNR Objects Analysis . . . . . . . . . . . . . . . . . . . . 10 81 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 10 82 5.2. Public Objects . . . . . . . . . . . . . . . . . . . . . 10 83 5.2.1. WHOIS Data of Domain . . . . . . . . . . . . . . . . 10 84 5.2.2. WHOIS Data of Contact . . . . . . . . . . . . . . . . 11 85 5.2.2.1. Registrant . . . . . . . . . . . . . . . . . . . 11 86 5.2.2.2. Admin Contact . . . . . . . . . . . . . . . . . . 12 87 5.2.2.3. Tech Contact . . . . . . . . . . . . . . . . . . 12 88 5.2.2.4. Billing Contact . . . . . . . . . . . . . . . . . 13 89 5.2.3. WHOIS Data of Nameserver . . . . . . . . . . . . . . 14 90 5.2.4. WHOIS Data of Registrar . . . . . . . . . . . . . . . 15 91 5.3. Other Objects . . . . . . . . . . . . . . . . . . . . . . 15 92 5.4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . 17 93 5.4.1. Preliminary Statistics . . . . . . . . . . . . . . . 17 94 5.4.2. Data Elements Analysis . . . . . . . . . . . . . . . 18 95 5.4.3. Labels Analysis . . . . . . . . . . . . . . . . . . . 19 96 5.4.4. Other Objects Analysis . . . . . . . . . . . . . . . 20 98 5.5. Limitation . . . . . . . . . . . . . . . . . . . . . . . 20 99 6. Reference Extension Objects . . . . . . . . . . . . . . . . . 21 100 6.1. RIR Reference Extension Objects . . . . . . . . . . . . . 21 101 6.2. DNR Reference Extension Objects . . . . . . . . . . . . . 21 102 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 103 8. Security considerations . . . . . . . . . . . . . . . . . . . 22 104 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 105 10. Normative References . . . . . . . . . . . . . . . . . . . . 22 106 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 23 107 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 109 1. Introduction 111 RIRs and DNRs have historically maintained a lookup service to permit 112 public access to some portion of the registry database. Most 113 registries offer the service via the WHOIS protocol [RFC3912], with 114 additional services being offered via world wide web pages, bulk 115 downloads, and other services, such as RPSL [RFC2622]. 117 Although the WHOIS protocol specified in [RFC3912] is widely adopted 118 and supported, it has several shortcomings that limits its usefulness 119 to the evolving needs of the Internet community. For example, the 120 WHOIS protocol has not been Internationalized, it does not 121 consistently support Internationalized Domain Name (IDN, described in 122 [RFC5890]); WHOIS has no query and response format; and WHOIS 123 protocol does not support user authentication, access control for 124 differentiated access. 126 This document is aimed to build an object inventory to facilitate 127 discussions of registration data objects. Based on this statistics 128 result, it may help to form and specify the RDAP response format. 130 In number space, there are altogether 5 RIRs. All RIRs provide 131 information about IP addresses, Autonomous System Number (ASNs) and 132 contacts, the data model used is different for each RIR. In domain 133 name space, there are now over 200 ccTLDs and 21 gTLDs. Different 134 domain name registries may have different WHOIS response objects and 135 formats. A common understanding of all these data formats is 136 critical. 138 This document describes the WHOIS data collection procedures and 139 gives a data object inventory analysis based on the collected data 140 from 5 RIRs and 106 ccTLDs and 18 gTLDs from DNRs. The RIR data 141 objects are classified into IP address, ASN, person or contact and 142 the organization that held the resource. The DNR data objects are 143 classified into domain, contact, nameserver and registrar related 144 objects. Other objects that do not belong to above categories are 145 viewed as private designed objects. In this document, we are not 146 intended to analyze all the query and response types existed in RIRs 147 and DNRs. The most common query objects will be discussed, other 148 objects such as RPSL data structure used by Internet Routing 149 Registries (IRRs) will be added at a later time if the community 150 feels it is necessary. 152 Since this is a document with statistics analysis and there are no 153 protocol specifications, the [RFC2119] language does not apply. 155 2. Terminology 157 o Data element -- The name of specific response object. 159 o Label -- Different registries may have different naming ways for 160 the same data element. So there may be several labels with the 161 same meaning and belong to one group of data element. 163 o Most popular label -- The label which is most supported by the 164 registries. 166 o Number of labels -- The number of different labels. 168 o Total count -- The number of registries that support a certain 169 data element. 171 3. Methodology 173 WHOIS information, including port 43 response and web response data, 174 is collected following the procedures described below. 176 RIR objects collection process: 178 (1) The process of RIR data collection is relatively easy. There 179 are altogether 5 RIRs which are AFRINIC, APNIC, ARIN, LACNIC and 180 RIPE NCC. All the RIRs provide information of IPs, ASNs and 181 contacts. Find the 5 RIR WHOIS servers firstly. 183 (2) Query the corresponding IPs, ASNs, contacts and organizations 184 registered in 5 RIRs and make a comparative analysis of the 185 responses data. 187 (3) Data elements with the same meaning, but using different labels, 188 are grouped together. 190 DNR objects collections process: 192 (1) A programming script is applied to collect port 43 response data 193 from 294 ccTLDs. "nic.ccTLD" is used as the query string which 194 is usually registered in a domain registry. Responses of 106 195 ccTLDs were received. 18 gTLDs' port 43 response data is 196 collected from their contracts with ICANN. So the sample size 197 of port 43 WHOIS response data is 124 registries in total. 199 (2) WHOIS data from web is collected manually from the 124 200 registries that have port 43 WHOIS responses. 202 (3) Some of the responses which are collected by program may not 203 seem to be correct. So data of top 10 ccTLD registries, like 204 .de, .eu and .uk etc., was re-verified by querying domain names 205 other than "nic.ccTLD". 207 (4) In accordance with the specification 4 of new gTLD applicant 208 guide book, [RFC5730], [RFC5731], [RFC5732] and [RFC5733], the 209 response data objects are classified into public and other data 210 objects. Public data objects are those which are defined in the 211 above two documents. Other objects are those which are self 212 designed data elements or objects in different registries. 214 (5) Data elements with the same meaning, but using different labels, 215 are grouped together. The numbers of registries that support 216 the data elements is calculated in the total count column. 218 4. RIR Objects Analysis 220 4.1. WHOIS Data of Organizations Holding a Resource 222 The following table shows the organization objects of 5 RIRs. 224 +------------+-----------+------+----------+-----------+------------+ 225 | RIR | AFRINIC | APNI | ARIN | LACNIC | RIPE NCC | 226 | Objects | | C | | | | 227 +------------+-----------+------+----------+-----------+------------+ 228 | Organizati | organisat | NA | Name | Owner | org-name | 229 | on name | ion | | | | | 230 | Organizati | org-name | NA | Handle | owner-id | organisati | 231 | on ID | | | | | on | 232 | Company | NA | NA | Company | NA | NA | 233 | Name of | NA | NA | NA | responsib | NA | 234 | person res | | | | le | | 235 | ponsible | | | | | | 236 | Type of or | org-type | NA | NA | NA | org-type | 237 | ganization | | | | | | 238 | Country | country | NA | country | country | country | 239 | Postal | address | NA | address | address | address | 240 | Address | | | | | | 241 | City | NA | NA | city | NA | address | 242 | State | NA | NA | StatePro | NA | address | 243 | | | | v | | | 244 | Postal | NA | NA | PostalCo | NA | address | 245 | Code | | | de | | | 246 | Phone | phone | NA | NA | phone | phone | 247 | Fax Number | fax-no | NA | NA | NA | fax-no | 248 | ID of admi | admin-c | NA | Admin | owner-c | admin-c | 249 | nistrative | | | POC | | (multiple) | 250 | contact | | | | | | 251 | ID of | tech-c | NA | Tech POC | tech-c | tech-c | 252 | technical | | | | | (multiple) | 253 | contact | | | | | | 254 | Reference | mnt-ref | NA | NOC POC | NA | mnt-ref | 255 | of | | | | | | 256 | maintainer | | | | | | 257 | Reference | mnt-by | NA | Abuse | NA | mnt-by | 258 | of | | | POC | | | 259 | maintainer | | | | | | 260 | Remarks | remarks | NA | NA | NA | remarks | 261 | Date of | Changed | NA | RegDate | created | Changed | 262 | record | | | | | | 263 | creation | | | | | | 264 | Date of | changed | NA | Updated | changed | changed | 265 | record | | | | | | 266 | changed | | | | | | 267 | List of | NA | NA | NA | list of | NA | 268 | resources | | | | resources | | 269 | Source | source | NA | NA | NA | source | 270 | Reference | NA | NA | Ref | NA | NA | 271 +------------+-----------+------+----------+-----------+------------+ 273 WHOIS Data of Organizations Holding a Resource 275 4.2. WHOIS Data of Contact 277 The following table shows the contact objects of 5 RIRs. 279 +--------------+---------+---------+------------+---------+---------+ 280 | RIR Objects | AFRINIC | APNIC | ARIN | LACNIC | RIPE | 281 | | | | | | NCC | 282 +--------------+---------+---------+------------+---------+---------+ 283 | Name | person | person | Name | person | person | 284 | Company | NA | NA | Company | NA | NA | 285 | Postal | address | address | Address | address | address | 286 | Address | | | | | | 287 | City | NA | NA | City | NA | address | 288 | State | NA | NA | StateProv | NA | address | 289 | Postal Code | NA | NA | PostalCode | NA | address | 290 | Country | NA | country | Country | country | NA | 291 | Phone | phone | phone | Mobile | phone | phone | 292 | Fax Number | fax-no | fax-no | Fax | NA | fax-no | 293 | Email | e-mail | e-mail | Email | e-mail | NA | 294 | ID | nic-hdl | nic-hdl | Handle | nic-hdl | nic-hdl | 295 | Remarks | remarks | remarks | Remarks | NA | remarks | 296 | Notify | notify | notify | NA | NA | notify | 297 | ID of | mnt-by | mnt-by | NA | NA | mnt-by | 298 | maintainer | | | | | | 299 | Registration | changed | NA | RegDate | created | changed | 300 | Date | | | | | | 301 | Registration | changed | changed | Updated | changed | changed | 302 | update | | | | | | 303 | Source | source | source | NA | NA | source | 304 | Reference | NA | NA | Ref | NA | NA | 305 +--------------+---------+---------+------------+---------+---------+ 307 WHOIS Data of Contact 309 4.3. WHOIS Data of IP 311 The following table shows the IP address objects of 5 RIRs. 313 +-----------+-------+------------+-----------+--------+-------------+ 314 | RIR | AFRIN | APNIC | ARIN | LACNIC | RIPE NCC | 315 | Objects | IC | | | | | 316 +-----------+-------+------------+-----------+--------+-------------+ 317 | IP | inetn | inetnum | NetRange | NA | inetnum | 318 | address | um | | | | | 319 | range | | | | | | 320 | IPV6 | inet6 | inet6num/i | CIDR | inetnu | inet6num/in | 321 | address | num | netnum | | m | etnum | 322 | range | | | | | | 323 | Descripti | descr | descr | NetName | NA | descr | 324 | on | | | | | | 325 | Remarks | remar | remarks | NA | NA | remarks | 326 | | ks | | | | | 327 | Origin AS | NA | origin (on | OriginAS | Origin | origin (on | 328 | | | route/6) | | AS (fu | route/6) | 329 | | | | | ture) | | 330 | Network | netna | netname | NetHandle | inetre | netname | 331 | name/ID | me | | | v | | 332 | Maintaine | mnt- | NA | NA | NA | mnt-by | 333 | r | by | | | | | 334 | Maintaine | mnt- | NA | NA | NA | NA | 335 | r | lower | | | | | 336 | Administr | admin | admin-c | OrgId | owneri | admin-c | 337 | ative | -c | | | d | | 338 | contact | | | | | | 339 | Parent | paren | NA | Parent | NA | NA | 340 | range | t | | | | | 341 | Status | statu | status | NetType | status | status | 342 | | s | | | | | 343 | Registrat | chang | NA | RegDate | create | changed | 344 | ion Date | ed | | | d | | 345 | Registrat | chang | changed | Updated | change | changed | 346 | ion | ed | (multiple) | | d | | 347 | update | | | | | | 348 | Reference | NA | NA | Ref | NA | NA | 349 | ID organi | org | NA | OrgId | owner | organisatio | 350 | zation | | | | | n | 351 | holding | | | | | | 352 | the | | | | | | 353 | resource | | | | | | 354 | Referral | NA | NA | ReferralS | NA | NA | 355 | server | | | erver | | | 356 | Technical | tech- | tech-c | OrgTechHa | tech-c | tech-c | 357 | contact | c | | ndle | | (multiple) | 358 | Abuse | NA | NA | OrgAbuseH | abuse- | abuse- | 359 | contact | | | andle | c | mailbox | 360 | Referral | NA | NA | RTechHand | NA | NA | 361 | technical | | | le | | | 362 | contact | | | | | | 363 | Referral | mnt- | mnt-irt | RAbuseHan | NA | NA | 364 | abuse | irt | | dle | | | 365 | contact | | | | | | 366 | Referral | NA | NA | RNOCHandl | NA | NA | 367 | NOC | | | e | | | 368 | contact | | | | | | 369 | Name | NA | NA | NA | nserve | NA | 370 | server | | | | r | | 371 +-----------+-------+------------+-----------+--------+-------------+ 373 WHOIS Data of IP 375 4.4. WHOIS Data of ASN 377 +------------+--------+---------+-------------+---------+-----------+ 378 | RIR | AFRINI | APNIC | ARIN | LACNIC | RIPE NCC | 379 | Objects | C | | | | | 380 +------------+--------+---------+-------------+---------+-----------+ 381 | ID | aut- | aut-num | ASNumber | aut-num | aut-num | 382 | | num | | | | | 383 | Descriptio | descr | descr | NA | NA | descr | 384 | n | | | | | | 385 | Organizati | org | NA | OrgId | owner | org | 386 | on | | | | | | 387 | Comment | remark | NA | Comment | NA | remarks | 388 | | s | | | | | 389 | Administra | admin- | admin-c | ASHandle | owner- | admin-c | 390 | tive | c | | | id | | 391 | contact ID | | | | | | 392 | Technical | tech-c | tech-c | OrgTechHand | routing | tech-c (m | 393 | contact ID | | | le | -c | ultiple) | 394 | Organizati | NA | nic-hdl | NA | owner-c | organisat | 395 | on ID | | | | | ion | 396 | Notify | notify | notify | NA | NA | NA | 397 | Abuse | NA | NA | OrgAbuseHan | abuse-c | NA | 398 | contact | | | dle | | | 399 | Maintainer | mnt-by | mnt-by | NA | NA | mnt-by | 400 | Maintainer | mnt- | mnt- | NA | NA | mnt-lower | 401 | | lower | lower | | | | 402 | Maintainer | NA | NA | NA | NA | mnt-ref | 403 | Registrati | change | NA | RegDate | created | NA | 404 | on Date | d | | | | | 405 | Registrati | change | changed | Updated | changed | NA | 406 | on update | d | (multip | | | | 407 | | | le) | | | | 408 | Source | source | source | NA | NA | source | 409 +------------+--------+---------+-------------+---------+-----------+ 411 WHOIS Data of ASN 413 4.5. Conclusion 415 As it can be observed, for each object (Organization, Contact Person, 416 Net-num and ASN) there are fields that are unique to only one or a 417 set of RIRs and there are fields that have the same meaning but are 418 referred different for each RIR. In order to construct a single data 419 model for each object a selection of the most common and useful 420 fields was made. That initial selection was the starting point of 421 the previous document of [I-D.ietf-weirds-json-response]. 423 5. DNR Objects Analysis 425 5.1. Overview 427 WHOIS data is collected from 124 registries, including 106 ccTLDs and 428 18 gTLDs. All the 124 registries support domain query. Among 124 429 registries, 8 ccTLDs and 15 gTLDs support contact query. 10 ccTLDs 430 and 18 gTLDs support name server query. 4 ccTLDs and 18 gTLDs 431 support registrar query. Domain WHOIS data contains 68 data elements 432 that use a total of 550 labels. There are total 392 other objects 433 for Domain WHOIS data. The raw data can be accessed with the 434 following link: WHOIS Statistics Data File [Stat-Data-File] 436 5.2. Public Objects 438 As mentioned above, public objects are those data elements selected 439 according to new gTLD application guide book, [RFC5730], [RFC5731], 440 [RFC5732] and [RFC5733]. They are generally classified into four 441 categories: domain, contact, nameserver and registrar related 442 information. 444 5.2.1. WHOIS Data of Domain 446 WHOIS data of domain includes "Domain Name", "Creation Date", "Domain 447 Status", "Expiration Date", "Updated Date", "Domain ID", "DNSSEC" and 448 "Last Transferred Date". The following table gives the element name, 449 most popular label and corresponding numbers of TLDs and labels. 451 +-------------------+-------------------+------------+--------------+ 452 | Data Element | Most Popular | No. of | No. of | 453 | | Label | TLDs | Labels | 454 +-------------------+-------------------+------------+--------------+ 455 | Domain Name | Domain Name | 118 | 6 | 456 | Creation Date | Created | 106 | 24 | 457 | Domain Status | Status | 95 | 8 | 458 | Expiration Date | Expiration Date | 81 | 21 | 459 | Updated Date | Modified | 70 | 20 | 460 | Domain ID | Domain ID | 34 | 5 | 461 | DNSSEC | DNSSEC | 14 | 4 | 462 | Last Transferred | Last Transferred | 4 | 3 | 463 | Date | Date | | | 464 +-------------------+-------------------+------------+--------------+ 466 WHOIS Data of Domain 468 Analyzing the above data, about 95.16% of the 124 registries support 469 "Domain Name" data element; 85.48% of the 124 registries support 470 "Creation Date" data element; 76.61% of the 124 registries support 471 "Domain Status" data element. On the other hand, some elements such 472 as "DNSSEC" and "Last Transferred Date" are only supported by 11.29% 473 and 3.23% of all the registries seperately. 475 5.2.2. WHOIS Data of Contact 477 In domain name space, contacts are typically divided into registrant, 478 administrative contact, technical contact and billing contact. 480 5.2.2.1. Registrant 482 The following table shows all the contact information of registrant. 483 14 data elements are listed below. 485 +--------------------+---------------------+-----------+------------+ 486 | Data Element | Most Popular Label | No. of | No. of | 487 | | | TLDs | Labels | 488 +--------------------+---------------------+-----------+------------+ 489 | Registrant Name | Name | 65 | 7 | 490 | Registrant Email | Registrant Email | 59 | 7 | 491 | Registrant ID | Registrant ID | 50 | 12 | 492 | Registrant Phone | Registrant Phone | 48 | 6 | 493 | Registrant Fax | Registrant Fax | 44 | 6 | 494 | Registrant | Registrant | 42 | 4 | 495 | Organization | Organization | | | 496 | Registrant Country | Country | 42 | 6 | 497 | Code | | | | 498 | Registrant City | Registrant City | 38 | 4 | 499 | Registrant Postal | Registrant Postal | 37 | 5 | 500 | Code | Code | | | 501 | Registrant | Registrant | 32 | 4 | 502 | State/Province | State/Province | | | 503 | Registrant Street | Registrant Street1 | 31 | 16 | 504 | Registrant Country | Registrant Country | 19 | 4 | 505 | Registrant Phone | Registrant Phone | 18 | 2 | 506 | Ext. | Ext. | | | 507 | Registrant Fax Ext | Registrant Fax Ext | 17 | 2 | 508 +--------------------+---------------------+-----------+------------+ 510 Registrant 512 Among all the data elements, "Registrant Name", "Registrant Email" 513 and "Registrant ID" are the top 3 data elements. 515 5.2.2.2. Admin Contact 517 The following table shows all the contact information of 518 administrative contact. 14 data elements are listed below. 520 +--------------------+--------------------+-----------+-------------+ 521 | Data Element | Most Popular Label | No. of | No. of | 522 | | | TLDs | Labels | 523 +--------------------+--------------------+-----------+-------------+ 524 | Admin Street | Address | 64 | 19 | 525 | Admin Name | Admin Name | 60 | 9 | 526 | Admin Email | Admin Email | 54 | 12 | 527 | Admin ID | Admin ID | 52 | 16 | 528 | Admin Fax | Admin Fax | 44 | 8 | 529 | Admin Phone | Admin Phone | 43 | 9 | 530 | Admin Organization | Admin Organization | 42 | 9 | 531 | Admin Country Code | Country | 42 | 7 | 532 | Admin City | Admin City | 35 | 5 | 533 | Admin Postal Code | Admin Postal Code | 35 | 7 | 534 | Admin | Admin | 28 | 5 | 535 | State/Province | State/Province | | | 536 | Admin Country | Admin Country | 17 | 5 | 537 | Admin Phone Ext. | Admin Phone Ext. | 17 | 3 | 538 | Admin Fax Ext. | Admin Fax Ext. | 17 | 3 | 539 +--------------------+--------------------+-----------+-------------+ 541 Admin Contact 543 Among all the data elements, "Admin Street", "Admin Name" and "Admin 544 Email" are the top 3 data elements. 546 5.2.2.3. Tech Contact 548 The following table shows all the information about domain name 549 technical contact. 14 data elements are listed below. 551 +--------------------+--------------------+-----------+-------------+ 552 | Data Element | Most Popular Label | No. of | No. of | 553 | | | TLDs | Labels | 554 +--------------------+--------------------+-----------+-------------+ 555 | Tech Email | Tech Email | 59 | 9 | 556 | Tech ID | Tech ID | 55 | 16 | 557 | Tech Name | Tech Name | 47 | 6 | 558 | Tech Fax | Tech Fax | 45 | 9 | 559 | Tech Phone | Tech Phone | 45 | 10 | 560 | Tech Country Code | Country | 43 | 9 | 561 | Tech Organization | Tech Organization | 39 | 7 | 562 | Tech City | Tech City | 36 | 4 | 563 | Tech Postal Code | Tech Postal Code | 36 | 7 | 564 | Tech | Tech | 30 | 4 | 565 | State/Province | State/Province | | | 566 | Tech Street | Tech Street1 | 27 | 16 | 567 | Tech Country | Tech Country | 18 | 5 | 568 | Tech Fax Ext | Tech Fax Ext | 18 | 3 | 569 | Tech Phone Ext. | Tech Phone Ext. | 13 | 3 | 570 +--------------------+--------------------+-----------+-------------+ 572 Tech Contact 574 Among all the data elements, "Tech Email", "Tech ID" and "Tech Name" 575 are the top 3 data elements. 577 5.2.2.4. Billing Contact 579 The following table shows all the information about domain name 580 billing contact. 14 data elements are listed below. 582 +--------------------+--------------------+-----------+-------------+ 583 | Data Element | Most Popular Label | No. of | No. of | 584 | | | TLDs | Labels | 585 +--------------------+--------------------+-----------+-------------+ 586 | Billing Name | Name | 47 | 5 | 587 | Billing Fax | Fax | 43 | 6 | 588 | Billing Email | Email Address | 42 | 7 | 589 | Billing Country | Country | 38 | 4 | 590 | Code | | | | 591 | Billing Phone | Phone Number | 34 | 6 | 592 | Billing ID | Billing ID | 28 | 9 | 593 | Billing City | Billing City | 28 | 4 | 594 | Billing | Billing | 28 | 5 | 595 | Organization | Organization | | | 596 | Billing Postal | Billing Postal | 27 | 4 | 597 | Code | Code | | | 598 | Billing | Billing | 21 | 4 | 599 | State/Province | State/Province | | | 600 | Billing Street | Billing Street1 | 19 | 13 | 601 | Billing Country | Billing Country | 13 | 5 | 602 | Billing Phone Ext. | Billing Phone Ext. | 10 | 2 | 603 | Billing Fax Ext | Billing Fax Ext | 10 | 2 | 604 +--------------------+--------------------+-----------+-------------+ 606 Billing Contact 608 Among all the data elements, "Billing Name", "Tech Fax" and "Billing 609 Email" are the top 3 data elements. 611 5.2.3. WHOIS Data of Nameserver 613 114 registries (about 92% of all the 124 registries) have the 614 nameserver data element in their WHOIS response. But there are 63 615 different labels for this element. Top 3 labels for this element are 616 Name Server which is supported by 25% of all the registries, Name 617 Servers which is supported by 16% of all the registries and nserver 618 which is supported by 12% of all the registries. 620 +--------------+--------------------+-------------+---------------+ 621 | Data Element | Most Popular Label | No. of TLDs | No. of Labels | 622 +--------------+--------------------+-------------+---------------+ 623 | NameServer | NameServer | 114 | 63 | 624 +--------------+--------------------+-------------+---------------+ 626 WHOIS Data of Nameserver 628 Some registries have nameserver elements such like "nameserver 1", 629 "nameserver 2" till "nameserver n". So there are more labels than of 630 other data elements. 632 5.2.4. WHOIS Data of Registrar 634 There are three data elements about registrar information. 636 +-------------------+---------------------+-----------+-------------+ 637 | Data Element | Most Popular Label | No. of | No. of | 638 | | | TLDs | Labels | 639 +-------------------+---------------------+-----------+-------------+ 640 | Sponsoring | Registrar | 84 | 6 | 641 | Registrar | | | | 642 | Created by | Created by | 14 | 3 | 643 | Registrar | | | | 644 | Updated by | Last Updated by | 11 | 3 | 645 | Registrar | Registrar | | | 646 +-------------------+---------------------+-----------+-------------+ 648 WHOIS Data of Registrar 650 67.7% of the registries have sponsoring registrar data element. 651 Elements such as "Created by Registrar" and "Updated by Registrar" 652 are supported by 11.3% and 8.9% of the registries. 654 5.3. Other Objects 656 So called other objects are those data elements that are self- 657 designed or are difficult to be classified. There are 392 other 658 objects altogether. The following tables lists the top 50 other 659 objects according to the data collection result. 661 +----------------------------------------+-------------+ 662 | Data Element | No. of TLDs | 663 +----------------------------------------+-------------+ 664 | Registrant | 41 | 665 | Phone | 32 | 666 | Technical contact | 26 | 667 | Administrative contact | 15 | 668 | source | 14 | 669 | fax-no | 13 | 670 | nic-hdl | 13 | 671 | Billing Contact | 12 | 672 | referral url | 11 | 673 | e-mail | 10 | 674 | WHOIS server | 9 | 675 | Admin Contact | 9 | 676 | Type | 9 | 677 | Website | 9 | 678 | zone-c | 8 | 679 | remarks | 7 | 680 | Registration URL | 6 | 681 | anonymous | 6 | 682 | anniversary | 6 | 683 | hold | 6 | 684 | nsl-id | 6 | 685 | obsoleted | 6 | 686 | Customer Service Contact | 5 | 687 | Customer Service Email | 4 | 688 | Registrar ID | 4 | 689 | org | 4 | 690 | person | 4 | 691 | Maintainer | 4 | 692 | Nombre | 3 | 693 | Sponsoring Registrar IANA ID | 3 | 694 | Trademark Number | 3 | 695 | Trademark Country | 3 | 696 | descr | 3 | 697 | url | 3 | 698 | Postal address | 3 | 699 | Registrar URL | 3 | 700 | International Name | 3 | 701 | International Address | 3 | 702 | Admin Contacts | 2 | 703 | Contractual Language | 2 | 704 | Date Trademark Registered | 2 | 705 | Date Trademark Applied For | 2 | 706 | IP Address | 2 | 707 | Keys | 2 | 708 | Language | 2 | 709 | NIC handle | 2 | 710 | Record maintained by | 2 | 711 | Registration Service Provider | 2 | 712 | Registration Service Provided By | 2 | 713 | Registrar URL (registration services) | 2 | 714 +----------------------------------------+-------------+ 716 Top 50 Other Objects 718 Some elements like "Registrant" are difficult to be classified into 719 any categories. A few registries have two levels of data elements, 720 for example: 722 Registrant: 723 Name: 724 Email: 725 ... 727 We do not think the first level of elements belong to any part. So 728 they are put into the scope of other objects. 730 Some other data elements, like "Remarks", "anniversary" and "Customer 731 service Contact" etc., are designed particularly for their own 732 purpose by different registries. 734 5.4. Conclusion 736 5.4.1. Preliminary Statistics 738 Some preliminary statistics conclusion could be drawn from the raw 739 data. 741 o All of the 124 domain registries have the object names in their 742 responses although they are in various formats. 744 o Of the 118 whois services contacted, 65 registries show their 745 registrant contact. About half of the registries (60 registries) 746 support admin contact information. There are 47 registries, that 747 is about one third of the total number, have technical and billing 748 contact information. And only 7 of all the 124 registries give 749 their abuse email in remarks part. No explicit abuse contact 750 information is provided. 752 o There are mainly two presentation formats. One is key:value, the 753 other is data block format. Example of key-value format: 755 Domain Information 756 Query: na-nic.com.na 757 Status: Delegated 758 Created: 17 Apr 2004 759 Modified: 14 Nov 2010 760 Expires: 31 Dec 9999 761 Name Servers: oshikoko.omadhina.net 762 ns1.na.afrisp.net 763 ns2.na.afrisp.net 764 ... 766 Example of data block format: 768 Whois database 769 domain nic.vg 771 Domain Name nic.vg 772 Registered 1998-09-02 773 Expiry 2012-09-02 775 Resource Records 777 a 195.153.6.27 778 mx 10 terpsichore.william.org 779 www a 195.153.6.27 781 Contact details 783 Registrant, 784 Technical Contact, 785 Billing Contact, 786 Admin. Contact AdamsNames Reserved Domains (i) 787 These domains are not available for registration 788 United Kingdom 789 Identifier: neams048s 791 Servidor Whois de NIC-Venezuela (.VE) 793 Este servidor contiene informacion autoritativa exclusivamente 794 de dominios .VE Cualquier consulta sobre este servicio, puede 795 hacerla al correo electronico whois@nic.ve 797 Titular: 798 Jhonny Valera (nic.ve-dom) jhovalera@conatel.gob.ve 799 Comision Nacional de Telecomunicaciones 800 Av. Veracruz con calle Cali, Edif Aguila, Urb. Las Mercedes 801 Caracas, Distrito Capital VE 802 0212-9090493 (FAX) +582127718599 804 o 11 registries give local script responses. The WHOIS information 805 of other registries are all represented in English. 807 5.4.2. Data Elements Analysis 809 Top 10 data elements are as follows: 811 +----------------------+-------------+ 812 | Data Element | No. of TLDs | 813 +----------------------+-------------+ 814 | Domain Name | 118 | 815 | Name Server | 114 | 816 | Creation Date | 106 | 817 | Domain Status | 95 | 818 | Sponsoring Registrar | 84 | 819 | Expiration Date | 81 | 820 | Updated Date | 70 | 821 | Registrant Name | 65 | 822 | Admin Street | 64 | 823 | Admin Name | 60 | 824 +----------------------+-------------+ 826 Top 10 Data Elements 828 Most of the domain related WHOIS information is included in the top 829 10 data elements. Other information like name server and registrar 830 name are also supported by most registries. 832 We did a cumulative distribution analysis of all the data elements. 834 (1) About 5% of data elements are supported by over 111 (90%) 835 registries. 837 (2) About 30% of data elements are supported by over 44 (35%) 838 registries. 840 (3) About 60% of data elements are supported by over 32 (26%) 841 registries. 843 (4) About 90% of data elements are supported by over 14 (11%) 844 registries. 846 From the above result, we can conclude that only a few registries 847 support all the public objects, most of the registries support just 848 parts of all the objects. 850 5.4.3. Labels Analysis 852 The top 10 labels of different data elements include: 854 +-------------------+---------------+ 855 | Labels | No. of Labels | 856 +-------------------+---------------+ 857 | Name Server | 63 | 858 | Creation Date | 24 | 859 | Expiration Date | 21 | 860 | Updated Date | 20 | 861 | Admin Street | 19 | 862 | Tech ID | 18 | 863 | Registrant Street | 16 | 864 | Admin ID | 16 | 865 | Tech Street | 16 | 866 | Billing Street | 13 | 867 +-------------------+---------------+ 869 Top 10 Labels 871 As explained above, name server label is a unique example that many 872 registries define the name server elements from "nameserver 1" till 873 "nameserver n". So label numbers of name server are much more than 874 other elements. Other elements about date, street name have more 875 labels. 877 A cumulative distribution analysis of label numbers was done. About 878 90% of data elements have more than 2 Labels. So it is very 879 necessary to specify a standard and unified format for object names 880 of WHOIS response. 882 5.4.4. Other Objects Analysis 884 According to statistics result, there are 392 other data objects in 885 total that are not easy to be classified or privately owned by 886 various registries. Top 50 other objects are listed in the table in 887 section 4.3. You can find that various different objects are 888 designed for some particular purpose. So in order to ensure 889 uniqueness of JSON names used in the Restful Whois service, 890 establishing an IANA registry is a necessary requirement. 892 5.5. Limitation 894 o The input "nic.ccTLD" maybe is not a good choice. 896 o The classification of local script data elements may not be 897 accurate. 11 registries give local script responses. 899 o The extension data elements are used randomly by different 900 registries. It is difficult to do statistical analysis. 902 o Sample sizes of contact, name server and registrar queries are 903 small. 905 * We only use "Whois contactID/nameserver/registrar" as the query 906 commands to check. 908 * Some registries may not support contact, name server or 909 registrar queries. 911 * Some may not support query contact by ID. 913 * Contact information of some registries may be protected. 915 6. Reference Extension Objects 917 There are some objects that are included in the existed WHOIS system 918 but not mentioned in the document of [I-D.ietf-weirds-json-response]. 919 This document is intended to give a list of reference extension 920 ogjects for discussion. 922 6.1. RIR Reference Extension Objects 924 o company -- the company name registered by the registrant. 926 o maintainer -- authentication information that identifies who can 927 modify the contents of this object. 929 o list of resources -- include a list of all the Internet resources 930 assigned to this organization. 932 o referral NOC contact -- the Network Operation Center contact. 934 6.2. DNR Reference Extension Objects 936 The following objects are selected from the Top 50 other objects in 937 section 5.3 that are supported by over 5 registries. These objects 938 are considered as possible extension objects. 940 o zone-c -- The handle of a 'role' object with authority over a 941 zone. 943 o maintainer -- authentication information that identifies who can 944 modify the contents of this object. 946 o Registration URL -- it is usually the website address of a 947 registry. 949 o anonymous -- whether the registration information is anonymous or 950 not. 952 o hold -- whethe the domain is hold or not. 954 o nsl-id -- nameserver list ID. 956 o obsoleted -- whether a domain is obsoleted or not. 958 o Customer Service Contact -- a kind of contact. 960 7. IANA Considerations 962 This document does not specify any IANA actions. 964 8. Security considerations 966 This document does not provide any other security services or 967 introduce any additional considerations. 969 9. Acknowledgements 971 This document has been reviewed and improved by the Weirds working 972 group. The authors especially thank the following individuals who 973 gave their suggestions and contributions to this document: Guangqing 974 Deng, Frederico A C Neves, Ray Bellis, Edward Shryane and Kaveh 975 Ranjbar. 977 10. Normative References 979 [I-D.ietf-weirds-json-response] 980 Newton, A. and S. Hollenbeck, "JSON Responses for the 981 Registration Data Access Protocol (RDAP)", draft-ietf- 982 weirds-json-response-07 (work in progress), April 2014. 984 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 985 Requirement Levels", BCP 14, RFC 2119, March 1997. 987 [RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D., 988 Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra, 989 "Routing Policy Specification Language (RPSL)", RFC 2622, 990 June 1999. 992 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 993 September 2004. 995 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 996 STD 69, RFC 5730, August 2009. 998 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 999 Domain Name Mapping", STD 69, RFC 5731, August 2009. 1001 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1002 Host Mapping", STD 69, RFC 5732, August 2009. 1004 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1005 Contact Mapping", STD 69, RFC 5733, August 2009. 1007 [RFC5890] Klensin, J., "Internationalized Domain Names for 1008 Applications (IDNA): Definitions and Document Framework", 1009 RFC 5890, August 2010. 1011 [Stat-Data-File] 1012 Kong, N., Zhou, L., and G. Deng, "WHOIS Statistics Data 1013 File", July 2012, . 1016 Appendix A. Change Log 1018 Initial -00: Adopted as working group document. 1020 -01: 1022 * Added Change Log section. 1024 * Added RIR data objects. 1026 * Exchanged section 2 and section 3. 1028 -02: 1030 * Modified some object names in the section of RIR Objects 1031 Analysis. 1033 * Added reference extension objects. 1035 -03: 1037 * Updated to the keep-alive version. Changed the expiry dates 1038 and the draft number. 1040 Authors' Addresses 1041 Linlin Zhou 1042 CNNIC 1043 4 South 4th Street, Zhongguancun, Haidian District 1044 Beijing, Beijing 100190 1045 China 1047 Phone: +86 10 5881 2677 1048 Email: zhoulinlin@cnnic.cn 1050 Ning Kong 1051 CNNIC 1052 4 South 4th Street, Zhongguancun, Haidian District 1053 Beijing, Beijing 100190 1054 China 1056 Phone: +86 10 5881 3147 1057 Email: nkong@cnnic.cn 1059 Sean Shen 1060 CNNIC 1061 4 South 4th Street, Zhongguancun, Haidian District 1062 Beijing, Beijing 100190 1063 China 1065 Phone: +86 10 5881 3038 1066 Email: shenshuo@cnnic.cn 1068 Steve Sheng 1069 ICANN 1070 4676 Admiralty Way, Suite 330 1071 Marina del Rey, CA 90292 1072 United States of America 1074 Phone: +1.310.823.9358 1075 Email: steve.sheng@icann.org 1077 Arturo Servin 1078 LACNIC 1079 Rambla Mexico 6125 1080 Montevideo, Montevideo 11400 1081 Uruguay 1083 Phone: +598-2604-2222 1084 Email: aservin@lacnic.net