- From: Eric Johnson <eric@tibco.com>
- Date: Sat, 29 Nov 2008 15:41:59 -0800
- To: "SOAP/JMS (list)" <public-soap-jms@w3.org>
FYI - auto-response from IETF...
-Eric.
-------- Original Message --------
Subject: [rt.amsl.com #12047] AutoReply: JMS URI Scheme submission
Date: Sat, 29 Nov 2008 15:40:55 -0800
From: IETF-IESG via RT <iesg-secretary@ietf.org>
Reply-To: iesg-secretary@ietf.org
To: eric@tibco.com
References: <RT-Ticket-12047@rt.amsl.com> <4931D2FB.4010209@tibco.com>
Greetings,
This message has been automatically generated in response to the
creation of a trouble ticket regarding:
"JMS URI Scheme submission",
a summary of which appears below.
There is no need to reply to this message right now. Your ticket has been
assigned an ID of [rt.amsl.com #12047].
Please include the string:
[rt.amsl.com #12047]
in the subject line of all future correspondence about this issue. To do so,
you may reply to this message.
Thank you,
iesg-secretary@ietf.org
-------------------------------------------------------------------------
To whom it may concern,
Being somewhat naive about the process by which a URI scheme might be
accepted, I think I've hit upon the fact that I'm supposed to email this
address requesting the start of the process for getting our "jms" URI
scheme draft published as an RFC (if that's even the right terminology,
and the right way to think about it?)
The data tracker link is here:
https://datatracker.ietf.org/drafts/draft-merrick-jms-uri/
And the latest draft is:
http://www.ietf.org/internet-drafts/draft-merrick-jms-uri-05.txt
Please advise as to the next steps.... Thanks.
Sincerely,
Eric Johnson.
Received on Saturday, 29 November 2008 23:42:35 UTC