Skip to main content

IMAP URL Scheme
draft-ietf-lemonade-rfc2192bis-09

Revision differences

Document history

Date Rev. By Action
2012-08-22
09 (System) post-migration administrative database adjustment to the No Objection position for Sam Hartman
2007-08-29
09 (System) IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor
2007-08-29
09 (System) IANA Action state changed to Waiting on RFC Editor from In Progress
2007-08-29
09 (System) IANA Action state changed to In Progress from Waiting on Authors
2007-08-28
09 (System) IANA Action state changed to Waiting on Authors from In Progress
2007-08-28
09 (System) IANA Action state changed to In Progress
2007-08-28
09 Amy Vezza State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza
2007-08-27
09 Amy Vezza IESG state changed to Approved-announcement sent
2007-08-27
09 Amy Vezza IESG has approved the document
2007-08-27
09 Amy Vezza Closed "Approve" ballot
2007-08-27
09 Lisa Dusseault State Changes to Approved-announcement to be sent from IESG Evaluation::AD Followup by Lisa Dusseault
2007-08-27
09 Sam Hartman [Ballot Position Update] Position for Sam Hartman has been changed to No Objection from Discuss by Sam Hartman
2007-08-24
09 (System) Removed from agenda for telechat - 2007-08-23
2007-08-23
09 Amy Vezza State Changes to IESG Evaluation::AD Followup from IESG Evaluation by Amy Vezza
2007-08-23
09 Jon Peterson [Ballot Position Update] New position, No Objection, has been recorded by Jon Peterson
2007-08-22
09 Lars Eggert [Ballot comment]
Please check all uses of "optional" and "optionally" in the document -
IMO they should all become RFC2119 OPTIONALs.
2007-08-22
09 Lars Eggert [Ballot Position Update] New position, No Objection, has been recorded by Lars Eggert
2007-08-21
09 Sam Hartman
[Ballot discuss]
Section 10.1 says:
>    The "user+" access identifier limits resolution of that URL
>    to a particular userid, whereas the "submit+" …
[Ballot discuss]
Section 10.1 says:
>    The "user+" access identifier limits resolution of that URL
>    to a particular userid, whereas the "submit+" access iden-
>    tifier is more general and simply requires that the session be
>    authorized by a user that has been granted a "submit" role within
>    the authentication system.  Use of either of these access identi-
>    fiers makes it impossible for an attacker, spying on the session,
>    to use the same URL, either directly or by submission to a message
>    submission entity.











