<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Ultimately, not even the data _we_have in our database is always
correct. Domains are sold all the time without the acquirer
bothering to update the whois records. Or people register domain
names for the companies they work for in their own name as they
just do not know any better. I could go on and on. <br>
</p>
<p>Ultimately, the person in the whois may not be the legal title
holder for any number of cases. We usually treat him as such, but
as the whois is a private not a public (as in government
sponsored) register, it carries no legally authoritative (sorry
for using that word here, but it fits in this case) power like a
trade register or a land register does.</p>
<p>Best,</p>
<p>Volker<br>
</p>
<br>
<div class="moz-cite-prefix">Am 17.05.2017 um 19:02 schrieb Chris
Pelling:<br>
</div>
<blockquote
cite="mid:129836616.253596.1495040576444.JavaMail.zimbra@netearth.net"
type="cite">
<div style="font-family: Arial; font-size: 12pt; color: #000000">
<div>Paul,</div>
<div><br data-mce-bogus="1">
</div>
<div>I totally disagree with you with regards "whats the problem
with harvesting" - just the other day as an example we ended
up spending an hour telling a registrant that information held
by domaintools is not correct - just because they say it is.
Even providing a whois from the registry to the registrant
was not proof enough.</div>
<div><br data-mce-bogus="1">
</div>
<div>There is no point debating that though as we will simply
disagree.</div>
<div><br>
</div>
<div data-marker="__SIG_PRE__">Kind regards,<br>
<br>
Chris</div>
<br>
<hr id="zwchr" data-marker="__DIVIDER__">
<div data-marker="__HEADERS__"><b>From: </b>"Paul Keating"
<a class="moz-txt-link-rfc2396E" href="mailto:Paul@law.es"><Paul@law.es></a><br>
<b>To: </b>"Greg Shatan" <a class="moz-txt-link-rfc2396E" href="mailto:gregshatanipc@gmail.com"><gregshatanipc@gmail.com></a>,
"Volker Greimann" <a class="moz-txt-link-rfc2396E" href="mailto:vgreimann@key-systems.net"><vgreimann@key-systems.net></a><br>
<b>Cc: </b>"gnso-rds-pdp-wg"
<a class="moz-txt-link-rfc2396E" href="mailto:gnso-rds-pdp-wg@icann.org"><gnso-rds-pdp-wg@icann.org></a><br>
<b>Sent: </b>Wednesday, 17 May, 2017 17:13:55<br>
<b>Subject: </b>Re: [gnso-rds-pdp-wg] IMPROTANT - Action
Items and Notes from Next-Generation RDS PDP Working Group
Call - 17 May 2017<br>
</div>
<br>
<div data-marker="__QUOTED_TEXT__">
<div>What is the problem with harvesting?</div>
<br>
<div>This is public data. There is no Intellectual Property
right in the data itself.</div>
<br>
<div>Asking for ME.</div>
<br>
<div>Paul</div>
<br>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family: Calibri; font-size: 11pt;
text-align: left; color: black; border-bottom: medium
none; border-left: medium none; border-top: #b5c4df 1pt
solid; border-right: medium none; padding: 3pt 0in 0in
0in;" data-mce-style="font-family: Calibri; font-size:
11pt; text-align: left; color: black; border-bottom:
medium none; border-left: medium none; border-top: #b5c4df
1pt solid; border-right: medium none; padding: 3pt 0in 0in
0in;"><span style="font-weight: bold;"
data-mce-style="font-weight: bold;">From: </span> <<a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>>
on behalf of Greg Shatan <<a moz-do-not-send="true"
href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>><br>
<span style="font-weight: bold;"
data-mce-style="font-weight: bold;">Date: </span>
Wednesday, May 17, 2017 at 6:02 PM<br>
<span style="font-weight: bold;"
data-mce-style="font-weight: bold;">To: </span> Volker
Greimann <<a moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>><br>
<span style="font-weight: bold;"
data-mce-style="font-weight: bold;">Cc: </span> RDS PDP
WG <<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>><br>
<span style="font-weight: bold;"
data-mce-style="font-weight: bold;">Subject: </span>
Re: [gnso-rds-pdp-wg] IMPROTANT - Action Items and Notes
from Next-Generation RDS PDP Working Group Call - 17 May
2017<br>
</div>
<br>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
style="border-left: #b5c4df 5 solid; padding: 0 0 0 5;
margin: 0 0 0 5;" data-mce-style="border-left: #b5c4df 5
solid; padding: 0 0 0 5; margin: 0 0 0 5;">
<div dir="ltr">
<div class="gmail_default" style="font-family:
verdana,sans-serif;" data-mce-style="font-family:
verdana,sans-serif;">Why do we want to prevent
harvesting? Asking for a friend.</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>
<p style="text-indent: 0in;"
data-mce-style="text-indent: 0in;"><span style="font-size: 12.8px;"
data-mce-style="font-size:
12.8px;"><a
moz-do-not-send="true"
name="UNIQUE_ID_SafeHtmlFilter_UNIQUE_ID_SafeHtmlFilter_UNIQUE_ID_SafeHtmlFilter__GoBack"></a></span><b
style="font-size:
12.8px;"
data-mce-style="font-size:
12.8px;"><span
style="font-size:
10pt; font-family:
Arial, sans-serif;
color: #002e62;"
data-mce-style="font-size:
10pt; font-family:
Arial, sans-serif;
color: #002e62;">Greg
Shatan<br>
</span></b><span
style="font-size: 10pt;
font-family:
Arial,sans-serif; color:
black;"
data-mce-style="font-size:
10pt; font-family:
Arial,sans-serif; color:
black;">C: 917-816-6428<br>
S: gsshatan</span><span
color="#000000"
face="Arial,sans-serif"
data-mce-style="color:
#000000; font-family:
Arial, sans-serif;"
style="color: #000000;
font-family: Arial,
sans-serif;"><span
style="font-size:
13.3333px;"
data-mce-style="font-size:
13.3333px;"><br>
</span></span><a
moz-do-not-send="true"
href="mailto:gregshatanipc@gmail.com"
style="font-family:
Arial,sans-serif;
font-size: 10pt;
text-indent: 0in;"
target="_blank"
data-mce-style="font-family:
Arial,sans-serif;
font-size: 10pt;
text-indent: 0in;"><span
style="color:
#1155cc;"
data-mce-style="color:
#1155cc;">gregshatanipc@gmail.com</span></a></p>
<p style="font-size: 12.8px;
text-indent: 0in;"
data-mce-style="font-size:
12.8px; text-indent: 0in;"><span
style="font-size: 10pt;
font-family: Arial,
sans-serif;"
data-mce-style="font-size:
10pt; font-family:
Arial, sans-serif;"></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Wed, May 17, 2017 at 11:58
AM, Volker Greimann <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
target="_blank">vgreimann@key-systems.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0 0 0
.8ex; border-left: 1px #ccc solid; padding-left:
1ex;" data-mce-style="margin: 0 0 0 .8ex;
border-left: 1px #ccc solid; padding-left: 1ex;">
<div>
<p>I can see dozens of legitimate reasons for
restricting access that are not related to the
efficiencies of the data retrieval system, first
of which is harvesting prevention. <br>
</p>
<p>Volker<br>
</p>
<div>
<div class="h5"> <br>
<div
class="m_274932282668893854moz-cite-prefix">Am
17.05.2017 um 17:55 schrieb Paul Keating:<br>
</div>
<blockquote>
<div style="color: #000000; font-family:
Calibri,sans-serif; font-size: 14px;"
data-mce-style="color: #000000;
font-family: Calibri,sans-serif;
font-size: 14px;"><b style="font-family:
Calibri; font-size:
14.666666984558105px;"
data-mce-style="font-family: Calibri;
font-size: 14.666666984558105px;"><i>“There
must be no RDS policies that prevent
RDS operators from applying
operational controls such as rate
limiting and CAPTCHA, provided that
they do not unreasonably restrict
legitimate access.“</i></b><span
style="font-family: Calibri; font-size:
14.666666984558105px;"
data-mce-style="font-family: Calibri;
font-size: 14.666666984558105px;">, </span></div>
<div style="color: #000000; font-family:
Calibri,sans-serif; font-size: 14px;"
data-mce-style="color: #000000;
font-family: Calibri,sans-serif;
font-size: 14px;"><span
style="font-family: Calibri; font-size:
14.666666984558105px;"
data-mce-style="font-family: Calibri;
font-size: 14.666666984558105px;"><br>
</span></div>
<div><span face="Calibri" size="3"
data-mce-style="font-family: Calibri;
font-size: medium;" style="font-family:
Calibri; font-size: medium;">Caveat.
The rate controls must be related to
controlling the efficiiciencies of the
underlying data retrieval system and not
for o there purposes.</span></div>
<div><span face="Calibri" size="3"
data-mce-style="font-family: Calibri;
font-size: medium;" style="font-family:
Calibri; font-size: medium;"><br>
</span></div>
<div><span face="Calibri" size="3"
data-mce-style="font-family: Calibri;
font-size: medium;" style="font-family:
Calibri; font-size: medium;">PRK</span></div>
<span
id="m_274932282668893854OLK_SRC_BODY_SECTION"
style="color: #000000; font-family:
Calibri,sans-serif; font-size: 14px;"
data-mce-style="color: #000000;
font-family: Calibri,sans-serif;
font-size: 14px;">
<div style="font-family: Calibri;
font-size: 11pt; text-align: left;
color: black; border-bottom: medium
none; border-left: medium none;
border-top: #b5c4df 1pt solid;
border-right: medium none; padding: 3pt
0in 0in 0in;"
data-mce-style="font-family: Calibri;
font-size: 11pt; text-align: left;
color: black; border-bottom: medium
none; border-left: medium none;
border-top: #b5c4df 1pt solid;
border-right: medium none; padding: 3pt
0in 0in 0in;"><span style="font-weight:
bold;" data-mce-style="font-weight:
bold;">From: </span> <<a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>>
on behalf of Amr Elsadr <<a
moz-do-not-send="true"
href="mailto:amr.elsadr@icann.org"
target="_blank">amr.elsadr@icann.org</a>><br>
<span style="font-weight: bold;"
data-mce-style="font-weight: bold;">Date:
</span> Wednesday, May 17, 2017 at 9:48
AM<br>
<span style="font-weight: bold;"
data-mce-style="font-weight: bold;">To:
</span> "<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a>"
<<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a>><br>
<span style="font-weight: bold;"
data-mce-style="font-weight: bold;">Subject:
</span> [gnso-rds-pdp-wg] IMPROTANT -
Action Items and Notes from
Next-Generation RDS PDP Working Group
Call - 17 May 2017<br>
</div>
<div><br>
</div>
<blockquote
id="m_274932282668893854MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
style="border-left: #b5c4df 5 solid;
padding: 0 0 0 5; margin: 0 0 0 5;"
data-mce-style="border-left: #b5c4df 5
solid; padding: 0 0 0 5; margin: 0 0 0
5;">
<div>
<div lang="EN-US">
<div
class="m_274932282668893854WordSection1">
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Dear Working Group
Members,<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Please find below the
action items and notes from
today’s Working Group call.<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Thanks.<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Amr<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<div style="border: none;
border-bottom: solid windowtext
1.0pt; padding: 0in 0in 1.0pt
0in;" data-mce-style="border:
none; border-bottom: solid
windowtext 1.0pt; padding: 0in
0in 1.0pt 0in;">
<p class="MsoNormal"
style="border: none; padding:
0in;" data-mce-style="border:
none; padding: 0in;"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span></span></p>
</div>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><i><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">These high-level
notes are designed to help
PDP WG members navigate
through the content of the
call and are not meant as a
substitute for the
transcript and/or recording.
The MP3, transcript, and
chat are provided separately
and are posted on the wiki
here: <a
moz-do-not-send="true"
href="https://community.icann.org/x/HMPRAw"
target="_blank">
https://community.icann.org/x/HMPRAw</a><span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></i></p>
<p class="MsoNormal"><i><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span></span></i></p>
<p class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Action Items:<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></b></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">1. Newcomers to RSVP
to Newcomer Tutorial
invitation if you plan to
attend<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">2. Staff to launch
poll the test revised item 2)
in <a moz-do-not-send="true"
href="https://community.icann.org/download/attachments/56986791/KeyConceptsDeliberation-WorkingDraft-9May2017.pdf?version=1&modificationDate=1494372838376&api=v2"
target="_blank">statement of
purpose</a> and revised 2
May agreement:<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"
style="margin-left: .5in;"
data-mce-style="margin-left:
.5in;"><span style="font-size:
11.0pt;"
data-mce-style="font-size:
11.0pt;">a. The test revised
item 2) in <a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/56986791/KeyConceptsDeliberation-WorkingDraft-9May2017.pdf?version=1&modificationDate=1494372838376&api=v2"
target="_blank">statement of
purpose</a>: "2) A purpose
of RDS is to facilitate
dissemination of gTLD
registration data of record,
such as domain names and their
domain contacts and name
servers, in accordance with
applicable policy.”<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"
style="margin-left: .5in;"
data-mce-style="margin-left:
.5in;"><span style="font-size:
11.0pt;"
data-mce-style="font-size:
11.0pt;">b. Revised 2 May
agreement: "gTLD registration
"thin data" must be accessible
without requestor
identification,
authentication, or stated
purpose"<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"
style="text-indent: .5in;"
data-mce-style="text-indent:
.5in;"><span style="font-size:
11.0pt;"
data-mce-style="font-size:
11.0pt;">WG members to
participate in poll by COB
Saturday 20 May.<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">3. Rod Rasmussen
and Vaibhav Aggarwal to work
together to define what
"unreasonably restrict
legitimate access" means in
the context of this statement
<b><i>“There must be no RDS
policies that prevent RDS
operators from applying
operational controls such
as rate limiting and
CAPTCHA, provided that
they do not unreasonably
restrict legitimate
access.“</i></b>, and
propose that definition to WG
mailing list, preferably
before next week's WG call<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Notes:<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></b></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">1) Roll Call/SOI
Updates<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Attendance will be
taken from AC<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Please remember to
state your name before
speaking and remember to
mute your microphones when
not speaking<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">SOI updates: none<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">2) Brief updates<br>
a) Newcomer tutorial plans:<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Tuesday 23 May,
immediately following WG
Call<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Recording to be
available for on-demand
replay<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<p class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Action Item:</span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"> Newcomers to RSVP to
Newcomer Tutorial invitation
if you plan to attend<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">b) ICANN59 meeting
plans:<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Monday 26 June
Cross-Community Session on
RDS<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Tuesday 27 June
Face-to-Face RDS PDP WG
Session<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">3) Review
proposed-final definition(s)
to replace "authoritative" in
Statement of Purpose, Item 2):<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/64078620/DataOfRecord-Proposal.pdf"
target="_blank">https://community.icann.org/download/attachments/64078620/DataOfRecord-Proposal.pdf</a><span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Recommendation on
how to proceed with
replacement term for
"authoritative"<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Starting with poll
results from 28 March for
Statement of Purpose item 2)
- substitute term "Data of
Record" so that item will
read:<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">"2) A purpose of
RDS is to facilitate
dissemination of gTLD
registration data of record,
such as domain names and
their domain contacts and
name servers, in accordance
with applicable policy.”<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Definition: "the
data set at a given time
relevant to a given
registration object that
expresses the data provided
in the then-current
registration for that
object.”<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Can still later
consider "source of record"
but does not appear needed
to convey intent of this
item in the statement of
purpose<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<p class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Proposed WG
Agreement (to test with
poll): </span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">"2) A purpose of RDS
is to facilitate dissemination
of gTLD registration data of
record, such as domain names
and their domain contacts and
name servers, in accordance
with applicable policy.”
(including footnoted
definition above)<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">4) Continue
deliberation on the charter
question 5: What steps should
be taken to control "thin
data" access?<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">See handout <a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/64078620/Charter%20Question%205%20-%20Handout%20-%20For17MayCall%20v2.pdf"
target="_blank">https://community.icann.org/download/attachments/64078620/Charter%20Question%205%20-%20Handout%20-%20For17MayCall%20v2.pdf</a><span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Full results
available at <a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/64078620/SummaryResults-Poll-from-9MayCall.pdf"
target="_blank">https://community.icann.org/download/attachments/64078620/SummaryResults-Poll-from-9MayCall.pdf</a><span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">a) Is "thin data"
access authentication required
or allowed?<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Proposed answer:
Based on Poll Question 2)
Option e)<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">"Thin data elements
must be accessible without
requestor authentication."<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">With 33 responses,
option e) had greatest
support and least opposition
- but not rough consensus<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Does "inquirers
identifying themselves" or
"authentication" imply a
person rather than a machine
making the request?<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">First proposed
change "gTLD registration
"thin data" should be
accessible without inquirer
identification or stating
purpose".<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Consider combining
option e) with this
agreement, and using
"requestor" instead of
"inquirer" for consistency<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Revised/combined
proposed change "gTLD
registration "thin data"
must be accessible without
requestor identification,
authentication, or stated
purpose".<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<p class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Proposed WG
Agreement (to test with
poll):</span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"> "gTLD registration
"thin data" must be accessible
without requestor
identification,
authentication, or stated
purpose".<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">b) Is "thin data"
access anonymity required or
allowed?<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Proposed answer:
Based on Poll Question 2)
Comment 9:<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">"Access to thin
registration data must be
provided to anonymous
requestors."<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Does anyone think
we must refer to anonymity
or is proposed agreement in
a) sufficient?<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Introduces a new
term that may be
problematic. <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Why do we need to
define anonymous now? Thick
data for LEA we may need to
define anonymous and
untraceable and a whole slew
of things but we are only on
thin data now, right?<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">The current
proposal (under a above)
says what the requestor does
_not_ have to give, rather
than trying to create an
attribute of the requestor<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">c) Do we need to
define "authentication"?<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">We might need to
define it later (since we
say that there is no
authentification required
for thin data) - may need to
define it for thick data<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Is "according to
policy" implicit in WG
agreements? We haven't yet
agreed on specific "thin
data" elements yet<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<p class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Action Item:</span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"> Staff to launch poll
the test revised item 2) in
statement of purpose and
revised 2 May agreement (the
two Proposed WG Agreements
above). WG members to
participate in poll by COB
Saturday 20 May.<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">d) Should policies
allow or prevent application
of operational controls?<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Rough consensus WG
Agreement (75%) on Poll
Question 3):<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><i><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">"There must be no
RDS policies that prevent
RDS operators from
applying operational
controls such as rate
limiting and CAPTCHA,
provided that they do not
unreasonably restrict
legitimate access."</span></i><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Need to define
specific policy for
"reasonable" and
"legitimate" during Phase 2
of this PDP?<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Is there a need for
an explicit statement like
this? If the information is
public, is it necessary to
limit to prevent scraping?
Or is rate limiting being
used to limit legitimate
access - can't ignore this
gaming/artificial limit
possibility.<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Note 2013 RAA 3.3.5
states "Registrar shall
permit use of data it
provides in response to
queries for any lawful
purposes except to...(b)
enable high volume,
automated, electronic
processes that send queries
or data to the systems of
any Registry Operator or
ICANN-Accredited registrar,
except as reasonably
necessary to register domain
names or modify existing
registrations."<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Perhaps rather than
saying something about
rate-limiting per se, we
need an SLA about the level
of access that must be
supported.<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Remaining silent on
this point may lead to
policies that interfere with
use of operational controls
- but using "unreasonably
restrict legitimate access"
may leap this too open ended<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Agreed to put this
rough consensus point on
hold, pending definition of
what "unreasonably restrict
legitimate access" means<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<p class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Action Item:</span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"> Rod Rasmussen
and Vaibhav Aggarwal to work
together to define what
"unreasonably restrict
legitimate access" means in
the context of this statement
and propose that definition to
WG mailing list, preferrably
before next week's WG call.<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">e) Review all of
charter question 5
sub-questions with goal to
complete first pass
deliberation on "thin data"
access in May<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">DEFERRED TO 23 MAY
WG MEETING<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">5) Confirm action
items and proposed decision
points<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Proposed WG
Agreement (to test with
poll): </span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">"2) A purpose of
RDS is to facilitate
dissemination of gTLD
registration data of record,
such as domain names and
their domain contacts and
name servers, in accordance
with applicable policy.”
(including footnoted
definition above)<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Proposed WG
Agreement (to test with
poll):</span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"> "gTLD registration
"thin data" must be
accessible without requestor
identification,
authentication, or stated
purpose".<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Action Item:</span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"> Newcomers to RSVP
to Newcomer Tutorial
invitation if you plan to
attend<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Action Item:</span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"> Staff to launch
poll the test revised item
2) in statement of purpose
and revised 2 May agreement
(the two Proposed WG
Agreements above). WG
members to participate in
poll by COB Saturday 20 May.<span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Action Item:</span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"> Rod Rasmussen
and Vaibhav Aggarwal to work
together to define what
"unreasonably restrict
legitimate access" means in
the context of this
statement and propose that
definition to WG mailing
list, preferably before next
week's WG call.<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">6) Confirm next
meeting date: 23 May 2017 at
16:00 UTC<span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">Meeting Materials</span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/64078620/DataOfRecord-Proposal.pdf?version=1&modificationDate=1494989338000&api=v2"
target="_blank">Data of
Record Proposal</a></span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/64078620/Charter%20Question%205%20-%20Handout%20-%20For17MayCall%20v2.pdf?version=1&modificationDate=1494961615000&api=v2"
target="_blank">Charter
Question 5 - Handout -
For17MayCall.pdf </a></span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/56986791/KeyConceptsDeliberation-WorkingDraft-9May2017.pdf?version=1&modificationDate=1494372838376&api=v2"
target="_blank">KeyConceptsDeliberation-WorkingDraft-9May2017.pdf</a> </span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">and <b><a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/56986791/KeyConceptsDeliberation-WorkingDraft-9May2017.docx?version=1&modificationDate=1494372853897&api=v2"
target="_blank">doc</a></b><span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></li>
</ul>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;">9 May Call Poll
Results -</span></b><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span>
<ul style="margin-top: 0in;"
data-mce-style="margin-top:
0in;" type="disc">
<li class="MsoNormal"><span
style="font-size:
11.0pt;"
data-mce-style="font-size:
11.0pt;">PDF of Poll
Questions:<b> <i><a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/64078610/Poll-from-9MayCall.pdf?version=1&modificationDate=1494374689000&api=v2"
target="_blank">Poll-from-9MayCall.pdf</a></i></b><span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size:
11.0pt;"
data-mce-style="font-size:
11.0pt;">SurveyMonkey
Summary Poll Results: <b><i><a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/64078620/SummaryResults-Poll-from-9MayCall.pdf?version=1&modificationDate=1494787660000&api=v2"
target="_blank">SummaryResults-Poll-from-9MayCall.pdf</a></i></b><span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span></span></li>
<li class="MsoNormal"><span
style="font-size:
11.0pt;"
data-mce-style="font-size:
11.0pt;">SurveyMonkey
Raw Data Poll Results: <b><i><a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/64078620/RawDataResults-Poll-from-9MayCall.zip?version=1&modificationDate=1494787676000&api=v2"
target="_blank">RawDataResults-Poll-from-9MayCall.zip</a></i></b> and <b><i><a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/64078620/RawDataResults-Poll-from-9MayCall.xls?version=1&modificationDate=1494787693000&api=v2"
target="_blank">XLS</a></i></b><span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span><span
data-mce-style="text-decoration: underline;" style="text-decoration:
underline;"></span></span></li>
</ul>
</li>
</ul>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
<p class="MsoNormal"><span
style="font-size: 11.0pt;"
data-mce-style="font-size:
11.0pt;"><span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span> <span
data-mce-style="text-decoration:
underline;"
style="text-decoration:
underline;"></span></span></p>
</div>
</div>
</div>
_______________________________________________ gnso-rds-pdp-wg mailing
list <a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote>
</span> <br>
<fieldset
class="m_274932282668893854mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
gnso-rds-pdp-wg mailing list
<a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
</div>
</div>
<pre class="m_274932282668893854moz-signature">--
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.: <a moz-do-not-send="true" href="tel:+49%206894%209396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a moz-do-not-send="true" href="tel:+49%206894%209396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a><a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a>
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.: <a moz-do-not-send="true" href="tel:+49%206894%209396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a moz-do-not-send="true" href="tel:+49%206894%209396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a><a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a moz-do-not-send="true" class="m_274932282668893854moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a>
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.
</pre>
</div>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
</blockquote>
</div>
<br>
</div>
_______________________________________________
gnso-rds-pdp-wg mailing list
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote>
</span>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
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: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
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: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
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.
</pre>
</body>
</html>