Subject: GA-DIGEST V1 #241
From: [email-masked] (GA-DIGEST)
To: [email-masked]

GA-DIGEST          Friday, February 16 2001          Volume 01 : Number 241

----------------------------------------------------------------------

Date: Thu, 15 Feb 2001 15:40:41 -0800
From: Jeff Williams <[email-masked]>
Subject: [ga] ICANN hearings. Take in the EU -Net governing body slammed from within

All,

  FYI.

http://news.bbc.co.uk/hi/english/sci/tech/newsid_1171000/1171793.stm

  Looks like Karl Aeurbach has gotten some media attention in the EU
as well....  This one is a well written and more detailed article than
some of the others I have read thus far.

Regards,

- --
Jeffrey A. Williams
Spokesman INEGroup (Over 112k members strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail [email-masked]
Contact Number:  972-447-1800 x1894 or 9236 fwd's to home ph#
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208

- --
This message was passed to you via the [email-masked] list.
Send mail to [email-masked] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html

------------------------------

Date: Thu, 15 Feb 2001 18:18:19 -0800
From: Jeff Williams <[email-masked]>
Subject: [ga] Update on IDNO web site and Mailing list

All,

 Contrary to Karl Peters earlier alarmist post to the contrary, the
following is the best information I have on the IDNO web site
outage and mailing list outage:

  For those of you that are IDNO members and on this list or are
interested parties of various sorts, the IDNO web site is down
until Dave Farrar takes it over.  The Mailing list is having its
software (Mailman?) upgraded.  As I understand it form Joop,
when these two tasks are completed, the web site will be back
up again.

  Let us all hope that in the future the IDNO will be a improved and
inclusive organization that will be rid of it's past hecklers and
alarmist that seem to have plagued it of late.

  I also want to take the time to thank Joop for privately updating me
at my private request on this occurrence in much more accurate
fashion.  Thank you Joop!  >;)

Kindest regards,

- --
Jeffrey A. Williams
Spokesman INEGroup (Over 112k members strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail [email-masked]
Contact Number:  972-447-1800 x1894 or 9236 fwd's to home ph#
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208

- --
This message was passed to you via the [email-masked] list.
Send mail to [email-masked] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html

------------------------------

Date: Fri, 16 Feb 2001 00:40:14 -0500
From: "Ben Edelman" <[email-masked]>
Subject: Re: [ga] Draft of Bylaws Recommendation concerning the General Assembly

(Note that I have received Kendall's 2/13 comments.  Am thinking about them,
and about possible adjustments that might respond to his suggestions.  Hope
to provide a response within the next few days.)

In Joanna's last message, she made, to my eye, four major suggestions:

1) Displaying the chat room on screen.

2) Increased fairness and even-handedness in selecting remote comments.

3) Accepting remote comments in advance of the start of the meeting.

4) Increased reliance on multimedia participation, perhaps via 6-10 folks
selected to participate in some special way for the occasion.

I'd like to respond to each suggestion in turn.

1) Re displaying the chat room on screen:

First, I hadn't previously understood that you were proposing to show the
chat room, rather than the remotely-submitted text comments (which, as you
may recall, are in a separate system -- web form submissions of longer
length and easier editing than is usually characteristic of a chat client).
Accordingly, you'll notice that my last message speaks only to the question
of displaying submitted text on screen, not the chat room specifically.

Now that I better understand your suggestion, some further responses:

* My "distraction" comment from the prior message stands, and I stand by it
even more forcefully than I did in the prior instance, even as I understand
that you are not convinced by this reasoning.  Again, based on prior
experience, when I did this in multiple prior meetings, I believe this is
distracting to at least some attendees.  There's just something different
about an in-person meeting (where the usual norm is to concentrate on the
one person talking) versus a webcast via computer (where the medium seems to
call out for multiple means of participation).

* The chat room really isn't intended to be a place of substantive,
on-the-record deliberation.  The introduction text viewed upon entrance to
the chat room says so pretty clearly.  And much of the discussion in the
chat rooms, in my experience (and as the logs reflect), is quite
nonsubstasntive.  I'm not anxious to project chat room comments re audio
problems, login problems, and the other various glitches that some folks
experience at various points in the meeting; it just doesn't seem helpful to
the work at hand.

