https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2706
Chris Maynard <christopher.maynard@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #8 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2010-10-21 12:01:41 PDT ---
(In reply to comment #7)
> I guess we'll wait to hear what the ITU says ...
On second thought, I think this bug report deserves to be treated like
football's "instant replay". It's obvious that there are ambiguities in the
ITU specification with respect to the Test TLV, but the original author
interpreted it as a normal TLV as described in Figure 9.1-2, as Jeff mentioned,
with the length including all bytes of the Value field. In the case of the
Test TLV, the Value field really is comprised of the Pattern Type, Test pattern
and CRC-32 (if present). This seems to be the most likely case and the bug is
very likely with the wording of the ITU specification rather than with
Wireshark's dissector.
So, with this in mind, I'm closing this bug as INVALID, letting "the call on
the field stand", so to speak, due to insufficient and inconclusive evidence to
overturn it. If the ITU or anyone else ever provides information to the
contrary, we can always overturn it at that point, in which case the patch
provided earlier could be applied.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
