RFC 3862: Common Presence and Instant Messaging (CPIM): Message Format
In plain English — editorial summary, not part of the RFC
This memo defines the MIME content type 'Message/CPIM', a message format for protocols that conform to the Common Profile for Instant Messaging (CPIM) specification. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3862
- Published
- August 2004
- Authors
- G. Klyne; D. Atkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3861Address Resolution for Instant Messaging and PresenceCurrent
August 2004
- RFC 3863Presence Information Data Format (PIDF)Current
August 2004
- RFC 3860Common Profile for Instant Messaging (CPIM)Current
August 2004
- RFC 3859Common Profile for Presence (CPP)Current
August 2004
- RFC 3867Payment Application Programmers Interface (API) for v1.0 Internet Open Trading Protocol (IOTP)Current
November 2004
- RFC 3876Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3)Current
September 2004
- RFC 3885SMTP Service Extension for Message TrackingCurrent
September 2004
- RFC 3838Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES)Current
August 2004
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?