The Jabber-ID Header Field
draft-saintandre-jabberid-11

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-09-23
Stream ISE
Intended RFC status Experimental
Formats plain text pdf html
IETF conflict review conflict-review-saintandre-jabberid
Stream ISE state Finding Reviewers
Document shepherd None
IESG IESG state I-D Exists (IESG: Dead)
Telechat date
Responsible AD Lisa Dusseault
Send notices to stpeter@jabber.org
Network Working Group                                     P. Saint-Andre
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Informational                        September 23, 2013
Expires: March 27, 2014

                       The Jabber-ID Header Field
                      draft-saintandre-jabberid-11

Abstract

   This document defines a header field that enables the author of an
   email or netnews message to include a Jabber ID in the message header
   block for the purpose of associating the author with a particular
   Extensible Messaging and Presence Protocol (XMPP) address.

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 March 27, 2014.

Copyright Notice

   Copyright (c) 2013 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Saint-Andre              Expires March 27, 2014                 [Page 1]
Internet-Draft                  Jabber-ID                 September 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     3.1.  Inclusion . . . . . . . . . . . . . . . . . . . . . . . . . 4
     3.2.  Generation  . . . . . . . . . . . . . . . . . . . . . . . . 4
     3.3.  Processing  . . . . . . . . . . . . . . . . . . . . . . . . 4
     3.4.  Disposition . . . . . . . . . . . . . . . . . . . . . . . . 5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 7
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . . . 7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 7

Saint-Andre              Expires March 27, 2014                 [Page 2]
Internet-Draft                  Jabber-ID                 September 2013

1.  Introduction

   The Extensible Messaging and Presence Protocol (XMPP), documented in
   [RFC6120], is a streaming XML technology that enables any two
   entities on a network to exchange well-defined but extensible XML
   elements (called "XML stanzas") in close to real time.  Given XMPP's
   heritage in the Jabber open-source community, one of the primary uses
   for XMPP is instant messaging and presence as documented in
   [RFC6121], and XMPP addresses are still referred to as Jabber IDs.

   Because almost all human users of Jabber/XMPP instant messaging and
   presence systems also use email systems [RFC5322] and because many
   also use netnews systems [RFC5536], it can be helpful for them to
   associate their Jabber IDs with the messages they author.  The
   Jabber-ID header field provides a standard location for that
   information.

   Members of the XMPP instant messaging and presence community have
   been experimenting with the Jabber-ID header field for many years.
   This document defines the syntax and usage of the Jabber-ID header
   field, including the information necessary to register the field in
   the Provisional Message Header Field Registry maintained by the IANA.

2.  Syntax

   The syntax of the Jabber-ID header field is defined below using
   Augmented Backus-Naur Form [RFC5234], where the "pathxmpp" rule is
Show full document text