Instant Message Disposition Notification (IMDN)
RFC 5438
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'Instant Messaging (IM) refers to the transfer of messages between users in real-time. This document provides … Received changes through RFC Editor sync (changed abstract to 'Instant Messaging (IM) refers to the transfer of messages between users in real-time. This document provides a mechanism whereby endpoints can request Instant Message Disposition Notifications (IMDN), including delivery, processing, and display notifications, for page-mode instant messages. The Common Presence and Instant Messaging (CPIM) data format specified in RFC 3862 is extended with new header fields that enable endpoints to request IMDNs. A new message format is also defined to convey IMDNs. This document also describes how SIP entities behave using this extension. [STANDARDS-TRACK]') |
|
2015-10-14
|
(System) | Notify list changed from simple-chairs@ietf.org to (None) |
|
2009-03-01
|
(System) | Posted related IPR disclosure: Nokia Corporation's Statement about IPR related to RFC 5438 |
|
2009-02-19
|
Cindy Morgan | State Changes to RFC Published from RFC Ed Queue by Cindy Morgan |
|
2009-02-19
|
Cindy Morgan | [Note]: 'RFC 5438' added by Cindy Morgan |
|
2009-02-18
|
(System) | RFC published |