<<<
Chronological Index
>>> <<<
Thread Index
>>>
[council] FW: GNSO Council Meeting 10 October 2013 / String Similarity Issues
- To: <council@xxxxxxxxxxxxxx>
- Subject: [council] FW: GNSO Council Meeting 10 October 2013 / String Similarity Issues
- From: "Jonathan Robinson" <jrobinson@xxxxxxxxxxxx>
- Date: Thu, 10 Oct 2013 14:40:06 +0100
- In-reply-to:
- List-id: council@xxxxxxxxxxxxxx
- Organization: Afilias
- References:
- Reply-to: <jrobinson@xxxxxxxxxxxx>
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: Ac7Fn6SnLH6g0BhxQDGT+Jm+jVueIAAHlBHw
All,
I have sent this information to Christine Willett in order to assist her
with preparing for today's council meeting.
Jonathan
-----Original Message-----
From: Jonathan Robinson [mailto:jonathan.robinson@xxxxxxxxxxx]
Sent: 10 October 2013 11:15
To: Christine Willett (christine.willett@xxxxxxxxx)
Cc: Akram Atallah (akram.atallah@xxxxxxxxx); Cyrus Namazi
(cyrus.namazi@xxxxxxxxx)
Subject: GNSO Council Meeting 10 October 2013 / String Similarity Issues
Dear Christine,
First, thank-you for agreeing to engage with the Council on this topic. In
this context, I thought it may be helpful to forward to you (See below) a
couple of emails on the subject of your participation.
Specifically, Thomas Rickert's question (which I expect he may ask on the
call, so it will be helpful if you are able to address it directly) seeks to
understand what is the scope of the GNSO Council's potential response.
Essentially, my sense is that Council recognises a problem, has drawn the
board's additional attention to it and is willing to assist in fixing it if
possible. But, in order for any Council initiative to be constructive, we
need to know the scope of what is possible from a legal perspective.
Therefore, as far as I can see it, the essence of the questions from the
GNSO Council will be along the following lines:
1. Has ICANN already come to a conclusion on how it will deal with the
apparent inconsistencies in outcomes?
(including when compared to one another and when referenced against
original, relevant GNSO policy) 2. Is there any (legal) advice that the
Council should consider when thinking about policy recommendations to remedy
the inconsistencies?
If we can get past 1 and 2 above, the Council may well be in a position to
recommend the formation of a group to rapidly address and suggest remedial
measures to deal with the apparent inconsistencies.
I trust that this is helpful additional information and context and look
forward to talking with you later today.
Best wishes,
Jonathan
-----Original Message-----
From: Thomas Rickert [mailto:rickert@xxxxxxxxxxx]
Sent: 06 October 2013 13:27
To: john@xxxxxxxxxxxxxxxxxxx
Cc: council@xxxxxxxxxxxxxx
Subject: Re: [council] Inviting Christine Willett to our next meeting
John,
I guess this is a good idea. I also think that it would be good if someone
could say something about the legal side of things that might impact / limit
the scope of the ways forward we may consider.
Thanks,
Thomas
Am 04.10.2013 um 17:46 schrieb john@xxxxxxxxxxxxxxxxxxx:
> Jonathan,
>
> In as much as we have a discussion of string confusion on our agenda and
that new gTLD program manager Christine Willett has recently discussed
ICANN's focus on "inconsistencies"
(http://www.icann.org/en/news/press/kits/video-willett-new-gtld-17sep13-en.h
tm) it might serve our understanding to have her participate.
>
> Cheers,
>
> Berard
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|