Discussion of scene and capture scene entry concepts
draft-groves-clue-scene-clarifications-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christian Groves , Weiwei Yang , Roni Even , Paul Kyzivat | ||
| Last updated | 2013-03-15 (Latest revision 2012-09-11) | ||
| 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
The CLUE framework document defines the concept of media captures which identify and describe the characteristics of media sent by a provider. A capture scene is a grouping concept that provides ties a number of captures together. Within the capture scene the media captures may further be grouped into capture scene entries. The current text in the CLUE framework document describing these concepts could be improved and clarified so that both providers and consumers use the same logic to encode/decode CLUE messages with capture scenes/ capture scene entries and media captures. This draft discusses these concepts and provides suggested updates.
Authors
Christian Groves
Weiwei Yang
Roni Even
Paul Kyzivat
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)