IMAP UNAUTHENTICATE Extension for Connection Reuse
RFC 8437
Revision differences
Document history
| Date | Rev. | By | Action |
|---|---|---|---|
|
2019-08-19
|
01 | Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events' |
|
2019-08-19
|
01 | Gunter Van de Velde | Assignment of request for Last Call review by OPSDIR to Carlos Martínez was marked no-response |
|
2018-11-19
|
01 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Carlos Martínez |
|
2018-11-19
|
01 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Carlos Martínez |
|
2018-11-08
|
01 | Carlos Martínez | Assignment of request for Last Call review by OPSDIR to Carlos Martínez was rejected |
|
2018-08-24
|
01 | (System) | Received changes through RFC Editor sync (created alias RFC 8437, changed title to 'IMAP UNAUTHENTICATE Extension for Connection Reuse', changed abstract to 'This specification … Received changes through RFC Editor sync (created alias RFC 8437, changed title to 'IMAP UNAUTHENTICATE Extension for Connection Reuse', changed abstract to 'This specification extends the Internet Message Access Protocol (IMAP) to allow an administrative client to reuse the same IMAP connection on behalf of multiple IMAP user identities.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-08-24, changed IESG state to RFC Published, created updates relation between draft-ietf-extra-imap-unauth and RFC 3501) |
|
2018-08-24
|
01 | (System) | RFC published |
|
2018-08-20
|
01 | (System) | RFC Editor state changed to <a href="http://www.rfc-editor.org/auth48/rfc8437">AUTH48-DONE</a> from AUTH48 |
|
2018-08-17
|
01 | (System) | RFC Editor state changed to <a href="http://www.rfc-editor.org/auth48/rfc8437">AUTH48</a> from AUTH48-DONE |
|
2018-08-17
|
01 | (System) | RFC Editor state changed to <a href="http://www.rfc-editor.org/auth48/rfc8437">AUTH48-DONE</a> from AUTH48 |
|
2018-08-13
|
01 | (System) | RFC Editor state changed to <a href="http://www.rfc-editor.org/auth48/rfc8437">AUTH48</a> from RFC-EDITOR |
|
2018-07-12
|
01 | (System) | RFC Editor state changed to RFC-EDITOR from EDIT |
|
2018-06-13
|
01 | (System) | IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor |
|
2018-06-12
|
01 | (System) | IANA Action state changed to Waiting on RFC Editor from Waiting on Authors |
|
2018-06-12
|
01 | (System) | IANA Action state changed to Waiting on Authors from In Progress |
|
2018-06-08
|
01 | (System) | IANA Action state changed to In Progress |
|
2018-06-08
|
01 | (System) | RFC Editor state changed to EDIT |
|
2018-06-08
|
01 | (System) | IESG state changed to RFC Ed Queue from Approved-announcement sent |
|
2018-06-08
|
01 | (System) | Announcement was received by RFC Editor |
|
2018-06-08
|
01 | Cindy Morgan | IESG state changed to Approved-announcement sent from Approved-announcement to be sent |
|
2018-06-08
|
01 | Cindy Morgan | IESG has approved the document |
|
2018-06-08
|
01 | Cindy Morgan | Closed "Approve" ballot |
|
2018-06-08
|
01 | Cindy Morgan | Ballot approval text was generated |
|
2018-06-08
|
01 | Alexey Melnikov | The updated version addressed IESG review and SecDir comments. |
|
2018-06-08
|
01 | Alexey Melnikov | IESG state changed to Approved-announcement to be sent from Approved-announcement to be sent::Point Raised - writeup needed |
|
2018-06-07
|
01 | Chris Newman | New version available: draft-ietf-extra-imap-unauth-01.txt |
|
2018-06-07
|
01 | (System) | New version approved |
|
2018-06-07
|
01 | (System) | Request for posting confirmation emailed to previous authors: Chris Newman <chris.newman@oracle.com> |
|
2018-06-07
|
01 | Chris Newman | Uploaded new revision |
|
2018-06-07
|
00 | Cindy Morgan | IESG state changed to Approved-announcement to be sent::Point Raised - writeup needed from Waiting for Writeup |
|
2018-06-07
|
00 | Ignas Bagdonas | [Ballot Position Update] New position, No Objection, has been recorded for Ignas Bagdonas |
|
2018-06-07
|
00 | Terry Manderson | [Ballot Position Update] New position, No Objection, has been recorded for Terry Manderson |
|
2018-06-06
|
00 | Adam Roach | [Ballot comment] This mechanism seems useful. Thanks to the author for sticking with it. I support Martin's comment. I also have a tiny editorial nit: … [Ballot comment] This mechanism seems useful. Thanks to the author for sticking with it. I support Martin's comment. I also have a tiny editorial nit: §8: > The original IMAP state machine was designed to allow a server > implementation approach where each IMAP authentication identity > matches an operating system identity and the server revokes all > administrative privilege onces authentication completes. Typo: "once" |
|
2018-06-06
|
00 | Adam Roach | [Ballot Position Update] New position, Yes, has been recorded for Adam Roach |
|
2018-06-06
|
00 | Martin Vigoureux | [Ballot comment] Hello, since you revise the state machine, shouldn't this Document update 3501? Thank you |
|
2018-06-06
|
00 | Martin Vigoureux | [Ballot Position Update] New position, No Objection, has been recorded for Martin Vigoureux |
|
2018-06-06
|
00 | Suresh Krishnan | [Ballot Position Update] New position, No Objection, has been recorded for Suresh Krishnan |
|
2018-06-06
|
00 | Ben Campbell | [Ballot comment] §2: There are a few instances of lower case 2119 keywords. Please consider using the boilerplate from RFC 8174 instead. §4.2, first paragraph, … [Ballot comment] §2: There are a few instances of lower case 2119 keywords. Please consider using the boilerplate from RFC 8174 instead. §4.2, first paragraph, 2nd sentence: The two MAYs seem more like statements of fact rather than new normative permissions. |
|
2018-06-06
|
00 | Ben Campbell | [Ballot Position Update] New position, No Objection, has been recorded for Ben Campbell |
|
2018-06-06
|
00 | Alissa Cooper | [Ballot comment] I was surprised to see normative language in this text in 4.2 since this behavior is specified elsewhere, not here: When a TLS … [Ballot comment] I was surprised to see normative language in this text in 4.2 since this behavior is specified elsewhere, not here: When a TLS [RFC5246] security layer is negotiated either via the STARTTLS command or use of the imaps port [RFC6186], IMAP servers MAY be configured to request a client certificate and IMAP clients MAY provide one. |
|
2018-06-06
|
00 | Alissa Cooper | [Ballot Position Update] New position, No Objection, has been recorded for Alissa Cooper |
|
2018-06-06
|
00 | Alvaro Retana | [Ballot Position Update] New position, No Objection, has been recorded for Alvaro Retana |
|
2018-06-06
|
00 | Eric Rescorla | [Ballot Position Update] New position, No Objection, has been recorded for Eric Rescorla |
|
2018-06-05
|
00 | Spencer Dawkins | [Ballot Position Update] New position, No Objection, has been recorded for Spencer Dawkins |
|
2018-06-04
|
00 | Benjamin Kaduk | [Ballot comment] Please consider using the RFC 8174 boilerplate instead of the RFC 2119 boilerplate; there seems to be at least one usage of a … [Ballot comment] Please consider using the RFC 8174 boilerplate instead of the RFC 2119 boilerplate; there seems to be at least one usage of a lowercase keyword. I do not remember seeing a response to the secdir review, which raises an issue that is probably worth addressing (even if it is largely editorial). I have a few other comments/questions, that happen by chance to all occur within Section 3. This command directs the server to reset all connection state, except for state at the TLS [RFC5465] layer. 5465 is IMAP NOTIFY, and a short Hamming distance from 5246 (TLS 1.2). Though I note that TLS 1.3 is in the RFC Editor's queue... If a mailbox was selected, the mailbox ceases to be selected but no expunge event is generated. If a SASL [RFC4422] security layer was active, it terminates immediately after the server sends the CRLF following the OK response. For the client, it terminates immediately after the CRLF following the UNAUTHENTICATE command. "terminate" applies only to outgoing messages, presumably? (Should this be made more explicit?) A similar thing applies to COMPRESS as enumerated in Section 4.1. Servers MAY choose to advertise the UNAUTHENTICATE capability only after authentication has completed. As a result, clients need to issue an IMAP CAPABILITY command after authentication in order to determine the availability of UNAUTHENTICATE. Is this because the ability to reset state may depend on the authentication mechanism used? |
|
2018-06-04
|
00 | Benjamin Kaduk | [Ballot Position Update] New position, No Objection, has been recorded for Benjamin Kaduk |
|
2018-06-04
|
00 | Mirja Kühlewind | [Ballot comment] Quick question, however, I really don't know much about IMAP: Would it already help to just use TLS1.3 0-RTT session resumption instead? |
|
2018-06-04
|
00 | Mirja Kühlewind | [Ballot Position Update] New position, No Objection, has been recorded for Mirja Kühlewind |
|
2018-06-03
|
00 | Warren Kumari | [Ballot Position Update] New position, No Objection, has been recorded for Warren Kumari |
|
2018-06-02
|
00 | Deborah Brungard | [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard |
|
2018-05-29
|
00 | David Waltermire | Request for Last Call review by SECDIR Completed: Has Nits. Reviewer: David Waltermire. Sent review to list. |
|
2018-05-29
|
00 | Alexey Melnikov | Ballot has been issued |
|
2018-05-29
|
00 | Alexey Melnikov | [Ballot Position Update] New position, Yes, has been recorded for Alexey Melnikov |
|
2018-05-29
|
00 | Alexey Melnikov | Created "Approve" ballot |
|
2018-05-29
|
00 | Alexey Melnikov | Ballot writeup was changed |
|
2018-05-22
|
00 | Roni Even | Request for Last Call review by GENART Completed: Ready. Reviewer: Roni Even. Sent review to list. |
|
2018-05-21
|
00 | (System) | IESG state changed to Waiting for Writeup from In Last Call |
|
2018-05-18
|
00 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Carlos Martinez |
|
2018-05-18
|
00 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Carlos Martinez |
|
2018-05-17
|
00 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to David Waltermire |
|
2018-05-17
|
00 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to David Waltermire |
|
2018-05-15
|
00 | (System) | IANA Review state changed to IANA OK - Actions Needed from IANA - Review Needed |
|
2018-05-15
|
00 | Sabrina Tanamal | (Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs: The IANA Services Operator has completed its review of draft-ietf-extra-imap-unauth-00. If any part of this review is inaccurate, please let … (Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs: The IANA Services Operator has completed its review of draft-ietf-extra-imap-unauth-00. If any part of this review is inaccurate, please let us know. The IANA Services Operator understands that, upon approval of this document, there is a single action which we must complete. In the Internet Message Access Protocol (IMAP) Capabilities Registry located at: http://www.iana.org/assignments/imap-capabilities/ a single, new registration is to be made as follows: Capability Name: UNAUTHENTICATE Reference: [ RFC-to-be ] The IANA Services Operator understands that this is the only action required to be completed upon approval of this document. Note: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed. Thank you, Sabrina Tanamal Senior IANA Services Specialist |
|
2018-05-10
|
00 | Jean Mahoney | Request for Last Call review by GENART is assigned to Roni Even |
|
2018-05-10
|
00 | Jean Mahoney | Request for Last Call review by GENART is assigned to Roni Even |
|
2018-05-10
|
00 | Alexey Melnikov | Placed on agenda for telechat - 2018-06-07 |
|
2018-05-07
|
00 | Amy Vezza | IANA Review state changed to IANA - Review Needed |
|
2018-05-07
|
00 | Amy Vezza | The following Last Call announcement was sent out (ends 2018-05-21):<br><br>From: The IESG <iesg-secretary@ietf.org> To: IETF-Announce <ietf-announce@ietf.org> CC: draft-ietf-extra-imap-unauth@ietf.org, extra@ietf.org, … The following Last Call announcement was sent out (ends 2018-05-21):<br><br>From: The IESG <iesg-secretary@ietf.org> To: IETF-Announce <ietf-announce@ietf.org> CC: draft-ietf-extra-imap-unauth@ietf.org, extra@ietf.org, brong@fastmailteam.com, extra-chairs@ietf.org, alexey.melnikov@isode.com, Bron Gondwana <brong@fastmailteam.com> Reply-To: ietf@ietf.org Sender: <iesg-secretary@ietf.org> Subject: Last Call: <draft-ietf-extra-imap-unauth-00.txt> (IMAP UNAUTHENTICATE for Connection Reuse) to Proposed Standard The IESG has received a request from the Email mailstore and eXtensions To Revise or Amend WG (extra) to consider the following document: - 'IMAP UNAUTHENTICATE for Connection Reuse' <draft-ietf-extra-imap-unauth-00.txt> as Proposed Standard 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 2018-05-21. 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. Abstract This specification extends the Internet Message Access Protocol (IMAP) to allow an administrative client to reuse the same IMAP connection on behalf of multiple IMAP user identities. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-extra-imap-unauth/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-extra-imap-unauth/ballot/ No IPR declarations have been submitted directly on this I-D. |
|
2018-05-07
|
00 | Amy Vezza | IESG state changed to In Last Call from Last Call Requested |
|
2018-05-07
|
00 | Alexey Melnikov | Last call was requested |
|
2018-05-07
|
00 | Alexey Melnikov | Last call announcement was generated |
|
2018-05-07
|
00 | Alexey Melnikov | Ballot approval text was generated |
|
2018-05-07
|
00 | Alexey Melnikov | Ballot writeup was generated |
|
2018-05-07
|
00 | Alexey Melnikov | IESG state changed to Last Call Requested from AD Evaluation |
|
2018-05-07
|
00 | Alexey Melnikov | IESG state changed to AD Evaluation from Publication Requested |
|
2018-04-26
|
00 | Bron Gondwana | Document Shepherd Write-Up for draft-extra-imap-unauth 1. This document is being requested as an Internet Standard because it extends an existing Internet Standard (RFC3501). … Document Shepherd Write-Up for draft-extra-imap-unauth 1. This document is being requested as an Internet Standard because it extends an existing Internet Standard (RFC3501). The request type is indicated in the title page header. 2. Technical Summary This spec extends IMAP to add a symetrical way to return to UNAUTHENTICATED state from an AUTHENTICATED connection. Working Group Summary This spec was accepted at the IETF101 meeting. It has been around for years, but there was nowhere to submit it. Document Quality The specification has been in use in at least one site for multiple years. The integrations with various IMAP extensions have been very carefully specified. Personnel Document Shepherd - Bron Gondwana (EXTRA co-chair) Responsible Area Director - Alexey Melnikov 3. The Document Shepherd has read the document through in detail and is happy that it's easy to implement. 4. It would be good to see another couple of reviews for this document during the last call period. 5. There is no review required for the document by other areas. 6. There are no concerns with this document that IESG should be aware of. 7. There have been no IPR disclosures for this spec. 8. There have been no IPR disclosures for this spec. 9. The WG consensus is solid. 10. There has been no discontent. 11. The ID nits tool found no issues. 12. This document doesn't define anything which needs formal review outside the working group. 13. All references have been identified as either normative or informative. 14. All normative references are published standards. 15. There are no downward normative references references. 16. This RFC does not change the status of any other RFCs. 17. The only IANA request is an additional IMAP capability. 18. There is no expert review required. 19. The formal sections are simple enough that eyeball reading was sufficient to validate them. |
|
2018-04-26
|
00 | Bron Gondwana | Responsible AD changed to Alexey Melnikov |
|
2018-04-26
|
00 | Bron Gondwana | IETF WG state changed to Submitted to IESG for Publication from In WG Last Call |
|
2018-04-26
|
00 | Bron Gondwana | IESG state changed to Publication Requested |
|
2018-04-26
|
00 | Bron Gondwana | IESG process started in state Publication Requested |
|
2018-04-26
|
00 | Alexey Melnikov | Intended Status changed to Proposed Standard from Internet Standard |
|
2018-03-29
|
00 | Bron Gondwana | Changed document writeup |
|
2018-03-29
|
00 | Bron Gondwana | IETF WG state changed to In WG Last Call from WG Document |
|
2018-03-29
|
00 | Bron Gondwana | Changed consensus to Yes from Unknown |
|
2018-03-29
|
00 | Bron Gondwana | Intended Status changed to Internet Standard from None |
|
2018-03-29
|
00 | Bron Gondwana | Notification list changed to Bron Gondwana <brong@fastmailteam.com> |
|
2018-03-29
|
00 | Bron Gondwana | Document shepherd changed to Bron Gondwana |
|
2018-03-29
|
00 | Bron Gondwana | This document now replaces draft-extra-imap-unauth instead of None |
|
2018-03-29
|
00 | Chris Newman | New version available: draft-ietf-extra-imap-unauth-00.txt |
|
2018-03-29
|
00 | (System) | WG -00 approved |
|
2018-03-27
|
00 | Chris Newman | Set submitter to "Chris Newman <chris.newman@oracle.com>", replaces to draft-extra-imap-unauth and sent approval email to group chairs: extra-chairs@ietf.org |
|
2018-03-27
|
00 | Chris Newman | Uploaded new revision |