datatracker.ietf.org
Sign in
Version 5.7.1.p2, 2014-10-29
Report a bug

URI Scheme for Java(tm) Message Service 1.0
RFC 6167

Document type: RFC - Informational (April 2011; Errata)
Was draft-merrick-jms-uri (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 6167 (Informational)
Responsible AD: Alexey Melnikov
Send notices to: eric@tibco.com, m8philli@uk.ibm.com, phil_adams@us.ibm.com, derek.rokicki@softwareag.com

Internet Engineering Task Force (IETF)                       M. Phillips
Request for Comments: 6167                                      P. Adams
Category: Informational                                              IBM
ISSN: 2070-1721                                               D. Rokicki
                                                             Software AG
                                                              E. Johnson
                                                                   TIBCO
                                                              April 2011

              URI Scheme for Java(tm) Message Service 1.0

Abstract

   This document defines the format of Uniform Resource Identifiers
   (URIs) as defined in RFC 3986, for designating connections and
   destination addresses used in the Java(tm) Messaging Service (JMS).
   It was originally designed for particular uses, but applies generally
   wherever a JMS URI is needed to describe the connection to a JMS
   provider, and access to a JMS Destination.  The syntax of this JMS
   URI is not compatible with previously existing, but unregistered,
   "jms" URI schemes.  However, the expressiveness of the scheme
   described herein should satisfy the requirements of all existing
   circumstances.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6167.

Phillips, et al.              Informational                     [Page 1]
RFC 6167                     jms" URI Scheme                  April 2011

Copyright Notice

   Copyright (c) 2011 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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Phillips, et al.              Informational                     [Page 2]
RFC 6167                     jms" URI Scheme                  April 2011

Table of Contents

   1. Introduction ....................................................3
      1.1. Requirements Notation ......................................4
   2. URI Scheme Name .................................................5
   3. Syntax of a JMS URI .............................................5
   4. URI Scheme Semantics ............................................5
      4.1. Shared Parameters ..........................................6
      4.2. "jndi" Variant .............................................7
      4.3. Vendor Destination Names -- Variants "queue" and "topic" ..11
      4.4. Custom Parameters .........................................12
   5. Encoding Considerations ........................................13
   6. Applications/Protocols That Use the JMS URI ....................13
   7. Interoperability Considerations ................................13
   8. Security Considerations ........................................14
      8.1. Reliability and Consistency ...............................14
      8.2. Malicious Construction ....................................14

[include full document text]