RFC 5524: Extended URLFETCH for Binary and Converted Parts
In plain English — editorial summary, not part of the RFC
The URLFETCH command defined as part of URLAUTH provides a mechanism for third parties to gain access to data held within messages in a user's private store; however, this data is sent verbatim, which is not suitable for a number of applications. This memo specifies a method for obtaining data in forms suitable for non-mail applications. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5524
- Published
- May 2009
- Authors
- D. Cridland
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent
August 2009
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 5259Internet Message Access Protocol - CONVERT ExtensionCurrent
July 2008
- RFC 4468Message Submission BURL ExtensionUpdated
May 2006
- RFC 4416Goals for Internet Messaging to Support Diverse Service EnvironmentsCurrent
February 2006
- RFC 5423Internet Message Store EventsCurrent
March 2009
- RFC 5257Internet Message Access Protocol - ANNOTATE ExtensionCurrent
June 2008
- RFC 5255Internet Message Access Protocol InternationalizationCurrent
June 2008
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?