This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Neels Hofmeyr nhofmeyr at sysmocom.deOn Fri, Mar 11, 2016 at 10:18:57PM +0700, Harald Welte wrote: > Please see 11.2.3.2.1 and 11.2.3.2.2 of 3GPP TS 24.007, e.g. the latest > version 12.0.0 Release 12 as available from > http://www.etsi.org/deliver/etsi_ts/124000_124099/124007/12.00.00_60/ts_124007v120000p.pdf > > There you can see that in Release99 and later networks, the message type > for MM, CC and SS is defined as having the upper two bits as "N (SD)", > whereas other protocols have other definitions for those bits. > > "N (SD)" is described in 11.2.3.2.3 of the same spec Ah, interesting! I'm not entirely sure how we want to handle whether we're Release99 or not ... is all our code Release99 per se (that's 17 years ago, right!?), or should that be decided at compile or run time? Here, I'd use the 0x3f mask for MM and CC, period; particularly because none of our message type definitions use bit 8 anyway. Opinions? ~Neels -- - Neels Hofmeyr <nhofmeyr at sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschäftsführer / Managing Directors: Holger Freyther, Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20160314/4657b8e8/attachment.bin>