Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

WebRTC 1.0 sync: H.264 parameters #158

Closed
aboba opened this issue Oct 27, 2014 · 1 comment
Closed

WebRTC 1.0 sync: H.264 parameters #158

aboba opened this issue Oct 27, 2014 · 1 comment
Labels
1.0 compatibility issue

Comments

@aboba
Copy link
Contributor

aboba commented Oct 27, 2014

For WebRTC 1.0, https://tools.ietf.org/html/draft-ietf-rtcweb-video Section 5.2 specifies the relevant parameters for H.264.

Within the ORTC API draft, Section 9.4.2.3 describes the supported H.264 parameters (max-recv-level and packetization-mode).

Rather than including its own set of parameters, the ORTC API should reference draft-ietf-rtcweb-video Section 5.2 and sync up with it.
@aboba
Copy link
Contributor Author

aboba commented Oct 29, 2014

The proposed revision is as follows:

9.4.2.3 H.264

The following capabilities are defined for H.264, as noted in [RFC6184] Section 8.1, and [RTCWEB-VIDEO] Section 5.2.

Property Name Values Notes
profile-level-id unsigned long
This parameter, defined in [RFC6184] Section 8.1, is mandatory to support, as noted in [RTCWEB-VIDEO] Section 5.2.

packetization-mode sequence
A sequence of unsigned shorts, each ranging from 0 to 2, indicating supported packetization-mode values. As noted in [RTCWEB-VIDEO] Section 5.2, support for packetization-mode 1 is mandatory.

max-mbps, max-smbps, max-fs, max-cpb, max-dpb, max-br unsigned long
As noted in [RTCWEB-VIDEO] Section 5.2, these optional parameters allow the implementation to specify that they can support certain features of H.264 at higher rates and values than those signalled with profile-level-id.

robin-raymond pushed a commit that referenced this issue Jan 22, 2015
Updated Section 8.3 to reflect proposed matching rules, reflecting:
a927ecf 
#48

Update to the Statistics API, reflecting:
#85

Update on 'automatic' use of scalable video coding, as noted in:
#156

Update to the H.264 parameters, as noted in:
#158

Update to the 'Big Picture', as noted in:
#159

Added support for maxptime, as noted in:
#160

Changed 'RTCIceTransportEvent' to 'RTCIceGathererEvent' as noted in:
#161

Update to RTCRtpUnhandledEvent as noted in:
#163

Added support for RTCIceGatherer.state as noted in:
#164

Revised the text relating to RTCIceTransport.start() as noted in:
#166

Added text relating to DTLS interoperability with WebRTC 1.0, as noted in:
#167

Revised the text relating to RTCDtlsTransport.start() as noted in:
#168

Clarified handling of incoming connectivity checks by the RTCIceGatherer as noted in:
#170

Added a reference to the ICE consent specification, as noted in:
#171
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1.0 compatibility issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aboba @robin-raymond