<div><div dir="auto">John, Michele and Volker all made some good points, but this is being presented as a black vs. white argument, when the truth is grey.</div></div><div dir="auto"><br></div><div dir="auto">It’s a fact that ePDP participation is restricted to those seated by ICANN structures. So it is an “insider” process in that respect, especially by comparison to the RDS WG. However, variations on this type of structure have been used many times before in ICANN policy-making, even though there was a recent spate of “big-tent” WGs and CCWGs.</div><div dir="auto"><br></div><div dir="auto">The ePDP is not happening in private. You can become an Observer, and get listen-only access to the Adobe Connect room and read-only access to the email list. (I just got off the call before writing this.) Anyone (Observer or not) can also review any meeting at your convenience, through the various recordings, transcripts, etc., posted on the ICANN website. This is a fairly transparent process, even if your nose is pressed up against the (transparent) glass.</div><div dir="auto"><br></div><div dir="auto">On the other hand, transparency is not the same thing as access to involvement.</div><div dir="auto"><br></div><div dir="auto">It’s true that virtually any organization or individual should be able to join <i>some</i> ICANN structure. But no one can join <i>any</i> structure. Some structures are open to “anyone” (or almost anyone), while others are open only to those with certain attributes, and can be be viewed as closed, essentially closed, or drawing from a very finite universe. Relatively open structures include the BC, NCUC and ALAC/At-Large. Relatively closed structures (to differing degrees and in differing ways) include GAC, RySG, RrSG, ISPCP, and IPC. SSAC and RSSAC are more closed still. Even within these more closed groups there are still varying views (and sometimes very varying views).</div><div dir="auto"><br></div><div dir="auto">Not every stakeholder has a natural entry point into the ICANN structure set-up. Some types of stakeholders have obvious or well-defined “home” structures. Some may even have more than one.</div><div dir="auto"><br></div><div dir="auto">However, others stakeholders don’t appear to have any obvious “home” structure. This is true even where the stakeholders seem quite relevant to ICANN and the issues dealt with here. Resellers, hosting companies, web developers, cybersecurity professionals, anti-spam, anti-malware, anti-threat and other anti-abuse professionals are among the relevant stakeholders that don’t have an obvious home.</div><div dir="auto"><br></div><div dir="auto">If you don’t feel there’s a group where you fit well, that is a huge impediment to participating in ICANN through the “structure” set-up. But even that is a hurdle, rather than a hard barrier. You can find someplace to fit, even if the fit is slightly awkward.</div><div dir="auto"><br></div><div dir="auto">Some may be able to join At-Large, but that’s not a great fit if they want to participate in their professional capacity and not as end-users.</div><div dir="auto"><br></div><div dir="auto">Some may be able to join BC, but that risks the BC becoming a grab-bag of business sectors with wildly varying viewpoints, united only by the fact that they are “in business.” </div><div dir="auto"><br></div><div dir="auto">Some maybe be able to join NCUC, but that’s not a great fit for many of those mentioned above. </div><div dir="auto"><br></div><div dir="auto">Some, if they are very, very brave, could even band together and try to start a new Constituency, falling under CSG or NCSG. If they are even more brave (and foolhardy and masochistic), they could even propose a more fundamental change to the ICANN structure system.</div><div dir="auto"><br></div><div dir="auto">Even if the fit isn’t great, you join a structure to carry your own torch and to persuade others to carry it with you — both those in your structure and those in the larger ICANN ecosystem. Ideally, you carry a torch for a common interest that transcends any particular stakeholder concerns — a healthy multi-stakeholder process demands that its stakeholders do this.</div><div dir="auto"><br></div><div dir="auto">Finding some way Into the system is of great importance. The “big tent” Working Group model (where all are welcome) represents only one working method and only one part of the process. You cannot count on that model for entree into all things ICANN. </div><div dir="auto"><br></div><div dir="auto">And even when you are in a structure, you need to build bridges beyond that structure, try to be persuasive and try to be flexible in order to find solutions that strike enough of a balance to be credible candidates for consensus. Also, there’s a significant value in showing up at ICANN meetings — participating in Working Groups without going to meetings is like piano with mittens on (and I should know, I did it for 6 years (the no meetings thing, not the piano/mittens thing)).</div><div dir="auto"><br></div><div dir="auto">However, the burden is not only on the underrepresented stakeholders to find a place and to make that place work. In the long run, the burden is on ICANN structures, their participants, ICANN org and the internal and external review processes to consider issues like this and make recommendations and changes.</div><div dir="auto"><br></div><div dir="auto">In sum, the system isn’t perfect. Far from it. But (in my view), it’s better to find ways to participate, rather than just throwing stones from the outside. (There’s plenty of room for throwing stones on the inside, too, and even that is more effective as a participant.)</div><div dir="auto"><br></div><div dir="auto">Best regards,</div><div dir="auto"><br></div><div dir="auto">Greg</div><div dir="auto">(Apologies for length)</div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Thu, Oct 11, 2018 at 11:08 AM Volker Greimann <<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>So you are saying there is no one within the ICANN community that
shares your views? And that does not tell you anything? <br>
</p>
<p>If you feel underrepresented, start working in the system. If you
do not participate, either directly or indirectly, you ave no
chance of being heard. <br></p></div><div text="#000000" bgcolor="#FFFFFF"><p>
</p>
<p>Volker<br>
</p>
<br>
<div class="m_-6029767261803282736moz-cite-prefix">Am 11.10.2018 um 17:02 schrieb John
Bambenek:<br>
</div>
<blockquote type="cite">
Exactly.
<div><br>
</div>
<div>You’re right, we’re wrong. Now that we’ve established this a
priori, why would I join a constituency? To carry your torches?<br>
<br>
<div id="m_-6029767261803282736AppleMailSignature" dir="ltr">--
<div>John Bambenek</div>
</div>
<div dir="ltr"><br>
On Oct 11, 2018, at 09:57, Volker Greimann <<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<p>Or find an insider willing to carry your torch. And if
there is no such person, maybe reconsider your torch.</p>
<p>Volker<br>
</p>
<br>
<div class="m_-6029767261803282736moz-cite-prefix">Am 11.10.2018 um 16:25 schrieb
John Bambenek via gnso-rds-pdp-wg:<br>
</div>
<blockquote type="cite">
“If you don’t like being an outsider, you have to play by
our rules and become an insider.”
<div><br>
</div>
<div>And yeah, I can write a letter to my legislator. That
doesn’t make me a Senator. </div>
<div><br>
<div id="m_-6029767261803282736AppleMailSignature" dir="ltr">--
<div>John Bambenek</div>
</div>
<div dir="ltr"><br>
On Oct 11, 2018, at 09:14, Michele Neylon - Blacknight
<<a href="mailto:michele@blacknight.com" target="_blank">michele@blacknight.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="m_-6029767261803282736WordSection1">
<p class="MsoNormal"><span lang="EN-GB">Again. You
are wrong.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">You, like
anyone else, can join any number of ICANN
groups.<br>
You choose not to.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">That’s
your choice.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Now you
can try to twist that around so that you can
tell people how you’ve been excluded, but the
reality is that you haven’t – you’ve chosen
that path.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Regards<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Michele<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">--<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Mr Michele Neylon<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Blacknight Solutions<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Hosting, Colocation &
Domains<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB"><a href="https://www.blacknight.com/" target="_blank">https://www.blacknight.com/</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB"><a href="https://blacknight.blog/" target="_blank">https://blacknight.blog/</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Intl. +353 (0) 59 9183072<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Direct Dial: +353 (0)59 9183090<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Personal blog: <a href="https://michele.blog/" target="_blank">https://michele.blog/</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Some thoughts: <a href="https://ceo.hosting/" target="_blank">https://ceo.hosting/</a>
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">-------------------------------<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Blacknight Internet Solutions
Ltd, Unit 12A,Barrowside Business
Park,Sleaty<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Road,Graiguecullen,Carlow,R93
X265,Ireland Company No.: 370845</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">John
Bambenek <<a href="mailto:jcb@bambenekconsulting.com" target="_blank">jcb@bambenekconsulting.com</a>><br>
<b>Date: </b>Thursday 11 October 2018 at
14:57<br>
<b>To: </b>Michele Neylon <<a href="mailto:michele@blacknight.com" target="_blank">michele@blacknight.com</a>><br>
<b>Cc: </b>Dotzero <<a href="mailto:dotzero@gmail.com" target="_blank">dotzero@gmail.com</a>>,
RDS PDP WG <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>><br>
<b>Subject: </b>Re: [gnso-rds-pdp-wg] Next
Gen RDS - Update from Leadership Team<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">“You can convince some
insider to carry your concern while they
deliberate in private.” <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">That is exactly
my point. You’ve excluded outsiders.<u></u><u></u></p>
<div id="m_-6029767261803282736AppleMailSignature">
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<p class="MsoNormal">John Bambenek<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Oct 11, 2018, at 04:55, Michele Neylon -
Blacknight <<a href="mailto:michele@blacknight.com" target="_blank">michele@blacknight.com</a>>
wrote:<u></u><u></u></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-GB">John</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-GB">That
isn’t true. Every SO and AC within ICANN
has representation. You and anyone else
can channel your concerns via your
respective constituency, stakeholder
group or AC.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-GB">Also
as is normal with any GNSO Working Group
the interim report and final report will
be open for public comment.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-GB">Regards</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-GB">Michele</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">--</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Mr
Michele Neylon</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Blacknight
Solutions</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Hosting,
Colocation & Domains</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB"><a href="https://www.blacknight.com/" target="_blank">https://www.blacknight.com/</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB"><a href="https://blacknight.blog/" target="_blank">https://blacknight.blog/</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Intl.
+353 (0) 59 9183072</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Direct
Dial: +353 (0)59 9183090</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Personal
blog: <a href="https://michele.blog/" target="_blank">
https://michele.blog/</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Some
thoughts: <a href="https://ceo.hosting/" target="_blank">
https://ceo.hosting/</a> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">-------------------------------</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Blacknight
Internet Solutions Ltd, Unit
12A,Barrowside Business Park,Sleaty</span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="color:black" lang="EN-GB">Road,Graiguecullen,Carlow,R93
X265,Ireland Company No.: 370845</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><u></u><u></u></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">gnso-rds-pdp-wg
<<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>>
on behalf of John Bambenek via
gnso-rds-pdp-wg <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>><br>
<b>Reply-To: </b>John Bambenek <<a href="mailto:jcb@bambenekconsulting.com" target="_blank">jcb@bambenekconsulting.com</a>><br>
<b>Date: </b>Wednesday 10 October
2018 at 23:50<br>
<b>To: </b>Dotzero <<a href="mailto:dotzero@gmail.com" target="_blank">dotzero@gmail.com</a>><br>
<b>Cc: </b>RDS PDP WG <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>><br>
<b>Subject: </b>Re: [gnso-rds-pdp-wg]
Next Gen RDS - Update from Leadership
Team</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I did take
notice that the new EPDP specifically
excludes all outsiders thus ensuring that
anyone who actually uses whois will not be
represented.<u></u><u></u></p>
<div id="m_-6029767261803282736AppleMailSignature">
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<p class="MsoNormal">John Bambenek<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Oct 10, 2018, at 17:28, Dotzero <<a href="mailto:dotzero@gmail.com" target="_blank">dotzero@gmail.com</a>>
wrote:<u></u><u></u></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">The proposed
termination document reflects the
reality of what has occurred. I'd
like to thank everyone else for
their efforts. I know that we had
some disagreements and the process
sometimes was painful. <u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Michael Hammer<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">On Wed, Oct 10,
2018 at 9:30 AM Anderson, Marc via
gnso-rds-pdp-wg <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>>
wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Fellow Next Gen
RDS members,</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">In March of
this year the RDS PDP
leadership team canceled
working group meetings,
effectively putting the
group on hold. This
decision was made because we
heard from ICANN org that it
was considering instituting
a temporary policy that
would greatly impact our
work. Out of respect for
members’ time it didn’t make
sense to continue
deliberations.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Since then, the
ICANN board did approve a
temporary specification (<a href="https://www.icann.org/resources/pages/gtld-registration-data-specs-en" target="_blank">https://www.icann.org/resources/pages/gtld-registration-data-specs-en</a>).
Subsequent to that, the GNSO
council initiated an
expedited PDP on that
temporary specification (<a href="https://www.icann.org/news/announcement-2018-07-19-en" target="_blank">https://www.icann.org/news/announcement-2018-07-19-en</a>).</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Given all this,
the RDS PDP leadership team
feels it doesn’t make sense
for the working group to
continue and is recommending
termination. The GNSO PDP
manual allows for
termination by the working
group and requires a written
“Termination Summary”
delivered to the GNSO
council via the council
liaison. The manual
provides “changing
circumstances” as an example
of a reason for termination
which this certainly
qualifies as.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Attached you
will find a proposed
“Termination Summary” for
the RDS PDP working group.
The leadership team plans to
deliver by 12 October so the
GNSO council can have it on
their agenda for ICANN 63.
Please let the leadership
team know if you have
questions or feedback.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Many thanks for
your hard work on this
project.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Best,<br>
RDS Leadership team</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<fieldset class="m_-6029767261803282736mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="m_-6029767261803282736moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a class="m_-6029767261803282736moz-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>
<pre class="m_-6029767261803282736moz-signature" cols="72">--
Volker A. Greimann
General Counsel and Policy Manager
KEY-SYSTEMS GMBH
T: +49 6894 9396901
F: +49 6894 9396851
W: <a class="m_-6029767261803282736moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a>
Key-systems is a company registered in Germany with Registration No.: HR B 18835 - Saarbruecken: CEO: Alexander Siffrin
Registered Offices: Im Oberen Werk 1, DE-66386 St. Ingbert, Germany
Part of the CentralNic Group PLC (LON: CNIC) a company registered in England and Wales with company number 8576358.
Registered Offices: 35-39 Moorgate, London, EC2R 6AR. </pre>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><span>_______________________________________________</span><br>
<span>gnso-rds-pdp-wg mailing list</span><br>
<span><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a></span><br>
<span><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></div>
</blockquote>
</div>
</blockquote>
<br>
<pre class="m_-6029767261803282736moz-signature" cols="72">--
Volker A. Greimann
General Counsel and Policy Manager
KEY-SYSTEMS GMBH
T: +49 6894 9396901
F: +49 6894 9396851
W: <a class="m_-6029767261803282736moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a>
Key-systems is a company registered in Germany with Registration No.: HR B 18835 - Saarbruecken: CEO: Alexander Siffrin
Registered Offices: Im Oberen Werk 1, DE-66386 St. Ingbert, Germany
Part of the CentralNic Group PLC (LON: CNIC) a company registered in England and Wales with company number 8576358.
Registered Offices: 35-39 Moorgate, London, EC2R 6AR. </pre>
</div>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a 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></blockquote></div></div>