[Openid-specs-fapi] Presentation about hypermedia login API

Wed Feb 10 08:26:04 UTC 2021

So, just to be clear, Curity has signed FAPI WG IPR Contribution agreement
as seen in
https://openid.net/wordpress-content/uploads/2020/07/Curity-AB_FAPI-WG_Contribution-Agreement_2020-07-28.pdf
.

The technology being patented is not a problem for OIDF WGs as the IPR
Contribution Agreement is a non-assert agreement.

Looking forward to talking with you later today.

Best,

Nat

On Wed, Feb 10, 2021 at 4:44 PM Travis Spencer via Openid-specs-fapi <
openid-specs-fapi at lists.openid.net> wrote:

> Thanks for clarifying, John. That helps a lot. We are OK with the
> non-assert. We think that a protocol that's patent will protect us all
> from trolls that might come in after a spec is made. That's why we
> patented it and are now talking about working on it with the group.
>
> On Wed, Feb 10, 2021 at 12:19 AM John Bradley via Openid-specs-fapi
> <openid-specs-fapi at lists.openid.net> wrote:
> >
> > Hi Travis,
> >
> > Hope you are well.
> >
> > You signed the working group IPR agrement.
> >
> > You can see the list of agrements at: Executed Contribution Agreements |
> OpenID
> >
> > Specificly for Curity:
> http://openid.net/wordpress-content/uploads/2020/07/Curity-AB_FAPI-WG_Contribution-Agreement_2020-07-28.pdf
> >
> > The contribution licence agrements that you are looking at are for
> opensource project contributions.
> >
> > The Working group IPR unlike IETF dosen't require pattent disclosures.
> >
> > It however requires a non assert over all openID specifications the WG
> produces.
> >
> > If you are OK with that then you can discuss what you want.
> >
> > If you are contributing code at some point then the other IPR
> contribution may be required.
> >
> > I hope that helps.
> >
> > John B.
> >
> > On 2/9/2021 5:14 PM, Travis Spencer via Openid-specs-fapi wrote:
> >
> > It can be checked with the secretary that Curity AB has signed the
> > CONTRIBUTOR AGREEMENT on July 27, 2020 that states:
> >
> > 1. INTELLECTUAL PROPERTY. OIDF intends to make Specifications (defined
> > in the OpenID Intellectual Property Rights Policy) broadly available
> > for implementation by others without a fee. To facilitate this,
> > Contributor grants certain rights in (and makes other commitments
> > regarding) its intellectual property. These grants and commitments are
> > set forth in the OpenID Intellectual Property Rights Policy
> > (“Policy”), which is fully incorporated into this Agreement by this
> > reference.
> >
> > The Policy in that term can be found at
> > https://openid.net/intellectual-property/ or more specifically
> >
> https://openid.net/wordpress-content/uploads/2017/06/OIDF-Policy-IPR-Policy-Final-6-19-2017.pdf
> > which states:
> >
> > VI.Patents.1.Limited Patent Promise.Each Contributor hereby
> > irrevocably makes the following promise (on behalf of itself and its
> > Related Entities) without the requirement of any monetary compensation
> > or any additional terms and conditions:Contributor (“I” or “me”)
> > hereby irrevocably promises not to assert any Necessary Claims [claims
> > of any patent or patent application] against any other entity (“you”)
> > for making, using, selling, offering for sale, importing, or
> > distributing any Implementation or offering any product or service to
> > the extent it contains or uses a Compliant Portion [those specific
> > portions of a product ... to the extent that they implement and are
> > compliant with all relevant portions of a particular Implementers
> > Draft or Final Specification]...
> >
> > The listed representatives in our signed CONTRIBUTOR AGREEMENT are me,
> > Mark Dobrinic, Jacob Ideskog, Renato Athaydes, and Pedro Felix. The
> > initial Working Group is "FAPI".
> >
> > It is not listed on
> > https://openid.net/intellectual-property/contribution-license-agreement/
> > but I think that is because that page is outdated (or because that
> > page is not listing what I think it's listing).
> >
> > IANAL either so please let me know if we can present tomorrow or not.
> >
> >
> >
> >
> > On Tue, Feb 9, 2021 at 8:33 PM Brian Campbell
> > <bcampbell at pingidentity.com> wrote:
> >
> > IANAL but in a previous/linked message on this topic said the following,
> which seems like it might have implications beyond the scope of the OIDF
> contribution agreement. But, again, IANAL.
> >
> > Our API is patent pending, but we're willing to offer royalty free use
> > of our invention should any of its embodiments end up in a spec.
> >
> >
> >
> > On Tue, Feb 9, 2021 at 12:03 PM Travis Spencer via Openid-specs-fapi <
> openid-specs-fapi at lists.openid.net> wrote:
> >
> > On Tue, Feb 9, 2021 at 6:40 PM ANTHONY NADALIN <nadalin at prodigy.net>
> wrote:
> >
> > I assume there are no IPR issues when presenting to this group?
> >
> > The WG has an IPR agreement, and we're members who have agreed to that.
> > _______________________________________________
> > Openid-specs-fapi mailing list
> > Openid-specs-fapi at lists.openid.net
> > http://lists.openid.net/mailman/listinfo/openid-specs-fapi
> >
> > CONFIDENTIALITY NOTICE: This email may contain confidential and
> privileged material for the sole use of the intended recipient(s). Any
> review, use, distribution or disclosure by others is strictly prohibited.
> If you have received this communication in error, please notify the sender
> immediately by e-mail and delete the message and any file attachments from
> your computer. Thank you.
> >
> > _______________________________________________
> > Openid-specs-fapi mailing list
> > Openid-specs-fapi at lists.openid.net
> > http://lists.openid.net/mailman/listinfo/openid-specs-fapi
> >
> > _______________________________________________
> > Openid-specs-fapi mailing list
> > Openid-specs-fapi at lists.openid.net
> > http://lists.openid.net/mailman/listinfo/openid-specs-fapi
> _______________________________________________
> Openid-specs-fapi mailing list
> Openid-specs-fapi at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-fapi
>

-- 
Nat Sakimura
NAT.Consulting LLC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20210210/71c45c01/attachment.html>