<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>This is not always the case. Many resellers are more like agents
of the registrant than agents of the registrar.</p>
<p>Best,</p>
<p>Volker<br>
</p>
<br>
<div class="moz-cite-prefix">Am 03.01.2017 um 23:51 schrieb Alan
Greenberg:<br>
</div>
<blockquote
cite="mid:89004116-4c22-4792-b48f-0aaaab1a51af@EXHUB2010-1.campus.MCGILL.CA"
type="cite">
How resellers work is relatively straight forward. They are agents
working on behalf of a registrar. The handle the transaction and
often
ongoing contact with the registrant. Some registrars have no
resellers,
others some resellers, and some registrars only work through
resellers
and have no direct registratns. Of course, you may find that a
reseller
is really a subsidiary of the registrar (or in some other business
relationship with them other than purely a reseller).<br>
<br>
Until relatively recently, ICANN took the position that since they
had no
contract with resellers, they had no control over what resellers
did. In
more recent RAAs, there are explicit clauses which require that if
a
registrar delegates anything to resellers, that they must ensure
that the
reseller fulfill any obligations that the registrar would have if
they
were dealing with the registrant directly. Past RAAs only covereed
some
of these requirements but my recollection is that the current RAA
pretty
much puts a registrant in the same situation regardless of whether
they
are dealing with the registrar directly or a reseller (I may be
wrong
about that, but that is my recollection).<br>
<br>
Of course, it is up to the registrar to ensure that these
obligations are
followed, or ICANN compliance to identify places where they may
not be
doing so.<br>
<br>
Is that any clearer?<br>
<br>
Alan<br>
<br>
<br>
<br>
At 03/01/2017 02:56 PM, Stephanie Perrin wrote:<br>
<br>
<blockquote type="cite" class="cite" cite=""><font size="1">Happy
New Year
all! You are probably going to hate me because I am going to
slow
us down again. The problem is that we frame the discussion
and
thinking so very differently, depending on the expertise that
we bring to
this debate, that understanding the minutiae is very
important. For
instance on a recent call I questioned whether an individual
needed
to look at WHOIS to see who their registrar is, and was
promptly
corrected in this matter. Naive person that I am, I had never
plumbed the depths of the reseller business, and I am not
finding much
useful information on the ICANN site that will help me do this
(please
help and point me to how this happens, what kind of contracts
pass on
obligations, how this is interpreted under DP law, why I
cannot find my
registrar on any of the lists of ICANN accredited registrars,
consumer
protection obligations under US law, how this works in the
privacy proxy
business etc.). IN my responses to the questionnaire, I have
pointed out that it is the registrars and registries or their
agents that
collect/generate the Thin data. The proposed RDS, which at
the
moment is still protean, is not an entity, cannot collect etc,
but is
instead a display mechanism or automated disclosure
instrument. So
framing this in terms of collection is in my view quite
misleading,
unless I am totally misunderstanding the poll (always
possible). <br>
</font><br>
<font size="1">Anyway if anyone can help me understand how
resellers work I
would be most grateful. It would probably also save us a pile
of
time if I understood it better, if that can possibly
incentivize some
brave soul.....<br>
</font><br>
<font size="1">cheers Stephanie Perrin<br>
</font><br>
<br>
<br>
On 2017-01-03 10:31, Gomes, Chuck wrote:<br>
<blockquote type="cite" class="cite" cite="">A few weeks ago one
of our WG
members said something to me that I think might be a good
challenge for
many of us as we begin 2017: “I think people (including me)
need to
snap back to attention. I think we lost focus because of the
incredible
amount of lost traffic on minutiae that was so hard for
non-ICANN
insiders to follow.”<br>
<br>
If this applies to you, I hope you will respond.<br>
<br>
I can tell you that no one gets more frustrated with minutiae
than
me. I have just been at this for so long that I have learned
minutiae for one person is important to someone else so I have
realized
that I have to have a lot of patience. Still, I often find
myself
wanting to push faster ahead and the leadership team has to
pull me
back.<br>
<br>
It has taken us about 11 months to get to where we are and it
may seem
like we have made very little progress but I am hopeful that
we have laid
some building blocks that will make our work ahead easier. We
need
to all keep in mind that the ICANN community has been
grappling with
Whois (RDS) issues for most of its 18-year existence with very
minimal
progress. If we are going to change that pattern, we will
have to
be patient and persistent.<br>
<br>
As we ended 2016 we reached the critical deliberation stage of
Work Plan
Phase 1. None of us should think that that will be easy or
quick; it
won’t be. But I am confident that we will start to see more
concrete results of our efforts.<br>
<br>
I encourage all of you to start off this year by completing
the poll that
was distributed last week. You have until Friday of this week
to
complete it. Here is the link to the poll:
<a moz-do-not-send="true"
href="https://www.surveymonkey.com/r/V3CWZBL">
https://www.surveymonkey.com/r/V3CWZBL</a> .<br>
<br>
Happy New Year.<br>
<br>
Chuck<br>
<br>
<br>
<br>
<pre>_______________________________________________
gnso-rds-pdp-wg mailing list
<a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" eudora="autourl">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;DM5PR03MB2714;9:nXzNtMhlVADHVMCUzhbtlse3mo88vTzyiZsiXovSBQcJvIeZJqqbYfygQEKXJI1Jb2TWAZLGNZT1b67ZkyXF0tdFqQAPj/R2GhXZnBdRBTZwDZX6iLsKIpCHVqWblgxYGdLcB/AHJ+A14AzNIVSR6Y9UEF11dqyDAyI36juG2uEGJ4n4k9l5pxq0PZGfEqWrA71z6nrU/XKn5IcwFAzgNBCDOfUMoC2LTSezPrKFOhU2vNcf/RSQpYC55UI3psiCJuIDVzUsvg8pd6zR7Orekj436ttCVBFTEN3BwFkukFqa31QipQQKH+5057VmlSwkrmwPz+b5flppc5oPjBRXuXIpZMtIXTOdBosvmDowtYMlQhsGd9XzunoOBxUxKrjF2/5+fPqKDXIUiZSf1jDtR1QCuVX2ReWT/Ik4Da7va4Vj16VCsm8Dfid/mIFbMpEl<br>
X-Microsoft-Antispam-Mailbox-Delivery:<br>
<x-tab> </x-tab>
ex:0;auth:0;dest:I;ENG:(20160514016)(520000050)(520002050)(750028);<br>
<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 moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
eudora="autourl">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote>
<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">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>
<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>