Requirements for Telepresence Multi-Streams
draft-ietf-clue-telepresence-requirements-06
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 7262.
|
|
|---|---|---|---|
| Authors | Dr. Allyn Romanow , Stephen Botzko , Mary Barnes | ||
| Last updated | 2013-11-27 (Latest revision 2013-10-21) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
GENART Last Call review
by Dan Romascanu
Almost ready
SECDIR Last Call review
by Joseph Salowey
Has issues
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Paul Kyzivat | ||
| Shepherd write-up | Show Last changed 2013-10-30 | ||
| IESG | IESG state | Became RFC 7262 (Informational) | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | Gonzalo Camarillo | ||
| Send notices to | clue-chairs@tools.ietf.org, draft-ietf-clue-telepresence-requirements@tools.ietf.org | ||
| IANA | IANA review state | IANA OK - No Actions Needed |
draft-ietf-clue-telepresence-requirements-06
Internet-Draft CLUE Telepresence Requirements October 2013 A.5. Changes from draft -01 o Cleaned up the Problem Statement section, re-worded. o Added Requirement Paragraph 17 in response to WG Issue #4 to make a requirement for dynamically changing information. Approved by WG o Added requirements #1.c and #1.d. Approved by WG o Added requirements #2.d and #2.e. Approved by WG A.6. Changes From Draft -00 o Requirement #2, The solution MUST support a means to identify monaural, stereophonic (2.0), and 3.0 (left, center, right) audio channels. changed to The solution MUST support a means to identify the number and spatial arrangement of audio channels including monaural, stereophonic (2.0), and 3.0 (left, center, right) audio channels. o Added back references to the Use case document. * Requirement #1 Use case point to point symmetric, and all other use cases. * Requirement #2 Use case point to point symmetric, and all use cases, especially heterogeneous. * Requirement #3 Use case point to point symmetric, and all use cases. * Requirement #4 Use case is asymmetric point to point, and multipoint. * Requirement #9 Use case heterogeneous and multipoint. * Requirement #12 Use case multipoint. Romanow, et al. Expires April 24, 2014 [Page 13] Internet-Draft CLUE Telepresence Requirements October 2013 Authors' Addresses Allyn Romanow Cisco Systems San Jose, CA 95134 USA Email: allyn@cisco.com Stephen Botzko Polycom Andover, MA 01810 US Email: stephen.botzko@polycom.com Mary Barnes Polycom Email: mary.ietf.barnes@gmail.com Romanow, et al. Expires April 24, 2014 [Page 14]