OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

imi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: IMI TC Minutes, Dec 17th


1. Call to order/roll call

Mario Ivkovic A-SIT, Zentrum fur sichere Informationstec...

Jeffrey Broberg CA*

John Bradley Individual

Michael McIntosh Individual

Marc Goodner Microsoft

Michael Jones Microsoft

Anthony Nadalin Microsoft

 

Lost voting status

None

 

Gained voting status

None

 

2. Approve minutes from previous call

Dec 3rd  

http://lists.oasis-open.org/archives/imi/200912/msg00005.html

 

3. Interop demo at RSA

http://lists.oasis-open.org/archives/imi/200912/msg00083.html

Looking at spaces now, several other TCs looking at participating

TC would define scenarios that drive our participation

OASIS would manage signage, venue logistics, time schedule between TCs in booth

Other participants must be OASIS members, should be members of TC but not required

Our TC working with OSIS on scenarios

Focus around ICAM profiles which could be an issue as some companies working on those scenarios are not OASIS members

Our scenario would focus around the ICAM profile to get GSA/NIH involvement

Dee will setup an interop list for the IMI TC

Tony, John and Mike will work on recruiting other participants

 

4. Issues

IMI-23 SAML 1.1 token encoding profile needed

http://tools.oasis-open.org/issues/browse/IMI-23

Resolved to close as we have created this profile

 

IMI-24 SAML 2.0 token encoding profile needed

http://tools.oasis-open.org/issues/browse/IMI-24

Resolved to close as we have created this profile

 

IMI-25: ic09:X509Principal and ic09:X509SubjectAndIssuerintroduced in locations that violate IMI 1.0 schema

http://lists.oasis-open.org/archives/imi/200912/msg00002.html

Resolved, part of latest IMI 1.1 draft

 

IMI-26 Conflict between SAML 2.0 token profile and WS-Trust

http://lists.oasis-open.org/archives/imi/200912/msg00050.html

http://lists.oasis-open.org/archives/imi/200912/msg00033.html

Resolved, part of latest 2.0 profile

 

IMI-27 Need for more specificity in issuer language for SAML 2.0 token profile

http://lists.oasis-open.org/archives/imi/200912/msg00051.html

http://lists.oasis-open.org/archives/imi/200912/msg00039.html

Resolved, part of latest 2.0 profile

 

IMI-28 Requirement for AudienceRestriction when AppliesTo provided may be overly restrictive

http://lists.oasis-open.org/archives/imi/200912/msg00052.html

http://lists.oasis-open.org/archives/imi/200912/msg00034.html

Close with no action

 

SAML 2.0 token profile

Current drafts

http://lists.oasis-open.org/archives/imi/200912/msg00075.html

http://lists.oasis-open.org/archives/imi/200912/msg00076.html

Diff:

http://lists.oasis-open.org/archives/imi/200912/msg00077.html

 

Editorial issues remain with draft, assigned to editors to resolve

 

SAML 1.1 token profile

Current draft:

http://lists.oasis-open.org/archives/imi/200912/msg00047.html

http://lists.oasis-open.org/archives/imi/200912/msg00048.html

 

Needs some editing related to IMI-28, otherwise complete for previous issues

Please review before next call

 

IMI-29 displayType Object Tag Property

http://lists.oasis-open.org/archives/imi/200912/msg00055.html

Allows web RP to display card image inline in page

 

IMI-30 requireUserInteraction Object Tag Property

http://lists.oasis-open.org/archives/imi/200912/msg00056.html

Allows RP to require explicit user interaction before submitting a card, allows override of card auto submission

IMI-31 tryGetTokenAutomatic Object Tag Method

http://lists.oasis-open.org/archives/imi/200912/msg00057.html

Similar to passive authN request in SAML 2 or check immediate in OpenID

Assumption that default card selected by user or provisioned by administrators

Triggered via script, not user interaction

 

IMI-32 hasCapability Object Tag Method

http://lists.oasis-open.org/archives/imi/200912/msg00058.html

From OSIS discussions, allows selectors to advertise capabilities they have, e.g. card tile support or authN mechanisms

Proposed list of capabilities, but this is extensible and expected TC may define more over time

 

Proposed resolutions for issues 29 – 32 above accepted for inclusion in new IMI 1.1 draft and assigned to editors

 

5. Other business

 

Next call is Jan 7th  and back to biweekly schedule

 

Discussion of both chairs being from the same company

Primary concern is optics external to TC, nothing in OASIS rules require chairs be from different companies

No action decided in absence of request from TC membership

 

6. Adjournment

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]