1 / 13

IMAP CONVERT

Alexey Melnikov Stéphane Maes Ray Cromwell draft-ietf-lemonade-convert-10.txt. IMAP CONVERT. Open issue. Do we need BODYPARTSTRUCTURE to be returned only when requested Always (i.e. on CONVERT.SIZE) only on the first request for a particular body part conversion. Arnt Gulbrandsen

christen-dixon
Download Presentation

IMAP CONVERT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Alexey Melnikov Stéphane Maes Ray Cromwell draft-ietf-lemonade-convert-10.txt IMAP CONVERT IETF 69 - Chicago, USA

  2. IETF 69 - Chicago, USA Open issue • Do we need BODYPARTSTRUCTURE to be returned • only when requested • Always (i.e. on CONVERT.SIZE) • only on the first request for a particular body part conversion

  3. Arnt Gulbrandsen Curtis King Alexey Melnikov draft-gulbrandsen-imap-notify-07.txt IMAP NOTIFY IETF 69 - Chicago, USA

  4. IETF 69 - Chicago, USA Major changes since Prague IETF • Extended the NOTIFY command to allow disabling of all events (NOTIFY NONE), replacement of events (NOTIFY SET) and addition of new events (NOTIFY ADD) • Defined which IMAP Access Control List rights needed to different events • Many clarifications about which responses are used for returning of different events. E.g. extended LIST response is used to return renamed mailboxes • Allow for better binding of events to mailboxes (.e.g. “a mailbox and its children” or “all subscribed mailboxes) • (editorial) Renamed events to keep in sync with draft-ietf-lemonade-msgevent-04.txt • (editorial) many fixes to examples, changes to ABNF, etc.

  5. IETF 69 - Chicago, USA Open Issues/ToDo(1 of 3) • (Arnt) it would be nice to control if STATUS responses are returned on NOTIFY SET/ADD or not [bandwidth] • (Arnt) does client need to tell the server to bind several IMAP connections together? • When the NOTIFY command should return tagged NO response due to access controls

  6. IETF 69 - Chicago, USA Open Issues(2 of 3) • (Alexey) Need to clarify that lack of the MessageExpunge event means default IMAP behaviour (== no EXPUNGE response can be sent when there is no command in progress) • Some events don't have a corresponding event in draft-ietf-lemonade-msgevent-04.txt (is this a problem?) • (Peter Coates) allow to specify a single search criteria for multiple events

  7. IETF 69 - Chicago, USA Open Issues(3 of 3) • (Peter Coates) Remove message-search-criteria from the NOTIFY extension, use CONTEXT instead • (Peter Coates) get rid of the fetch-atts on MessageNew event [Alexey: Disallow fetch-atts on non-selected mailboxes (?)]

  8. Dave Cridland Alexey Melnikov Stéphane Maes draft-ietf-lemonade-profile-bis-05.txt LEMONADE Profile bis IETF 69 - Chicago, USA

  9. IETF 69 - Chicago, USA ESMTP AUTH STARTTLS PIPELINING 8BITMIME CHUNKING BINARYMIME DSN SIZE ENHANCEDSTATUSCODES BURL Profile MUST implement IMAP • STARTTLS • CATENATE • URLAUTH • UIDPLUS • LITERAL+ • CONDSTORE • NAMESPACE • IDLE

  10. IETF 69 - Chicago, USA Phase bis - MUST implement(IMAP, documents completed) [green – need to be added to the Profile Bis draft] • All of Profile • Quick Reconnect (QRESYNC), SASL-IR • Search/sort extensions: ESEARCH, WITHIN, SORT • COMPARATOR (draft-imapext-i18n) • Views: CONTEXT=SEARCH, CONTEXT=SORT & ESORT (?)(draft-cridland-imap-contexts-03.txt) • ENABLE, METADATA, LIST-EXTENDED • Bandwidth optimizations • COMPRESS=DEFLATE • BINARY (including APPEND) • Content Transformation: CONVERT (Static) • Allow Partial URLs in CATENATE and URLAUTH (needs new IMAP capability)

  11. IETF 69 - Chicago, USA Phase bis - MUST implement(IMAP, work in progress) • In-band notifications: NOTIFY (draft-gulbrandsen-imap-notify-07.txt) • Streaming (URLAUTH extension) ? • Storing views on the server: draft-melnikov-imapext-filters-00.txt (?)

  12. IETF 69 - Chicago, USA Phase bis - MUST implement (SMTP) • All of Profile • QUICKSTART (draft-fanf-smtp-quickstart-00) - out?

  13. IETF 69 - Chicago, USA SIEVE Filters (?) IMAP Sieve How to manage scripts? Phase bis - Optional/undecided Out-band notifications • Format • One or more example binding to a notification protocol (BIFF BOF?)

More Related