Push Extensions to the IMAP Protocol (P-IMAP)
draft-maes-lemonade-p-imap-12

Document Type Expired Internet-Draft (individual)
Last updated 2006-03-06
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-maes-lemonade-p-imap-12.txt

Abstract

Push Extensions to the IMAP protocol (P-IMAP) defines extensions to the IMAPv4 Rev1 protocol [RFC3501] for optimization in a mobile setting, aimed at delivering extended functionality for mobile devices with limited resources. The first enhancement of P-IMAP is extended support to push changes actively to a client, rather then requiring the client to initiate contact to ask for state changes. In addition, P-IMAP contains extensions for email filter management, message delivery, and maintaining up-to-date personal information. Bindings to specific transport are explicitly defined. Eventually P- IMAP aims at being neutral to the network transport neutrality. P-IMAP is a recommendation for interoperable intermediate implementations awaiting [LEMONADEPROFILEBIS] or the realization of the OMA MEM enabler using it.

Authors

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)