Wireshark-bugs: [Wireshark-bugs] [Bug 3974] wrong decoding of gtp.target identification
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 07 Dec 2012 06:46:33 +0000

Comment # 16 on bug 3974 from 
(In reply to comment #15)
> 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 should voice thoce concerns in the 3GPP work group - the dissector deals
with the standard as published.

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