1. New version looks good to me, I agree with sending the letter.
2. I have refrained from expressing my views on what I perceive to be rather serious privacy implications of this transfer policy. However, if I am correct in my understanding of the Privacy risks described, this is a serious abrogation of privacy rights. Proxy services have been recognized as a partial, reasonably priced solution to the whois disclosure problem, in the absence of enforcement of privacy law. However, revealing the registrant's identity during the transfer displays a rather cynical disregard or the registrant's privacy rights and expectations, which undermines confidence iný ICANN's policy and procedures for proxy services.  It would be a pity if this were to happen.
Stephanie Perrin
Sent from my BlackBerry 10 smartphone on the Bell network.
From: Darcy Southwell
Sent: Tuesday, November 29, 2016 9:49 PM
To: council@gnso.icann.org
Cc: Susan Kawaguchi; Phil Corwin; Anthony Harris
Subject: Re: [council] RE: [council] Motion – GNSO Council Communication to ICANN Board Regarding Transfer Policy

All,

 

I appreciate the support for James’ suggestion. 

 

Based on concerns expressed by some, I’ve revised the last two paragraphs of the letter slightly (they are redlined so you can easily see the changes) and offer this friendly amendment (so to speak) to the draft letter that goes with this motion.  For those of you who already expressed support for James’ suggestion and the prior draft, is this new draft still agreeable to you?  I believe this new draft captures the same spirit, but opens up the possibility of solutions to what could end up being something more appropriate than the PPSAI IRT.

 

Please let me know if you have questions.  I’m happy to answer.

 

Best,

Darcy

 

From: Anthony Harris <anthonyrharris@gmail.com>
Date: Tuesday, November 29, 2016 at 5:10 PM
To: Phil Corwin <psc@vlaw-dc.com>
Cc: Susan Kawaguchi <susank@fb.com>, Darcy Southwell <darcy.southwell@endurance.com>, "council@gnso.icann.org" <council@gnso.icann.org>
Subject: Re: [council] RE: [council] Motion – GNSO Council Communication to ICANN Board Regarding Transfer Policy

 

I also agree with the letter being sent to the Board

 

Tony

 

On Mon, Nov 28, 2016 at 9:09 PM, Phil Corwin <psc@vlaw-dc.com> wrote:

Concurring with my BC colleague.

 

Philip S. Corwin, Founding Principal

Virtualaw LLC

1155 F Street, NW

Suite 1050

Washington, DC 20004

202-559-8597/Direct

202-559-8750/Fax

202-255-6172/Cell

 

Twitter: @VlawDC

 

"Luck is the residue of design" -- Branch Rickey

 

From: owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Susan Kawaguchi
Sent: Monday, November 28, 2016 6:11 PM
To: Darcy Southwell; council@gnso.icann.org
Subject: [council] Re: [council] Motion – GNSO Council Communication to ICANN Board Regarding Transfer Policy

 

Hello,

 

I agree with the letter being sent to the Board instead of a formal motion.

 

 

 

Susan Kawaguchi

Domain Name Manager

Facebook, Inc.

Legal Dept.

 

1601 Willow Road

Menlo Park, CA 94025

 

 

From: <owner-council@gnso.icann.org> on behalf of Darcy Southwell <darcy.southwell@endurance.com>
Date: Sunday, November 20, 2016 at 3:41 PM
To: "council@gnso.icann.org" <council@gnso.icann.org>
Subject: [council] Motion – GNSO Council Communication to ICANN Board Regarding Transfer Policy

 

All,

 

Attached is the Motion – GNSO Council Communication to ICANN Board Regarding Transfer Policy along with a proposed draft communication.  You will recall from our meetings in Hyderabad that ICANN GDD staff advised us that Council would need to submit this issue to the Board for consideration and further direction to ICANN staff.  This motion and the draft communication were prepared based on that advice, and I’d appreciate this being heard at our December 1 meeting.

 

Best,

Darcy

__________

Darcy Southwell | Compliance Officer

M: +1 503-453-7305 │ Skype: darcy.enyeart

tps://ci5.googleusercontent.com/proxy/tjCmzaF_7ZGN1PtB2KAV5OVQn-Q_Xvh_p3zhRf5gB5-ISEZOkC_6lvGj1xU-T1CFq

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7859 / Virus Database: 4664/13314 - Release Date: 10/30/16
Internal Virus Database is out of date.