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


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

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

Subject: [security-services] AI-31: ipr & copyright issues wrt Liberty specs

    - AI-31. Jeff to send email to list on his interpretation of IPR
      issues surrounding using Liberty material

Looking at the "Notice" near the beginning of [1] (page 2), and at the LAP
Sponsor's agreement [2], it seems that to create a derivative work -- eg incorp
features described in the Liberty specs in a future SAML spec -- those creating
such work (eg the SSTC) would need some sort of copyright license from the LAP
folk. The second paragraph of the "Notice" says this explicitly. It appears
from sec. 3.5(a) of [2] that if the LAP management board were to decide that it
wished for such derivative works to be created, then such a license could be
granted by any subset of the companies listed in the "Notice". 

IPR licenses are a separate question. Without any other specific provision, and
due to stipulations in sec. 3.5(b) of [2], such licenses would be at least
RAND. It is worth noting that among the LAP members, the default licensing
arrangement is "RF w/reciprocity". In anycase it appears that if the SSTC were
to embark on creating derivative works, that the IPR aspects could be clarified
using the usual OASIS procedures. 


[1] Liberty Protocols & Schema Spec v1.1

[2] Liberty Alliance Sponsor Agreement

To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

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