[OAUTH-WG] Fw: IPR Disclosure: - What to Do with JWT ?

Oleg Gryb <oleg_gryb@yahoo.com> Thu, 28 February 2013 19:21 UTC

Return-Path: <oleg_gryb@yahoo.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC11821F8B0A for <oauth@ietfa.amsl.com>; Thu, 28 Feb 2013 11:21:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFNpVlNp79Hb for <oauth@ietfa.amsl.com>; Thu, 28 Feb 2013 11:21:07 -0800 (PST)
Received: from nm18-vm0.bullet.mail.bf1.yahoo.com (nm18-vm0.bullet.mail.bf1.yahoo.com [98.139.213.138]) by ietfa.amsl.com (Postfix) with SMTP id 7DEFE21F89A4 for <oauth@ietf.org>; Thu, 28 Feb 2013 11:21:07 -0800 (PST)
Received: from [98.139.212.147] by nm18.bullet.mail.bf1.yahoo.com with NNFMP; 28 Feb 2013 19:21:06 -0000
Received: from [98.139.212.202] by tm4.bullet.mail.bf1.yahoo.com with NNFMP; 28 Feb 2013 19:21:06 -0000
Received: from [127.0.0.1] by omp1011.mail.bf1.yahoo.com with NNFMP; 28 Feb 2013 19:21:06 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 941986.26418.bm@omp1011.mail.bf1.yahoo.com
Received: (qmail 29395 invoked by uid 60001); 28 Feb 2013 19:21:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1362079266; bh=Vwgggfgx4DflXHKDIa/xWfku98jB/JxiGYMgUIcsTYk=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=ibtU4j7gsr+axYQsVEIgl+YyxF/ZTfbRpAFUY6JkkLBFLpACzcB0JGkH20vibp9yE62jsi/DudBvJj0iHw4fF808jig0bV/wH3jYBee6pcHgHvAhxVx/x11ZG/4fKolU+Cd0tbKIODkjJH3/Sut9WqgEIngWJ1ujL38GqxJMaMY=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=sYvzLERWXEy1c7ziSyiO2XmkdZ45UWjJv2fZH9RyQTaFSRU5mmPrHbRQSiu9vc/0GPoao/HscuKORtA+Ue1+ngmpNnX6Vt4Khs9tEJtkxh/U0CUSljcHn6a2WtRb6Bj+wIiOVSPytDBjpmfZjPlC/kJBn4gmhF6QhP6uuwFDY7M=;
X-YMail-OSG: kfI_PtYVM1nO3OUP1TbbgaLeC.DTXkd4CrxgzPlsKRf0H66 _mHJwwUffdF8TDxkW9.4MblRdPDW7d6csehlN5WEAfK64IC3i.UJ5PvJs.Tc GHY0BVNZJg4i88SiXxKSeMWFoddYbHIOslhlmU7zuiHXTTfuJMecPha92VoV R6Csxkta_NrLcV2Xlj9aIstU6ejHZx5XXEkLezsXBzH4n.qKa_lnx4yYXK1w L139WT6yn1ROwpbhFuh0Vd3JLlFaxI4qH5LyLUUSjdhIuCjENYFmy69GIZHe M3GDI51UfAvxhKUbnUvDCQ8ThtlshvINOX3xHAXD9E6PF1A9VEYz1ksTgO5r _njSB6nVqF6qXImmI1HHXnrUmgda.CEFn.8UrwObMX0ZEfM0clWrL4X4Gv8_ 9fhCDxvb0W4VO0bkqbfdPGvoyVpWYJ5g.vnPp6SbzA2ayoUwUSC8lR5Pw_8n Oxqo4Q.yTRi08OxiK7ioYVWzHSPYI1wgtDdVBuJLhTTlLrVXeBvMnrVVhdJ9 OYdsuV3QdulN38hI-
Received: from [199.16.140.28] by web141002.mail.bf1.yahoo.com via HTTP; Thu, 28 Feb 2013 11:21:06 PST
X-Rocket-MIMEInfo: 001.001, RGVhciBPQXV0aCBXRyBhbmQgQ2hhaXJzLA0KDQpDYW4gc29tZWJvZHkgcGxlYXNlIGNvbW1lbnQgdGhlIENlcnRpY29tJ3MgZGlzY2xvc3VyZSBiZWxvdz8gSWYgdGhlIHB1cnBvc2Ugb2YgdGhpcyBkaXNjbG9zdXJlIGlzIHRvIGluZm9ybSB1cyB0aGF0IEpXVCBjYW4gYmUgcG90ZW50aWFsbHkgYSBzdWJqZWN0IG9mIHJveWFsdGllcyBhbmQgb3RoZXIgcG9zc2libGUgbGVnYWwgYWN0aW9ucywgdGhlIHZhbHVlIG9mIGFkb3B0aW5nIEpXVCBpbiB0aGUgc2NvcGUgb2YgT0F1dGggMi4wIElFVEYgc3RhbmRhcmQBMAEBAQE-
X-Mailer: YahooMailClassic/15.1.4 YahooMailWebService/0.8.135.514
Message-ID: <1362079266.8952.YahooMailClassic@web141002.mail.bf1.yahoo.com>
Date: Thu, 28 Feb 2013 11:21:06 -0800
From: Oleg Gryb <oleg_gryb@yahoo.com>
To: oauth@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="348076277-717348825-1362079266=:8952"
Subject: [OAUTH-WG] Fw: IPR Disclosure: - What to Do with JWT ?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: oleg@gryb.info
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Feb 2013 19:21:09 -0000

Dear OAuth WG and Chairs,

Can somebody please comment the Certicom's disclosure below? If the purpose of this disclosure is to inform us that JWT can be potentially a subject of royalties and other possible legal actions, the value of adopting JWT in the scope of OAuth 2.0 IETF standard would definitely diminish and if this is the case shouldn't we consider replacing it with something similar, but different, which would not be a subject of the future possible litigation?    

I'm not a lawyer and might not understand the statement below correctly, so please let me know if/where I'm wrong. Please keep in mind also that the popularity of JWT is growing fast along with the implementations, so we need to do something quickly.

Thanks,
Oleg.


--- On Wed, 2/27/13, IETF Secretariat <ietf-ipr@ietf.org> wrote:

From: IETF Secretariat <ietf-ipr@ietf.org>
Subject: [OAUTH-WG] IPR Disclosure: Certicom Corporation's Statement about IPR related to draft-ietf-oauth-json-web-token-06 (2)
To: mbj@microsoft.com, ve7jtb@ve7jtb.com, n-sakimura@nri.co.jp
Cc: derek@ihtfp.com, oauth@ietf.org, ipr-announce@ietf.org
Date: Wednesday, February 27, 2013, 4:16 PM


Dear Michael Jones, John Bradley, Nat Sakimura:

 An IPR disclosure that pertains to your Internet-Draft entitled "JSON Web Token
(JWT)" (draft-ietf-oauth-json-web-token) was submitted to the IETF Secretariat
on 2013-02-20 and has been posted on the "IETF Page of Intellectual Property
Rights Disclosures" (https://datatracker.ietf.org/ipr/1968/). The title of the
IPR disclosure is "Certicom Corporation's Statement about IPR related to draft-
ietf-oauth-json-web-token-06 (2)."");

The IETF Secretariat

_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth