I think this proposal is shooting at sparrows with cannons, in other words: it makes too much out of a small thing, it ôverengineers a simple issue. Labeling as such means nothing more that ensuring that when looking at the whois it has to visible that the domain is under privacy. In most cases, this is achieved by saying so in the registrant name sections. Lets try to keep this lightweight without having to send this to our tech teams to achieve something that is already achievable in the current whois. The fields also seem to be over-specific as the WG never specified any information beyond the fact that a privacy service is used to be included in the whois. Best, Volker Am 13.02.2017 um 17:29 schrieb theo geurts:
+1 Steve That would be good to know.
Though the proposal is very good in the sense that it becomes very clear WHOIS output wise, I am not sure however how that would work with third party service providers in obtaining that information.
Something for tomorrow :)
On a side note, I did not receive this email, until Steve replied to it.
Theo
On 13-2-2017 16:44, Metalitz, Steven wrote:
Amy, did the staff consider alternatives that would not involve any additional new fields -- for instance requiring certain words or characters in entries in existing fields? This would build upon the status quo in which a fairly reliable indication can be gleaned from the Whois record as to whether a proxy/privacy registration is involved.
Steve Metalitz
*On behalf of Coalition for Online Accountability (COA) | www.onlineaccountability.net*
**
*image001*
*Steven J. Metalitz *|***Partner, through his professional corporation*
T: +1.202.355.7902 |met@msk.com <mailto:met@msk.com>**
*Mitchell Silberberg & Knupp**LLP*|*www.msk.com <http://www.msk.com/>*
1818 N Street NW, 8th Floor, Washington, DC 20036
*_THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED ONLY FOR THE PERSONAL AND CONFIDENTIAL USE OF THE DESIGNATED RECIPIENTS._**THIS MESSAGE MAY BE AN ATTORNEY-CLIENT COMMUNICATION, AND AS SUCH IS PRIVILEGED AND CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS NOT AN INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REVIEW, USE, DISSEMINATION, FORWARDING OR COPYING OF THIS MESSAGE IS STRICTLY PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY REPLY E-MAIL OR TELEPHONE, AND DELETE THE ORIGINAL MESSAGE AND ALL ATTACHMENTS FROM YOUR SYSTEM. THANK YOU.*
*From:*gdd-gnso-ppsai-impl-bounces@icann.org [mailto:gdd-gnso-ppsai-impl-bounces@icann.org] *On Behalf Of *Amy Bivins *Sent:* Friday, February 10, 2017 12:27 PM *To:* gdd-gnso-ppsai-impl@icann.org *Subject:* [Gdd-gnso-ppsai-impl] Privacy/Proxy RDDS labeling document attached for 14 Feb IRT call
Hello, All,
Attached is an initial discussion proposal for Tuesday’s IRT call, exploring how we could potentially implement the Final Report’s recommendation that, “To the extent that this is feasible, domain name registrations involving P/P service providers should be clearly labelled as such in WHOIS.” (See Final Report, p. 9)
To summarize, we have explored several possible alternatives for implementing this recommendation. The attached proposes to add four new fields, but also identifies the other possible alternatives that were considered.
We are seeking your feedback on any and all elements of this proposal, including (1) the specific fields to be added; (2) the location(s) of the new fields; and (3) ensuring that this can be implemented from an operational perspective (particularly if/when a provider is not affiliated with the registrar). Once we have discussed the new fields and the preferred locations for these fields, we will ensure the final product is consistent with the new CL&D requirements.
On Tuesday, I’ll run through the proposal briefly and also note the other alternatives that were considered but not included here. The rest of the call will be dedicated to your discussion and feedback on this. Please share any preliminary feedback on the list and I look forward to talking with you on Tuesday.
Best, Amy
*Amy E. Bivins*
Registrar Policy Services Manager
Registrar Services and Industry Relations
Internet Corporation for Assigned Names and Numbers (ICANN)
Direct: +1 (202) 249-7551
Fax: +1 (202) 789-0104
Email: amy.bivins@icann.org <mailto:amy.bivins@icann.org>
www.icann.org <http://www.icann.org>
_______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl
_______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl
-- 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@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@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.
