Protocol for Controlling Multiple Streams for Telepresence (CLUE)
RFC 8847
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2023-02-01
|
Jenny Bui | Posted related IPR disclosure Koninklijke KPN N.V.'s Statement about IPR related to RFC 8845, RFC 8846, and RFC 8847 |
|
2021-01-21
|
(System) | IANA registries were updated to include RFC8847 |
|
2021-01-18
|
(System) | Received changes through RFC Editor sync (created alias RFC 8847, changed abstract to 'The Controlling Multiple Streams for Telepresence (CLUE) protocol is an application … Received changes through RFC Editor sync (created alias RFC 8847, changed abstract to 'The Controlling Multiple Streams for Telepresence (CLUE) protocol is an application protocol conceived for the description and negotiation of a telepresence session. The design of the CLUE protocol takes into account the requirements and the framework defined within the IETF CLUE Working Group. A companion document, RFC 8848, delves into CLUE signaling details as well as the SIP / Session Description Protocol (SDP) session establishment phase. CLUE messages flow over the CLUE data channel, based on reliable and ordered SCTP-over-DTLS transport. ("SCTP" stands for "Stream Control Transmission Protocol".) Message details, together with the behavior of CLUE Participants acting as Media Providers and/or Media Consumers, are herein discussed.', changed pages to 62, changed standardization level to Experimental, changed state to RFC, added RFC published event at 2021-01-18, changed IESG state to RFC Published) |
|
2021-01-18
|
(System) | RFC published |