Disposition Notification Requirements for Deferred Messaging
draft-stafford-simple-dmdn-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Matthew Stafford | ||
| Last updated | 2007-01-19 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo expands the set of use cases for SIP MESSAGE and SIP- controlled MSRP sessions. Following OMA, the new use cases include MSRP for one time messages that exceed the size limit for SIP requests over UDP, and extend the paradigm to deferred messaging. In deferred messaging, which is invoked when the intended recipient is not available, the message is sent to a store and forward server. The new requirements are for disposition notification functionality in this context.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)