datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

A Uniform Resource Name (URN) Namespace for Extensions to the Extensible Messaging and Presence Protocol (XMPP)
RFC 4854

Document type: RFC - Informational (April 2007)
Was draft-saintandre-xmpp-urn (individual in app area)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 4854 (Informational)
Responsible AD: Ted Hardie
Send notices to: stpeter@jabber.org

Network Working Group                                     P. Saint-Andre
Request for Comments: 4854                                           XSF
Category: Informational                                       April 2007

              A Uniform Resource Name (URN) Namespace for
  Extensions to the Extensible Messaging and Presence Protocol (XMPP)

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This document describes a Uniform Resource Name (URN) namespace for
   uniquely identifying Extensible Markup Language (XML) formats and
   protocols that provide extensions to the Extensible Messaging and
   Presence Protocol (XMPP) and are defined in specifications published
   by the XMPP Standards Foundation (XSF).

Saint-Andre                  Informational                      [Page 1]
RFC 4854           URN Namespace for XMPP Extensions          April 2007

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Specification Template  . . . . . . . . . . . . . . . . . . . . 3
   3.  Namespace Considerations  . . . . . . . . . . . . . . . . . . . 6
   4.  Community Considerations  . . . . . . . . . . . . . . . . . . . 6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 8
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 8

Saint-Andre                  Informational                      [Page 2]
RFC 4854           URN Namespace for XMPP Extensions          April 2007

1.  Introduction

   While the Extensible Messaging and Presence Protocol (XMPP), as
   specified in [XMPP-CORE] and [XMPP-IM], provides basic messaging and
   presence functionality, the fact that XMPP is at root a technology
   for streaming Extensible Markup Language [XML] data makes it possible
   to include virtually any structured information within XMPP, as long
   as such information is qualified by appropriate XML namespaces
   [XML-NAMES].  When sent over XMPP, such structured data formats and
   protocols are generally referred to as "XMPP extensions".

   A large number of such XMPP extensions exist.  The main standards
   development organization in which such extensions are defined is the
   XMPP Standards Foundation (XSF) (formerly the Jabber Software
   Foundation), which contributed XMPP to the Internet Standards
   process.  Typically, such extensions are defined within the XSF's
   XMPP Extension Protocol (XEP) specification series.  To date, the XML
   namespaces defined within the Jabber/XMPP community have used names
   of the form "jabber:*" (deprecated since early 2002) and
   "http://jabber.org/protocol/*" (not including names of the form
   "urn:ietf:params:xml:ns:xmpp-*" specified in the XMPP RFCs).
   However, it is desirable that names associated with future XMPP
   extensions be both unique and persistent, which is not necessarily
   the case with names that are also HTTP URLs.  Therefore, in
   accordance with the process defined in [MECHANISMS], this document
   registers a formal namespace identifier (NID) for Uniform Resource
   Names [URN] associated with XMPP extensions published in the XSF's
   XEP series and for XML namespaces registered with the XSF's XMPP
   Registrar function [REGISTRAR].

2.  Specification Template

   Namespace ID:

      The Namespace ID "xmpp" is requested.

   Registration Information:

      Version 1
      Date: 2007-04-27

   Declared Registrant of the Namespace:

      Registering organization
         Organization: XMPP Standards Foundation
         Address: P.O. Box 1641, Denver, CO 80201 USA

Saint-Andre                  Informational                      [Page 3]
RFC 4854           URN Namespace for XMPP Extensions          April 2007

      Designated contact
         Role: XMPP Registrar
         Email: registrar@xmpp.org

   Declaration of Syntactic Structure:

      The Namespace Specific String (NSS) of all URNs that use the
      "xmpp" NID shall have the following structure:

         urn:xmpp:{ShortName}:{SubName}

      The keywords have the following meaning:

         (1) the "ShortName" is a required US-ASCII string that
         conforms to the URN syntax requirements (see RFC 2141)

[include full document text]