* I'm concerned that the stream-of-consciousness tone of the chat room isn't
appropriate in the setting of the in-person public meeting.  Furthermore,
general and enduring display of such messages might cause the in-person
participants not to take remote participants seriously.  Instead, I think
remote participation might be better received if remote participants
contributed occasional well-thought-out comments, rather than continuing
marginally-on-topic banter, for lack of a better word, which truly has been
my experience in prior meetings.  (That is, in my experience, the chat room
comments often stray from the discussion in the in-person meeting, and I'm
not sure that's helpful on balance.)  Ultimately, the chat room just doesn't
seem consistent to me with the tone of a public meeting, with the tone of
the speakers at the microphone, and with the expectations of those attending
the meetings in person.

* On some occasions, we've had some pretty serious violations of chat room
policy -- personal attacks, flames, obscene comments, etc.  I've never had
to ask anyone to leave the chat room, nor to remove anyone using the
technical means at my disposal, but I've come close (issuing "this is your
second and final warning" messages).  Again, this sort of thing isn't
appropriate for display to the general audience, and neither would it be
helpful in that context.  It's all fully & publicly archived if anyone is
interested, but projecting it just doesn't make sense to me.

2) Re increased fairness and even-handedness in selecting remote comments.

Your comments here, as well as Kendall's, raise a serious set of questions,
to which I hope to reply at some length, pending further discussion among my
team, as well as other personal obligations (other work to be done!) and
some further investigation re our technical capabilities.  That said, here's
what immediately comes to mind.

You wrote:

> The principle is that remote participation should not be manipulated
> unnecessarily as this gives false feedback to those in the public
auditorium
> about the nature and extent of online commentary.

Certainly I don't think of the current selection process as "manipulation,"
so I think some commentary is in order here.

When in November 1998 I first wrote the code that is the basis of the remote
participation system still in place today, my goal was simple: to take
public comments, in real-time, in a way that hadn't been possible at the
IFWP meetings that preceded ICANN's formation.  It seemed immediately clear
to me that we'd get more online comments than we'd have time to read, and
indeed this proved true in every ICANN meeting.  But simply reading the
first few comments was clearly an unacceptable methodology; after all, that
would encourage a race to submit comments as early as possible, clearly (I
thought) an undesirable outcome.

In response to concern about how to select questions to answer, two
significant systems were put in place: First, a "meeting section" selection
box -- in which users would self-classify their comments to map to agenda
items on a drop-down list.  The "ask a question" screen clearly reports
which section is currently in progress, and the Remote Participation Liaison
chooses comments for a particular section's Audience Q&A session exclusively
from the comments marked for that section.  Second, a Remote Participation
Liaison was carefully selected and trained -- in the first instance by
Jonathan Zittrain, the Berkman Center faculty member working on the Center's
initial remote participation efforts -- to select comments solely for their
clarity and relevance to current discussion, but not for a particular
substantive position, one way or the other.  That's not to say that our
efforts on that front have been successful in every instance -- I imagine
there are plenty of allegations that they have not! -- but it was certainly
our goal, I hope pretty clearly articulated in the documentation &
instructions for the remote participation system.

Kendall suggested an interesting alternative way to select comments -- some
variation of a vote by online participants.  I'm still investigating the
feasibility & practicality of doing so, as well as other concerns like fraud
control, perceived fairness, etc.  Again, a response on all this is
forthcoming.

3) Accepting remote comments in advance of the start of the meeting.

You wrote:

> ... I would think about requesting some questions and comments through
> the GA list, submitted in advance.

We have considered this in the past, but have ultimately concluded that it's
not the best way to proceed.  ICANN and the DNSO maintain numerous methods
of receiving comments from online participants in non-real-time contexts --
public mailing lists (including this one), the ICANN public comment boards,
messages sent directly to staff, Board Members, NC members, constituency
representatives, etc.  It's certainly not the intention of the webcast
efforts to replace or compete with any of these systems, and we don't seek
to do so.  Accordingly, our rule, since the November 1998 meetings, has been
to accept only real-time (not presubmitted) comments.  In practice we'll
accept any comment meeting the length requirement (less than 1000
characters -- roughly the amount we can display on a single projection
screen in a large font) and have no way of knowing when a remote participant
actually drafted the comment.  But the responsibility is on the remote
participant to submit a comment during the meeting if it is to be treated as
a comment submitted to the meeting itself, as distinguished from the
non-realtime comment-receiving systems.

For whatever it's worth, this is (as best I can remember) the first time
I've received this comment, i.e. the suggestion that presubmitted comments
should be accepted along with "live remote participant" comments.  My sense
previously was that everyone thought it was a good idea to require that
comments be submitted during the meetings; no one has ever said otherwise.

> If not, you have the task of selecting
> questions on the fly, while trying to ensure a fair and even handed input,
> without knowing what's going to hit the screen next, or when you're going
to
> get a decent comment to read out.  This is not a trivial matter.

