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 22:04:46 +0100

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

On Dec 24, 2013, at 12:45 PM, Pascal Quantin <pascal.quantin () gmail com>

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.

3GPP2 isn't GSM. :-)  (Or, speaking as a North American, perhaps that
should be :-( - at least with LTE maybe everybody will be doing their
mobile phone/mobile-broadband-not-called-WiMAX-etc. stuff the same way,
even if, with LTE, you are in a maze of twisty little frequency bands, all
different.  Maybe someday in my lifetime all mobile
phones/tablets/mobile-phone-modems/etc. will be world phones/etc.....)

That's why I'd vote for not putting "gsm" into the name, either; it's also
used by ANSI IS-637-A.

Well, ANSI IS-37-A refers to this encoding as GSM 7bit also ;) And as its
own ANSI 7 bits encoding format (which encoding is different - starting
from MSB and not LSB).

And a "7 bit item" could be a single 7-bit field, so I'd vote for

That could be a trade-off :p
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 ]