URI Scheme for Java(tm) Message Service 1.0
draft-merrick-jms-uri-12
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2012-08-22
|
12 | (System) | post-migration administrative database adjustment to the Yes position for Alexey Melnikov |
2011-02-22
|
12 | (System) | IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor |
2011-02-22
|
12 | (System) | IANA Action state changed to Waiting on RFC Editor from In Progress |
2011-02-22
|
12 | (System) | IANA Action state changed to In Progress from Waiting on Authors |
2011-02-04
|
12 | (System) | IANA Action state changed to Waiting on Authors from In Progress |
2011-02-04
|
12 | (System) | IANA Action state changed to In Progress from Waiting on Authors |
2011-02-04
|
12 | (System) | IANA Action state changed to Waiting on Authors from In Progress |
2011-01-27
|
12 | (System) | IANA Action state changed to In Progress |
2011-01-27
|
12 | Cindy Morgan | State changed to RFC Ed Queue from Approved-announcement sent. |
2011-01-26
|
12 | Cindy Morgan | IESG state changed to Approved-announcement sent |
2011-01-26
|
12 | Cindy Morgan | IESG has approved the document |
2011-01-26
|
12 | Cindy Morgan | Closed "Approve" ballot |
2011-01-26
|
12 | Cindy Morgan | Approval announcement text regenerated |
2011-01-21
|
12 | Alexey Melnikov | State Change Notice email list has been changed to eric@tibco.com, m8philli@uk.ibm.com, phil_adams@us.ibm.com, derek.rokicki@softwareag.com from eric@tibco.com, peaston@progress.com, derek.rokicki@softwareag.com, m8philli@uk.ibm.com, … State Change Notice email list has been changed to eric@tibco.com, m8philli@uk.ibm.com, phil_adams@us.ibm.com, derek.rokicki@softwareag.com from eric@tibco.com, peaston@progress.com, derek.rokicki@softwareag.com, m8philli@uk.ibm.com, draft-merrick-jms-uri@tools.ietf.org |
2011-01-21
|
12 | Alexey Melnikov | Ballot writeup text changed |
2011-01-21
|
12 | (System) | Removed from agenda for telechat - 2011-01-20 |
2011-01-20
|
12 | (System) | New version available: draft-merrick-jms-uri-12.txt |
2011-01-20
|
12 | Cindy Morgan | State changed to Approved-announcement to be sent::Point Raised - writeup needed from IESG Evaluation. |
2011-01-20
|
12 | Dan Romascanu | [Ballot Position Update] New position, No Objection, has been recorded |
2011-01-20
|
12 | Adrian Farrel | [Ballot Position Update] New position, No Objection, has been recorded |
2011-01-20
|
12 | Sean Turner | [Ballot Position Update] New position, No Objection, has been recorded |
2011-01-19
|
12 | Russ Housley | [Ballot Position Update] New position, No Objection, has been recorded |
2011-01-19
|
12 | Robert Sparks | [Ballot Position Update] New position, No Objection, has been recorded |
2011-01-19
|
12 | Alexey Melnikov | Ballot writeup text changed |
2011-01-19
|
12 | Ron Bonica | [Ballot Position Update] New position, No Objection, has been recorded |
2011-01-19
|
12 | Gonzalo Camarillo | [Ballot Position Update] New position, No Objection, has been recorded |
2011-01-19
|
12 | Stewart Bryant | [Ballot Position Update] New position, No Objection, has been recorded |
2011-01-18
|
12 | Peter Saint-Andre | [Ballot Position Update] New position, No Objection, has been recorded |
2011-01-18
|
12 | Alexey Melnikov | Ballot writeup text changed |
2011-01-18
|
12 | Alexey Melnikov | Ballot writeup text changed |
2011-01-17
|
12 | Lars Eggert | [Ballot comment] INTRODUCTION, paragraph 4: > The syntax of this 'jms' URI is not compatible with any known current > vendor implementation, but … [Ballot comment] INTRODUCTION, paragraph 4: > The syntax of this 'jms' URI is not compatible with any known current > vendor implementation, but the expressivity of the format should > permit all vendors to use it. So are there vendor implementations of 'jms' already? If yes, what it the value in publishing a specification that is not compatible with any of them? Or do we have an indication that the vendors will adopt this spec? |
2011-01-17
|
12 | Lars Eggert | [Ballot Position Update] New position, No Objection, has been recorded |
2011-01-14
|
12 | Alexey Melnikov | [Ballot comment] It looks like IANA issue was actually addressed in the last revision. |
2011-01-14
|
12 | Alexey Melnikov | [Ballot Position Update] Position for Alexey Melnikov has been changed to Yes from Discuss |
2011-01-14
|
12 | Alexey Melnikov | [Ballot discuss] Holding a DISCUSS on behalf of IANA: IANA would like to suggest a different registration procedure for the new registry to be created … [Ballot discuss] Holding a DISCUSS on behalf of IANA: IANA would like to suggest a different registration procedure for the new registry to be created by this document. Section 9.2.1 says, "IANA should use its judgment to assess whether the registering party has a reasonable claim to the 'vendorname' portion of the pattern, and if not, reject the registration. If the portion looks legitimate to the IANA, but it is not registered in the [VENDOR-REGISTRY], IANA should register the at the same time as it registers the corresponding JMS variant name." IANA would prefer that this procedure be changed either to Expert Review or to a version of First Come First Served that does not require IANA to determine whether a registrant has a "reasonable claim" to a name. |
2011-01-14
|
12 | Alexey Melnikov | [Ballot Position Update] Position for Alexey Melnikov has been changed to Discuss from Yes |
2011-01-14
|
12 | Alexey Melnikov | State changed to IESG Evaluation from Waiting for AD Go-Ahead::AD Followup. |
2011-01-14
|
12 | Alexey Melnikov | [Ballot Position Update] New position, Yes, has been recorded for Alexey Melnikov |
2011-01-14
|
12 | Alexey Melnikov | Ballot has been issued |
2011-01-14
|
12 | Alexey Melnikov | Created "Approve" ballot |
2011-01-14
|
12 | Alexey Melnikov | Ballot writeup text changed |
2011-01-13
|
12 | (System) | Sub state has been changed to AD Follow up from New Id Needed |
2011-01-13
|
11 | (System) | New version available: draft-merrick-jms-uri-11.txt |
2010-12-28
|
12 | Alexey Melnikov | State changed to Waiting for AD Go-Ahead::Revised ID Needed from Waiting for AD Go-Ahead. |
2010-12-28
|
12 | (System) | State changed to Waiting for AD Go-Ahead from In Last Call. |
2010-12-23
|
12 | Amanda Baber | IANA would like to suggest a different registration procedure for the new registry to be created by this document. Section 9.2.1 says, "IANA should use … IANA would like to suggest a different registration procedure for the new registry to be created by this document. Section 9.2.1 says, "IANA should use its judgment to assess whether the registering party has a reasonable claim to the 'vendorname' portion of the pattern, and if not, reject the registration. If the portion looks legitimate to the IANA, but it is not registered in the [VENDOR-REGISTRY], IANA should register the at the same time as it registers the corresponding JMS variant name." IANA would prefer that this procedure be changed either to Expert Review or to a version of First Come First Served that does not require IANA to determine whether a registrant has a "reasonable claim" to a name. IANA has no problem registering the JMS URI scheme or creating the JMS URI scheme variant registry. |
2010-12-15
|
12 | Alexey Melnikov | Placed on agenda for telechat - 2011-01-20 |
2010-11-30
|
12 | Amy Vezza | Last call sent |
2010-11-30
|
12 | Amy Vezza | State changed to In Last Call from Last Call Requested. The following Last Call Announcement was sent out: From: The IESG To: IETF-Announce Reply-To: ietf@ietf.org … State changed to In Last Call from Last Call Requested. The following Last Call Announcement was sent out: From: The IESG To: IETF-Announce Reply-To: ietf@ietf.org Subject: Last Call: (URI Scheme for Java(tm) Message Service 1.0) to Informational RFC The IESG has received a request from an individual submitter to consider the following document: - 'URI Scheme for Java(tm) Message Service 1.0' as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2010-12-28. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://datatracker.ietf.org/doc/draft-merrick-jms-uri/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-merrick-jms-uri/ |
2010-11-30
|
12 | Alexey Melnikov | Last Call was requested |
2010-11-30
|
12 | (System) | Ballot writeup text was added |
2010-11-30
|
12 | (System) | Last call text was added |
2010-11-30
|
12 | (System) | Ballot approval text was added |
2010-11-30
|
12 | Alexey Melnikov | State changed to Last Call Requested from AD Evaluation::AD Followup. |
2010-11-23
|
12 | (System) | Sub state has been changed to AD Follow up from New Id Needed |
2010-11-23
|
10 | (System) | New version available: draft-merrick-jms-uri-10.txt |
2010-11-17
|
12 | Alexey Melnikov | Intended Status has been changed to Informational from None |
2010-11-17
|
12 | Alexey Melnikov | State changed to AD Evaluation::Revised ID Needed from AD is watching::AD Followup. |
2010-09-15
|
09 | (System) | New version available: draft-merrick-jms-uri-09.txt |
2010-07-27
|
08 | (System) | New version available: draft-merrick-jms-uri-08.txt |
2010-07-19
|
12 | Alexey Melnikov | State Changes to AD is watching::AD Followup from AD is watching by Alexey Melnikov |
2010-07-19
|
12 | Alexey Melnikov | Draft Added by Alexey Melnikov in state AD is watching |
2010-05-18
|
07 | (System) | New version available: draft-merrick-jms-uri-07.txt |
2009-07-01
|
06 | (System) | New version available: draft-merrick-jms-uri-06.txt |
2008-11-18
|
05 | (System) | New version available: draft-merrick-jms-uri-05.txt |
2008-10-13
|
04 | (System) | New version available: draft-merrick-jms-uri-04.txt |
2008-04-22
|
03 | (System) | New version available: draft-merrick-jms-uri-03.txt |
2008-04-17
|
02 | (System) | New version available: draft-merrick-jms-uri-02.txt |
2008-02-15
|
01 | (System) | New version available: draft-merrick-jms-uri-01.txt |