Steve Had a chat with chuck and we will try to have a chat soon on those. One point raised is that the original description was too broad and was not clear for all. One of the clear recommendations were to rethink rework and come back. Also if we needed to break the document in two or three. I certainly remember the minutes of the day when we explained. But am sure when we have a chat today we should be able to clear the air on these. Kris

On 30 Oct 2017, at 16:15, Metalitz, Steven <met@msk.com> wrote:

Thanks Kris but I am not sure what I am looking at here, especially the first page. It seems to go well beyond what I thought the subteam 5 task was (see below from Chuck 10/16 e-mail). Or has the task now been expanded to include recommendations re e.g. RSEP?

i. List and briefly describe tasks commonly involved in carrying out this purpose. ii. Describe the parties who often access gTLD registration data in pursuit of Regulatory or Contractual Enforcement purposes iii. List gTLD registration data often involved in this purpose. iv. Describe the purpose succinctly in one paragraph

<image001.gif> Steven J. Metalitz | Partner, through his professional corporation T: 202.355.7902 | met@msk.com Mitchell Silberberg & Knupp LLP | 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: gnso-rds-pdp-5-bounces@icann.org [mailto:gnso-rds-pdp-5-bounces@icann.org] On Behalf Of Kris Seeburn Sent: Monday, October 30, 2017 5:02 AM To: GNSO-RDS-pdp-5@icann.org Subject: [Gnso-rds-pdp-5] redrafted document

Just sending in case you guys did not receive this document.

Kris Seeburn seeburn.k@gmail.com www.linkedin.com/in/kseeburn/

<image002.gif>

Yes of course we need to agree what we incorporate or not as a team. I just laid the stuff that i felt were potential considerations. Thats the only thing i did. We are a team and we need to work through together. Am sure we will surely find the right middle ground and more clearer document with less ambiguities. So we should talk and agree. It’s just my initial input. So no worries steve.I am opened and williing t work this out so we can move forward. Kris

On Oct 30, 2017, at 17:31, Metalitz, Steven <met@msk.com> wrote:

Breaking into two I understand and could support but this draft goes well beyond that.

Sent with Good (www.good.com <http://www.good.com/>)

-----Original Message----- From: Kris Seeburn [seeburn.k@gmail.com <mailto:seeburn.k@gmail.com>] Sent: Monday, October 30, 2017 06:22 AM Pacific Standard Time To: Metalitz, Steven Cc: GNSO-RDS-pdp-5@icann.org <mailto:GNSO-RDS-pdp-5@icann.org> Subject: Re: [Gnso-rds-pdp-5] redrafted document

Steve

Had a chat with chuck and we will try to have a chat soon on those.

One point raised is that the original description was too broad and was not clear for all. One of the clear recommendations were to rethink rework and come back. Also if we needed to break the document in two or three. I certainly remember the minutes of the day when we explained. But am sure when we have a chat today we should be able to clear the air on these.

Kris

On 30 Oct 2017, at 16:15, Metalitz, Steven <met@msk.com <mailto:met@msk.com>> wrote:

...

Thanks Kris but I am not sure what I am looking at here, especially the first page. It seems to go well beyond what I thought the subteam 5 task was (see below from Chuck 10/16 e-mail). Or has the task now been expanded to include recommendations re e.g. RSEP?

i. List and briefly describe tasks commonly involved in carrying out this purpose. ii. Describe the parties who often access gTLD registration data in pursuit of Regulatory or Contractual Enforcement purposes <> iii. List gTLD registration data often involved in this purpose. iv. Describe the purpose succinctly in one paragraph

<image001.gif> Steven J. Metalitz |Partner, through his professional corporation T: 202.355.7902 |met@msk.com <mailto:met@msk.com> Mitchell Silberberg & KnuppLLP|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: gnso-rds-pdp-5-bounces@icann.org <mailto:gnso-rds-pdp-5-bounces@icann.org> [mailto:gnso-rds-pdp-5-bounces@icann.org <mailto:gnso-rds-pdp-5-bounces@icann.org>] On Behalf Of Kris Seeburn Sent: Monday, October 30, 2017 5:02 AM To: GNSO-RDS-pdp-5@icann.org <mailto:GNSO-RDS-pdp-5@icann.org> Subject: [Gnso-rds-pdp-5] redrafted document

Just sending in case you guys did not receive this document.

Kris Seeburn seeburn.k@gmail.com <mailto:seeburn.k@gmail.com> <>www.linkedin.com/in/kseeburn/ <http://www.linkedin.com/in/kseeburn/>

<image002.gif>

Kris Seeburn seeburn.k@gmail.com www.linkedin.com/in/kseeburn/ <http://www.linkedin.com/in/kseeburn/>