The need for audio rendering tag mechanism in the CLUE Framework
draft-romanow-clue-audio-rendering-tag-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Allyn Romanow , Robert Hansen , Andy Pepperell, Brian Baldino | ||
| Last updated | 2012-12-01 (Latest revision 2012-05-30) | ||
| 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 purpose of this draft is for discussion in the CLUE working group. It proposes adding an audio rendering tag to the CLUE framework [I-D.ietf-clue-framework], which makes it possible for the consumer to correctly render audio with respect to video in a multistream video conference. The solution proposed is in partial response to CLUE Task #10, Does Framework provide sufficient info for receiver?
Authors
Dr. Allyn Romanow
Robert Hansen
Andy Pepperell
Brian Baldino
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)