28 Sep
2011
28 Sep
'11
8:02 p.m.
Hi Pablo,
On Tue, Sep 27, 2011 at 02:47:12PM +0200, Pablo Neira Ayuso wrote:
This new library, whose proposed name can be
"libosmo-net", would
initially support:
- E1 interfaces.
- Ethernet + IPA TCP/IP.
- rs232 (as required by bs11 its config interface).
This support is included in libosmo-abis, so my idea is to extract
this code from it and leave in libosmo-abis only the specific A-bis
bits.
I'm not sure if such a split is practical. What exactly woould remain
A-bis specific? The TRAU frame handling for voice channels?
For the A interface, I'd propose some hypothetical
libosmo-a library
that will contain the specific A interface protocols.
Once again I'm not entirely convinced that this is neccessarry. We
already have libosmo-sccp for the SCCP parsing routines, and the
BSSAP/BSSMAP layer is handled in osmo-bsc directly. So I don't really
see what would be left over as A-specific parts.
In order to stop further proliferation of small library fragments, I
would rather suggest to include any (if at all) remaining A-bis and A
related parts in the same libosmo-net.
btw: I'm still trying to come up with a better name. libosmo-signalling
is wrong as it will also deal with voice/trau/rtp. libosmo-interface
maybe? Also not a quite obvious naming. libosmo-netif as a compromise?
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)