<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><font face="Calibri,sans-serif">Yes, legally. &nbsp;They are the agent of a &nbsp;principle.</font></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> Volker Greimann &lt;<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>&gt;<br><span style="font-weight:bold">Date: </span> Thursday, July 27, 2017 at 5:56 PM<br><span style="font-weight:bold">To: </span> Paul Keating &lt;<a href="mailto:paul@law.es">paul@law.es</a>&gt;, &lt;<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>&gt;<br><span style="font-weight:bold">Subject: </span> Re: [gnso-rds-pdp-wg] List discussion topics<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 http-equiv="Content-Type" content="text/html;

      charset=windows-1252">

  <div text="#000000" bgcolor="#FFFFFF">

    <p>Hi Paul,</p>

    <p>that would be the expectation, but are they really? Are they

      asked if they agreed to be put in the whois? Have they provided

      explicit permission for their data to be collected (and in whois:

      published)? <br>

    </p>

    <p>Best,</p>

    <p>Volker<br>

    </p>

    <br>

    <div class="moz-cite-prefix">Am 27.07.2017 um 14:19 schrieb Paul

      Keating:<br>

    </div>

    <blockquote type="cite" cite="mid:D59FA5F5.AB6C8%25Paul@law.es">

      <div>Sorry but I disagree.</div>

      <div><br>

      </div>

      <div>A tech or admin contact generally fits into one of the

        following categories:</div>

      <div><br>

      </div>

      <div>1.<span class="Apple-tab-span" style="white-space:pre">        </span>Agent

        of the registrant (e.g. Hired or retained to serve).</div>

      <div>2.<span class="Apple-tab-span" style="white-space:pre">        </span>Employee

        of the registrant</div>

      <div>3.<span class="Apple-tab-span" style="white-space:pre">        </span>A

        non-individual.</div>

      <div><br>

      </div>

      <div>As to #1 and 2, the service in the capacity is part of the

        responsibilities of the agent/employee. &nbsp;The contact information

        is the contact information used by the agent/employee for

        commercial purposes. &nbsp;In fact it is generally either the

        business email address of the non-individual company or of the

        registrant. This is not in fact personal information any more

        than my email address for my law firm is personal information.

        &nbsp;If it were otherwise the world would grind to a halt because no

        one could use or publish even an email issued by the

        agent/employee on behalf of and in his/her capacity as an

        agent/employee.</div>

      <div><br>

      </div>

      <div>As for #3, non-individual information is not covered by any

        of the relevant data protection laws.</div>

      <div><br>

      </div>

      <div>Again, lets focus on the data sets and not incorporate )(at

        this stage) issues of what level of access should be granted to

        those sets.</div>

      <div><br>

      </div>

      <div>Paul</div>

      <div><br>

      </div>

      <div><br>

      </div>

      <div><br>

      </div>

      <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; 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> &lt;<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a>&gt;

          on behalf of Volker Greimann &lt;<a href="mailto:vgreimann@key-systems.net" moz-do-not-send="true">vgreimann@key-systems.net</a>&gt;<br>

          <span style="font-weight:bold">Date: </span> Thursday, July

          27, 2017 at 11:51 AM<br>

          <span style="font-weight:bold">To: </span> &lt;<a href="mailto:gnso-rds-pdp-wg@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>&gt;<br>

          <span style="font-weight:bold">Subject: </span> Re:

          [gnso-rds-pdp-wg] List discussion topics<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 http-equiv="Content-Type" content="text/html;

              charset=windows-1252">

            <div text="#000000" bgcolor="#FFFFFF">

              <p>I think consent is one of the most basic problems for

                the non-registrant contacts, e.g. tech, admin (and

                billing in some cases). As the registrar is (at best)

                only interacting directly with the registrant, and the

                other contacts are not subject to any agreement and/or

                policy directly, we had to trust that the registrant (or

                his agent) had obtained the appropriate content from the

                entities listed for those roles. <br>

              </p>

              <p>Clearly, this is no longer sufficient under the new

                data privacy regime where consent bust be explicitly

                given by the data subject. <br>

              </p>

              <p>Abuse would be a new role to consider, however the same

                basically applies. <br>

              </p>

              <p>I think the descriptions from the EWG are good and

                sufficient.<br>

              </p>

              <p>Best,</p>

              <p>Volker<br>

              </p>

              <br>

              <div class="moz-cite-prefix">Am 26.07.2017 um 22:21

                schrieb Chuck Gomes Consulting:<br>

              </div>

              <blockquote type="cite" cite="mid:004501d3064c$b98c30d0$2ca49270$@cgomes.com">

                <meta http-equiv="Content-Type" content="text/html;

                  charset=windows-1252">

                <meta name="Generator" content="Microsoft Word 15

                  (filtered medium)">

                <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}

