Home page logo
/

wireshark logo Wireshark mailing list archives

Re: 3GPP 23.038 encoding and string length
From: Pascal Quantin <pascal.quantin () gmail com>
Date: Tue, 24 Dec 2013 21:45:15 +0100

2013/12/24 Guy Harris <guy () alum mit edu>


On Dec 24, 2013, at 5:30 AM, mmann78 () netscape net wrote:

Isn't it simple enough to add a proto_tree_add_gsm_sms_item (or similar)
API

We already have tvbuff and proto_tree_ routines that take bit offsets and
bit counts, so this may be another case where the regular routines don't
work; a routine to handle TS 23.038 encoding, taking a *bit* offset and a
count of *characters*, might be the best solution here.

I'd vote for proto_tree_add_ts_23_038_item(), though - that encoding isn't
used only in the GSM/3GPP/LTE version of SMS.


I would vote for proto_tree_add_gsm_7bits_item() as TS 23.038 talks about 8
bits data and UCS2 encoding also and defines this alphabet as GSM 7bit. We
should not put SMS in its name as it has a much wider use in 3GPP / 3GPP2.

Pascal.
___________________________________________________________________________
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-request () wireshark org?subject=unsubscribe

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]