ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 3974] wrong decoding of gtp.target identification

Date: Fri, 07 Dec 2012 04:58:55 +0000

Comment # 15 on bug 3974 from
Yes,
It is clear now "The preamble of the 'Target RNC-ID' (numerical value of e.g.
0x20) however shall not be included in octets 4-n.".
But if you notice the latest change request CR0913 in TS29.060(in attachment),
you may realize how bad are the serials of change request raised by Ericsson.
In order to contain the EnodeB ID, we have to introduce a new IE in GTP
message.
It would have been a simple call of RANAP dissector to decode all types of
Target ID, now it becomes the work of GTP.
Are those programmers really cheap today?

To emphasize my opinion, it is not the task of 3GPP TS29.060 to decode the
TargetRNCid, eitherr EnodeBid.


You are receiving this mail because:
  • You are the assignee for the bug.
  • You are watching all bug changes.