TelcoSIG20081016

Liberty Alliance Project
Telecommunications SIG
Conference Call Notes
October 16, 2008
10:30am-11:45am
Author: Kurt Kolok

Attendance:

NTT, Shin Adachi
TeliaSonera, Olli Jussila
TeliaSonera, Mikko Laukkanen
Ericsson, Jonas Hogberg
Voice Security Systems, Sherry Adcock
Deutsche Telekom AG, Ingo Friese
Sun Microsystems, Fulup Ar Foll

Liberty Staff, Brett McDowell
Liberty Staff, Britta Glade
Liberty Staff, Joni Brennan
Liberty Staff, Kurt Kolok

Agenda:

1. Introductions
2. Review Charter
3. Identify & discuss deliverables, next steps and topics of interest
4. AOB

1. Introductions:

Shin Adachi: from NTT.
Jonas Hogberg: from Ericsson; based in Madrid, works in systems department. Half the time he is working in standardization within LAP the other half of the time he is supporting product management within digital identity.
Olli Jussila: Works in mobility services R&D within TeliaSonera.
Sherry Adcock –CEO of Voice Security Systems; her desire is to keep up on standards for interoperability, and to gain additional information about standards. VSS licenses their technology.
Ingo Friese of Deutsche Telecom: has an interest in achieving solid standards and learn more about how to deal with identities from web world/IMS perspectives.

2. Review the charter

http://wiki.projectliberty.org/index.php/Liberty_Telecommunications_SIG_Charter

3. Identify & discuss deliverables, next steps & topics of interest

There is an activity within TEG to develop a white paper describing how IMS and Digital Identity Management can work together. The document should be completed by the end of 2008. Ideally they will use BMEG (LAP Business Marketing Expert Group) resources to drive the white paper from a marketing perspective.

We should look at what is happening within LAP as well as outside of LAP for the purposes of coordination and to identify and accelerate things that are not being addressed at all. This group could possibly coordinate with, accelerate or identify things that are not currently being addressed at all.

What role can the SIG play with regard to documentation/what can the SIG do?

There are volunteers within the SIG that can bring issues into the LAP expert groups. We can use the wiki to build ideas and discuss issues.

How would the SIG coordinate with other groups?

Some SIG members with rights to participate in LAP expert groups (EGs) are able to feed documents into those EGs for approval and publication as Liberty deliverables.

How does this SIG differ from the Standards SIG?

The Standards SIG communicates solely through a mail list and without teleconferences lacks the ability to support brainstorming opportunities. The Standards SIG is open only to Liberty members.

Topics of interest:

Trusted Module on SIM: putting trusted module that is in the Advanced Client onto the SIM card. Orange/FT is proposing a SIM card use case. (KARML, looking to ensure that the attribute privacy is protected, etc…). It would be helpful to have guidelines/recommendations.

Re: the Liberty TEG (Technology Expert Group) whitepaper—it is a typical Telco activity, but TEG would like to approve the document for publication by Liberty.

Support conversations between Telco SIG and GSMA Access. GSMA Access is developing some type of restful APIs.

Is there anything else happening within LAP that would be related to Telco? IAF (Identity Assurance Framework)—has anyone considered either IAF or the accreditation program as areas of interest? Non-technical issues are probably the most challenging at the moment.

X.eaa (entity authentication & authorization) is working with LAP and we hope it will result in Identity Assurance work opening the group up to some great opportunities for coordination.

IDP Selector work in BMEG

The IDP Selector work is a continuation of the work done in the Fidelity Project (how to select your IDP is very difficult and it is being investigated more thoroughly within BMEG). The IDP Selector problem is not unique to SAML deployments. OPEN ID shares similar problems.

Action 20081016-1: Kurt will check the LAP members on this call and make sure they are all on the BMEG mail list. In Progress

Concordia can be traced back to the Telco sector. The WSFederation protocol is leaning toward using SAML Authn Context. Government participants within LAP have developed a profile re: how to deploy SAML—that is an opportunity for this SIG (is it needed in telecommunications?). US Government has come to LAP to do interoperability testing. Voice XML Forum has approached LAP to have a liaison relationship because they have a voice biometrics effort (working group). Voice biometrics by themselves do not have much value—authentication would be relevant.

Fulup: FT/Orange is working on a use case for transfer of SSO from one device to another (something Telcos should be interested in). It would be useful to have Paul Madsen present the use case to this group at some point.

There is a big market education opportunity (to educate the public about the technical work of Liberty as it applies to Telcos). The entire community (operators and end users) need to be educated (this was a major finding of the Fidelity Project).

Fulup mentioned an example of a new SAML-based standard.

Jonas: We should have a discussion re: could we extend SAML in WSF-based service?

We will plan the next call for the week after next (week of Oct. 27).

Possible call schedule/frequency: Today’s time seems to work well for those currently on the call. Ericsson would prefer that an operator take the chair role, but if that is not feasible Jose Luis has agreed to step into the chair role. Teliasonera is not currently able to take a chair lead, but does plan on being an active participant.

Action 20081016-2: Brett will follow up with Orange—would they like to chair the group?

4. AOB—None

GSMA Access-related links:
http://www.project*liberty*.org/*liberty*/content/download/4473/30604/file/draft-*liberty*-idwsf-*mdsso*-deployguide-v1.0-02.pdf

Overview of GSMA 3rd Party Access:
http://www.w3.org/2008/07/pisa/GSMA_Access_Introduction.pdf

GSM Association beta project (to deliver standard developer APIs to allow common access to Network Services across all Operators):
https://gsma.securespsite.com/access/entry/default.aspx

Meeting Adjourned