This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14514 - A 44 byte header seems excessive. Consider that for a modern speech codec like Speex, a 20ms payload may only be 10 bytes. Even bundling 80ms together, the header will be larger than the payload.
Summary: A 44 byte header seems excessive. Consider that for a modern speech codec li...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard: WebRTC
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-19 19:53 UTC by contributor
Modified: 2012-07-18 18:40 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2011-10-19 19:53:51 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/video-conferencing-and-peer-to-peer-communication.html
Multipage: http://www.whatwg.org/C#the-data-stream
Complete: http://www.whatwg.org/c#the-data-stream

Comment:
A 44 byte header seems excessive.  Consider that for a modern speech codec
like Speex, a 20ms payload may only be 10 bytes.  Even bundling 80ms together,
the header will be larger than the payload.

Posted from: 17.197.111.181
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/534.51.22 (KHTML, like Gecko) Version/5.1.1 Safari/534.51.22
Comment 1 Ian 'Hixie' Hickson 2011-12-01 23:14:18 UTC 
WebRTC is now done by the public-webrtc@w3.org group.