RFC 5285 defines "A General Mechanism for RTP Header Extensions", this includes a mecanism to negotiate a ID to type mapping. This needs to be signalled down and back up (as they are subject to SDP Offer/Answer negotiation). So we should probably add it to the CodecOffer.. For each possibility, the relevant fields are: ID (a uint), direction (sendrecv, recvonly, sendonly, inactive), URI
To support this, avpf, rtcp xr, maybe we should have a asv in the CodecOffer or something.
I forgot to mention, these are not per-codec, they are per Content.
There can also be extension attributes for each one, so maybe we should add a asv. Although nothing in the RFC says they will be using the a=b form.
An array, containing: u: ID u: send/recv/both/none s: URI s: misc
Drafted: http://git.collabora.co.uk/?p=user/tester/telepathy-spec.git;a=shortlog;h=refs/heads/rtp-hdrext
Remove Method Port to MediaDescription Remove the Local.. it is the answer the Description always has the remote
Drafted at: http://git.collabora.co.uk/?p=user/tester/telepathy-spec.git;a=shortlog;h=refs/heads/rtp-hdrext-mediadesc As for rtcp-fb and codecs, I think the Remote in the property should go
Again, I think s/Remote/Supported/ Also, I think you mean "list" below: 68 A lost of remote header extensions which have been set Otherwise, ++
I went for s/Remote// (a la rtcp-fb-mediadesc) instead, and pushed to: http://git.collabora.co.uk/?p=user/alsuren/telepathy-spec.git;a=commitdiff;h=refs/heads/rtp-hdrext-mediadesc-ftfy
++
Abusing Assigned to mean "merged in alsuren/call and available at http://people.freedesktop.org/~alsuren/telepathy-spec-call/spec/". There was a trivial patch required compared to what was reviewed (http://git.collabora.co.uk/?p=user/alsuren/telepathy-spec.git;a=commitdiff;h=0fe25dbc2175557a4ade4db78154a186ffd4452f) to actually make the thing compile. I took the liberty of considering it insta-reviewed.
*cough*
Marged to master.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.