[Fwd: S/MIME WG Text Conferencing at IETF 55]
Stephen Farrell <[email protected]> Fri, 08 Nov 2002 15:47:00 +0000
| Newsgroups | gmane.ietf.sacred |
|---|---|
| Organization | Baltimore Technologies Ltd. |
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --------------42F248A95743A11A986ADCAA Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I'm being lazy here, do the obvious replacement and see what you think about the attached. If enough people want to try it, the sacred meeting can join the experiment. Send the chairs a mail offlist if you think we should do this, and in particular, say if you'd participate but won't be in Atlanta, or if you'll be in Atlanta and will act as scribe. We'll let the list know in a week how many of each we've gotten. Stephen. -- ____________________________________________________________ Stephen Farrell Baltimore Technologies, tel: (direct line) +353 1 881 6716 39 Parkgate Street, fax: +353 1 881 7000 Dublin 8. mailto:[email protected] Ireland http://www.baltimore.com --------------42F248A95743A11A986ADCAA Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Return-Path: <[email protected]> Received: from emeairlsw1.baltimore.com (emeairlsw1.ie.baltimore.com [10.153.25.53]) by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id PAA09686; Fri, 8 Nov 2002 15:37:13 GMT Received: from Baltimore-FW2 (wilde-i-2.ie.baltimore.com) by emeairlsw1.baltimore.com (Content Technologies SMTPRS 4.2.5) with SMTP id <[email protected]>; Fri, 8 Nov 2002 15:29:28 +0000 Received: from ([172.19.1.101]) by Baltimore-FW2; Fri, 08 Nov 2002 15:36:02 +0000 (GMT) Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ocasey.baltimore.com (8.11.6/8.9.3) with ESMTP id gA8FZkU18408; Fri, 8 Nov 2002 15:35:46 GMT Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id gA8FDl628128 for ietf-smime-bks; Fri, 8 Nov 2002 07:13:47 -0800 (PST) Received: from vulcan.rsasecurity.com (mail.rsasecurity.com [204.167.114.123]) by above.proper.com (8.11.6/8.11.3) with SMTP id gA8FDkv28123 for <[email protected]>; Fri, 8 Nov 2002 07:13:46 -0800 (PST) Received: from no.name.available by vulcan.rsasecurity.com via smtpd (for mail.imc.org [208.184.76.43]) with SMTP; 8 Nov 2002 15:13:47 UT Received: from ebola.securitydynamics.com (ebola.securid.com [192.80.211.4]) by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id KAA19395 for <[email protected]>; Fri, 8 Nov 2002 10:13:46 -0500 (EST) Received: from exeu00.securid.com (localhost [127.0.0.1]) by ebola.securitydynamics.com (8.10.2+Sun/8.10.2) with ESMTP id gA8FB3T14888 for <[email protected]>; Fri, 8 Nov 2002 10:11:04 -0500 (EST) Received: by exeu00.eu.rsa.net with Internet Mail Service (5.5.2653.19) id <W3JALS10>; Fri, 8 Nov 2002 15:17:51 -0000 Received: from HOUSLEY-LAP.rsasecurity.com (HOUSLEY-LAP [10.3.9.48]) by exna00.securitydynamics.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 3TPWLFNW; Fri, 8 Nov 2002 10:13:40 -0500 Message-Id: <[email protected]> X-Sender: [email protected] X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 08 Nov 2002 09:47:22 -0500 To: [email protected] From: "Housley, Russ" <[email protected]> Subject: S/MIME WG Text Conferencing at IETF 55 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_8063584==_" Sender: [email protected] Precedence: bulk List-Archive: <http://www.imc.org/ietf-smime/mail-archive/> List-ID: <ietf-smime.imc.org> List-Unsubscribe: <mailto:[email protected]?body=unsubscribe> X-Mozilla-Status2: 00000000 --=====================_8063584==_ Content-Type: text/plain; charset="us-ascii"; format=flowed We are running an experiment at the IETF meeting in Atlanta. This note is to find out whether the S/MIME WG wants to participate in the experiment or not. The experiment is to determine if Jabber can be used during the IETF meeting to allow people who cannot come to Atlanta to participate. Jabber conference rooms have been set up for each working group that will hold a session in Atlanta. For the S/MIME WG, the conference room is: Group/Room: smime Server: conference.ietf.jabber.com I have attached the instructions for accessing the rooms, and so on. If I do not get a volunteer to be the scribe, then we will not participate in this experiment. Russ --=====================_8063584==_ Content-Type: text/plain; charset="us-ascii" Content-Disposition: attachment; filename="text-conferencing1.txt" Remote Access for the 55th IETF meeting in Atlanta: 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 55th 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 conference.ietf.jabber.com 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. 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. If you don't have a server available, email your presentation to To: [email protected] Subject: foobar and the Secretariat will put the presentation in a server so it can be accessed under: http://atlanta.ietf.org/presentations/foobar/ Don't wait until the last minute to send the email. 2.4. Where to find the conference log http://www.jabber.com/chatbot/logs/conference.ietf.jabber.com/foobar/ 2.5. Finally This is an experiment. Let's see how well it works and discuss it after the meeting. ####### --=====================_8063584==_-- --------------42F248A95743A11A986ADCAA--