[council] Registration Data Access Protocol (RDAP) Operational Profile for gTLD Registries and Registrars

James M. Bladel jbladel at godaddy.com
Sat Jan 9 14:32:14 UTC 2016


Speaking as a Registrar - I agree with Volker.

The protocol development is getting ahead of the policy work, and I am
similarly concerned that RDAP will either (a) tie the hands of the RDS
working group, or (b) become a short-lived interim approach that is
discarded if/when RDS is adopted.  This isn¹t a comment on the substance
of RDAP, but rather a recognitions that it is touching on the same work as
the RDS group is just getting underway.

Would it be valuable to ask GNSO Policy Staff to work with their
counterparts on the RDAP group, and flag those areas of the protocol that
have policy implications, and report back to the GNSO?


Thanks‹


J.






On 1/8/16, 10:25 , "owner-council at gnso.icann.org on behalf of Volker
Greimann" <owner-council at gnso.icann.org on behalf of
vgreimann at key-Systems.net> wrote:

>
>Dear all,
>
>ICANN recently launched a Public Comment on the above. This proposal as
>it stands is not merely a technical protocal, but appears to have
>significant policy implicantions that I feel need to be approved by the
>GNSO prior to adoption and implementation.
>
>I would therefore propose that the council comments and firmly
>establishes its intent to review the policy implications with a view of
>initiating policy work to either confirm or reject the policy aspects of
>this proposal.
>
>I also worry that this proposal is somewhat superfluous with regard to
>the already ongoing implementation work for thick whois and the upcoming
>policy work on the RDS, which would replace all of this. Bearing in mind
>the costs of implementation, we would be well advised to avoid work that
>is potentially overridden in short order.
>
>Potentially, the council might therefore also request that the
>implementation work on RDAP be halted until the RDS work is completed.
>
>-- 
>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.
>
>
>





More information about the council mailing list