Re: [OAUTH-WG] IPR on OAuth bearer

Michael Thomas <mike@mtcc.com> Wed, 09 May 2012 19:15 UTC

Return-Path: <mike@mtcc.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 8536211E80E0 for <oauth@ietfa.amsl.com>; Wed, 9 May 2012 12:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6k8-nYOjAeX for <oauth@ietfa.amsl.com>; Wed, 9 May 2012 12:15:34 -0700 (PDT)
Received: from mtcc.com (mtcc.com [50.0.18.224]) by ietfa.amsl.com (Postfix) with ESMTP id 80E6311E80CA for <oauth@ietf.org>; Wed, 9 May 2012 12:15:34 -0700 (PDT)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id q49JFTLl019410 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 9 May 2012 12:15:29 -0700
Message-ID: <4FAAC251.3010903@mtcc.com>
Date: Wed, 09 May 2012 12:15:29 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Eran Hammer <eran@hueniverse.com>
References: <0E17EDDE-567A-40BF-9CB9-0D6B757FF0A5@gmx.net> <0CBAEB56DDB3A140BA8E8C124C04ECA2010259C4@P3PWEX2MB008.ex2.secureserver.net> <6CE569CC-091C-456D-8426-FB3200ED4667@gmx.net> <0CBAEB56DDB3A140BA8E8C124C04ECA201025F4F@P3PWEX2MB008.ex2.secureserver.net>
In-Reply-To: <0CBAEB56DDB3A140BA8E8C124C04ECA201025F4F@P3PWEX2MB008.ex2.secureserver.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2356; t=1336590930; x=1337454930; c=relaxed/simple; s=thundersaddle.kirkwood; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[OAUTH-WG]=20IPR=20on=20OAuth=20bearer |Sender:=20 |To:=20Eran=20Hammer=20<eran@hueniverse.com> |Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20 format=3Dflowed |Content-Transfer-Encoding:=207bit |MIME-Version:=201.0; bh=hVWfR66t3xZg+h4dGAL9/hUD0q9UmykFJUQMPHuYEKM=; b=rOWa6r1avBrRfx4hMYTuCFWFTEhyJ8ExvGhq2MNU6npZuf0Uh8jHUldrOj tZVfr6ZdrR5DASSUr0FkzT0hRfC0vIEkdHPxYM/VOybxwzINzo6KUcbMJa4X ZQusMfSiOvbGUqgMGDSw2lDLubdYwTazzEIhgSGDmPseBU3ORnif4=;
Authentication-Results: ; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from mtcc.com/thundersaddle.kirkwood verified; ); dkim-asp=pass header.From=mike@mtcc.com
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] IPR on OAuth bearer
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Wed, 09 May 2012 19:15:35 -0000

On 05/09/2012 12:06 PM, Eran Hammer wrote:
> So no discussion of this is expected on the list - correct? That's what I wanted to clarify. You asked the WG to "think" about its potential implications but I don't want that "thinking" to happen out-loud on this list...
>
> Raising the issue with your internal IPR team is the right step.

What internal IPR team? The IETF is not a corpro-only club.

Mike
>
> EH
>
>> -----Original Message-----
>> From: Hannes Tschofenig [mailto:hannes.tschofenig@gmx.net]
>> Sent: Wednesday, May 09, 2012 11:37 AM
>> To: Eran Hammer
>> Cc: Hannes Tschofenig; oauth@ietf.org WG
>> Subject: Re: [OAUTH-WG] IPR on OAuth bearer
>>
>> Hi Eran,
>>
>> if you care about the specification (and want to use it in your products) then
>> you may want to reach out to your IPR folks and ask for their judgement.
>> They may be able to tell you whether they find the cited IPR applicable and
>> whether they had experience with the IPR holder already.
>>
>> Ciao
>> Hannes
>>
>> On May 9, 2012, at 8:51 PM, Eran Hammer wrote:
>>
>>> What exactly is the expected WG discussion on this? I hope people here
>> are not expected to read the patent and make legal decisions about the
>> patent's validity or even applicability as these are questions for lawyers, not
>> engineers.
>>> EH
>>>
>>>> -----Original Message-----
>>>> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On
>>>> Behalf Of Hannes Tschofenig
>>>> Sent: Wednesday, May 09, 2012 10:44 AM
>>>> To: oauth@ietf.org WG
>>>> Subject: [OAUTH-WG] IPR on OAuth bearer
>>>>
>>>> Hi all,
>>>>
>>>> an IPR disclosure had been submitted for the OAuth bearer document
>>>> recently. In case you may have missed it, here is the link to it:
>>>> https://datatracker.ietf.org/ipr/1752/
>>>>
>>>> The ADs will re-run the IETF last call due to this new IPR filing and
>>>> we would also like the working group to check the IPR and to think
>>>> about potential implications.
>>>>
>>>> Thanks.
>>>>
>>>> Ciao
>>>> Hannes&  Derek
>>>>
>>>> _______________________________________________
>>>> OAuth mailing list
>>>> OAuth@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/oauth
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth