[RDS-WHOIS2-RT] Scope of RDS-WHOIS2-RT

Mon Jul 3 09:49:40 UTC 2017

Thank you for your thoughts, Alan,

As discussed in our informal meeting, I mostly agree with your 
assessment, however I do feel we should not exclude any issues that have 
arisen since the first review team presented its report or that may have 
been overlooked at the time. This includes the issue of conflicts with 
privacy legislation. While I agree that we should not attempt to solve 
this issue, we do need to look at it and point out the problems that 
exist. If we turned a blind eye to any such issues, we would not have 
done our work properly.

Best,
Volker

Am 26.06.2017 um 23:00 schrieb Alan Greenberg:
> In preparation for the meeting tomorrow, I would like to explain why I 
> feel that we should limit our scope to an in depth review of the first 
> WHOIS-RT recommendations and their implementation. This is 
> specifically called for in section (iv) of the Bylaw governing this 
> review: /The Directory Service Review Team shall assess the extent to 
> which prior Directory Service Review recommendations have been 
> implemented and the extent to which implementation of such 
> recommendations has resulted in the intended effect.
>
> /As the first phase of this, MSSI should, with the support of the 
> appropriate ICANN departments, prepare a full assessment of the 
> WHOIS_RT Recommendations and their implementation, and do so prior to 
> our first formal face-to-face meeting.
>
> Any future replacement for WHOIS is being discussed in the GNSO 
> Next-Generation RDS PDP and is clearly our of scope. Privacy issues 
> with the current WHOIS are clearly an issue, but I do not believe that 
> this RT is the proper place to design any "fix" to meet GDPR issues, n 
> ot would our time-frame meet requirements to act in the next several 
> months.
>
> The GNSO has suggested nine focus areas that we should look at, and I 
> would like to review them here.
>
>> 1. Assess whether the RDS efforts currently underway in the ICANN 
>> community are on target to meet the “legitimate needs of law 
>> enforcement, promoting consumer trust and safeguarding registrant data.”
>
> The prime RDS effort is the GNSO PDP. Given that the PDP is not at a 
> stage to make any recommendations, I do see how we could assess its 
> outcomes. If indeed it is thought to be in trouble, it is the sole 
> responsibility of the GNSO to take action. A RT recommendation to the 
> Board cannot do that.
>
>> 2. Assess the RDS efforts currently underway (or planned in the near 
>> term), for the purpose of making recommendations regarding how they 
>> might be improved and better coordinated.
>
> Again, I do not know what crystal ball we have to do this.
>
>> 3. Ongoing work by the Privacy and Proxy Services Accreditation 
>> Issues Implementation Review Team (see Recommendation 10 of the 2012 
>> WHOIS Review Team Final Report).
>
> To the extent that this is an aspect of a previous WHOIS-RT 
> recommendation, it falls within the purview of the review of the last 
> RT's work
>
>> 4. Progress of cross validation implementation (see Recommendations 6 
>> and 7, 2012 WHOIS Review Team Final Report).
>
> Same here.
>
>> 5. Review compliance enforcement actions, structure and processes 
>> (see Recommendation 4, 2012 WHOIS Review Team Final Report).
>
> Same here.
>
>> 6. Availability of transparent data concerning enforcement of 
>> contractual obligations of WHOIS.
>
> I am not sure exactly what this means, but it may well fall within the 
> reasonable purview of this RT.
>
>> 7. Assess the value and timing of RDAP as a replacement protocol.
>
> Although RDAP, or an evolution of it, is a likely choice for 
> implementing a future RDS, I do not see how we can assess the value of 
> RDAP without having the specific requirements for that RDS. In terms 
> of timing, if the current RDAP ends up being sufficient, timing is not 
> an issue, and if it required enhancement, the timing is not something 
> that we are really equipped to predict.
>
>> 8. To the extent time and bandwidth permit, evaluate the 
>> effectiveness of any other steps ICANN has taken to implement 
>> Recommendations 3-11 of the 2012 WHOIS Review Team Final Report.
>
> Agreed.
>
>> 9. Ensure no duplication of work that is the responsibility of the 
>> GNSO’s RDS Policy Development Process Working Group.
>
> Agreed.
>
> Alan
>
>
> _______________________________________________
> RDS-WHOIS2-RT mailing list
> RDS-WHOIS2-RT at icann.org
> https://mm.icann.org/mailman/listinfo/rds-whois2-rt

-- 
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 at key-systems.net

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 at key-systems.net

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt/attachments/20170703/483c8045/attachment.html>