(Paging LTE experts here....) On Oct 12, 2011, at 8:02 AM, wme...@wireshark.org wrote:
> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=39384 > > User: wmeier > Date: 2011/10/12 08:02 AM > > Log: > Fix a benign bug: Use correct proto_tree_add_item() encoding arg. At least as I read RFC 3095: UOR-2-TS 0 1 2 3 4 5 6 7 +---+---+---+---+---+---+---+---+ | 1 1 0 | TS | +===+===+===+===+===+===+===+===+ |T=1| M | SN | +---+---+---+---+---+---+---+---+ | X | CRC | +---+---+---+---+---+---+---+---+ neither the old code nor the new code are correct - the "M" bit is in the octet after the TS field. I don't see anything obvious in 3GPP TS 36.323 itself that says the format is different; does something in a later RFC specify something different? ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
