[Gnso-igo-ingo-crp] IGO PDP -- suggested text for recommendation language tweaks, and manually generated redline

Petter Rindforth petter.rindforth at fenixlegal.eu
Wed Jun 20 00:43:23 UTC 2018


Let's discuss this further on our WG meeting this Thursday.


Petter Rindforth, LL M

Fenix Legal KB
Stureplan 4c, 4tr
114 35 Stockholm
Fax: +46(0)8-4631010
Direct phone: +46(0)702-369360
E-mail: petter.rindforth at fenixlegal.eu

This e-mail message is intended solely for the individual or individuals to whom it is addressed.
It may contain confidential attorney-client privileged information and attorney work product.
If the reader of this message is not the intended recipient, you are requested not to read,
copy or distribute it or any of the information it contains.
Please delete it immediately and notify us by return e-mail.
Fenix Legal KB, Sweden, www.fenixlegal.eu
Thank you

20 juni 2018 02:24:33 +02:00, skrev George Kirikos <icann at leap.com>:

> Hi folks,
> During the last call, Phil suggested a redline of proposed changes
> would be desirable. I don't own software of my own that does this. I
> also searched for online tools that do this, but couldn't find
> anything suitable. But, I did attempt to create such "redline" text
> manually, and it's attached as a PDP.
> I started with Recommendation 2, since that was the 'easiest' (i.e.
> adding 4 words, to restrict things definitively to "trademark and
> service mark" rights).
> For Recommendation 1, I reordered and rephrased the existing
> recommendation slightly, for clarity. I also added the text that I
> thought should be in a recommendation that no specific new DRP be
> created for IGOs.
> Since some would rather keep Recommendation 1 limited only to INGOs, I
> then offered an alternative, namely adding it into Recommendation 3
> instead.
> Also, I'm not sure if folks noticed, but some text was deleted from
> Recommendation 3, compared to what appeared in January 2017. I pointed
> out phrases that we might want to put back, for clarity.
> I also found a possible error in how Recommendation 3 was worded,
> relative to the comparable text from January 2017. Back in January
> 2017, there was some text after a semi-colon (i.e. a separate
> thought), that somehow got merged now into the prior text, without any
> semi-colon. So, it doesn't make sense anymore to me. This stuff was
> non-controversial (i.e. the assignee, licensee, agent procedural
> guidance), but it kind of got mixed up with other text that was after
> the semi-colon.
> Sincerely,
> George Kirikos
> 416-588-0266
> <http://www.leap.com/>
> _______________________________________________
> Gnso-igo-ingo-crp mailing list
> Gnso-igo-ingo-crp at icann.org
> <https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-igo-ingo-crp/attachments/20180620/f0a7c64c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 20169 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-igo-ingo-crp/attachments/20180620/f0a7c64c/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 6210 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-igo-ingo-crp/attachments/20180620/f0a7c64c/attachment-0001.png>

More information about the Gnso-igo-ingo-crp mailing list