[xrblock] FW: [91attendees] New draft offers suggestions/guidance for Jabber scribes...

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sat, 08 November 2014 12:18 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 2907D1A6FF1 for <xrblock@ietfa.amsl.com>; Sat, 8 Nov 2014 04:18:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.493
X-Spam-Status: No, score=-7.493 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id x1jkICkQBLuO for <xrblock@ietfa.amsl.com>; Sat, 8 Nov 2014 04:18:33 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com []) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A7A81A6FF2 for <xrblock@ietf.org>; Sat, 8 Nov 2014 04:18:33 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.07,340,1413259200"; d="txt'?scan'208,217";a="93781392"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 08 Nov 2014 07:18:31 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 08 Nov 2014 07:18:31 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([]) with mapi id 14.03.0174.001; Sat, 8 Nov 2014 13:18:30 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: xrblock <xrblock@ietf.org>
Thread-Topic: [91attendees] New draft offers suggestions/guidance for Jabber scribes...
Thread-Index: Ac/7ThgtCA1Hm1wDRsWyg8JTeUcHPg==
Date: Sat, 08 Nov 2014 12:18:29 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C8FA0F1@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/mixed; boundary="_004_9904FB1B0159DA42B0B887B7FA8119CA5C8FA0F1AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/uuygXyR5nKcuQdDfzDJ5ir5i-Tw
Subject: [xrblock] FW: [91attendees] New draft offers suggestions/guidance for Jabber scribes...
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock/>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Nov 2014 12:18:36 -0000

Recommendations for the brave volunteer who will support the meeting this week is taking jabber notes.

It's an even more important mission this time as we expect a higher than usual rate of remote attendees at this meeting.

Thanks and Regards,


From: 91attendees [mailto:91attendees-bounces@ietf.org] On Behalf Of Dan York
Sent: Friday, November 07, 2014 6:14 PM
To: 91attendees@ietf.org
Subject: [91attendees] New draft offers suggestions/guidance for Jabber scribes...

IETF 91 attendees,

If you are going to serve as a "Jabber scribe" in meetings next week at IETF 91 (or wind up being asked to do that), Peter St. Andre and I tried to capture some of the experiences we and others have had as Jabber scribes and advice we've received from others in a new draft:


Our hope is that this can be helpful to people who might get tasked with performing this role that is so VERY critical for remote attendees.

I'd also encourage folks who haven't considered it to volunteer as jabber scribes.  I do it often because I've been a remote attendee and know how much I came to rely on the scribe relay... and also because it's a great way to learn the names of people involved with a working group and to get involved with helping out with the IETF processes.  (And also quite frankly because it forces me to pay attention to what's happening in the room instead of wandering off into email or something...)

Anyway... the draft is out there and we would welcome any feedback that people have.  If you are doing jabber scribing (or what we called "chatroom relay" to be product-neutral) next week at IETF 91 and come up with any additional tips or tricks, please do let us know.  The goal is to help provide suggestions that can make this role work smoother and easier and through that to help improve the experience for remote attendees.