Re: [OAUTH-WG] IPR on OAuth bearer

Eran Hammer <eran@hueniverse.com> Wed, 09 May 2012 19:17 UTC

Return-Path: <eran@hueniverse.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 55BA811E80E1 for <oauth@ietfa.amsl.com>; Wed, 9 May 2012 12:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.545
X-Spam-Level:
X-Spam-Status: No, score=-2.545 tagged_above=-999 required=5 tests=[AWL=0.054, 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 ulE9UJ5bmnda for <oauth@ietfa.amsl.com>; Wed, 9 May 2012 12:17:46 -0700 (PDT)
Received: from p3plex2out01.prod.phx3.secureserver.net (p3plex2out01.prod.phx3.secureserver.net [184.168.131.12]) by ietfa.amsl.com (Postfix) with ESMTP id AD9ED11E80C8 for <oauth@ietf.org>; Wed, 9 May 2012 12:17:46 -0700 (PDT)
Received: from P3PWEX2HT002.ex2.secureserver.net ([184.168.131.10]) by p3plex2out01.prod.phx3.secureserver.net with bizsmtp id 7vHm1j0030Dcg9U01vHmJR; Wed, 09 May 2012 12:17:46 -0700
Received: from P3PWEX2MB008.ex2.secureserver.net ([169.254.8.88]) by P3PWEX2HT002.ex2.secureserver.net ([184.168.131.10]) with mapi id 14.02.0247.003; Wed, 9 May 2012 12:17:45 -0700
From: Eran Hammer <eran@hueniverse.com>
To: Michael Thomas <mike@mtcc.com>
Thread-Topic: [OAUTH-WG] IPR on OAuth bearer
Thread-Index: AQHNLgtSd1ClKC8By0eIWfRqfLMBr5bBvE/AgACCdgD//5IooIAAeIaA//+KuqA=
Date: Wed, 09 May 2012 19:17:45 +0000
Message-ID: <0CBAEB56DDB3A140BA8E8C124C04ECA201026058@P3PWEX2MB008.ex2.secureserver.net>
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> <4FAAC251.3010903@mtcc.com>
In-Reply-To: <4FAAC251.3010903@mtcc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.74.213.174]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:17:47 -0000

Whoever you talk to for legal advice about IPR issues related to standards you might implement. My only point is, this group is not qualified to comment on IPR matters.

EH

> -----Original Message-----
> From: Michael Thomas [mailto:mike@mtcc.com]
> Sent: Wednesday, May 09, 2012 12:15 PM
> To: Eran Hammer
> Cc: Hannes Tschofenig; oauth@ietf.org WG
> Subject: Re: [OAUTH-WG] IPR on OAuth bearer
> 
> 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