o\:* {behavior:url(#default#VML);}

w\:* {behavior:url(#default#VML);}

.shape {behavior:url(#default#VML);}

</style><![endif]-->

                <style><!--

/* Font Definitions */

@font-face

        {font-family:Wingdings;

        panose-1:5 0 0 0 0 0 0 0 0 0;}

@font-face

        {font-family:"Cambria Math";

        panose-1:2 4 5 3 5 4 6 3 2 4;}

@font-face

        {font-family:Calibri;

        panose-1:2 15 5 2 2 2 4 3 2 4;}

/* Style Definitions */

p.MsoNormal, li.MsoNormal, div.MsoNormal

        {margin:0in;

        margin-bottom:.0001pt;

        font-size:11.0pt;

        font-family:"Calibri",sans-serif;}

a:link, span.MsoHyperlink

        {mso-style-priority:99;

        color:#0563C1;

        text-decoration:underline;}

a:visited, span.MsoHyperlinkFollowed

        {mso-style-priority:99;

        color:#954F72;

        text-decoration:underline;}

span.EmailStyle17

        {mso-style-type:personal-compose;

        font-family:"Calibri",sans-serif;

        color:windowtext;}

.MsoChpDefault

        {mso-style-type:export-only;

        font-family:"Calibri",sans-serif;}

@page WordSection1

        {size:8.5in 11.0in;

        margin:1.0in 1.0in 1.0in 1.0in;}

div.WordSection1

        {page:WordSection1;}

/* List Definitions */

@list l0

        {mso-list-id:1013610293;

        mso-list-template-ids:86133948;}

@list l0:level1

        {mso-level-number-format:bullet;

        mso-level-text:\F0B7;

        mso-level-tab-stop:.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@list l0:level2

        {mso-level-number-format:bullet;

        mso-level-text:o;

        mso-level-tab-stop:1.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:"Courier New";

        mso-bidi-font-family:"Times New Roman";}

@list l0:level3

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:1.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level4

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:2.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level5

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:2.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level6

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:3.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level7

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:3.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level8

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:4.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level9

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:4.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

ol

        {margin-bottom:0in;}

ul

        {margin-bottom:0in;}

--></style><!--[if gte mso 9]><xml>

<o:shapedefaults v:ext="edit" spidmax="1026" />

</xml><![endif]--><!--[if gte mso 9]><xml>

<o:shapelayout v:ext="edit">

<o:idmap v:ext="edit" data="1" />

</o:shapelayout></xml><![endif]-->

                <div class="WordSection1">

                  <p class="MsoNormal">In addition to discussion about

                    the topics in this week&#8217;s poll, members are

                    encouraged to also discuss the following on the WG

                    list between now and our meeting next week:<o:p></o:p></p>

                  <p class="MsoNormal"><o:p>&nbsp;</o:p></p>

                  <p class="MsoNormal" style="margin-left:.25in">For

                    admin, technical, abuse, and privacy/proxy roles,

                    all WG members encouraged to discuss on-list the

                    following questions: <o:p></o:p></p>

                  <p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.75in;text-indent:-.25in;mso-list:l0

                    level1 lfo1"><!--[if !supportLists]--><span style="font-size: 10pt;"><span style="mso-list:Ignore">�<span style="font-style: normal; font-variant-caps:

                          normal; font-weight: normal; font-size: 7pt;

                          line-height: normal; font-family: 'Times New

                          Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]-->Are

                    these roles needed? <o:p></o:p></p>

                  <p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.75in;text-indent:-.25in;mso-list:l0

                    level1 lfo1"><!--[if !supportLists]--><span style="font-size: 10pt;"><span style="mso-list:Ignore">�<span style="font-style: normal; font-variant-caps:

                          normal; font-weight: normal; font-size: 7pt;

                          line-height: normal; font-family: 'Times New

                          Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]-->How

                    do they differ from each other? <o:p></o:p></p>

                  <p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.75in;text-indent:-.25in;mso-list:l0

                    level1 lfo1"><!--[if !supportLists]--><span style="font-size: 10pt;"><span style="mso-list:Ignore">�<span style="font-style: normal; font-variant-caps:

                          normal; font-weight: normal; font-size: 7pt;

                          line-height: normal; font-family: 'Times New

                          Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]-->How

                    might they differ from the registrant? <o:p></o:p></p>

                  <p class="MsoNormal" style="margin-bottom:12.0pt">The

                    following description of these roles, excerpted from

                    the EWG report, may be helpful in kicking off

                    discussion:<br>

                    <br>

                    <img style="width:8.802in;height:6.1041in" id="_x0000_i1025" src="cid:part1.E420ADAE.06135A2A@key-systems.net" alt="Emacs!" class="" moz-do-not-send="true" height="586" width="845">&nbsp;<br>

                    <br>

                    Note: The above contact types (roles) are being

                    discussed first because they received broad support

                    in our 28 June call poll. The EWG Report defined two

                    additional contact types (roles) which received less

                    support in our 28 June call poll; to enable focus on

                    possible common ground, additional contact types

                    will be discussed separately.<o:p></o:p></p>

                  <p class="MsoNormal" style="margin-bottom:12.0pt">Chuck<o:p></o:p></p>

                  <p class="MsoNormal"><o:p>&nbsp;</o:p></p>

                </div>

                <br>

                <fieldset class="mimeAttachmentHeader"></fieldset>

                <br>

                <pre wrap="">_______________________________________________

gnso-rds-pdp-wg mailing list

<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>

              </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" moz-do-not-send="true">vgreimann@key-systems.net</a>

Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net" moz-do-not-send="true">www.RRPproxy.net</a><a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com" moz-do-not-send="true">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" moz-do-not-send="true">www.facebook.com/KeySystems</a><a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" moz-do-not-send="true">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" moz-do-not-send="true">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" moz-do-not-send="true">vgreimann@key-systems.net</a>

Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net" moz-do-not-send="true">www.RRPproxy.net</a><a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com" moz-do-not-send="true">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" moz-do-not-send="true">www.facebook.com/KeySystems</a><a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" moz-do-not-send="true">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" moz-do-not-send="true">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" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>

          <a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote>

      </span>

    </blockquote>

    <br>

    <pre class="moz-signature" cols="72">-- 