ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

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

  • To: Marika Konings <marika.konings@xxxxxxxxx>, "James M. Bladel" <jbladel@xxxxxxxxxxx>, Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>, Council <council@xxxxxxxxxxxxxx>
  • Subject: RE: [council] Registration Data Access Protocol (RDAP) Operational Profile for gTLD Registries and Registrars
  • From: "Austin, Donna" <Donna.Austin@xxxxxxxxxxx>
  • Date: Tue, 12 Jan 2016 18:29:23 +0000
  • Accept-language: en-US
  • In-reply-to: <D2BAEC42.599A1%marika.konings@icann.org>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <568FE2DD.2060003@key-systems.net> <D2B67422.A5805%jbladel@godaddy.com> <D2BAEC42.599A1%marika.konings@icann.org>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: AQHRSjHMq4QZC+ZYVUKeIha1FtKGTp7zlH4AgATcrQD//8aA0A==
  • Thread-topic: [council] Registration Data Access Protocol (RDAP) Operational Profile for gTLD Registries and Registrars

Marika 

I think this would be helpful. 

At the Dublin meeting I also suggested during the session with Margie, that it 
would be useful to understand how her team was managing the many differing 
WHOIS pieces from a staff perspective. Margie indicated in a follow-up 
conversation with me that she would be willing to host a webinar outlining the 
plan. I think this would be extremely useful if this could happen in the near 
future given the current formation of the RDS PDP WG and the RDAP developments. 

Thanks

Donna

-----Original Message-----
From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx] On 
Behalf Of Marika Konings
Sent: Tuesday, 12 January 2016 8:47 AM
To: James M. Bladel <jbladel@xxxxxxxxxxx>; Volker Greimann 
<vgreimann@xxxxxxxxxxxxxxx>; Council <council@xxxxxxxxxxxxxx>
Subject: Re: [council] Registration Data Access Protocol (RDAP) Operational 
Profile for gTLD Registries and Registrars


James, if helpful we can work with our GDD colleagues to put something together 
in time for the Council meeting in February to facilitate the Council's 
conversations on this topic?

Best regards,

Marika

On 09/01/16 15:32, "owner-council@xxxxxxxxxxxxxx on behalf of James M.
Bladel" <owner-council@xxxxxxxxxxxxxx on behalf of jbladel@xxxxxxxxxxx>
wrote:

>
>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@xxxxxxxxxxxxxx on behalf of Volker 
>Greimann" <owner-council@xxxxxxxxxxxxxx on behalf of 
>vgreimann@xxxxxxxxxxxxxxx> 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@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.
>>
>>
>>
>
>






<<< Chronological Index >>>    <<< Thread Index >>>