[Standards] XEP-0167: Jingle RTP Sessions - payload type parameters w/o value?

Daniel Gultsch daniel at gultsch.de
Wed Jun 17 14:36:04 UTC 2020

There is a 2011 thread on the same topic:
https://mail.jabber.org/pipermail/jingle/2011-March/001438.html that
as far as I can tell (my personal archives don’t go back that far)
never went anywhere.

Am Mi., 17. Juni 2020 um 14:17 Uhr schrieb Daniel Gultsch <daniel at gultsch.de>:
> Hi,
> I've seen a couple of Jingle RTP implementations in the wild that send
> XML looking like this: (note the lack o a 'name' attribute)
> <payload-type channels="1" name="telephone-event" clockrate="8000" id="101">
>   <parameter value="0-15" xmlns="urn:xmpp:jingle:apps:rtp:1"/>
> </payload-type>
> which is illegal according to the (non normative) scheme (both name
> and value are required attributes) whereas the normative text doesn’t
> say anything on whether either or both value and name can be omitted.
> Can someone more familiar with what this actually maps to clarify?
> Note that the implementations sending this are parsing this from firefoxes SDP.
> cheers
> Daniel

More information about the Standards mailing list