RFC 5383: Deployment Considerations for Lemonade-Compliant Mobile Email
In plain English — editorial summary, not part of the RFC
This document discusses deployment issues and describes requirements for successful deployment of mobile email that are implicit in the IETF lemonade documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5383
- Published
- October 2008
- Authors
- R. Gellens
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- app
- Pages
- 12
- Also known as
- BCP143
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5423Internet Message Store EventsCurrent
March 2009
- RFC 5429Sieve Email Filtering: Reject and Extended Reject ExtensionsCurrent
March 2009
- RFC 5337Internationalized Delivery Status and Disposition NotificationsObsoleted
September 2008
- RFC 5336SMTP Extension for Internationalized Email AddressesObsoleted
September 2008
- RFC 5335Internationalized Email HeadersObsoleted
September 2008
- RFC 5435Sieve Email Filtering: Extension for NotificationsUpdated
January 2009
- RFC 5436Sieve Notification Mechanism: mailtoCurrent
January 2009
- RFC 5437Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)Current
January 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?