Re: [gnso-rap-dt] RAPWG meeting agenda -- Monday 17 August at 14:00 UTC

[George Kirikos <icann+rap@xxxxxxxx>]

Hi folks,

On Thu, Aug 13, 2009 at 5:37 PM, Mike Rodenbaugh wrote:
>
> The cybersquatting group has not made any progress since the last call.  We
> did make progress on the last call itself though (or was it the call before
> that?).  Perhaps a better action item is to capture that progress and see
> where we are.
>
> Could Marika or someone else on Staff please go through the recording of
> that call, where we discussed the cybersquatting definition, and markup the
> wiki with summary of comments that were made on the call?

Those deliverables were due before August 3rd (i.e. last conference
call), and were assigned two conference calls ago (July 20), see:

http://forum.icann.org/lists/gnso-rap-dt/msg00256.html

"Cybersquatting group (Fred,, Mike R., James, Michael Y., Paul, Phil): put
existing material on the wiki and work on it there between now and next
call.  Add exclusions/defenses from UDRP and ACPA so as to note what
not considered cybersquatting."

Deliverables should actually be delivered early, in advance of calls,
so that folks can be productive during the conference calls, instead
of hearing something for the first time and having to immediately
react. This same topic came up on the GNSO council list, see:

http://gnso.icann.org/mailing-lists/archives/council/msg07154.html

"Let's assume we have consensus on instituting a rule of requiring
those doing a status report to submit it in advance. How long before
the meeting should they be required to do so?"

where we got the cheeky response:

http://gnso.icann.org/mailing-lists/archives/council/msg07156.html

"Q: How long before  the meeting should they be required to do so?
A: Target 7 days, latest 24 hours.

Q: Also what do we do if someone does not submit a report - allow them
to give it orally or just skip the report?
A: If staff, a hanging. If volunteers, a round of drinks for the
entire Council."

That's 6 people to do 1 little job. I think 6 rounds of drinks are
required (maybe more since that was as of 10 days ago!). :)

On a more serious note, during the last conference call, there was
deafening silence on writing up the front running topic. I said to
myself, "Sheesh, this can't be too hard." so I stepped up and
volunteered, took a few hours on the weekend to get the job done, and
delivered everything last Sunday afternoon:

http://forum.icann.org/lists/gnso-rap-dt/msg00299.html

8 days before the scheduled conference call to give everyone ample
time to review things and continue the mailing list discussions. This
wasn't some Herculean effort, it's just doing what was promised.

We have *34* people listed as being members of this workgroup:

https://st.icann.org/reg-abuse-wg/index.cgi?registration_abuse_policies_working_group

If everyone can't handle the work, especially work that they promised
to do, they should seriously consider dropping out, instead of trying
to reassign more work to Marika.

Marika does a fine job, and it's unfair to her to give her more work
to do when others aren't carrying their loads. She's the type of
hard-working trooper that would likely not say anything, and would do
the work anyway. So, let me say what she's too kind and generous to
say herself, namely that it truly is unreasonable to abuse her
generosity and turn her into the workgroup doormat!

It's now Thursday. If six people can't do what I did in only a few
hours in at most 1/3rd the time it took me, then something is really
wrong, especially since they've had *24 days* to work on it. I suggest
they simply go with the UDRP definition of cybersquatting and leave it
at that, as that's what the consensus definition has been. If we're
going to go down the road of redefining what cybersquatting is, you
can expect to find everyone giving their own personal "wish list"
items, which will only divert attention from this group's main work.

And I hope Marika (and other staff) enjoy their weekend (don't
overwork yourselves!).

Sincerely,

George Kirikos
416-588-0269
http://www.leap.com/