https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6783
--- Comment #6 from Anders Broman <anders.broman@xxxxxxxxxxxx> 2012-02-01 12:28:09 PST ---
(In reply to comment #5)
> (In reply to comment #4)
> > Hi,
> > As I read the RFC the header extension is per payload-type AND then a number
> > is used. As there is no registration body for extension types there is a big
> > risk of collisions especialy if people choses "1" as the extension number.
> > That said your solution might be OK as we currently have no extensions
> > registered that I know of.
> > Regards
> > Anders
>
> Good to see you agreed with the patch. What is the process to incorporate it in
> wireshark source code?
>
> And, for information, from where in the RFC do you read the header extension is
> per payload? For me, it is a completely separate feature.
Ok I must have missread :-) however
5.3.1 RTP Header Extension
An extension mechanism is provided to allow individual
implementations to experiment with new payload-format-independent
^^^^^^^^^^
functions that require additional information to be carried in the
RTP data packet header
:
Note that this header extension is intended only for limited use.
:
Most potential uses of this mechanism would be better done another
way,..
:
Additional information required for a particular payload
format SHOULD NOT use this header extension..
:
To allow
multiple interoperating implementations to each experiment
independently with different header extensions, or to allow a
particular implementation to experiment with more than one type of
header extension, the first 16 bits of the header extension are left
open for distinguishing identifiers or parameters. The format of
these 16 bits is to be defined by the profile specification under
which the implementations are operating. This RTP specification does
not define any header extensions itself.
--- end quote --
"defined by the profile specification" was what caught my eye.
I'm not sure RTP extensions belong in Wireshark at all as it seems to me that
thay shouldn't realy be used, exept in short lived experiments.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
