X-Apparently-To: [log in to unmask] via 206.190.49.197; Thu, 27 Apr 2006 07:23:24 -0700
X-Originating-IP: [192.0.35.121]
Authentication-Results: mta296.mail.mud.yahoo.com
  from=melbourneit.com.au; domainkeys=neutral (no sig)
Received: from 192.0.35.121  (EHLO greenriver.icann.org) (192.0.35.121)
  by mta296.mail.mud.yahoo.com with SMTP; Thu, 27 Apr 2006 07:23:24 -0700
Received: from greenriver.icann.org (greenriver [127.0.0.1])
	by greenriver.icann.org (8.12.11.20060308/8.12.11) with ESMTP id k3REKnv8023225;
	Thu, 27 Apr 2006 07:20:49 -0700
Received: (from majordomo@localhost)
	by greenriver.icann.org (8.12.11.20060308/8.12.11/Submit) id k3REKn18023224;
	Thu, 27 Apr 2006 07:20:49 -0700
X-Authentication-Warning: greenriver.icann.org: majordomo set sender to [log in to unmask] using -f
Received: from pechora2.icann.org (pechora2.icann.org [192.0.34.37])
	by greenriver.icann.org (8.12.11.20060308/8.12.11) with ESMTP id k3REKnoN023221
	for <[log in to unmask]>; Thu, 27 Apr 2006 07:20:49 -0700
Received: from melbourneit.com.au (mail.MelbourneIT.com.au [203.31.199.194])
	by pechora2.icann.org (8.13.6/8.13.6) with ESMTP id k3REKint029272;
	Thu, 27 Apr 2006 07:20:49 -0700
Received: from balius.mit (localhost.mit [127.0.0.1])
	by melbourneit.com.au (8.11.6/8.11.6) with ESMTP id k3REKha07068;
	Fri, 28 Apr 2006 00:20:43 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [gtld-council] Brussels Committee meeting on new gTLDs PDP - new dates Thursday 11 May 06 to Saturday 13 May 06 - and information on travel support
Date: Fri, 28 Apr 2006 00:20:54 +1000
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Brussels Committee meeting on new gTLDs PDP - new dates Thursday 11 May 06 to Saturday 13 May 06 - and information on travel support
thread-index: AcZpyLxdcKMWz0JtQtS9wl2Lo6mW8QAOCR7g
From: "Bruce Tonkin" <[log in to unmask]>
To: <[log in to unmask]>
X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on pechora2.icann.org
X-Virus-Status: Clean
X-MIME-Autoconverted: from quoted-printable to 8bit by greenriver.icann.org id k3REKnoN023222
Sender: [log in to unmask]
Precedence: discussion
Content-Length: 1811
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx3.syr.edu id k3RGvUZf029016

Hello All,

First my apologies for the delay in getting back to you with firm informa=
tion on dates and travel arrangements since my email last week:
http://forum.icann.org/lists/gtld-council/msg00102.html

There has been a lot of work going on behind the scenes by the ICANN staf=
f in finalising travel funding, meeting location, and dates.  Unfortunate=
ly since my last email, I found out that I would not be available to atte=
nd a meeting later in May due to other work commitments.  I have therefor=
e reverted to the alternative set of dates when most committee members se=
em to be available based on the information provided to the GNSO Secretar=
iat.   I realize that this is close the INTA conference May 6-10 in Toron=
to (http://www.inta.org/annual/2006/index.html ) that several Council mem=
bers will be attending, but hopefully they can either arrive a bit later,=
 or attend via teleconference.


The basic details are:

Dates: Thursday 11 May 06 to Saturday 13 May 06

Location: Renaissance Brussels Hotel
http://marriott.com/property/propertypage/BRUBR=20


Meeting purpose:=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

To complete work on Term of Reference 4 - "Policy to Guide Contractual Co=
nditions for New Top Level Domains" (see http://www.icann.org/announcemen=
ts/announcement-06dec05.htm) of the new gTLD policy development process (=
PDPDec05), so that we can complete an Initial Report by the ICANN meeting=
 in Marrakech, Morocco.


ICANN funding available:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

There will be ICANN funding for one member per constituency, one of =20
the nominating committee appointees to Council, plus funding for the =20
GNSO Committee Chair. =20

The funding will consist of economy class airfares,  hotel room, and lunc=
hes during the meeting.    Attendees will be responsible for their own br=
eakfast/ dinners and other incidental expenses.

The representatives from each constituency should decide which representa=
tive should receive funding for this meeting, and notify the GNSO Secreta=
riat (Glen de Saint G=E9ry).   Glen will then provide information on what=
 ICANN forms will need to be filled out to receive funding, and provide i=
nformation on how to arrange flights (e.g approved ICANN travel agency et=
c).

Please note that this funding is made available as a special case.  Any f=
uture funding of GNSO related meetings will need to be considered as part=
 of the ICANN operating plan for the 2006/2007 financial year, and approv=
ed by the ICANN Board as part of the normal budget approval process.


Audio-visual facilities for remote participation
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

There will be an audio conference link, Internet connection, and =20
projector at the meeting venue.  We will also be using remote =20
participation technology to enable Committee members who cannot attend in=
 =20
person to participate on line.   The ICANN staff are currently trialling =
a potential solution that meets the requirements identified so far, and a=
nyone wanting to participate in such trials prior to the meeting should c=
ontact the GNSO Secretariat.


Attendance:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

As per the Washington meeting, each constituency is entitled to have thre=
e representatives attend the meeting in-person and participate in the dis=
cussions.   The three nominating committee appointees to the Council are =
also welcome to attend.   In addition any members of the PDPFeb06 task fo=
rce are welcome to attend as observers.   =20

Other observers are possible, but space will be limited.  A recording wil=
l be made of the meeting, and any meeting materials will be made public.


Please confirm with the GNSO Secretariat your attendance -- either =20
remotely or in-person -- so logistical arrangements can be completed.

Regards,
Bruce Tonkin