CLUE protocol
draft-presta-clue-protocol-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Roberta Presta , Simon Pietro Romano | ||
| Last updated | 2014-05-08 (Latest revision 2013-11-04) | ||
| Replaced by | draft-ietf-clue-protocol, draft-ietf-clue-protocol, RFC 8847 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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 CLUE protocol is an application protocol conceived for the description and negotiation of a CLUE telepresence session. The design of the CLUE protocol takes into account the requirements and the framework defined, respectively, in [I-D.ietf-clue-framework] and [I-D.ietf-clue-telepresence-requirements]. The companion document [I-D.kyzivat-clue-signaling] delves into CLUE signaling details, as well as into the SIP/SDP session establishment phase. We herein focus on the application level perspective. Message details, together with the behavior of CLUE participants acting as Media Providers and/or Media Consumers, are discussed.
Authors
Roberta Presta
Simon Pietro Romano
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)