UPDATED: JEP-0180 (Jingle Video Content Description Format)

Version 0.3 of JEP-0180 (Jingle Video Content Description
Format) has been released.

Abstract: This document defines a content description format
for Jingle video sessions.

Changelog: Modified namespace to track JEP-0166. (psa)

CVS Diff: http://www.jabberstu
dio.org/cgi-bin/viewcvs.cgi/cvs/jeps/0180/jep-0180.xml?r1=1.
2&r2=1.3

URL: http://www.j
abber.org/jeps/jep-0180.html

JEP Editor wrote:
> Version 0.3 of JEP-0180 (Jingle Video Content
Description Format) has been released.
> 
> Abstract: This document defines a content description
format for Jingle video sessions.
> 
> Changelog: Modified namespace to track JEP-0166. (psa)
> 
> CVS Diff: http://www.jabberstu
dio.org/cgi-bin/viewcvs.cgi/cvs/jeps/0180/jep-0180.xml?r1=1.
2&r2=1.3
> 
> URL: http://www.j
abber.org/jeps/jep-0180.html
> 
> 

One problem with current JEP 0180 is that it doesn't allow
for codec
dependant parameters. In SDP, these are usually specified as
'a=' lines,
with the name defined in the RTP payload RFC, which are
based off the
MIME Type Registration details. For example, see the a=fmtp
definition
in http://www.
rfc-editor.org/rfc/rfc3640.txt (section 4.4).

Maybe there's some way we can define based on the MIME type
parameters,
but note that applications are generally allowed to define
more parameters.


Thanks,
Rob Taylor