I don't understand how the last sentence is true at all.
2007-08-21
09 Sam Hartman [Ballot Position Update] New position, Discuss, has been recorded by Sam Hartman
2007-08-21
09 Dan Romascanu [Ballot Position Update] New position, No Objection, has been recorded by Dan Romascanu
2007-08-20
09 Ron Bonica [Ballot Position Update] New position, No Objection, has been recorded by Ron Bonica
2007-08-20
09 David Ward [Ballot Position Update] New position, No Objection, has been recorded by David Ward
2007-08-20
09 Jari Arkko [Ballot comment]
FYI: I verified the ABNF -- its OK, or at least it compiles.
2007-08-20
09 Jari Arkko [Ballot comment]
FYI - I verified the ABNF.
2007-08-20
09 Jari Arkko [Ballot Position Update] New position, No Objection, has been recorded by Jari Arkko
2007-08-17
09 Chris Newman [Ballot Position Update] New position, Recuse, has been recorded by Chris Newman
2007-08-16
09 Cullen Jennings Placed on agenda for telechat - 2007-08-23 by Cullen Jennings
2007-08-16
09 Ron Bonica Removed from agenda for telechat - 2007-08-23 by Ron Bonica
2007-08-16
09 Russ Housley
[Ballot comment]
Please turn off hyphenation.

  At the bottom of each page, I expect the authors to be
  "Melnikov & Newman" (not "Newman …
[Ballot comment]
Please turn off hyphenation.

  At the bottom of each page, I expect the authors to be
  "Melnikov & Newman" (not "Newman & Co").

  It looks like the usual postprocessor was not used since the
  bottom of each page includes "FORMFEED[Page x]".

  Section 6.1.1.2 says:
  >
  > The mailbox access key is a random string with at least 128 bits of
  > entropy.  It is generated by software (not by the human user), and
  > MUST be unpredictable.
  >
  As written, I do not think this is an easily tested MUST statement.
  So, I suggest dropping the MUST statement.  I propose:
  >
  > The mailbox access key is an unpredictable, random string.  To
  > ensure unpredictability, the random string with at least 128 bits of
  > entropy is generated by software or hardware (not by the human user).
2007-08-16
09 Russ Housley [Ballot Position Update] New position, No Objection, has been recorded by Russ Housley
2007-08-14
09 Ross Callon [Ballot Position Update] New position, No Objection, has been recorded by Ross Callon
2007-08-14
09 Tim Polk [Ballot Position Update] New position, No Objection, has been recorded by Tim Polk
2007-08-09
09 (System) New version available: draft-ietf-lemonade-rfc2192bis-09.txt
2007-07-31
09 Lisa Dusseault Placed on agenda for telechat - 2007-08-23 by Lisa Dusseault
2007-07-31
09 Lisa Dusseault State Changes to IESG Evaluation from Waiting for AD Go-Ahead::AD Followup by Lisa Dusseault
2007-07-31
09 Lisa Dusseault Ballot has been issued by Lisa Dusseault
2007-07-30
09 (System) Sub state has been changed to AD Follow up from New Id Needed
2007-07-30
08 (System) New version available: draft-ietf-lemonade-rfc2192bis-08.txt
2007-07-24
09 Lisa Dusseault State Changes to Waiting for AD Go-Ahead::Revised ID Needed from Waiting for AD Go-Ahead by Lisa Dusseault
2007-07-24
09 Lisa Dusseault Chris to suggest license text?
2007-07-06
09 Samuel Weiler Request for Last Call review by SECDIR Completed. Reviewer: Shawn Emery.
2007-06-28
09 (System) State has been changed to Waiting for AD Go-Ahead from In Last Call by system
2007-06-20
09 Yoshiko Fong
IANA Evaluation Comments:

Upon approval of this document, the IANA will make
the following changes in "Uniform Resource Identifer
(URI) Schemes" registry located at

http://www.iana.org/assignments/uri-schemes.html …
IANA Evaluation Comments:

Upon approval of this document, the IANA will make
the following changes in "Uniform Resource Identifer
(URI) Schemes" registry located at

http://www.iana.org/assignments/uri-schemes.html

[sub-registry "Permanent URI Schemes"]

OLD:
URI Scheme Description Reference
---------- ----------- ---------
imap internet message access protocol [RFC2192]

NEW:
URI Scheme Description Reference
---------- ----------- ---------
imap internet message access protocol [RFC-lemonade-rfc2192bis-07]

We understand the above to be the only IANA Action
for this document.
2007-06-15
09 Samuel Weiler Request for Last Call review by SECDIR is assigned to Shawn Emery
2007-06-15
09 Samuel Weiler Request for Last Call review by SECDIR is assigned to Shawn Emery
2007-06-14
09 Amy Vezza Last call sent
2007-06-14
09 Amy Vezza State Changes to In Last Call from Last Call Requested by Amy Vezza
2007-06-14
09 Lisa Dusseault Last Call was requested by Lisa Dusseault
2007-06-14
09 Lisa Dusseault State Changes to Last Call Requested from Publication Requested by Lisa Dusseault
2007-06-14
09 Lisa Dusseault [Ballot Position Update] New position, Yes, has been recorded for Lisa Dusseault
2007-06-14
09 Lisa Dusseault Ballot has been issued by Lisa Dusseault
2007-06-14
09 Lisa Dusseault Created "Approve" ballot
2007-06-14
09 (System) Ballot writeup text was added
2007-06-14
09 (System) Last call text was added
2007-06-14
09 (System) Ballot approval text was added
2007-06-01
09 Chris Newman
As I'm a co-editor for this document, I have to recuse myself from the
IESG process.

This document is a revision of RFC 2192 (the …
As I'm a co-editor for this document, I have to recuse myself from the
IESG process.

This document is a revision of RFC 2192 (the first RFC I wrote) that
folds in changes from RFC 4467 (URLAUTH) so the URL scheme is documented
in one place.  This replaces the portion of RFC 4467 that extends the
IMAP URL scheme, but does not replace the portion of RFC 4467 that
extends IMAP.  Although Alexey did almost all of the work on this
revision, it still contains a large amount of text I wrote and thus it
would be inappropriate for me to be responsible AD for this document.

Passing AD ownership to Lisa.
2007-06-01
09 Chris Newman Responsible AD has been changed to Lisa Dusseault from Chris Newman
2007-06-01
09 Chris Newman Need to add a permission grant for the sample code since the IETF Trust copyright doesn't do that.
2007-06-01
09 Chris Newman State Change Notice email list have been change to lemonade-chairs@tools.ietf.org, alexey.melnikov@isode.com, chris.newman@sun.com from lemonade-chairs@tools.ietf.org
2007-05-24
09 Dinara Suleymanova
PROTO Write-up

(1.a) Document Shepherd: Eric Burger, eburger@bea.com, personally reviewed
this document. This document is ready for publication.

(1.b) Work group review: The lemonade …
PROTO Write-up

(1.a) Document Shepherd: Eric Burger, eburger@bea.com, personally reviewed
this document. This document is ready for publication.

(1.b) Work group review: The lemonade work group provided review of this
document.

(1.c) Further review required: This document does not need further
specialized review, as it has received review by many members of the IMAP
community. There are no concerns regarding internationalization, as one of
the co-editors is an expert on internationalization.

(1.d.i) Document Shepherd Comfort Level: High
(1.d.ii) Document Useful and Needed: Yes
(1.d.iii) IPR Disclosures: None known

(1.e) Work Group Consensus: There is a solid WG consensus behind the
document.

Note that the document is a normative dependency of the Lemonade Profile
Bis document.

(1.f) There are no members with objections or concerns. There are no
threats of appeal or process issues.

(1.g.i) ID-nits: Checked and verified with idnits 2.04.07; warnings are a
lack of TOC, a lack of (or rather, bizarre) page separators, an incorrectly
identified unused reference [DATETIME] which appears in an ABNF comment, and
the self-reference RFCXXXX. The real errors of the page separators and the
self-reference are for the RFC Editor to correct.

(1.g.ii) MIB Doctor: Not applicable
(1.g.iii) Media Type: Not applicable
(1.g.iv) URI Type: As it defines a URI scheme, it should have URI expert
review. Ted Hardie, one of the URI experts, reviewed the document.
However, I forgot to send a note to the URI review list. That will happen
in parallel with this request to publish.

(1.h.i) Reference split: Yes
(1.h.ii) Downward normative references: No
(1.h.iii) References to drafts: No

(1.i) IANA Considerations: Yes, correct, consistent, and follows RFC 3501
rules.

(1.j) ABNF: Passes Bill's ABNF parser.

(1.k) Document Announcement:

Technical Summary

IMAP (RFC 3501) is a rich protocol for accessing remote message stores.
It provides an ideal mechanism for accessing public mailing list
archives as well as private and shared message stores. This document
defines a URL scheme for referencing objects on an IMAP server.

This document obsoletes RFC 2192 and updates RFC 4467.


Working Group Summary
This document removed support for IMAP URLs for listing the contents of a
mailbox. There was a clear consensus that this feature (originally
described in RFC 2192) was never implemented.

Some of the changes to the document were a result of the Lemonade
interoperability event of October 2006 held in London, England.

Document Quality

The document received several positive reviews. In particular it is
worth noting Ted Hardie and Zoltan Ordogh have done detailed reviews of the
document. This document addresses all issues raised.

Personnel
Eric Burger shepherds this document on behalf of Chris Newman, the
responsible Area Director. Eric Burger reviewed this document and
believes it is ready for forwarding to the IESG for publication.
2007-05-24
09 Dinara Suleymanova Draft Added by Dinara Suleymanova in state Publication Requested
2007-05-22
07 (System) New version available: draft-ietf-lemonade-rfc2192bis-07.txt
2007-05-08
06 (System) New version available: draft-ietf-lemonade-rfc2192bis-06.txt
2007-05-04
05 (System) New version available: draft-ietf-lemonade-rfc2192bis-05.txt
2007-01-29
04 (System) New version available: draft-ietf-lemonade-rfc2192bis-04.txt
2006-11-28
03 (System) New version available: draft-ietf-lemonade-rfc2192bis-03.txt
2006-05-15
02 (System) New version available: draft-ietf-lemonade-rfc2192bis-02.txt
2006-02-06
01 (System) New version available: draft-ietf-lemonade-rfc2192bis-01.txt
2005-10-06
00 (System) New version available: draft-ietf-lemonade-rfc2192bis-00.txt