The Jabber Scribe Role at IETF Meetings
draft-saintandre-jabber-scribe-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-02-18
Replaces draft-saintandre-chatroom-relay
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
IETF conflict review conflict-review-saintandre-jabber-scribe
Additional URLs
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                     P. Saint-Andre
Internet-Draft                                                      &yet
Intended status: Informational                                   D. York
Expires: August 22, 2015                                Internet Society
                                                       February 18, 2015

                The Jabber Scribe Role at IETF Meetings
                   draft-saintandre-jabber-scribe-00

Abstract

   During IETF meetings, individual volunteers often help sessions run
   more smoothly by relaying information back and forth between the
   physical meeting room and an associated textual chatroom.  Such
   volunteers, commonly called "Jabber scribes", might benefit from the
   suggestions provided in this document.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 22, 2015.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Saint-Andre & York       Expires August 22, 2015                [Page 1]
Internet-Draft             Jabber Scribe Role              February 2015

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Know Your Users . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Primary Tasks . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Additional Tasks  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Suggestions . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Before the Session  . . . . . . . . . . . . . . . . . . .   4
     5.2.  As the Session Is Starting  . . . . . . . . . . . . . . .   5
     5.3.  During the Session  . . . . . . . . . . . . . . . . . . .   6
   6.  Reporting Problems  . . . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   9.  Informative References  . . . . . . . . . . . . . . . . . . .   8
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   During IETF meetings, individual volunteers often help sessions run
   more smoothly by relaying information back and forth between the
   physical meeting room and an associated textual chatroom.  Because
   these chatrooms are currently implemented using Jabber/XMPP
   technologies (see [RFC6120] and [XEP-0045]) the role is commonly
   referred to as that of a "Jabber scribe".

   This role is important because it is the primary way for a remote
   attendee to provide feedback or comments back into most IETF meeting
   sessions.  Although there are multiple ways that a remote attendee
   can listen and follow along, the chatroom provides a method of
   returning feedback to the physical meeting in something close to real
   time.  These methods hold true for IETF working group sessions, IRTF
   research group sessions, IETF "birds of a feather" (BoF) sessions,
   and similar sessions at IETF meetings.

   This document provides suggestions for fulfilling the role of a
   Jabber scribe, based on the authors' personal experience as well as
   input from other individuals who frequently volunteer as Jabber
   scribes.

2.  Know Your Users

   The participants in a chatroom typically fall into three categories,
   labelled here for ease of understanding:

Saint-Andre & York       Expires August 22, 2015                [Page 2]
Internet-Draft             Jabber Scribe Role              February 2015

   o  Remote Participants

      Remote attendees who are listening to the audio stream or in some
      cases following the proceedings using a real-collaboration system
Show full document text