- From: Iñaki Baz Castillo via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 May 2017 11:27:36 +0000
- To: public-webrtc@w3.org
ibc has just created a new issue for https://github.com/w3c/webrtc-pc: == Are camelCase codec parameters useful at all? == Currently EDGE does not use camelCase RTP codec parameters (it uses `packetization-mode` rather than `packetizationMode` and so on). Also, there is no proper "conversion rule". In SDP land we have parameters such as `sprop-maxcapturerate`, `useinbandfec` and `L` that are mapped to `spropMaxCaptureRate`, `useInbandFec` and `l` forcing the implementation to keep a map of them (as [here](https://github.com/versatica/mediasoup/blob/master/lib/extra/index.js#L3)). But, at the end, not even EDGE implements the ORTC camelCase syntax. Given that having a different naming provides zero benefit here, why not keep untouched the SDP naming? Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1179 using your GitHub account
Received on Monday, 8 May 2017 11:27:43 UTC