<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16981" name=GENERATOR></HEAD>
<BODY
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space">
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=206383813-25032010>Hi
Paul,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=206383813-25032010>Some
clarifications below on envisioned TECHNICAL SPECIFICATIONS
:</SPAN></FONT></DIV>
<UL>
<LI><FONT face=Arial color=#0000ff size=2><SPAN class=206383813-25032010><FONT
color=#000000>Section (4) DRAFT TECHNICAL SPECIFICATIONS: second bullet
addition: this may be fine, we'd like to learn more about the nature of the
ISA (e.g. does it assume an unmodified
browser?)</FONT> </SPAN></FONT></LI></UL>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=206383813-25032010>
Yes we assume an ISA in the network accessed through a possibly unmodified
browser (as opposed to the ISA in the device = browser add-on).
</SPAN></FONT></DIV>
<UL>
<LI><FONT face=Arial color=#0000ff size=2><SPAN class=206383813-25032010><FONT
color=#000000>Section (4) DRAFT TECHNICAL SPECIFICATIONS: third bullet
addition: we don't entirely understand this. Seems to imply that we shouldn't
make up entirely new things; try to reuse existing SAML metadata. Perhaps
"newly designed features should be as compatible and consistent as possible
with existing specifications" is part of the intent
here.</FONT></SPAN></FONT></LI></UL>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=206383813-25032010>In
fact, we envisoned here that some specifications already exist and could be
extended to enable IDPs to express their capabilities and presentation
characteristics (same as what is refered as "Identity Provider Inputs" here :
<A
href="http://kantarainitiative.org/confluence/display/ulx/Inputs+to+the+RP+Pop+Up+UI">http://kantarainitiative.org/confluence/display/ulx/Inputs+to+the+RP+Pop+Up+UI</A>).
For a SAML IDP, we can leverage the SAML Metadata specifications, for OpenID
OPs, we can maybe leverage the YADIS/XRDS specifications, ... We have
presented the following slides in the IDPS session last week on this topic :
<A
href="http://kantarainitiative.org/confluence/download/attachments/41027190/IDP+Metadata+Status+and+Evo+v02.ppt">http://kantarainitiative.org/confluence/download/attachments/41027190/IDP+Metadata+Status+and+Evo+v02.ppt</A>
that describe lacks in existing specs and evolution proposals (we already had
some comments during the session and on the mailing list). So our intent is as
you wrote : "newly designed features should be as compatible and consistent as
possible with existing specifications" but it does not mean that there is
nothing to do and we are opened to discuss all technical solutions (including
entirely new things if it makes sense).<BR></DIV></BLOCKQUOTE></SPAN></FONT>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=206383813-25032010>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=206383813-25032010>Gaël</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=206383813-25032010> </DIV></SPAN></FONT><BR>
<DIV class=OutlookMessageHeader lang=fr dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>De :</B> wg-ulx-bounces@kantarainitiative.org
[mailto:wg-ulx-bounces@kantarainitiative.org] <B>De la part de</B> Paul
Trevithick<BR><B>Envoyé :</B> mercredi 17 mars 2010
23:01<BR><B>À :</B> wg-ulx@kantarainitiative.org.<BR><B>Objet :</B>
[WG-ULX] Notes from today's call<BR></FONT><BR></DIV>
<DIV></DIV><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px"><A
href="http://kantarainitiative.org/confluence/display/ulx/ULX+Teleconference+2010-03-17">http://kantarainitiative.org/confluence/display/ulx/ULX+Teleconference+2010-03-17</A></SPAN></FONT>
<DIV><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px"><BR></SPAN></FONT></DIV>
<DIV><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Copied here:<BR></SPAN></FONT>
<DIV>
<H3><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Agenda</SPAN></FONT></H3>
<H5><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px"><A name=ULXTeleconference2010-03-17-0)Roll></A>0)
</SPAN></FONT><A
href="http://kantarainitiative.org/confluence/display/ulx/Participant%20Roster"
rel=nofollow><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px"><FONT class=Apple-style-span color=#000000><SPAN
class=Apple-style-span
style="TEXT-DECORATION: none">Roll</SPAN></FONT></SPAN></FONT></A><FONT
class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px"> Call</SPAN></FONT></H5>
<UL>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">RL Bob Morgan</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">John Bradley</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Paul Trevithick</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Nate Klingenstein</SPAN></FONT> </LI></UL>
<H5><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px"><FONT class=Apple-style-span color=#000000><A
name=ULXTeleconference2010-03-17-1)IdPSULXWGcommoncharter></A>1) IdPS + ULX WG
common charter</FONT></SPAN></FONT></H5>
<P><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">We reviewed the IDPS/ULX common charter document that
had been prepared by Philippe Clement and sent to the list
today</SPAN></FONT></P>
<UL>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (2) PURPOSE: Problem: There is a mention made
of the "Liberty Identity Provider Selector MRD" people may not have access
to</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (2) PURPOSE: Strike "the ISA" and replace
"identity services" with "identity services including identity providers and
identity selection agents (ISA)s"</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (2) PURPOSE: second and fifth bullets also
mention the Liberty MRD</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (3) SCOPE: fourth bullet (same problem as
above)</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (3) SCOPE: (new) sixth bullet: fine as
is</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (3) SCOPE: ninth bullet: fine as
is</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (4) DRAFT TECHNICAL SPECIFICATIONS: first
bullet addition: fine</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (4) DRAFT TECHNICAL SPECIFICATIONS: second
bullet addition: this may be fine, we'd like to learn more about the nature of
the ISA (e.g. does it assume an unmodified browser?)</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (4) DRAFT TECHNICAL SPECIFICATIONS: third
bullet addition: we don't entirely understand this. Seems to imply that we
shouldn't make up entirely new things; try to reuse existing SAML metadata.
Perhaps "newly designed features should be as compatible and consistent as
possible with existing specifications" is part of the intent
here.</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (4) DRAFT TECHNICAL SPECIFICATIONS: fourth
bullet: This might be okay.</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (6) LEADERSHIP: Addition of Philippe as a
co-chair to carry forward the IDPS WG work makes sense to us.</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (8) DURATION: the addition is fine other than
the general issue of citing the Liberty MRD</SPAN></FONT>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Section (12) PROPOSERS: Not sure how to handle a
retroactive change like this.</SPAN></FONT> </LI></UL>
<P><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">We had a discussion about the fact that if we wanted to
change the group's IPR regime, this re-chartering effort was a good moment to do
so. Changing the IPR regime is may best done by closing this group, starting a
new group (under the new regime) and then having the old group contribute the
existing IPR. If the new IPR regime is not the Liberty regime then the
contributors would have to state that they are waiving their patent rights over
their contributions.</SPAN></FONT></P>
<P><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">It appears that at Kantara the Creative Commons and
Apache 2 licenses can't be used for groups that produce technical specifications
(like this one).</SPAN></FONT></P>
<H5><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px"><FONT class=Apple-style-span color=#000000><A
name=ULXTeleconference2010-03-17-2)UpdateonWebMockup></A>2) Update on Web
Mockup</FONT></SPAN></FONT></H5>
<UL>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Paul: We are now past the hiccup related to funding to
Kevin. I will convey to Kevin (a) the enhancements that we've already
discussed and (b) the consensus that we want to also "finish" the
mockup--meaning that all paths through the mockup should be coded (no dead
ends) and that the user experience should simulate a working login experience.
We'll try to get the Web Mockup done so Valeska can show it at the
</SPAN></FONT><A href="http://2010.iasummit.org" rel=nofollow><FONT
class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px"><FONT class=Apple-style-span color=#000000><SPAN
class=Apple-style-span
style="TEXT-DECORATION: none">IA2010</SPAN></FONT></SPAN></FONT></A><FONT
class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px"> conference in Phoenix April 9th at a poster
session.</SPAN></FONT> </LI></UL>
<H5><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px"><FONT class=Apple-style-span color=#000000><A
name=ULXTeleconference2010-03-17-3)OnemorepieceofinputfromRSA></A>3) One more
piece of input from RSA</FONT></SPAN></FONT></H5>
<UL>
<LI><FONT class=Apple-style-span size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px">Paul: Our pop UX must be conform to the Americans with
Disabilities Act</SPAN></FONT> </LI></UL>
<DIV><BR></DIV></DIV></DIV></BODY></HTML>