Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-ac3-01.txt

[Dave Singer <singer at apple.com>]

At 10:58 AM +0000 2/6/05, Colin Perkins wrote:
> Brian,
>
> On 20 Jan 2005, at 18:21, Link, Brian wrote:
> > I'm open to this idea, and I note the support from Dave and John. I'm
> > not familiar enough with the infrastructure of RTP to know the possible
> > mechanisms for associating data with any payload format. How would this
> > be done?
>
> One possibility might be to standardise a new RTP profile, with 
> additional header fields (e.g. as is being done for the RTP profile 
> for TFRC). Another might be a standard header extension, or new RTCP 
> packet types.
>
> > And from a procedural perspective, what is needed?
>
> Initially, a draft explaining the problem, and some analysis of why 
> is can't be solved using RTP + existing signalling mechanisms.
>
> Colin

Given that at least SMPTE time-codes tend to be calculable in 
segments, initial values in SDP and updates in RTCP was the way I was 
thinking.  I'll read 
<http://quimby.gnus.org/internet-drafts/draft-harrison-avt-precision-av-00.txt> 
also to see what else is on the table.
--
David Singer
Apple Computer/QuickTime

_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www1.ietf.org/mailman/listinfo/avt