From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [sim-auth RFCv2 2/4] Added doc/sim-authentication-api.txt.
Date: Tue, 18 Jan 2011 21:34:51 -0600 [thread overview]
Message-ID: <4D365BDB.7020109@gmail.com> (raw)
In-Reply-To: <1294873702-10316-3-git-send-email-Pekka.Pessi@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
Hi Pekka,
On 01/12/2011 05:08 PM, Pekka.Pessi(a)nokia.com wrote:
> From: Pekka Pessi <Pekka.Pessi@nokia.com>
>
> The authentication mechanisms include SIM authentication (basic A8
> authentication used with GSM), AKA authentication and UICC-based GBA
> authentication.
>
> The SIM and AKA can be used to implement EAP and GBA authentication
> algorithms.
>
> The interface can be applied to both SIM/USIM or ISIMs.
So I think this is a great start, but the entirety of this proposal
might be too much (at least for me) to digest all at once. So my vote
would be that we start with the simplest SIM authentication mechanism
and implement it first. We can mark the API as experimental during this
time. Then add additional mechanisms as we gain better understanding /
have time to read the specs.
Specifically I'd like to see the flow from the core atom to the AT / ISI
modem.
Regards,
-Denis
next prev parent reply other threads:[~2011-01-19 3:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 23:08 [sim-auth RFCv2 0/4] Pekka.Pessi
2011-01-12 23:08 ` [sim-auth RFCv2 1/4] TODO: add SIM authentication Pekka.Pessi
2011-01-12 23:08 ` [sim-auth RFCv2 2/4] Added doc/sim-authentication-api.txt Pekka.Pessi
2011-01-12 23:08 ` [sim-auth RFCv2 3/4] Add GBA documents to doc/standards.txt Pekka.Pessi
2011-01-12 23:08 ` [sim-auth RFCv2 4/4] Include doc/sim-authentication-api.txt in dist Pekka.Pessi
2011-01-19 3:35 ` [sim-auth RFCv2 3/4] Add GBA documents to doc/standards.txt Denis Kenzior
2011-01-19 3:34 ` Denis Kenzior [this message]
2011-01-19 3:27 ` [sim-auth RFCv2 1/4] TODO: add SIM authentication Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D365BDB.7020109@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.