ICANN/DNSO
DNSO Mailling lists archives

[nc-whois]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [nc-whois] Next steps.....


I could meet on Sunday, but after 4:30pm
Oscar

At 08:38 PM 10/21/2001, Cade,Marilyn S - LGA wrote:

Paul

I'm pleased to accept the teaming proposal you have put forward. thanks for
your continued leadership.

I'll continue to try to line up when folks are arriving,  and get a meeting
room in MdR... .

I do want to caution everyone that beginning 8:00 am. 11/12, some of us have
back to back commitments ---since we are elected reps to constituencies.

Let's try for a Sunday afternoon meeting a bit earlier than you suggested:
like in the p.m. Sunday for 2-3 hours-- I'd suggest maybe 3-6:00 p.m. or
4-6:00 p.m.  Let's see if we have critical mass for a working session, even
if all can't be available....

I suspect most of us already have dinner plans and working commitments on
Sunday to prepare for the rest of the week. 

And,  it's important to have this meeting before 11/12, so that we can
provide at least a preliminary report/status at the Constituencies and NC
meetings. 

If we can gather sufficient(5-6)of our members Sunday in this time, we
should proceed. Then, we can brief our other members before any public
discussions.

Then, perhaps we can find another hour later in the meeting.

Can folks reply once again about availability and arrival.


Marilyn


-----Original Message-----
From: Paul M. Kane [mailto:Paul.Kane@reacto.com]
Sent: Sunday, October 21, 2001 2:18 PM
To: WHOIS Committee - DNSO
Subject: [nc-whois] Next steps.....


Hello all

I am delighted we now have the raw data so we can start the review work.
I have taken a brief look and the format of the data will help us
considerably in the evaluation, and I see that ICANN has not "cleaned"
the data as there are three repetitive entries implying the sender had
some transit problems in sending in the data to the survey server.

Appreciating the desire to work in teams of two, a number of you have
asked that I select the teams at random ... so here goes....

Miriam    Danny
YJ           Marilyn
Oscar      Tony
Axel         Registrar's rep (TBA)

Next we need to determine the structure of the review.

May I ask each of you to review at least 100 responses (I would suggest
25/30 from each category batch) in advance of your meeting in LA so you
can (come prepared to) discuss the structure and framework of the
evaluation.
I would suggest a question by question assessment... remember our task
is to establish if there was consensus amongst the respondents on a
specific issue and/or where additional work should be undertaken, and
the form of that additional work item. Remember the raw data needs to be
divided amongst the group.

Due to contractual obligations I will be unable to attend LA, and I hope
the Registrar's Constituency will be able to appoint a representative to
the Committee so you can meet face to face in LA. Once the Registrar
elections are held I will be leaving the Committee so you also need to
think about the next Chair of the Committee.

As for the day of the meeting.  I have been asked to comment.... but as
I am not attending, I have no strong views. Sunday afternoon seems the
easiest to accommodate from a timetable perspective... as ICANN hasn't
started and most of  you will be in LA on Sun eve, but it could be that
(like MV) two meetings one at the start and one at the end of the ICANN
event may be beneficial ......
If a meeting were to be held on Sunday, what time would folks prefer,
how about .....

Sunday 6-00pm until 8-00pm (thereby leaving time for dinner meetings
etc...) - meet at the reception of the Marina Beach Marriott for the
details of the specific meeting room.

As mentioned I will not be there, so it is up to you all.... just that I
was asked to put a proposal on the table!

Best

Paul

        Saludos,

        Oscar Robles

Top Level Domain .MX            NIC-Mexico
Tel +52 (8)3875346 Fax 0183875346 ext 111
http://www.nic.mx

El contenido del presente mensaje de datos es confidencial. El Emisor no es apoderado de NIC-Mexico ni tiene facultad alguna para obligar a NIC-Mexico con la transmision y contenido del presente mensaje de datos, incluyendo el (los) archivo(s) anexo(s).


<<< Chronological Index >>>    <<< Thread Index >>>