Re: [gnso-thickwhoispdp-wg] Two items that may be relevant

[Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>]

Hi Alan,

indeed these have been part of the discussion with ICANN in the RAA 
negotiations, both flowing from requests of the registrars.
The first point is still a bit contentious as ICANN seems very reluctant 
to remove any part of whois obligations, however for us as registrars it 
does not make sense to provide this data if it is not referred to by the 
registry and the duplication of the service may lead to inconsistencies 
in the results displayed. If the whois data is displayed by the 
registry, and therefore the registry no longer points to the whois 
server of the registrar, that server becomes redundant. To say it 
differently: While we currently operate whois servers for the domains we 
have in thick TLDs, the number of queries we get for those are negligible.
Of the two proposals, 2. is as good as a done deal because poth parties 
agree that a "uniform whois" is a good idea. There are still differences 
about the exact language, but basic agreement is there.
This is the current language of the relevant section of the new Whois 
Specification:
_Following the publication by the IETF of a Proposed Standard, Draft 
Standard or Internet Standard and any revisions thereto (as specified in 
RFC 2026) relating to_the web-based _directory service _as specified in 
the IETF _Web _Extensible Internet Registration Data Service working 
group_, Registrar shall implement the directory service specified in any 
such standard (or any revision thereto)_no later than 135 days after 
_such implementation is requested by ICANN_. Registrar shall implement 
internationalized registration data publication guidelines according to 
the specification published by ICANN following the work of the ICANN 
Internationalized Registration Data Working Group (IRD-WG) and its 
subsequent efforts, no later than 135 days after it is approved by the 
ICANN Board.
1.1. The format of responses shall follow a semi-free text format 
outline below, followed by a blank line and a legal disclaimer 
specifying the rights of Registrar, and of the user querying the database.
1.2. Each data object shall be represented as a set of key/value pairs, 
with lines beginning with keys, followed by a colon and a space as 
delimiters, followed by the value.
1.3. For fields where more than one value exists, multiple key/value 
pairs with the same key shall be allowed (for example to list multiple 
name servers). The first key/value pair after a blank line should be 
considered the start of a new record, and should be considered as 
identifying that record, and is used to group data, such as hostnames 
and IP addresses, or a domain name and registrant information, together.
1.4. *Domain Name Data:*

1.4.1. *Query format: *whois --h whois.example-registrar.tld EXAMPLE.TLD

1.4.2. *Response format**:*

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@xxxxxxxxxxxxx

Registrar Abuse Contact Phone: +1.1235551234

Reseller: EXAMPLE RESELLER [/*Note: Pending discussion with registrars. 
Inserted based on request from Law Enforcement]*/
Domain Status: clientDeleteProhibited

Domain Status: clientRenewProhibited

Domain Status: clientTransferProhibited

Registry Registrant ID: 5372808-ERL

Registrant Name: EXAMPLE REGISTRANT

Registrant Organization: EXAMPLE ORGANIZATION

Registrant Street: 123 EXAMPLE STREET

Registrant City: ANYTOWN

Registrant State/Province: AP

Registrant Postal Code: A1A1A1

Registrant Country: AA

Registrant Phone: +1.5555551212

Registrant Phone Ext: 1234

Registrant Fax: +1.5555551213

Registrant Fax Ext: 4321

Registrant Email: EMAIL@xxxxxxxxxxx

Registry Admin ID: 5372809-ERL

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@xxxxxxxxxxx

Registry Tech ID: 5372811-ERL

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@xxxxxxxxxxx

Name Server: NS01.EXAMPLE-REGISTRAR.TLD

Name Server: NS02.EXAMPLE-REGISTRAR.TLD

DNSSEC: signedDelegation

URL of the ICANN WHOIS Data Problem Reporting System: 
http://wdprs.internic.net/[/*Note: this item is in response to a 
drafting team request]*/
>>> Last update of WHOIS database: 2009-05-29T20:15:00Z <<<

1.5. The format of the following data fields: domain status, individual 
and organizational names, address, street, city, state/province, postal 
code, country, telephone and fax numbers, email addresses, date and 
times must conform to the mappings specified in EPP RFCs 5730-5734 (or 
its successors), and IPv6 addresses format should conform to RFC 5952 
(or its successor), so that the display of this information (or values 
returned in WHOIS responses) can be uniformly processed and understood.

> There are two issues that I understand may be under discussion in the 
> RAA amendment process that might have an impact on this PDP.
> 1. The September RAA Negotiation update (*http://tinyurl.com/Sept-RAA* 
> <http://tinyurl.com/Sept-RAA>) includes (Item 11) "The registrars have 
> requested that the obligation to provide a registrar-­-operator Whois 
> service be limited to "thin" registries (i.e., .com and .net), as 
> "thick" registries provide centralized public data to Whois data. 
> Registries in the New gTLD Program are required to be "thick" and 
> follow service level agreements." The status says that there is 
> agreement in principle. If that is a done-deal, they we can take that 
> question off of our list.
> 2. There has been discussion of ICANN requiring a uniform presentation 
> of Whois information by all registrars 
> (*http://tinyurl.com/Whois-display* 
> <http://tinyurl.com/Whois-display>). I don't see this in the list of 
> RAA topics, so I am not sure of the status. If this too is a 
> done-deal, then uniformity of display no longer needs to be on our 
> list. (Thanks to Michele Neylon for the heads up on this).
> Perhaps Volker can update us on both of these.
>
> Alan 

--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.

Mit freundlichen Grüßen,

Volker A. Greimann
- Rechtsabteilung -

Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann@xxxxxxxxxxxxxxx

Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com

Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
www.facebook.com/KeySystems
www.twitter.com/key_systems

Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534

Member of the KEYDRIVE GROUP
www.keydrive.lu

Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen 
Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder 
Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht 
nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder 
telefonisch in Verbindung zu setzen.

--------------------------------------------

Should you have any further questions, please do not hesitate to contact us.

Best regards,

Volker A. Greimann
- legal department -

Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann@xxxxxxxxxxxxxxx

Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com

Follow us on Twitter or join our fan community on Facebook and stay updated:
www.facebook.com/KeySystems
www.twitter.com/key_systems

CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534

Member of the KEYDRIVE GROUP
www.keydrive.lu

This e-mail and its attachments is intended only for the person to whom it is 
addressed. Furthermore it is not permitted to publish any content of this 
email. You must not use, disclose, copy, print or rely on this e-mail. If an 
addressing or transmission error has misdirected this e-mail, kindly notify the 
author by replying to this e-mail or contacting us by telephone.