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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-07-23 (latest revision 2015-06-04)
Replaces draft-saintandre-chatroom-relay
Stream ISE
Intended RFC status Informational
Formats plain text pdf html bibtex
IETF conflict review conflict-review-saintandre-jabber-scribe
Additional URLs
Stream ISE state Sent to the RFC Editor
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2015-07-06)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to "Nevil Brownlee" <rfc-ise@rfc-editor.org>
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions
RFC Editor RFC Editor state EDIT
Network Working Group                                     P. Saint-Andre
Internet-Draft                                                      &yet
Intended status: Informational                                   D. York
Expires: December 6, 2015                               Internet Society
                                                            June 4, 2015

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

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 December 6, 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 December 6, 2015                [Page 1]
Internet-Draft             Jabber Scribe Role                  June 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 . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Know Yourself . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Primary Tasks . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Additional Tasks  . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Suggestions . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Getting Set Up with Jabber  . . . . . . . . . . . . . . .   6
     6.2.  Before the Session Begins . . . . . . . . . . . . . . . .   6
     6.3.  As the Session Is Starting  . . . . . . . . . . . . . . .   7
     6.4.  During the Session  . . . . . . . . . . . . . . . . . . .   8
     6.5.  As the Session Is Ending  . . . . . . . . . . . . . . . .   9
   7.  Advanced Tips . . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  Dealing with Abusive or Inappropriate Behavior  . . . . . . .  10
   9.  Reporting Problems at the Meeting Venue . . . . . . . . . . .  10
   10. Intellectual Property Rights (IPR)  . . . . . . . . . . . . .  10
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   12. Security Considerations . . . . . . . . . . . . . . . . . . .  11
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     13.2.  Informative References . . . . . . . . . . . . . . . . .  11
     13.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .  11
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

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" (however, nothing prevents
   the IETF from using some other technology for chatrooms in the
   future, or from discontinuing the use of chatrooms entirely).

   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
Show full document text