Review of MSRP Delivery Mechanisms
draft-levin-simple-msrp-review-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Orit Levin | ||
Last updated | 2004-04-06 | ||
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 paper shows that the currently defined per-message hop-by-hop mechanism doesn22t scale for large deployments and is not feasible for scalable IM conferencing. Instead, the paper proposes to replace this mechanism with an MSRP layer "per TCP connection keep-alive mechanism". This paper also reinforces the need for the end-to-end mechanism to be defined in the core MSRP specification and to become the abstraction for all MSRP applications regardless the underlying topology in use.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)