| RFC 0000 | CLUE Framework | June 2020 |
| Duckworth, et al. | Standards Track | [Page] |
This document defines a framework for a protocol to enable devices in a telepresence conference to interoperate. The protocol enables communication of information about multiple media streams so a sending system and receiving system can make reasonable decisions about transmitting, selecting, and rendering the media streams. This protocol is used in addition to SIP signaling and Session Description Protocol (SDP) negotiation for setting up a telepresence session.¶
This is an Internet Standards Track document.¶
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.¶
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc0000.¶
Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
Current telepresence systems, though based on open standards such as RTP [...]¶
A Provider MAY include as much or as little of the original source Capture information as it requires.¶
The spatial-related attributes of an MCC indicate its area of capture and point of capture within the scene, just like any other media capture. The spatial information does not imply anything about how other captures are composed within an MCC.¶
For example: a virtual scene could be constructed for the MCC capture with two Video Captures with a "MaxCaptures" attribute set to 2 and an "Area of Capture" attribute provided with an overall area. Each of the individual Captures could then also include an "Area of Capture" attribute with a subset of the overall area. The Consumer would then know how each capture is related to others within the scene, but not the relative position of the individual captures within the composed capture.¶
Here is an example using <artwork>.¶
| Capture Scene #1 | |
|---|---|
| VC1 |
AreaofCapture=(0,0,0)(9,0,0)
(0,0,9)(9,0,9)
¶
|
| VC2 |
AreaofCapture=(10,0,0)(19,0,0)
(10,0,9)(19,0,9)
¶
|
| MCC1(VC1,VC2) |
MaxCaptures=2
AreaofCapture=(0,0,0)(19,0,0)
(0,0,9)(19,0,9)
¶
|
| CSV(MCC1) |
Here is an example using <td> with align=right.¶
| Capture Scene #1 | |
|---|---|
| VC1 |
AreaofCapture=(0,0,0)(9,0,0) (0,0,9)(9,0,9) |
| VC2 |
AreaofCapture=(10,0,0)(19,0,0) (10,0,9)(19,0,9) |
| MCC1(VC1,VC2) |
MaxCaptures=2 AreaofCapture=(0,0,0)(19,0,0) (0,0,9)(19,0,9) |
| CSV(MCC1) |
| Capture Scene #1 | |
|---|---|
| VC1 |
AreaofCapture=(0,0,0)(9,0,0) (0,0,9)(9,0,9) |
| VC2 |
AreaofCapture=(10,0,0)(19,0,0) (10,0,9)(19,0,9) |
| MCC1(VC1,VC2) | MaxCaptures=2 |
|
AreaofCapture=(0,0,0)(19,0,0) (0,0,9)(19,0,9) |
|
| CSV(MCC1) |
Here is an example using <ul>.¶
| Capture Scene #1 | |
|---|---|
| VC1 |
|
| VC2 |
|
| MCC1(VC1,VC2) | |
| CSV(MCC1) |
The subsections below describe the MCC-only attributes.¶