<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [council] Some initial reactions from the ccNSO on the GNSO's message to Board regarding IDN TLDs
- To: "'Council GNSO'" <council@xxxxxxxxxxxxxx>
- Subject: RE: [council] Some initial reactions from the ccNSO on the GNSO's message to Board regarding IDN TLDs
- From: "Mike Rodenbaugh" <mxrodenbaugh@xxxxxxxxx>
- Date: Tue, 15 Jan 2008 10:24:19 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language; b=BI3Gcti70rZvEfLdYl5ekCZOqTLy91B+oraStSZnYZBIrVIV7is1oabrKR0Hel3Va7kHQKtYy5n2I9/mzwqpanazXN8vI0HnPt9Mu8OY51Jw+s8nSWv+4D43s3PAK34o0MMAWnTWF9KpP0DMG2zt07R0a3fgIxTkrqkFohX5v+8= ;
- In-reply-to: <046F43A8D79C794FA4733814869CDF07021DB2A8@dul1wnexmb01.vcorp.ad.vrsn.com>
- List-id: council@xxxxxxxxxxxxxx
- References: <CCBFEBFD-FB82-4A03-BBF7-1DCFF015E6B7@psg.com> <046F43A8D79C794FA4733814869CDF07021DB2A8@dul1wnexmb01.vcorp.ad.vrsn.com>
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: AchXVcfLOYPrLgxqQaa1zmMd/Di/aAANsDOgAAW5UtA=
Both points sound like good ideas to me.
Noting Chuck's valid point about overlapping meeting schedules, not to
mention the heavy workload already expected of Councilors, perhaps an ICANN
Staff policy expert would be the best liason?
-Mike
-----Original Message-----
From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx] On
Behalf Of Gomes, Chuck
Sent: Tuesday, January 15, 2008 7:46 AM
To: Avri Doria; Council GNSO
Subject: RE: [council] Some initial reactions from the ccNSO on the GNSO's
message to Board regarding IDN TLDs
Both ideas sound good to me.
With regard to the liaison idea, one of the things we should probably
start thinking about is whether the GNSO liaison to the ccNSO should be
a GNSO Councilor or not. On the one hand it seems like it would be
easiest if our liaison was selected from one of the Councilors. But
during in-person meetings at ICANN regional meetings, GNSO meetings
typically conflict with ccNSO meetings; conflicts could also happen for
teleconference meetings. In cases like that it might be desirable to
have a liaison who was not a Council voting member but who could
participate as an observer in all GNSO meetings when there is not a
conflict. Obviously, this issue needs a lot more thought and discussion
but thought it might be helpful to start it off.
Chuck
-----Original Message-----
From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx]
On Behalf Of Avri Doria
Sent: Tuesday, January 15, 2008 3:59 AM
To: Council GNSO
Subject: [council] Some initial reactions from the ccNSO on the GNSO's
message to Board regarding IDN TLDs
Hi,
I have been having some background discussions with Chris Desspain, the
chair of the ccNSO council, and others regarding the GNSO
council's message and request to the Board. At, at least, the first
reading, there has been some level of concern on his part and the part
of others in the ccNSO community with our message to the Board relating
to IDN TLDs. It has been interpreted by some as indicating that the
GNSO is against the fast track and against IDNs. While I tried to
explain that this is neither what was written nor what was intended, it
does seem to be interpreted that way by some. The ccNSO
is meeting today to discuss a reaction to the GNSO council's message.
I expect to have more information on that tomorrow.
Regardless of what happens with their reaction two possibilities have
come out of the discussion:
- the possibility of a face to face meeting between the two councils in
New Delhi to discuss some of the different perspectives on the IDN TLD
issue
- the exchange of liaisons between the two councils, so that in the
future there would be a better understanding of each others intentions,
processes and decisions.
I would like to find out if there is support for these two items among
others on the council.
thanks
a.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|