[dhcwg] jabber at dhc WG meeting in Vienna

Ralph Droms <rdroms@cisco.com> Thu, 10 July 2003 00:19 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00442; Wed, 9 Jul 2003 20:19:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aP9J-0004n3-0J; Wed, 09 Jul 2003 20:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aP8L-0004mN-4s for dhcwg@optimus.ietf.org; Wed, 09 Jul 2003 20:18:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00385 for <dhcwg@ietf.org>; Wed, 9 Jul 2003 20:17:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aP8J-0005dM-00 for dhcwg@ietf.org; Wed, 09 Jul 2003 20:17:59 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138]) by ietf-mx with esmtp (Exim 4.12) id 19aP8I-0005dI-00 for dhcwg@ietf.org; Wed, 09 Jul 2003 20:17:58 -0400
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h6A0HQpp015556 for <dhcwg@ietf.org>; Wed, 9 Jul 2003 17:17:27 -0700 (PDT)
Received: from rdroms-w2k.cisco.com (sjc-vpn3-342.cisco.com [10.21.65.86]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR) with ESMTP id AAN50251; Wed, 9 Jul 2003 20:17:24 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030709201416.04451a98@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 09 Jul 2003 20:17:23 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] jabber at dhc WG meeting in Vienna
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

I would like to use jabber conferencing at the
dhc WG meeting in Vienna, to provide remote access
to the meeting and to capture a log of the meeting.

I'll need someone to volunteer to act as scribe.  I'm
asking now for a scribe so the volunteer can be
prepared (see below for details) prior to the WG
meeting.

So, if you'd like to act as scribe in Vienna, let
me know...

Also - if you are on the agenda for the dhc WG
meeting, please forward any slides you might
be planning to use to me as soon as possible so
I can post them to a web server (TBD)...

- Ralph

=====


	     Remote Access for the 57th IETF meeting in Vienna:
                              Text Conferencing

At each IETF meeting, two of the working group meeting rooms are equipped
for video multicast and remote participation.  That is, for every IETF
meeting slot, two of the working groups can see and hear the
meeting. For the 57th IETF, in *addition* to the usual network A/V, text
conferencing will be provided for every working group that meets.

All of the conference rooms will be hosted on

     ietf.jabber.at

and each is named using the official IETF abbreviation found in the
agenda (e.g., "apparea",  "dhc", "forces", and so on -- for all the
examples that follow, we'll use "foobar" as the abbreviation).

Each conference room also has a 'bot which records everything that gets
sent. So, the minute taker can review this information right after the
meeting.

In addition to the conference rooms for each wg that is meeting, there
are three others of general interest: bar, hallway, and plenary.


1. Before the meeting:

1.1. If you want to participate

If you don't already have one, get yourself a Jabber client, here are some
suggestions:

     platform    suggestion
     --------    ----------
     win32       http://exodus.jabberstudio.org
     'nix        http://gabber.sf.net
     macos       http://jabberfox.sf.net

When you start the client for the first time, it will eventually ask if
you want to register on a public server. Go ahead and do
that.

If you want to find out more, instead of choosing these defaults, here
are pointers to some additional information:

     list of clients:    http://www.jabber.org/user/clientlist.php
               howto:    http://www.jabber.org/user/userguide/
         server list:    http://www.jabber.org/user/publicservers.php

To make sure everything is running ok, do a "Join Group Chat" with your
Jabber client:

     Group/Room: testing
     Server:     conference.ietf.jabber.com

This conference room is up and running right now (although probably no
one will be in it when you connect).

1.2. What the Chair does

If you want to make text conferencing available, you'll need to have a
volunteer scribe in the meeting room. The scribe will be typing in a
running commentary as to what's going on in the room (who's presenting,
what question is being asked, etc.)

So, why not send an email out on the mailing list now, before the
meeting, to ask for volunteers?


2. At the meeting

2.1. What the Chair does

When a session starts, the chair asks if someone in the room is willing
to act as "scribe". If no one volunteers, read no further, we're done!

Otherwise, the scribe should do a "Join Group Chat" with their Jabber
client, e.g.,

     Group/Room: foobar
     Server:     conference.ietf.jabber.com


2.2. What the Scribe does

The scribe types in a running commentary as to what's going on in the
room. For example, if a speaker makes a presentation, the scribe types
in the URL for the presentation (more on this in a bit).

Simlarly, during question time, a remote participant can type a question
into the room and the scribe can pass it on to the speaker.


2.3. What each Presenter does

Each presenter should put a copy of their presentation on a web server
somewhere, so remote participants can follow along.


2.4. Where to find the conference log

[ tbd: i'm still working on this one... ]

                                   #######


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg