<html>
<body>
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 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 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" 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>
gnso-rds-pdp-wg@icann.org<br>
<a 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>
</body>
</html>