[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-ac3-01.txt
On Feb 6, 2005, at 2:58 AM, Colin Perkins wrote:
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.
Reaching out to the folks involved in AES standardization efforts would
be a good thing to do early in the process:
http://www.aes.org/technical/nas/
And also, to reach out to other standards bodies who are stake holders.
Part of the reason why RTP MIDI has taken so long to bring to closure
(the research effort began in Fall 2000) was the number of times the
protocol
needed to be reworked to take into account the views of new parties
that joined
the effort mid-stream. In large part, because I didn't engage and
evangelize
the global MIDI constituency up front, but instead waited for them to
discover
the project themselves ...
---
John Lazzaro
http://www.cs.berkeley.edu/~lazzaro
lazzaro [at] cs [dot] berkeley [dot] edu
---
_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www1.ietf.org/mailman/listinfo/avt