Re: [codec] Frames to Packets in draft-ietf-codec-opus-07?

I agree that this can be handled in PAYLOAD / packetization.

While I see some value in ensuring that OPUS can run over non-RTP
transports, I am thinking that we really don't need to re-create all the
packetization features available in RTP inside of OPUS elementary streams.
At some point the level of return on the investment of time drops off - I am
thinking we are reaching that point.

Stephen Botzko

On Fri, Jul 29, 2011 at 9:57 AM, Kevin P. Fleming <kpfleming@digium.com>wrote:

> On 07/28/2011 07:53 PM, Timothy B. Terriberry wrote:
>
>> Would it be possible to add an appendix or create an additional document
>>> that describes how a middlebox could detect mode changes and avoid
>>> concatenating in these cases?
>>>
>>
>> This is basically as simple as examining the first byte of the packet.
>> But if you have some example text I'd be happy to make an appendix for
>> it (and possibly other related issues).
>>
>
> If the PAYLOAD group ends up defining a multi-frame packetization mechanism
> for RTP encapsulation of Opus, then a middlebox could just use that
> mechanism and not have to care about whether the encoder changed modes
> between frames.
>
> --
> Kevin P. Fleming
> Digium, Inc. | Director of Software Technologies
> Jabber: kfleming@digium.com | SIP: kpfleming@digium.com | Skype: kpfleming
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> Check us out at www.digium.com & www.asterisk.org
>
> ______________________________**_________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/**listinfo/codec<https://www.ietf.org/mailman/listinfo/codec>
>