[gnso-rds-pdp-wg] 2013 RAA Data Elements

Greg Aaron gca at icginc.com
Tue Jun 13 21:19:31 UTC 2017


All:

There are five additional fields in thin output below that are not in red, that I think can be included without controversy.  None involve personally identifiable information, and all have legitimate purposes for being published publicly. They are:

  *   Registry Domain ID
  *   Registrar Abuse Contact Email
  *   Registrar Abuse Contact Phone
  *   Reseller
  *   URL of the ICANN WHOIS Data Problem Reporting System

In addition, a recent  ICANN Consensus Policy requires that registrars and registries to provide info about EPP status codes in output, specifically for the information of registrants.  See: https://www.icann.org/resources/pages/policy-awip-2014-07-02-en     This should be included in our "minimum public data set" also.

A bit of explanation of what those fields are:

Registry Domain ID: this is a unique identifier and is useful for differentiating different "lifetimes" of a domain.  For example: someone registers domain1.tld; that domain gets an ID.  A year later the domain expires and is not renewed.  Some time later someone else registers domain1.tld again; this time it will receive a different ID.  Each of those "lifetimes" will have different Domain IDs.  The ID can be used for tracking ownership, billing reference, etc.

Registrar Abuse Contact Email and Registrar Abuse Contact Phone: these were added so people can easily contact the registrar if the domain is being used for malicious purposes.  Among other things, this information is: a) a helpful way to help protect the public and make the Internet safer, and b) useful when the registrar's web site is in a language different from the one you speak.

Reseller: the registrar populates this field if it wants to and it is applicable.  (The field itself is mandatory to display, but filling it is optional, and is it sometimes left blank.)  Purpose: Business Domain Name Purchase/Sale, domain maintenance.  The reseller is usually responsible for providing customer service to the  registered name holder (not the registrar); the reseller is the place to go for account info and login to manage the domain.  Some registrars like to populate this field in WHOIS so registrants and other inquiries are directed to the right party.

URL of the ICANN WHOIS Data Problem Reporting System: provided as a way to encourage data accuracy.

All best,
--Greg


From: gnso-rds-pdp-wg-bounces at icann.org [mailto:gnso-rds-pdp-wg-bounces at icann.org] On Behalf Of Lisa Phifer
Sent: Tuesday, June 13, 2017 2:12 PM
To: RDS PDP WG <gnso-rds-pdp-wg at icann.org>
Subject: [gnso-rds-pdp-wg] 2013 RAA Data Elements

All,

Per the action item given to staff in today's WG call -

>From the RAA WHOIS requirements for Registrants<https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#whois> (2013), below appears a list of gTLD registration data elements.

Data elements highlighted in red are included in what the RDS PDP WG has now agreed to refer to as the "minimum public data set" - the list of fields that will always be public no matter the gTLD.

As discussed during today's WG call, when WG deliberation proceeds beyond the minimum public data set, the WG will deliberation on all of the additional data elements not highlighted in red below.


Section 1.4 of the 2013 RAA

1.4. Domain Name Data:
1.4.1. Query format: whois -h whois.example-registrar.tld EXAMPLE.TLD
1.4.2. Response format:
The format of responses shall contain all the elements and follow a semi-free text format outline below. Additional data elements can be added at the end of the text format outlined below. The data element may, at the option of Registrar, be followed by a blank line and a legal disclaimer specifying the rights of Registrar, and of the user querying the database (provided that any such legal disclaimer must be preceded by such blank line).
Domain Name: EXAMPLE.TLD
Registry Domain ID: D1234567-TLD
Registrar WHOIS Server: whois.example-registrar.tld
Registrar URL: http://www.example-registrar.tld
Updated Date: 2009-05-29T20:13:00Z
Creation Date: 2000-10-08T00:45:00Z
Registrar Registration Expiration Date: 2010-10-08T00:44:59Z
Registrar: EXAMPLE REGISTRAR LLC
Registrar IANA ID: 5555555
Registrar Abuse Contact Email: email at registrar.tld<mailto:email at registrar.tld>
Registrar Abuse Contact Phone: +1.1235551234
Reseller: EXAMPLE RESELLER1
Domain Status: clientDeleteProhibited2
Domain Status: clientRenewProhibited
Domain Status: clientTransferProhibited
Registry Registrant ID: 5372808-ERL3
Registrant Name: EXAMPLE REGISTRANT4
Registrant Organization: EXAMPLE ORGANIZATION
Registrant Street: 123 EXAMPLE STREET
Registrant City: ANYTOWN
Registrant State/Province: AP5
Registrant Postal Code: A1A1A16
Registrant Country: AA
Registrant Phone: +1.5555551212
Registrant Phone Ext: 12347
Registrant Fax: +1.5555551213
Registrant Fax Ext: 4321
Registrant Email: EMAIL at EXAMPLE.TLD<mailto:EMAIL at EXAMPLE.TLD>
Registry Admin ID: 5372809-ERL8
Admin Name: EXAMPLE REGISTRANT ADMINISTRATIVE
Admin Organization: EXAMPLE REGISTRANT ORGANIZATION
Admin Street: 123 EXAMPLE STREET
Admin City: ANYTOWN
Admin State/Province: AP
Admin Postal Code: A1A1A1
Admin Country: AA
Admin Phone: +1.5555551212
Admin Phone Ext: 1234
Admin Fax: +1.5555551213
Admin Fax Ext: 1234
Admin Email: EMAIL at EXAMPLE.TLD<mailto:EMAIL at EXAMPLE.TLD>
Registry Tech ID: 5372811-ERL9
Tech Name: EXAMPLE REGISTRANT TECHNICAL
Tech Organization: EXAMPLE REGISTRANT LLC
Tech Street: 123 EXAMPLE STREET
Tech City: ANYTOWN
Tech State/Province: AP
Tech Postal Code: A1A1A1
Tech Country: AA
Tech Phone: +1.1235551234
Tech Phone Ext: 1234
Tech Fax: +1.5555551213
Tech Fax Ext: 93
Tech Email: EMAIL at EXAMPLE.TLD<mailto:EMAIL at EXAMPLE.TLD>
Name Server: NS01.EXAMPLE-REGISTRAR.TLD10
Name Server: NS02.EXAMPLE-REGISTRAR.TLD
DNSSEC: signedDelegation
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2009-05-29T20:15:00Z <<<
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20170613/00b1850a/attachment-0001.html>


More information about the gnso-rds-pdp-wg mailing list