I'm a little confused about what you mean here.  I think you may be
confusing the live chat room (an "IRC chat," like an AOL chat room or some
such) with the remote comment submission system (web forms that submit text
to a database).  Our remote participation liaison can readily review all
messages in the database, can mark messages for (one-button) display on the
projection screen, can classify messages according to a variety of criteria
(whether or not read yet, meeting section if not so classified by the
submitter, etc.), and can generally keep pretty good track of what's going
on.  I'd like to think that we do know quite well what's going to hit the
screen next!  (Indeed, each comment is displayed on-screen while it's
read -- as the scribe's notes generally reflect, i.e. "remote comment #1234
from Tom Smith read in its entirety and displayed on screen" might be
entered into scribe's notes when that is the case).

In terms of fairness and evenhandedness, I understand the concern here, and
agree that it's a serious one.  But please understand the other issues we
also face here: For example, I hope you appropriately consider the concern I
expressed in my last message about reading & presenting off-topic messages
(perhaps "stale" -- read too late, i.e. after the topic in question was
discussed by the meeting -- or perhaps inherently off-topic).  Doing so
causes the audience to literally cringe, in my experience, as if to say "Why
are those Berkman Center people so dumb as to read us a question about
*that*, when we just finished discussing it, and were all quite tired of the
topic after such a prolonged discussion of the subject?"  For this reason,
and for others too (ad hominem attacks, questions not appropriately
addressed to the current meeting or group, messages submitted from what
immediately seem to be false identities, etc.), we've come to think that any
automated way of selecting comments is likely to be undesirable for other
reasons, notwithstanding the underlying desirability of an automated way of
choosing messages to be read aloud.  Again, I look forward to responding to
Kendall's suggestion on this subject, and so I'd propose to bracket this
discussion for the moment.

> We could aim for consensus in the GA as to the topics that need
highlighting
> in this way. Questions could be supplemented or even substituted by live
> comments on the day if desirable, but it would give the online
participation
> some much needed structure and ensure quality questions are heard on a
wide
> range of topics at agreed points in the schedule, interwoven with those
from
> the audience (some of which I'm sure are prepared in advance).  I'd be
very
> surprised if a call for questions did not receive a very positive response
> from the GA list over say a 2 week period.

Certainly any effort to increase GA participation both in the GA's physical
meeting and in other ICANN sessions seems to me highly desirable, and I
applaud such attempts.

If these attempts are successful and lead to insightful and clearly-stated
questions closely related to the topics under discussion on the various
meeting agendas, I'm confident that the remote participation liaison will
properly present these messages to the assembled group.

My sense in prior meetings has been that, in general, the liaison is usually
successful in presenting a reasonable range of messages, giving appropriate
recognition to major topic areas of the submitted questions and reading a
substantial portion of the messages received.  I know that there have been
instances when this has not been the case -- when public comment (both
in-person and via remote participation) has been cut short due to shortness
of time, or when the meeting chair has used his or her prerogative to
recognize disproportionately many in-person commenters.  (Incidentally, I do
continue to believe remains a significant factor to keep in mind -- the
assembled group, and the queue at the microphone, can prove quite a force to
be reckoned with, given their physical presence, travel expenses incurred,
and general immediacy, especially as against a seemingly invisible and
distant online audience.  I continue to suggest to the chair of each meeting
that a remote comment be recognized after every two microphone comments, and
at times we've gotten into an excellent rhythm this way.  But the underlying
issue surely remains.)

4) Increased reliance on multimedia participation, perhaps via 6-10 folks
selected to participate in some special way for the occasion.

You wrote:

> ... Also, two
> contributors are not sufficient in number to establish this format as part
> of the process, hence it is easily reduced to an irritant in the
> proceedings. My suggestion would be to have 6-10 contributors, as the
> schedule allows, either interwoven at regular intervals or introduced as a
> block, but all using the same screen, speaking individually in rotation.

Can you propose a specific technical means (hardware and software) for doing
so?  At the moment I'm a bit unclear on what specifically you're talking
about -- videoconferencing, or something else.

How would we choose the 6-10 contributors?  No one gets a similarly-favored
position in the physical meeting, so I'd be concerned that this approach
might not receive the support of physical meeting attendees.

Again, I thank everyone on this list for their suggestions.  I remain
interested in further comments -- everything from improving the wording of
web pages announcement emails to more far-reaching comments like the ideas
submitted so far.  I certainly can't promise that the Berkman Center will do
everything that's suggested here -- but we're listening, and, we think,
thinking seriously about these issues.

Ben Edelman
Berkman Center

- --
This message was passed to you via the [email-masked] list.
Send mail to [email-masked] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html

------------------------------

Date: Fri, 16 Feb 2001 12:46:30 +0800
From: "McMeikan, Andrew" <[email-masked]>
Subject: RE: [ga] NC telecon, 24 January 2001, minutes

This is a multi-part message in MIME format.
- --------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	charset="iso-8859-1"

I just thought I would voice an opinion for consideration about
constituencies.

Not all constituencies are the same, some are bigger some are smaller, some
are to represent interests that have a lot of money at stake and others
might represent volunteers, non-profit organizations or individuals.

To say you have a bill of $107,600 and divide by the number of
constituencies (either the 7 now or pro-rata) is to ignore the distinction
between the number of groups and the number of people within those groups.
Some might prefer to compare dollars within each group for that comparison.

Each constituency will have a different ability to pay, according to its
members ability to pay.  To demand a fixed payment, whether the payment is
constituency membership fees or DNSO dues is running the sever risk that
representation will be excluded to those who may most need it.

The whole goal is bottom up.  Collect what is possible, accept what can be
given in excess, a best effort should cover expenses.  Collect what can be
paid then *don't spend more* 

I urge that everyone who has some webspace (which is probably in the vast
majority of this assembly) put up a page where visitors can make a donation
because it does take money to keep things happening and the smaller the
constituency the more important it will be to be seen and to get general
public support.

For an example donation page feel free to copy http://opendesign.cx/gold.htm
and change to suit your account and link details, many other methods are out
there, if the presumption that representation is going to require $15,371
continues then those without access to lots of money better start worrying
where they will be heard.

Imagine you bleed money out of your constituency, get recognized, pay your
dues, put forward the concerns represented and yet there is not any
certainty about what would happen next.  There is nothing preventing the
situation of the following groups (example only but indicative of the lack
of non-commercial representation in the real world) setting up,
IP-lobby,music-recording-lobby,movie-lobby,consumer-goods-makers-lobby,conte
nt-renter-lobby all with lots of common members, all paying lots of money
towards having their voice in as many places as possible.  This is of course
getting into the "Education and Outreach"

Anyway I had to get that off my chest, if I am grossly mistaken somewhere
please point it out.

	cya,	Andrew...

> -----Original Message-----
> From:	DNSO Secretariat [SMTP:[email-masked]]
> Sent:	Thursday, February 15, 2001 11:39 PM
> To:	[email-masked]
> Subject:	[ga] NC telecon, 24 January 2001, minutes
> 
> [ To: [email-masked]
> [ To: [email-masked], [email-masked] ]
> 
> [ cf. http://www.dnso.org/dnso/notes/20010124.NCtelecon-minutes.html ]
> 
> 
> ICANN/DNSO
> 
>        DNSO Names Council Teleconference on 24 January 2001 - minutes
>   ------------------------------------------------------------------------
> 
> 24 January 2001 
> 
<snip>
>                In order to meet expenses amounting to $ 107,600 and
>                expecting the number of DNSO Constituency staying unchanged
>                (7) due per Constituency for 2001 will amount to $15,371.
> 
<list/webserver vs translation snip>

>           Ph. Sheppard asked for the clarification as to the increase of
>           Constituency dues.
> 
>           K. Stubbs responded that this budget is based on existing
>           Constituencies and any newly formed Constituency will pay its
> due
>           on pro rata based conditions.
> 
>           D. Vandromme reiterated his request, already made at the Marina
>           del Rey meeting for a 50% reduction for Non Commercial
>           Constituency due.
> 
>           The NC has taken a note of this request.
> 
>           L. Touton inquired if there is a practical report on voluntary
>           funding.
> 
>           R. Cocheti recalled the NC decision to accept voluntary
> donations.
>           Budget Committee will submit a complete plan on how to employ
> this
>           part of the revenue later.
> 
>           P. Kane suggested that NC examine specific expenses in more
>           details and takes budget expenses listed here as information.
> 
>           R. Cochetti restated that these are only budgetary category
> items,
>           and when the NC will have a professional support the more
> specific
>           financial reports will be provided regularly.
> 
>           First attempt to vote on the budget failed and those who have
>           abstained provided explanation of their vote:
>              + D. Vandromme: cannot commit the Non Commercial constituency
>                with such a high due.
>              + Ph. Sheppard: Budget Committee reached a decision in
>                principle on an assumption to collect the 2001 dues from
> the
>                Constituencies who have not paid their 2000 dues yet.
>              + H. Hotta: due to his late arrival has not had a chance to
>                follow a discussion.
> 
>           E. Roberts suggested taking separate votes on constituencies'
> dues
>           and on indicative budget for year 2001.
> 
>           R. Cochetti disagreed explaining that those two points are
> linked
>           as we have to start collecting the money and start sending out
>           invoices for year 2001.
> 
>           K. Stubbs called the NC to vote on a Budget Committee report:
> 
>           The motion did not pass: with 7 votes in favour (de Blanc,
>           Porteneuve, Caray, Cochetti, Stubbs, Chicoine, Aus der Muhlen),
> 9
>           abstentions (Sheppard, Hotta, Harris, Schneider (by proxy)
>           Swinehart, Roberts, Kane, Park, Vandromme), and no vote against.
> 
<big snip of the rest>

- --------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="InterScan_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="InterScan_Disclaimer.txt"

- ------------------------------------------------------------
The information transmitted is intended for the person or entity to 
which it is addressed and may contain confidential and/or privileged 
material. Any review, retransmission, dissemination, copying or other 
use of, or taking any action in reliance upon, this information by 
persons or entities other than the intended recipient is prohibited. If 
you have received this in error, please contact the sender and delete 
the material from your system. Logica is not responsible for any
changes made to the material other than those made by Logica or for
the effect of the changes on the meaning of the material. 

- --------------InterScan_NT_MIME_Boundary--
- --
This message was passed to you via the [email-masked] list.
Send mail to [email-masked] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html

------------------------------

Date: Fri, 16 Feb 2001 18:01:48 +1100
From: "Dassa" <[email-masked]>
Subject: RE: [ga] NC telecon, 24 January 2001, minutes

Hello Andrew

Whilst I agree some form of pro-rata system may work with regards to the payment of any dues levied against the Constituencies, there will then be some concern that larger Constituencies with higher members will be paying more and should have more of a say.  Whilst I agree with this personally, others find the notion disagreeable.

Personally, I would like to see any fees based on the membership numbers and the number of representatives allowed on the NC also in line with both the fee and membership numbers within the Constituencies.  There should be a cap on the level of fees and representation allowed from any one Constituency.

So all in all, I think we are in some agreement.

Darryl (Dassa) Lynch.

|>-----Original Message-----
|>From: [email-masked] 
|>On Behalf Of McMeikan, Andrew
|>Sent: Friday, February 16, 2001 3:47 PM
|>Subject: RE: [ga] NC telecon, 24 January 2001, minutes
|>
|>
|>I just thought I would voice an opinion for consideration about
|>constituencies.
|>
|>Not all constituencies are the same, some are bigger some are smaller, some
|>are to represent interests that have a lot of money at stake and others
|>might represent volunteers, non-profit organizations or individuals.
|>
|>To say you have a bill of $107,600 and divide by the number of
|>constituencies (either the 7 now or pro-rata) is to ignore 
|>the distinction between the number of groups and the number of people within 
|>those groups. Some might prefer to compare dollars within each group for 
|>that comparison.
|>
|>Each constituency will have a different ability to pay, 
|>according to its members ability to pay.  To demand a fixed payment, whether 
|>the payment is constituency membership fees or DNSO dues is running the 
|>sever risk that representation will be excluded to those who may most need it.
|>
|>The whole goal is bottom up.  Collect what is possible, 
|>accept what can be given in excess, a best effort should cover expenses.  
|>Collect what can be paid then *don't spend more* 
|>
|>I urge that everyone who has some webspace (which is probably 
|>in the vast majority of this assembly) put up a page where visitors can 
|>make a donation because it does take money to keep things happening and the 
|>smaller the constituency the more important it will be to be seen and to 
|>get general public support.
|>
<<SNIP>>

- --
This message was passed to you via the [email-masked] list.
Send mail to [email-masked] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html

------------------------------

Date: Fri, 16 Feb 2001 02:43:43 -0500
From: Sotiropoulos <[email-masked]>
Subject: Re: [ga] Draft of Bylaws Recommendation concerning the General Assembly

Ben Edelman wrote:
>
> Now that I better understand your suggestion, some further responses:
> 
> * My "distraction" comment from the prior message stands, and I stand by it
> even more forcefully than I did in the prior instance, even as I understand
> that you are not convinced by this reasoning.  

Ben, I will make cause with Joanna on this one. 
Your reasoning is your own, and you've a right to
it, no doubt.  However, I disagree with your
position, and I fully support Joanna's proposal,
seconding her motion/move/whatever.  I think it's
an excellent idea, and one that should be (and
ultimately, will be) put into practice, to one
degree or another.  There's plenty of ways to do
this, which will also ensure widespread
participation and interest in the proceedings. 
This *is* the Internet we're dealing with here... 
If the pattern holds, opinions/questions will
probably be put forward by those bold enough to
pipe up on the text chat.  I conjecture that it
may indeed be possible to conduct an orderly
remote text chat participation, and there's still
plenty of time to examine the options.  At least,
we should be open-minded.  Also, think of the
positive publicity of just giving it a shot! 
Surely ICANN could use some inspiring news?

>Again, based on prior
> experience, when I did this in multiple prior meetings, I believe this is
> distracting to at least some attendees.

Ben, the truth is, that much more is at stake than
a few audience-seats in an auditorium.  

>There's just something different
> about an in-person meeting (where the usual norm is to concentrate on the
> one person talking) versus a webcast via computer (where the medium seems to
> call out for multiple means of participation).

Which is why we must incorporate every means at
hand to foster participation, education, and
outreach as much as we're able.  I believe it is
possible to work out a schema which could include
what Joanna has proposed. This gesture would go a
long way, believe it.
 
> * The chat room really isn't intended to be a place of substantive,
> on-the-record deliberation.  The introduction text viewed upon entrance to
> the chat room says so pretty clearly.  And much of the discussion in the
> chat rooms, in my experience (and as the logs reflect), is quite
> nonsubstasntive.  

Again, Ben, this is your opinion.  If there are
others who agree with you, let them come forward
and speak on it.  I, myself, agree with Joanna's
perspective and not yours.

>I'm not anxious to project chat room comments re audio
> problems, login problems, and the other various glitches that some folks
> experience at various points in the meeting; it just doesn't seem helpful to
> the work at hand.

Perhaps we could find ways and means that would
share out the burden?  Mayhap such avenues should
be explored? 

> 
> * I'm concerned that the stream-of-consciousness tone of the chat room isn't
> appropriate in the setting of the in-person public meeting.  Furthermore,
> general and enduring display of such messages might cause the in-person
> participants not to take remote participants seriously. 

Again, your opinion, unless others speak up. 
There are ways to circumvent possible misuse or
treatment of this option, including active weeding
of the forum.  Such a schema could easily be
devised within the telephony program firetalk with
its rather remarkable remote forum capacities. (I
was actually a witness to their first official
firetalk welcome forum, at which there was an
audience of up to 500 persons at a time, all
listening to the speakers, and having the
possibility of engaging in text chat with one
another, as well as the ability to send questions
to the presenting panel.  Of course, none of the
audience had speaking privileges.  The event was a
flying success!  I was a participant, so I am
telling you all that I experienced this first
hand.)  Anyway, I have contacted one of the
functionaries from the company and they would be
interested in exploring the issue, should anybody
here be interested in coordinating.

> Instead, I think
> remote participation might be better received if remote participants
> contributed occasional well-thought-out comments, rather than continuing
> marginally-on-topic banter, for lack of a better word, which truly has been
> my experience in prior meetings.  (That is, in my experience, the chat room
> comments often stray from the discussion in the in-person meeting, and I'm
> not sure that's helpful on balance.)  Ultimately, the chat room just doesn't
> seem consistent to me with the tone of a public meeting, with the tone of
> the speakers at the microphone, and with the expectations of those attending
> the meetings in person.

I'm unsure as to why you keep speaking about the
"expectations of those attending
the meetings in person" as a cause for trepidation
in an overall move toward a  more inclusive
process.  Does it really come down to auditorium
comfort?
 
> * On some occasions, we've had some pretty serious violations of chat room
> policy -- personal attacks, flames, obscene comments, etc.  I've never had
> to ask anyone to leave the chat room, nor to remove anyone using the
> technical means at my disposal, but I've come close (issuing "this is your
> second and final warning" messages).  

The firetalk system would allow us to cut out this
element entirely, and still be able to present
effective "real-time" participation efforts from a
significantly wider audience.  I would be more
than interested in exploring its application with
you.  

>Again, this sort of thing isn't
> appropriate for display to the general audience, and neither would it be
> helpful in that context.  It's all fully & publicly archived if anyone is
> interested, but projecting it just doesn't make sense to me.

Oh, and I fully agree... 
 
> 2) Re increased fairness and even-handedness in selecting remote comments.
> 
> Your comments here, as well as Kendall's, raise a serious set of questions,
> to which I hope to reply at some length, pending further discussion among my
> team, as well as other personal obligations (other work to be done!) and
> some further investigation re our technical capabilities.  That said, here's
> what immediately comes to mind.
> 
> You wrote:
> 
> > The principle is that remote participation should not be manipulated
> > unnecessarily as this gives false feedback to those in the public
> auditorium
> > about the nature and extent of online commentary.
> 
> Certainly I don't think of the current selection process as "manipulation,"
> so I think some commentary is in order here.
> 
> When in November 1998 I first wrote the code that is the basis of the remote
> participation system still in place today, my goal was simple: to take
> public comments, in real-time, in a way that hadn't been possible at the
> IFWP meetings that preceded ICANN's formation.  It seemed immediately clear
> to me that we'd get more online comments than we'd have time to read, and
> indeed this proved true in every ICANN meeting.  But simply reading the
> first few comments was clearly an unacceptable methodology; after all, that
> would encourage a race to submit comments as early as possible, clearly (I
> thought) an undesirable outcome.
> 
> In response to concern about how to select questions to answer, two
> significant systems were put in place: First, a "meeting section" selection
> box -- in which users would self-classify their comments to map to agenda
> items on a drop-down list.  The "ask a question" screen clearly reports
> which section is currently in progress, and the Remote Participation Liaison
> chooses comments for a particular section's Audience Q&A session exclusively
> from the comments marked for that section.  

All of this can be done much more efficiently in a
firetalk forum.  I appreciate your structure, and
I think we can effectively apply it to
firetalk.    

Second, a Remote Participation
> Liaison was carefully selected and trained -- in the first instance by
> Jonathan Zittrain, the Berkman Center faculty member working on the Center's
> initial remote participation efforts -- to select comments solely for their
> clarity and relevance to current discussion, but not for a particular
> substantive position, one way or the other.  That's not to say that our
> efforts on that front have been successful in every instance -- I imagine
> there are plenty of allegations that they have not! -- but it was certainly
> our goal, I hope pretty clearly articulated in the documentation &
> instructions for the remote participation system.
> 
> Kendall suggested an interesting alternative way to select comments -- some
> variation of a vote by online participants.  I'm still investigating the
> feasibility & practicality of doing so, as well as other concerns like fraud
> control, perceived fairness, etc.  Again, a response on all this is
> forthcoming.

I will continue to maintain that firetalk can
solve all of these issues.
 
> 3) Accepting remote comments in advance of the start of the meeting.
> 
> You wrote:
> 
> > ... I would think about requesting some questions and comments through
> > the GA list, submitted in advance.
> 
> We have considered this in the past, but have ultimately concluded that it's
> not the best way to proceed. ICANN and the DNSO maintain numerous methods
> of receiving comments from online participants in non-real-time contexts --
> public mailing lists (including this one), the ICANN public comment boards,
> messages sent directly to staff, Board Members, NC members, constituency
> representatives, etc.  It's certainly not the intention of the webcast
> efforts to replace or compete with any of these systems, and we don't seek
> to do so.  Accordingly, our rule, since the November 1998 meetings, has been
> to accept only real-time (not presubmitted) comments.  In practice we'll
> accept any comment meeting the length requirement (less than 1000
> characters -- roughly the amount we can display on a single projection
> screen in a large font) and have no way of knowing when a remote participant
> actually drafted the comment.  But the responsibility is on the remote
> participant to submit a comment during the meeting if it is to be treated as
> a comment submitted to the meeting itself, as distinguished from the
> non-realtime comment-receiving systems.

A firetalk forum would allow much more flexibility
in all of these circumstances and must be
seriously considered.
 
> For whatever it's worth, this is (as best I can remember) the first time
> I've received this comment, i.e. the suggestion that presubmitted comments
> should be accepted along with "live remote participant" comments.  My sense
> previously was that everyone thought it was a good idea to require that
> comments be submitted during the meetings; no one has ever said otherwise.
> 
> > If not, you have the task of selecting
> > questions on the fly, while trying to ensure a fair and even handed input,
> > without knowing what's going to hit the screen next, or when you're going
> to
> > get a decent comment to read out.  This is not a trivial matter.
> 
> I'm a little confused about what you mean here.  I think you may be
> confusing the live chat room (an "IRC chat," like an AOL chat room or some
> such) with the remote comment submission system (web forms that submit text
> to a database).  Our remote participation liaison can readily review all
> messages in the database, can mark messages for (one-button) display on the
> projection screen, can classify messages according to a variety of criteria
> (whether or not read yet, meeting section if not so classified by the
> submitter, etc.), and can generally keep pretty good track of what's going
> on.  I'd like to think that we do know quite well what's going to hit the
> screen next!  

Absolutely no argument from me on that wise.  But
unwarranted censorship of any kind must be guarded
against.

>(Indeed, each comment is displayed on-screen while it's
> read -- as the scribe's notes generally reflect, i.e. "remote comment #1234
> from Tom Smith read in its entirety and displayed on screen" might be
> entered into scribe's notes when that is the case).
> 
> In terms of fairness and evenhandedness, I understand the concern here, and
> agree that it's a serious one.  But please understand the other issues we
> also face here: For example, I hope you appropriately consider the concern I
> expressed in my last message about reading & presenting off-topic messages
> (perhaps "stale" -- read too late, i.e. after the topic in question was
> discussed by the meeting -- or perhaps inherently off-topic).  Doing so
> causes the audience to literally cringe, in my experience, as if to say "Why
> are those Berkman Center people so dumb as to read us a question about
> *that*, when we just finished discussing it, and were all quite tired of the
> topic after such a prolonged discussion of the subject?"  

This is a problem of the past, not the future. 
let us move forward and explore what is readily
available now.

>For this reason,
> and for others too (ad hominem attacks, questions not appropriately
> addressed to the current meeting or group, messages submitted from what
> immediately seem to be false identities, etc.), we've come to think that any
> automated way of selecting comments is likely to be undesirable for other
> reasons, notwithstanding the underlying desirability of an automated way of
> choosing messages to be read aloud.  Again, I look forward to responding to
> Kendall's suggestion on this subject, and so I'd propose to bracket this
> discussion for the moment.

Not for long, I hope.
 
> > We could aim for consensus in the GA as to the topics that need
> highlighting
> > in this way. Questions could be supplemented or even substituted by live
> > comments on the day if desirable, but it would give the online
> participation
> > some much needed structure and ensure quality questions are heard on a
> wide
> > range of topics at agreed points in the schedule, interwoven with those
> from
> > the audience (some of which I'm sure are prepared in advance).  I'd be
> very
> > surprised if a call for questions did not receive a very positive response
> > from the GA list over say a 2 week period.
> 
> Certainly any effort to increase GA participation both in the GA's physical
> meeting and in other ICANN sessions seems to me highly desirable, and I
> applaud such attempts.
> 
> If these attempts are successful and lead to insightful and clearly-stated
> questions closely related to the topics under discussion on the various
> meeting agendas, I'm confident that the remote participation liaison will
> properly present these messages to the assembled group.
> 
> My sense in prior meetings has been that, in general, the liaison is usually
> successful in presenting a reasonable range of messages, giving appropriate
> recognition to major topic areas of the submitted questions and reading a
> substantial portion of the messages received.  I know that there have been
> instances when this has not been the case -- when public comment (both
> in-person and via remote participation) has been cut short due to shortness
> of time, or when the meeting chair has used his or her prerogative to
> recognize disproportionately many in-person commenters.  (Incidentally, I do
> continue to believe remains a significant factor to keep in mind -- the
> assembled group, and the queue at the microphone, can prove quite a force to
> be reckoned with, given their physical presence, travel expenses incurred,
> and general immediacy, especially as against a seemingly invisible and
> distant online audience.  I continue to suggest to the chair of each meeting
> that a remote comment be recognized after every two microphone comments, and
> at times we've gotten into an excellent rhythm this way.  But the underlying
> issue surely remains.)

I'm sorry, but which "underlying issue" do you
mean here exactly?
 
> 4) Increased reliance on multimedia participation, perhaps via 6-10 folks
> selected to participate in some special way for the occasion.
> 
> You wrote:
> 
> > ... Also, two
> > contributors are not sufficient in number to establish this format as part
> > of the process, hence it is easily reduced to an irritant in the
> > proceedings. My suggestion would be to have 6-10 contributors, as the
> > schedule allows, either interwoven at regular intervals or introduced as a
> > block, but all using the same screen, speaking individually in rotation.
> 
> Can you propose a specific technical means (hardware and software) for doing
> so?  At the moment I'm a bit unclear on what specifically you're talking
> about -- videoconferencing, or something else.

Firetalk.
 
> How would we choose the 6-10 contributors?  No one gets a similarly-favored
> position in the physical meeting, so I'd be concerned that this approach
> might not receive the support of physical meeting attendees.

Vote?
 
> Again, I thank everyone on this list for their suggestions.  I remain
> interested in further comments -- everything from improving the wording of
> web pages announcement emails to more far-reaching comments like the ideas
> submitted so far.  I certainly can't promise that the Berkman Center will do
> everything that's suggested here -- but we're listening, and, we think,
> thinking seriously about these issues.

That's what we're asking you to do... listen.  We
certainly hope you will seriously consider all
viable options.  I have experienced the remote
participation during Yokohama, and I know it is
possible to do it better.  

Sincerely,

Sotiris Sotiropoulos
	Hermes Network, Inc.
- --
This message was passed to you via the [email-masked] list.
Send mail to [email-masked] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html

------------------------------

End of GA-DIGEST V1 #241
************************