RFC 4566 Section 6 defines ptime and maxptime attributes: http://tools.ietf.org/html/rfc4566 Note that these operate at the m-line level, not codec: http://www.ietf.org/mail-archive/web/sip/current/msg14153.html However, "vsel" allows ptime but not max/min control at the codec level: http://www.ietf.org/mail-archive/web/mmusic/current/msg04253.html My suggestion would be to expose a sequence of ptime values in RTCRtpCodecCapability.parameters and then choose one in RTCRtpCodecParameters.parameters. On Nov 12, 2014, at 9:09 AM, pthatcherg <notifications@github.com<mailto:notifications@github.com>> wrote: Should we just put this in RtpCodecParameters.parameters, or should we have a specific RtpCodecParameters.ptime? Or do we want .minptime and .maxptime? On Wed Nov 12 2014 at 3:34:03 AM steely-glint <notifications@github.com<mailto:notifications@github.com>> wrote: > There are some situations where this would be useful. I'm thinking of > lowbandwidth audio only situations - like GSM Edge or BGAN or some > TV-whitespace deployments which work much better with bigger less frequent > packets. > > — > Reply to this email directly or view it on GitHub > <https://github.com/openpeer/ortc/issues/160#issuecomment-62717816>. > — Reply to this email directly or view it on GitHub<https://github.com/openpeer/ortc/issues/160#issuecomment-62774792>.
Received on Wednesday, 12 November 2014 20:12:16 UTC