RFC 5442: LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile Email (MEM) Using Internet Mail
In plain English — editorial summary, not part of the RFC
This document specifies the architecture for mobile email, as described by the Open Mobile Alliance (OMA), using Internet Mail protocols. This architecture was an important consideration for much of the work of the LEMONADE (Enhancements to Internet email to Support Diverse Service Environments) working group in the IETF. This document also describes how the LEMONADE architecture meets OMA's requirements for their Mobile Email (MEM) service. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5442
- Published
- March 2009
- Authors
- E. Burger; G. Parsons
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3523Internet Emergency Preparedness (IEPREP) Telephony Topology TerminologyCurrent
April 2003
- RFC 5437Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)Current
January 2009
- RFC 5436Sieve Notification Mechanism: mailtoCurrent
January 2009
- RFC 5435Sieve Email Filtering: Extension for NotificationsUpdated
January 2009
- RFC 5429Sieve Email Filtering: Reject and Extended Reject ExtensionsCurrent
March 2009
- RFC 5458Security Requirements for the Unidirectional Lightweight Encapsulation (ULE) ProtocolCurrent
March 2009
- RFC 5423Internet Message Store EventsCurrent
March 2009
- RFC 5463Sieve Email Filtering: Ihave ExtensionCurrent
March 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?