Additional H.241 Parameter in the RTP Payload Format for H.264 Video
draft-kristensen-payload-rtp-h241param-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tom Kristensen , Malcolm Walters | ||
| Last updated | 2013-04-18 (Latest revision 2012-10-15) | ||
| 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
As systems increasingly are able to run video at 60 frames per second, there is a need to signal desired frame rate to optimise resolution choices and to avoid unnecessary resource or energy usage. This document updates RFC6184 and defines a new optional parameter addressing recent extensions currently supported in H.323 systems: The signalling of the maximum frames per second that can be efficiently received or that can be sent.
Authors
Tom Kristensen
Malcolm Walters
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)