oFono release plan?

oFono release plan?

[Sjur BRENDELAND]

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

Hi Denis and Marcel.

Do you have a release plan defined for oFono? 
When will you release oFono 1.0?

Thanks,

Regards
Sjur

Re: oFono release plan?

[Denis Kenzior]

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

Hi Sjur,

On 12/17/2010 10:21 AM, Sjur BRENDELAND wrote:
> Hi Denis and Marcel.
> 
> Do you have a release plan defined for oFono? 
> When will you release oFono 1.0?
> 

We do not have a concrete plan as of yet.  For the most part we were
quite happy with the current set of oFono APIs, however with LTE support
on the horizon we might have to revisit some of them.

Regards,
-Denis

Re: oFono release plan?

[Marcel Holtmann]

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

Hi Sjur,

> > Do you have a release plan defined for oFono? 
> > When will you release oFono 1.0?
> > 
> 
> We do not have a concrete plan as of yet.  For the most part we were
> quite happy with the current set of oFono APIs, however with LTE support
> on the horizon we might have to revisit some of them.

the upcoming LTE support holds us a little bit back. So Denis and I are
a bit careful about calling it 1.0 just yet.

In general the rule was to go for 1.0, when the D-Bus API seemed to be
working out nicely. For most atoms we have that right now and I am
pretty happy with the current API. It might need one additional in depth
review, but changes would be absolutely minor (besides LTE of course).

And then we wanted to get at least one GCF pre-certification result
before calling it 1.0 for real.

Regards

Marcel

Re: oFono release plan?

[Aki Niemi]

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

Hi Marcel,

2010/12/21 Marcel Holtmann <marcel@holtmann.org>:
> the upcoming LTE support holds us a little bit back. So Denis and I are
> a bit careful about calling it 1.0 just yet.

Can you elaborate here? I thought the conclusion of our discussions
was that the D-Bus API will see practically no changes due to LTE.

Cheers,
Aki

Re: oFono release plan?

[Marcel Holtmann]

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

Hi Aki,

> > the upcoming LTE support holds us a little bit back. So Denis and I are
> > a bit careful about calling it 1.0 just yet.
> 
> Can you elaborate here? I thought the conclusion of our discussions
> was that the D-Bus API will see practically no changes due to LTE.

we don't know that yet for sure. They might be all internal, but there
might be also D-Bus visible changes. We will see once LTE support lands
in oFono.

Regards

Marcel

Re: oFono release plan?

[Aki Niemi]

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

Hi Marcel,

2010/12/21 Marcel Holtmann <marcel@holtmann.org>:
> we don't know that yet for sure. They might be all internal, but there
> might be also D-Bus visible changes. We will see once LTE support lands
> in oFono.

Well, from my point of view there are some key APIs we know for sure
are missing. Off the top of my head:

- LCS, neighbor cell info
- CDMA support
- the SMS (history) agent API
- SIM authentication API (EAP-SIM, EAP-AKA, IMS and GBA)

Then again, I don't really see the point in a 1.0 beyond marketing.
It's not like the current D-Bus API is allowed to change a lot as it
stands currently.

Cheers,
Aki

Re: oFono release plan?

[Sankar]

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

Hi Aki,

On Tue, Dec 21, 2010 at 9:58 PM, Aki Niemi <aki@protocolpolice.com> wrote:

> Hi Marcel,
>
> 2010/12/21 Marcel Holtmann <marcel@holtmann.org>:
> > we don't know that yet for sure. They might be all internal, but there
> > might be also D-Bus visible changes. We will see once LTE support lands
> > in oFono.
>
> Well, from my point of view there are some key APIs we know for sure
> are missing. Off the top of my head:
>
> - LCS, neighbor cell info
> - CDMA support
>

Can you please add more light on what all is planned under the CDMA support.



> - the SMS (history) agent API
> - SIM authentication API (EAP-SIM, EAP-AKA, IMS and GBA)
>
Can you please add more light on what is supported. I could not find this
info in the todo list.

>
> Then again, I don't really see the point in a 1.0 beyond marketing.
> It's not like the current D-Bus API is allowed to change a lot as it
> stands currently.
>
> Cheers,
> Aki
>

Regards,
Sankar.

> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> http://lists.ofono.org/listinfo/ofono
>

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 2125 bytes --]

Re: oFono release plan?

[Aki Niemi]

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

Hi Sankar,

On Thu, 2010-12-23 at 15:16 +0530, ext Sankar wrote:

> Can you please add more light on what all is planned under the CDMA
> support.

See under doc the cdma-* files. However, these are proposals still, and
code is just being submitted for implementing these. That is not yet 1.0
material, IMHO.
 
>         - the SMS (history) agent API
>         - SIM authentication API (EAP-SIM, EAP-AKA, IMS and GBA)
> Can you please add more light on what is supported. I could not find
> this info in the todo list. 

In short, we need to expose certain security services offered by the SIM
card that utilize the crypto algorithms on the card. This is used for
instance in voice over LTE authentication procedures. Probably needs to
be added to the TODO.

Cheers,
Aki

Re: oFono release plan?

[Marcel Holtmann]

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

Hi Aki,

> >         - SIM authentication API (EAP-SIM, EAP-AKA, IMS and GBA)
> > Can you please add more light on what is supported. I could not find
> > this info in the todo list. 
> 
> In short, we need to expose certain security services offered by the SIM
> card that utilize the crypto algorithms on the card. This is used for
> instance in voice over LTE authentication procedures. Probably needs to
> be added to the TODO.

right now Andrew is looking into the SIM application discovery with AT
command modems. Once we have that, we can look into what is needed for
using the EAP methods and add details TODO items.

Just adding a simple TODO item entry that we split out later into more
detailed once would be fine with me.

In theory we want an interface that suits all SIM authentication needs.
Besides IMS, the second big user will be WISPr 2.0 for WiFi hotspots.

Regards

Marcel