RE: [gnso-thickwhoispdp-wg] FW: Synchronization

[Carolyn Hoover <choover@xxxxxxxxxxxx>]

As a small registry which handles these issues directly, I agree with the 
issues that Volker presents.  I think his suggestion on the port 43 requirement 
is a good solution for dealing with the Synchronization issue.  dotCoop tries 
to maintain data and communicate effectively with registrars on issues 
concerning data differences but sometimes it is very difficult for items that 
require manual intervention to ensure that data is properly updated. Since what 
is on the registry drives what is used for transfers, Certificate information, 
etc., I believe that the registry information has to be considered what is 
authoritative and it is important to present a possible solution to address 
inconsistent information being available between registries and registrars.

Luckily we have not had any court-ordered changes so I can't comment directly 
on that.

Regards,

Carolyn

From: owner-gnso-thickwhoispdp-wg@xxxxxxxxx 
[mailto:owner-gnso-thickwhoispdp-wg@xxxxxxxxx] On Behalf Of Volker Greimann
Sent: Wednesday, March 20, 2013 8:51 AM
To: Marika Konings
Cc: gnso-thickwhoispdp-wg@xxxxxxxxx
Subject: Re: [gnso-thickwhoispdp-wg] FW: Synchronization

Hi Marika, hi Susan,

a few comments on the template:

The answers contained do not take into account the insynchronicities which may 
arise by modifications to the registry records by the registry without 
registrar submission, as may be required by a court order, or even worse, a 
closed court order.

In thin registries, in cases of a domain name being transferred without the 
losing registrars knowledge, this may lead to the registrar outputting outdated 
whois data for a domain name no longer under his control. Effectively, one 
domain name could have two or more registrars outputting wildly different data 
for the same domain name, and while the registry will reference the correct 
registrar, depending on where a third party performs his lookup, his results 
may differ.

In thick registries, this may lead to inconsistencies between the registrar 
whois and the registry whois may arise as such modifications are not 
necessarily transmitted to the registrar. Effectively, registries and 
registrars could conceivably output wildly different whois data. This would 
however be easily fixed by removing the port 43 whois requirement for 
registrars in thick registries. While the registrar would still have and escrow 
that data, the synchonization issue would be removed.

I am noting this because it is an actual problem (though easily fixed when 
noticed) where we had cases in thick and thin registries where changes occured 
at a registry level where we as registrar were either not informed at all, 
informed in a non-automated and not-documented manner (email) or informed 
incompletely ("... certain actions were taken with respect to the domain name 
xyz.xyz.").

Best,

Volker




From: Susan kawaguchi <skawaguchi@xxxxxx<mailto:skawaguchi@xxxxxx>>
Date: Mon, 18 Mar 2013 18:16:23 -0700
To: 
<owner-gnso-thickwhoispdp-wg@xxxxxxxxx<mailto:owner-gnso-thickwhoispdp-wg@xxxxxxxxx>>
Subject: Synchronization

Please see the attached template on Synchronization.

Susan Kawaguchi
Domain Name Manager
Facebook Legal Dept.

Phone - 650 485-6064




--

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<mailto:vgreimann@xxxxxxxxxxxxxxx>



Web: www.key-systems.net<http://www.key-systems.net> / 
www.RRPproxy.net<http://www.RRPproxy.net>

www.domaindiscount24.com<http://www.domaindiscount24.com> / 
www.BrandShelter.com<http://www.BrandShelter.com>



Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:

www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>

www.twitter.com/key_systems<http://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<http://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<mailto:vgreimann@xxxxxxxxxxxxxxx>



Web: www.key-systems.net<http://www.key-systems.net> / 
www.RRPproxy.net<http://www.RRPproxy.net>

www.domaindiscount24.com<http://www.domaindiscount24.com> / 
www.BrandShelter.com<http://www.BrandShelter.com>



Follow us on Twitter or join our fan community on Facebook and stay updated:

www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>

www.twitter.com/key_systems<http://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<http://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.