Re: [RFC PATCH 0/4] Automatic provisioning of GPRS context settings

[Marcel Holtmann <marcel@holtmann.org>]

[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]

Hi Jukka,

> Here is a first attempt to implement automatic provisioning of
> Internet and MMS GPRS context settings. ("Internet Access Provider
> database" TODO item).
> 
> In case there are no previously configured contexts found during gprs
> atom registration, this code tries to provision Internet and MMS
> contexts based on MCC, MNC and SPN (Service Provider Name) values read
> from SIM. Settings are read from an operator settings database.
> 
> Settings database is CSV (comma separated values) formatted file(s)
> with fields for: (type=INTERNET|MMS protocol=ipv4|ipv6)
> MCC,MNC,SPN,type,UI name, APN, username, password, protocol, proxy IP address, proxy port, MMS server URL
> 
> e.g. file /etc/ofono/operator-settings/50-default.csv:
> 001,01,test,INTERNET,Network Tester GPRS,internet,,,,,,
> 246,81,oFono,INTERNET,Phonesim Internet,internet.apn,,,ipv4,,,
> 246,81,oFono,MMS,Phonesim MMS,mms.apn,mmsuser,mmspass,ipv4,10.10.10.10,8080,http://192.168.0.111:8002
> 
> This format is loosely based on what was used in Nokia N900 for
> similar use.

I am really not set on a file format, but my obvious question is if we
don't wanna better use keyfile or XML based database since that are the
file formats we are currently using inside oFono. We have not used CSV
at all so far.

My vote would go for keyfile or XML since it is a bit more self
explanatory with its fields. And the order of values doesn't really
matter.

The one thing that I don't like about CSV is that you have no real
flexibility with its format. Especially coming think about that we might
have to extend this additional information for IMS or operator specific
behavior.

Regards

Marcel