Using MESSAGE for IM Sessions
draft-rosenberg-simple-message-session-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Jonathan Rosenberg | ||
Last updated | 2002-05-03 | ||
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
The SIMPLE working group has been debating the issue of the IM session model for quite some time. The primary issue is what transport to use for the IMs once the session is established with SIP. Proposals have included the SIP MESSAGE request itself, IMSX, and a SIP spin-off, called IMTP. The usage of SIP MESSAGE, the very first proposal, had been rejected by the group because of several technical issues. This document revists that decision, based on the recent enhancements made to SIP itself. We believe that SIP MESSAGE now represents the ideal transport choice for the IM session model.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)