W3C home > Mailing lists > Public > public-ortc@w3.org > November 2014

Re: [ortc] WebRTC 1.0 compatibility: support for p-time (#160)

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Wed, 12 Nov 2014 20:11:43 +0000
To: "public-ortc@w3.org" <public-ortc@w3.org>, "pthatcher@google.com" <pthatcher@google.com>, Robin Raymond <robin@hookflash.com>
CC: openpeer/ortc <ortc@noreply.github.com>
Message-ID: <7CD5709E-4C9C-4FC5-ADD9-A8B80413BC25@microsoft.com>
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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:39:54 UTC