CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 20:20:26 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=iLSxfndBm.MeWV.OCr5ykI8L3dytwXosjIxfIWBn2Wo-1760127626-1.0.1.1-V09qshlH9UQCSFntv6NmBxRH____.p.LCG7UQ6yqnuyrTeFWXoAC2Cr5J_lzvwJVP7MjYbp_oD7zz7JruR5xhvhQeabc4z6VgETUka6rOqI; path=/; expires=Fri, 10-Oct-25 20:50:26 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c8d17aca4fe8e0-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8850 » RFC Editor
Search RFCs
RFC 8850
Controlling Multiple Streams for Telepresence (CLUE) Protocol Data Channel, January 2021
- File formats:
- Also available: XML file for editing
- Status:
- EXPERIMENTAL
- Author:
- C. Holmberg
- Stream:
- IETF
- Source:
- clue (art)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8850
Discuss this RFC: Send questions or comments to the mailing list clue@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8850
Abstract
This document defines how to use the WebRTC data channel mechanism to realize a data channel, referred to as a Controlling Multiple Streams for Telepresence (CLUE) data channel, for transporting CLUE protocol messages between two CLUE entities.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us