[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: IMI TC Minutes, April 2nd 2009
|
1. Call to order/roll call Mario
Ivkovic A-SIT, Zentrum fur sichere Informationstec... Jeffrey
Broberg CA* Drummond
Reed Cordance* Michael
McIntosh IBM Bruce
Rich IBM John
Bradley Individual Scott
Cantor Internet2 Marc
Goodner Microsoft Corporation Michael
Jones Microsoft Corporation Dale
Olds Novell* Mike
Kirkwood Polka Networks, Inc. Lost
voting status None Gained
voting status None 2.
Reading/Approving minutes from last meeting http://lists.oasis-open.org/archives/imi/200903/msg00018.html Minutes
approved 3.
TC Logistics (10 minutes or less) Reminder;
chat room: http://webconf.soaphub.org/conf/room/imi
IMI
1.0 Public review ends Apr 27th, we have a call scheduled Apr 30th
We
should make sure to focus on resolving IMI 1.0 issues so editors can have a
draft ready to promote to CS on the 30th If
not we only have one other opportunity on May 14th call to approve a
CS before May 15th cutoff for June Agreed
on additional calls, cancel if not needed, on Apr 23rd and May 7th
to handle v1 issues to get a CS preparred in time 4.
Issues list -
Actions Old
issue list needs to be cleaned up, e.g. all issues marked closed or pointing to
new issue list as appropriate. Old
issue list: http://wiki.oasis-open.org/imi/IssueList Not
done AI
Chairs to add link to home page to new issue list. Not
done -
Issues http://tools.oasis-open.org/issues/browse/IMI IMI
1.0 issues PR
comment to change RSA key to public key in section 3.3.5.2 http://tools.oasis-open.org/issues/browse/IMI-1 Agreed
with proposal in mail, assigned to editors. Agreed
editorial and non-substantive change. PR
spec needs a 2119 review http://tools.oasis-open.org/issues/browse/IMI-2 Terms
in namespace table don’t need to be normative. Agree. Section
2.2, line 343, optional after MUST doesn’t seem normative. Suggest
deleting optional in that case. Assigned
to apply, but continue review. Agreed
editorial and non-substantive change. Validate
XML in spec is well formed http://tools.oasis-open.org/issues/browse/IMI-6
No
update. There
is no XSD file with the schema for the ic07 elements defined in the spec http://tools.oasis-open.org/issues/browse/IMI-7 Not
a change, just producing schema for what is in the spec. Propose
to send to list and add to doc repository. Agreed,
assigned to editors Agreed
editorial and non-substantive change. Card
image MIME types not enumerated in the specification http://tools.oasis-open.org/issues/browse/IMI-8
Propose
to update spec to reflect content present in schema Agreed,
assigned to editors Agreed
editorial and non-substantive change. Claim
value type ic:Value is specified as containing an xs:String, where as a SAML
attribute is specified as containing an xs:anyType http://tools.oasis-open.org/issues/browse/IMI-9 String
not consistent with SAML attribute which specifies xs:Any Text
in spec is about self issued cards where all values are strings, so change doesn’t
add value Proposal
is to close with no change, unstructured self issued would be work for a future
version Close
with no action, agreed The
color space for the ic:BackgroundColor element is not defined http://tools.oasis-open.org/issues/browse/IMI-10 Proposal
accepted, assigned to editors Agreed
editorial and non-substantive change. Section
12 uses the word "claim" to describe element values that are not
claims http://tools.oasis-open.org/issues/browse/IMI-11 Language
left over from addressing spec, not a claim a set of enumerated types Propose
changing from claim to representation Proposal
accepted, assigned to editors Agreed
editorial and non-substantive change. Language
in comments refers to "array of claims", where in context, they are
actually arrays of claim type URIs http://tools.oasis-open.org/issues/browse/IMI-12 From
a comment in an example, change to array of URIs of required claim types Proposal
accepted, assigned to editors Agreed
editorial and non-substantive change. Sec
8.1 Definition of canonical string representation of the IP address of the
server. Is ambiguous http://tools.oasis-open.org/issues/browse/IMI-16
Client
pseudonym text leaving zeros in for canonicalization of IP address is not
specified, not specified behavior Believe
there was an RFC where string representation of IP address had no zeroes Agree
this should be made explicit and reference relevant RFC (if applicable, e.g.
assuming one actually specifies no zeros) IPv6
mapping, should say the same thing for IPv6 mapping of IPv4 addresses Mike
believe this exists, will find reference and add Discussion
of complexity of referenced specs, value of this specifying vs referencing
(when assumed that standard IPv6 libraries will be used) In
testing lots of people don’t have domain names so this does not seem that
edge Proposal:
Mike to find references to canonicalization to IPv4 and IPv6 and add to
specification Proposal
accepted, assigned to editors Agreed
editorial and non-substantive change. IMI
1.1 issues IMI
version next prerequisites http://tools.oasis-open.org/issues/browse/IMI-3 Do
editors have everything they need to prep the doc? Yes Affirmative
statements with information cards http://tools.oasis-open.org/issues/browse/IMI-4 Not
discussed. Sending
data from RP to IdP http://tools.oasis-open.org/issues/browse/IMI-5
Not
discussed. Add
the new optional elements ic:InformationCard/ic09:CardType and
ic:InformationCard/ic09:IssuerName http://tools.oasis-open.org/issues/browse/IMI-13 Details
are provided in the attachment at http://lists.oasis-open.org/archives/imi/200904/msg00000.html Proposal
accepted, assigned to editors Discussion
will continue off of next editor draft X509
credential enhancements http://tools.oasis-open.org/issues/browse/IMI-14
Details
are provided in the attachment at http://lists.oasis-open.org/archives/imi/200904/msg00000.html Lots
of discussion, boils down to: STS
won’t know public key associated cert, just issuer and subject, issuer
will check chain when used as opposed to issued Suggestion:
Where possible would be good to refer to XMLkey info where possible Also,
look into improvements/feedback to xmldsig based on difficulties being
addressed here Proposal
accepted, assigned to editors Discussion
will continue off of next editor draft Information
Card Provisioning http://tools.oasis-open.org/issues/browse/IMI-15 Details
are provided in the attachment at http://lists.oasis-open.org/archives/imi/200904/msg00000.html Proposal
accepted, assigned to editors Discussion
will continue off of next editor draft 5.
Other business John has
an issue to file on v1 Scott has
an issue to file on v2 (refactoring spec) 6.
Adjournment |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]