Re: [gnso-irtpd] here's the little summary of that sequence of events i rattled off on the call just now -- registrant role in TDRP
Thanks Rob and Mikey the one piece of the puzzle Mikey added was to work through what documentation would be required for the registrant to establish improper transfer of the domain name. One of the issues that has been raised is the possibility of a 'flood' of potentially vexatious complaints. So we need to have a check list of some sort to say that, if you the registrant are going to compliance, they will ask the following. Hopefully, it will both weed out potentially vexatious complaints and assist registrants with a genuine complaint in addressing their problem. Holly On 06/12/2013, at 12:06 AM, Rob Golding wrote:
can you expand on why you prefer the idea that Compliance get's involved over making a determination?
Depends on your definition of 'determination' - I more expect them to review things and prompt the registrar(s) as necessary (subject to previous posts about fees) if policy has not been followed.
Afterall isn't compliance role/remit to ensure that all registrars follow policy/process?
If a registrant thinks that is not what has been done, they already have the option(s) to talk to compliance (and we all know registrants regularly talk to them about complete nonsense/trivia anyway) .
just looking for ideas on what the appropriate role would be for Compliance, not trying to mousetrap you.
The appropriate role would be for them to do their job, just their job and only their job - and to apply/enforce those items of policy fairly and consistently across all registrars...
Rob
hi all, Marika and i came up with some ideas on moving this conversation forward. these ideas were battle tested and refined on the drafting subgroup call that happened this morning. see what you think. first, thanks all for the lively conversation this week. it helped me understand a few things better and shaped this scheme. here's the short version of the idea. let's: 1) develop a series of scenarios and use them to explore the boundaries of policy and roles. 2) acknowledge that there's a gap right now -- the implementation of registrant-transfer in IRTP-C. once this is further along we may find that there are other options that registrants can use pursue certain complaints, that the policy is insufficient, that additional mechanisms need to be developed, etc. in a sense, we're ahead of that process -- but we're also coming across issues that need to be fed into it. since we're ahead, we might as well document those things as we come across them. 3) also acknowledge that the TDRP is currently not very visible to registrants, nor do they understand either the policy or the role of registrars in implementing it. perhaps we can beef up the notification that registrars provide about the policy, and registrants options as to how they can proceed, especially at the time when a registrant comes to the registrar with a problem. here's some more detailed material about the "scenarios" idea. when building our scenarios, let's use these dimensions for starters. you're encouraged to invent more dimensions, by the way. - policy - existing IRTP/TDRP clearly applies - "inter registrant transfer" version of IRTP clearly applies - ICANN policy clearly does NOT apply - murky puzzler - parties - disputes entirely between registrants - disputes entirely between registrars - disputes between registrants where registrars may be a party to the dispute - disputes between registrars where registrants may be a party to the dispute - murky puzzler - role of ICANN Compliance - Compliance clearly has a role under existing IRTP/TDRP policy - Compliance could have a role under the "inter registrant transfer" version of IRTP - Compliance clearly does NOT have a role under any circumstance - murky puzzler let's run a few scenarios through that sifter and see whether this is getting us anywhere. i'm hopeful. thanks all, mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)
participants (2)
-
Holly Raiche -
Mike O'Connor