<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">Volker, </div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><br></div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">No insult intended but I believe you are making an error because you are (IMHO) approaching the “problem” using the narrow set of use-case-facts you may know..</div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><br></div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><br></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">Volker Greimann <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a> wrote: <span style="font-family: -webkit-standard; font-size: medium; background-color: rgb(255, 255, 255);"> example, but Whois not necessarily needed for that. Each company could just have asked their registrars to certify their ownership of the domain names. Most registrars provide this service if asked, either for a fee or as included part of their management services. These certifications could then be handed to the "opposing" counsel.</span></div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><span style="font-family: -webkit-standard; font-size: medium; background-color: rgb(255, 255, 255);"><br></span></div></blockquote><div><span style="background-color: rgb(255, 254, 254);">As an attorney having engaged in m any similar transactions, I can assure you that obtaining a certificate of ownership and being able to investigate WHOIS, including historical information via aggregators, it is NOT at all the same.</span></div><div><span style="background-color: rgb(255, 254, 254);"><br></span></div><div>Case 1.<span class="Apple-tab-span" style="white-space:pre"> </span>As a seller I must represent and warrant that I have good and marketable title and own the asset free of claims and encumbrances. Depending upon the value of the domain name, the client may require that the historical ownership be verified and compared with acquisition records so as to determine a clean history of title (the same a title company does when you purchase real estate).</div><div><br></div><div>Case 2.<span class="Apple-tab-span" style="white-space:pre"> </span>I represent auditing companies and must establish the accuracy of transactional records evidencing purchase. To do so I must access a third party source (independent of the client). Thus, I turn to WHOIS aggregators who maintain historical information that can be used to verify ownership against the purchase documentation.</div><div><br></div><div>Case 3.<span class="Apple-tab-span" style="white-space:pre"> </span>I am representing a client faced with a tax audit. I must establish by independent means the acquisition of the domain name(s).</div><div><br></div><div>Case 4.<span class="Apple-tab-span" style="white-space:pre"> </span>I am assisting a client recover a domain name that has been highjacked. The WHOIS, both current and historical provides extremely valuable data without which I could not accomplish my task.</div><div><br></div><div>In all of the above, the domain may have been registered at various registrars during its life. My client may not even know all of the registrars in the title history (e.g. Some may have been automated or prior to ownership). Those client who acquire via the drop often have 10’s – 20’s registrar accounts and although they attempt to consolidate that is not an easy task. So, merely asking my client’s current registrar for data is a no-go.</div><div><br></div><div>Further, using your “system” I must pay each point of data requests – surely the registrars will attempt to create a revenue model – something I suspect they want all along and is a major driver for them in this issue. So, instead of dealing with an automated task with a single purchase transaction point I must now deal with a manual process with multiple transaction points.</div><div><br></div><div><br></div><div><br></div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><br></div><span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); 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; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> <<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>> on behalf of Volker Greimann <<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>><br><span style="font-weight:bold">Date: </span> Friday, April 28, 2017 at 11:59 AM<br><span style="font-weight:bold">To: </span> <<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [gnso-rds-pdp-wg] Proposed Agenda for RDS PDP WG Meeting Tuesday 25 April 16.00 UTC<br></div><div><br></div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div>
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<blockquote cite="mid:CA+aOHUQKmMQihKEqWuFauSXrZPcT2=YvOA-CXEa=ESeye35v9g@mail.gmail.com" type="cite">
<div>
<div class="gmail_default" style="font-family:verdana,sans-serif">As another use case, a
recent merger of two companies created a company with a
combined portfolio of approximately 7000 domain names. In the
course of preparation and due diligence for the transaction,
the law firms working on the merger probably both accessed the
Whois records for all those domain names, as well as receiving
reports from the registrars. The law firms may have accessed
them directly, or through a service like DomainTools. Some of
these were almost certainly ccTLDs but I would guess the vast
majority were gTLDs.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
</div>
</blockquote>
Good example, but Whois not necessarily needed for that. Each
company could just have asked their registrars to certify their
ownership of the domain names. Most registrars provide this service
if asked, either for a fee or as included part of their management
services. These certifications could then be handed to the
"opposing" counsel.<br>
<br>
Volker<br>
<br>
<br>
<blockquote cite="mid:CA+aOHUQKmMQihKEqWuFauSXrZPcT2=YvOA-CXEa=ESeye35v9g@mail.gmail.com" type="cite">
<div><br>
<p style="font-size:12.8px;text-indent:0in"><span style="font-size: 10pt; font-family: Arial, sans-serif;"></span></p>
</div>
<div class="gmail_extra">
<br>
<div class="gmail_quote">On Wed, Apr 26, 2017 at 7:51 PM,
Anderson, Marc <span dir="ltr"><<a moz-do-not-send="true" href="mailto:mcanderson@verisign.com" target="_blank">mcanderson@verisign.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div class="m_-2708956984384442313WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Greg,
my apologies for misquoting you, please consider me
corrected.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">I
don’t think that a future RDS that facilitates
access to the BPS of data rather than a one stop
aggregator of data (which comes with synchronization
and update challenges) would create a tsunami.
After all this is how the DNS works today and it has
much higher volumes than RDS. That said you make a
fair point about possible unintended consequences
and not letting perfect be the enemy of the good.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">I
would be interested in hearing more about the
registrar that needs access to 10k plus whois
records a day. Has that use case been accounted for
in the list of potential RDS requirements the
working group has collected?</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Thanks,<br>
Marc</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">
Greg Shatan [mailto:<a moz-do-not-send="true" href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.<wbr>com</a>]
<br>
<b>Sent:</b> Wednesday, April 26, 2017 3:16 PM<br>
<b>To:</b> Anderson, Marc<br>
<b>Cc:</b> Gomes, Chuck; <a moz-do-not-send="true" href="mailto:gtheo@xs4all.nl" target="_blank">gtheo@xs4all.nl</a>;
<a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a></span></p>
<div>
<div class="h5"><br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg]
Proposed Agenda for RDS PDP WG Meeting Tuesday 25
April 16.00 UTC</div>
</div>
<div>
<div class="h5">
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;">Marc,</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;">I
don't think the importance of convenience or
"one-stop" to information related to the
registration should be underestimated. I
have heard that one registrar I know of
accesses approximately 10,000 WHOIS records
a day. Slicing and dicing the data
currently in WHOIS could have massive ripple
effects (maybe tsunami effects is more
appropriate), if one look-up now becomes
several look-ups later. The possible split
between thin and thick is bad enough.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;">Also,
if some of the data is taken from the best
possible (avoiding "authoritative") source
(BPS), rather than the RDS database being
the best possible source, then that should
be explained and understood. Methods for
insuring the highest fidelity to the BPS
should be put in place, and the gaps should
be generally explained and understood (e.g.,
if the RDS and the BPS only sync once a day
or once an hour that should be understood,
so that if you need absolutely current
information from the BPS, you may need to go
to the BPS as well). </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;">Whatever
we do, there will still be some know-how and
tricks of the trade, but we shouldn't let
the perfect be the enemy of the good.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;">Finally,
to be clear, your statement, based on my
statement, isn't quite accurate (e.g., my
email would be the BPS...). </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;">You
said, "As has been pointed out in another
thread, this isn’t just the “Privacy Working
Group”; it’s the “Next Gen RDS Working
Group”."</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;">It
would be a more accurate paraphrase to say,
"</span><span style="font-size: 9.5pt; font-family: Verdana, sans-serif;">As
has been pointed out in another thread, this
isn’t the “Privacy Working Group”; it’s just
the “Next Gen RDS Working Group”."</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Verdana, sans-serif;">Greg</span></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
</p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p><a moz-do-not-send="true" name="m_-2708956984384442313_UNIQUE_ID_SafeHtmlFilter_UNIQUE_ID_SafeH"></a><b><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(0, 46, 98);">Greg
Shatan<br>
</span></b><span style="font-size: 10pt; font-family: Arial, sans-serif; color: black;">C:
<a moz-do-not-send="true" href="tel:%28917%29%20816-6428" value="+19178166428" target="_blank">917-816-6428</a><br>
S: gsshatan<br>
Phone-to-Skype: <a moz-do-not-send="true" href="tel:%28646%29%20845-9428" value="+16468459428" target="_blank">646-845-9428</a><br>
</span><a moz-do-not-send="true" href="mailto:gregshatanipc@gmail.com" target="_blank"><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(17, 85, 204);">gregshatanipc@gmail.com</span></a></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On Wed, Apr 26, 2017 at
2:15 PM, Anderson, Marc via gnso-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>>
wrote:</p>
<div>
<div>
<p class="MsoNormal">Chuck, I didn’t do a
very good job explaining my hesitation on
yesterday’s call so let me try again here.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I appreciate that we’ve
gotten bogged down recently and that the
leadership team is trying to move the PDP
forward. From my perspective though, we
went from trying to define a purpose(s) of
RDS and discussing what data elements
should be collected (making sure they map
back to a purpose) and then defining who
should have access to those data elements
and under what circumstances to just
throwing up our hands and saying hey, the
elements of today’s “thin” whois don’t
seem to have any personally identifiable
information in them, does anyone object to
just making it all available for unlimited
anonymous access in a future RDS solution.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">When you asked if
anyone objects I felt left with a choice:
either say nothing which would in effect
be agreeing that this working group has
reached rough consensus that all of
today’s “thin” whois elements should
continue to be available via unlimited
anonymous access or object. While I’m not
sure exactly what I would have been
agreeing to by remaining silent I don’t
feel comfortable saying that existing thin
whois should continue as is.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">On a previous call we
discussed the Registrar field and if that
should be required or not. We ran out of
time before fully getting into the
discussion. Aside from the “Sponsoring
Registrar IANA ID” field, I don’t think it
makes sense to require other registrar
meta data in a domain query response. For
example the Whois Server, Referral URL and
(newly required) Registrar abuse phone and
Registrar abuse email fields. These are
all registrar specific data elements not
domain data elements. If querying a
registrar RDS service, you already know
the whois server and referral URL so it
really doesn’t make sense to have those in
the response.</p>
<p class="MsoNormal">As ICANN accredits
registrars and already maintains public
lists of them, to me it makes more sense
to have that data centrally
managed/maintained and made available by
ICANN. At risk of pre-supposing a
solution, RDAP would provide the ability
to bring that data together in a single
client pulling from separate (more
appropriate) data sources.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I have questions about
other fields as well. Name Server
information for example is already
available via DNS. There is undoubtedly a
convenience factor to being able to get
that from whois as well. I know that
authoritative is a loaded term but in the
event that whois and DNS were different I
don’t think anyone would consider whois
authoritative using any definition of the
term. Shouldn’t we consider if it makes
sense to continue to provide the same
domain data elements in two different
places?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Domain statuses have
been discussed a little bit by this
working group but to my knowledge not in
detail. From what I’ve heard so far I’m
not sure that data should be available to
anyone other than the registrar and
registrant. I’m not saying there isn’t a
valid use case, but unless I missed it, I
don’t think we’ve really had a chance to
discuss, much less come to consensus.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Again I realize we are
trying to move things forward and if the
intent is to table some of these
discussions so we can get to the gated
access discussion, I get it. It felt to
me on the call though that we had boiled
things down to since there is no
personally identifiable information in
traditional thin whois, let’s just have
all of that be available for unlimited
anonymous access. As has been pointed out
in another thread, this isn’t just the
“Privacy Working Group”; it’s the “Next
Gen RDS Working Group”.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Hopefully that helps
explain my hesitation and why I put a red
“X” in Adobe.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks,</p>
<p class="MsoNormal">Marc</p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></p>
<div>
<div style="border:none;border-top:solid
#b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">
<a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.<wbr>org</a>
[mailto:<a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-<wbr>bounces@icann.org</a>]
<b>On Behalf Of </b>Gomes, Chuck
via gnso-rds-pdp-wg<br>
<b>Sent:</b> Tuesday, April 25, 2017
6:02 PM<br>
<b>To:</b> <a moz-do-not-send="true" href="mailto:gtheo@xs4all.nl" target="_blank">gtheo@xs4all.nl</a>;
<a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">
gnso-rds-pdp-wg@icann.org</a></span></p>
<div>
<div>
<p class="MsoNormal"><br>
<b>Subject:</b> [EXTERNAL] Re:
[gnso-rds-pdp-wg] Proposed Agenda
for RDS PDP WG Meeting Tuesday 25
April 16.00 UTC</p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif;">Thanks
Theo. Do I understand you are
saying that you could support thin
Whois data elements as public data
in the RDS?</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif;">Regardless,
I would still like to see if we can
find a resolution to Marc’s concern
as long as we don’t spend an
inordinate amount of time on it. I
will try to reach out to Marc to see
if I can understand his position
better. And the Leadership team
will try to schedule a call later
this week to work on this further.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif;">Chuck</span></p>
<p class="MsoNormal"><a moz-do-not-send="true" name="m_-2708956984384442313_m_-6279980457633982584__MailEndCompose"><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></a></p>
<div>
<div style="border:none;border-top:solid
#e1e1e1 1.0pt;padding:3.0pt 0in 0in
0in">
<p class="MsoNormal"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">
<a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.<wbr>org</a>
[<a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">mailto:gnso-rds-pdp-wg-<wbr>bounces@icann.org</a>]
<b>On Behalf Of </b>theo geurts<br>
<b>Sent:</b> Tuesday, April 25,
2017 2:31 PM<br>
<b>To:</b> <a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> [EXTERNAL] Re:
[gnso-rds-pdp-wg] Proposed
Agenda for RDS PDP WG Meeting
Tuesday 25 April 16.00 UTC</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Repeating
my agreement with the below as
mentioned earlier on the call.<br>
<br>
Regarding my earlier comments about NO
WHOIS, still technically feasible, and
in my opinion good to think outside of
the box and check what the purpose is,
and I think we should keep checking
the purpose all the time. For the
progress of the WG, it is best to move
to gated access and use thin WHOIS for
now as available public data. <br>
<br>
For the discussion about gated access
perhaps it is an idea look at the
IPC/RrSG developed framework for the
PPSAI to see if that is sufficient to
address copyright and trademark
concerns. Could save us work if that
is workable.
<br>
<br>
Best,<br>
<br>
Theo Geurts</p>
<div>
<p class="MsoNormal">On 25-4-2017
16:40, Victoria Sheckler wrote:</p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif;">Apologies
for missing last week’s and
today’s meeting. With respect to
item 4 below, based on the
discussion we’ve had to date, I
believe all thin whois data should
be publicly available as it is
either not personally identifiable
information, or, in extreme edge
cases (such as a long domain name
that includes personal
information), then it is clear
that that individual has chosen to
make such information public. </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></p>
<div>
<div style="border:none;border-top:solid
#e1e1e1 1.0pt;padding:3.0pt 0in
0in 0in">
<p class="MsoNormal"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">
<a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.<wbr>org</a>
[<a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">mailto:gnso-rds-pdp-wg-<wbr>bounces@icann.org</a>]
<b>On Behalf Of </b>Lisa
Phifer<br>
<b>Sent:</b> Monday, April 24,
2017 12:51 PM<br>
<b>To:</b> 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>
<b>Subject:</b>
[gnso-rds-pdp-wg] Proposed
Agenda for RDS PDP WG Meeting
Tuesday 25 April 16.00 UTC</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family: Calibri, sans-serif;">Dear
all,<br>
<br>
The next GNSO Next-Gen RDS PDP
Working Group teleconference will
take place on <b>
Tuesday, 25 April at 16.00 UTC</b>
<br>
<br>
Below please find the proposed
agenda for this meeting, along
with links to meeting materials,
which can all be found on the
meeting page:
<a moz-do-not-send="true" href="https://community.icann.org/x/DcPRAw" target="_blank">https://community.icann.org/x/<wbr>DcPRAw<br>
<br>
</a>Regards,<br>
Lisa<br>
<br>
<u>Proposed Agenda for RDS PDP WG
Meeting 25 April 16.00 UTC<br>
</u>1) Roll Call/SOI Updates<br>
2) Plan to complete in-progress
tasks<br>
a) ccTLD questions<br>
b) Definition of authoritative<br>
3) Revised Task 12 sequence and
timeline<br>
See <a moz-do-not-send="true" href="https://community.icann.org/download/attachments/56986784/RDSPDP-Task12-Revised-21April2017.pdf?version=1&modificationDate=1492802630734&api=v2" target="_blank">
RDSPDP-Task12-Revised-<wbr>21April2017.pdf</a><br>
4) Start deliberation on the
charter question/subquestion 5.1:<br>
<i>Should gTLD registration
"thin data" be entirely public
or should access be controlled?<br>
</i> See <a moz-do-not-send="true" href="https://community.icann.org/download/attachments/64078605/NewSection5-Intro-KeyConcepts-21April2017.pdf?version=1&modificationDate=1492802791000&api=v2" target="_blank">
NewSection5-Intro-KeyConcepts-<wbr>21April2017.pdf</a><br>
5) Confirm action items and
proposed decision points<br>
6) Confirm next meeting date: 2
May 2017 at 16:00 UTC <br>
<br>
<b>Meeting Materials:</b> <a moz-do-not-send="true" href="https://community.icann.org/x/DcPRAw" target="_blank">
https://community.icann.org/x/<wbr>DcPRAw</a></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"> </p>
<pre>______________________________<wbr>_________________</pre><pre>gnso-rds-pdp-wg mailing list</pre><pre><a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a></pre><pre><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre></blockquote><p class="MsoNormal"> </p></div></div></div></div><p class="MsoNormal">
______________________________<wbr>_________________
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/<wbr>listinfo/gnso-rds-pdp-wg</a></p></div><p class="MsoNormal"> </p></div></div></div></div></div></blockquote></div></div><fieldset class="mimeAttachmentHeader"></fieldset><pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><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></pre></blockquote><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></div></div>_______________________________________________
gnso-rds-pdp-wg mailing list
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote></span></body></html>