W3C home > Mailing lists > Public > public-soap-jms@w3.org > October 2010

RE: Notes on IANA registration of variants for JMS URI scheme

From: Peter Easton <peaston@progress.com>
Date: Thu, 21 Oct 2010 09:04:13 -0400
To: Eric Johnson <eric@tibco.com>, Amelia A Lewis <alewis@tibco.com>
CC: SOAP-JMS <public-soap-jms@w3.org>
Message-ID: <6F07B1E4CA74F3469AAA1DA148515F84014B40B539@PSCMAIL02.bedford.progress.com>
Hi,

It's possible Progress might use a different variant. The use case would be addressing a Sonic business process by name(versus the queue, topic, or jndi destination that the named process listens on).(I'm not saying that we'll actually do this, it's just an example).

Also vnd-, private-use would work.

Peter

-----Original Message-----
From: public-soap-jms-request@w3.org [mailto:public-soap-jms-request@w3.org] On Behalf Of Eric Johnson
Sent: Wednesday, October 20, 2010 5:29 PM
To: Amelia A Lewis
Cc: SOAP-JMS
Subject: Re: Notes on IANA registration of variants for JMS URI scheme

Hi Amy,

An important question, which I'm thinking we should explicitly ask of 
this group.

Given an actual RFC for JMS URI, would others on this list need use of 
"variants" not currently specified?

If yes, can you provide any details about what that variant might be?

-Eric.

On 10/20/10 11:37 AM, Amelia A Lewis wrote:
> I thought that the reason for specifying variants was because several
> of the vendors in the consortium had private, existing schemes, which
> could be effectively "grandfathered" by prefixing with "jms:"?
>
> Amy!
> On Wed, 20 Oct 2010 11:20:04 -0700, Eric Johnson wrote:
>> My action 218 [1] is to report back to the group on options for IANA
>> registration of variants in the JMS URI scheme.
>>
>> In case you're curious, you can look at the long list of current
>> registrations [4].
>> The registration question is governed by RFC 5226 [2].
>>
>> One option - a "delegated" namespace - think Java package names, or
>> DNS names (where the IANA only manages the top level).
>>
>> Another option - one or more designated experts that will review
>> proposed registrations.
>>
>> The IANA defines the following "policy" definitions for ways to treat
>> registration [3]:
>>
>>     * private use
>>     * experimental use
>>     * hierarchical allocation
>>     * first-come, first-served
>>     * expert review
>>     * specification required
>>     * RFC required
>>     * IETF review
>>     * standards action
>>     * IESG approval
>>
>> We can divide up the "space" of possible registered variants, for
>> example defining a prefix for variants like "x-" which defines
>> "private use" or "experimental use", and perhaps everything else
>> comes under "specification required."
>>
>> My suggestion:
>> Since we do not expect any further registration of JMS variants, in a
>> sense, it almost doesn't matter what we choose.  It seems like a
>> combination of first-come, first-served registration, coupled with an
>> "x-" prefix for experimental use will provide appropriately low
>> overhead.
>>
>> Thoughts?
>>
>> If we follow my suggestion, I suggest the following changes to the spec:
>>
>> In section 4:
>> After:
>> The three recognized variants (<jms-variant>  above) are "jndi",
>> "queue", and "topic".
>>
>> ... add:
>> Variant names starting with "x-" are reserved for experimental use.
>>
>> Also, section 9 needs changes, but depending on what we decide above,
>> that will affect what we put there.
>>
>> -Eric.
>>
>> [1] http://www.w3.org/2002/ws/soapjms/tracker/actions/218
>> [2] http://tools.ietf.org/html/rfc5226
>> [3] http://tools.ietf.org/html/rfc5226#section-4.1
>> [4] http://www.iana.org/protocols/
>>
>>
Received on Thursday, 21 October 2010 13:05:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:16:25 GMT