Re: [OAUTH-WG] IPR on OAuth bearer

Dick Hardt <dick.hardt@gmail.com> Wed, 16 May 2012 16:13 UTC

Return-Path: <dick.hardt@gmail.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 B0C7321F8655 for <oauth@ietfa.amsl.com>; Wed, 16 May 2012 09:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.271
X-Spam-Level:
X-Spam-Status: No, score=-3.271 tagged_above=-999 required=5 tests=[AWL=-0.272, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_LOW=-1]
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 732RhDBzOpgi for <oauth@ietfa.amsl.com>; Wed, 16 May 2012 09:13:54 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9D16521F8659 for <oauth@ietf.org>; Wed, 16 May 2012 09:13:54 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so1335239pbc.31 for <oauth@ietf.org>; Wed, 16 May 2012 09:13:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=TOp8obPu44xIG1ZPU5/Ht+hI9etH/YZRR05/IO7OGzE=; b=hWUT5jfAAwOnwnSoQlzpnxmsqDlbPytmBn+xTwM8EotT/i7Zs1XTa8HZCxeY0Mz5CR uk0Has/Ih2cgKH151ITBcWlapyLpYvr6pDi4ZzBy5XJ3YhawWSizeiSYbu2/olVzKPB1 9D2fqPkEwyrRdPX2qKLdVosdnqEf3Bz1CJYmb30N3NXzVfRoDWbHKFvT2fWBSya3XZ01 Bv9a3d8Z60PVHXDpcFIQEQzkNcpaFxXvVBLxu0GxLUIigMQFxm4wRxjDConmEcnSeUU0 2eWNT89cbRf8HyDJ+7DFeztXgHeQwqPR7/ov6IwBai99y3eYMGl42xv4G5VVBaFtXIwm hsuA==
Received: by 10.68.233.102 with SMTP id tv6mr17588955pbc.153.1337184830506; Wed, 16 May 2012 09:13:50 -0700 (PDT)
Received: from [10.0.0.4] (c-24-5-69-173.hsd1.ca.comcast.net. [24.5.69.173]) by mx.google.com with ESMTPS id ou5sm5891556pbb.54.2012.05.16.09.13.46 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 16 May 2012 09:13:49 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="us-ascii"
From: Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <tslbolxgha4.fsf@mit.edu>
Date: Wed, 16 May 2012 09:13:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F2F53B5-20EB-402B-BD3B-030455450B13@gmail.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> <4FAAC251.3010903@mtcc.com> <0CBAEB56DDB3A140BA8E8C124C04ECA201026058@P3PWEX2MB008.ex2.secureserver.net> <4FAAC6C4.7080502@mtcc.com> <4FAAD2DF.4080500@cs.tcd.ie> <4FAAD43C.501@mtcc.com> <tslbolxgha4.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1278)
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, 16 May 2012 16:13:55 -0000

3) I have read the IPR and I believe I could deploy this specification.

NOTE: I am not a legal expert, but I do have extensive experience with identity related patents and after reviewing the claims, I do not believe that the OAuth 2.0 or OAuth bearer specifications infringe on patent 7272639.

-- Dick

On May 9, 2012, at 2:45 PM, Sam Hartman wrote:

> So, here are statements that  you could make as part of this discussion
> that would be entirely in scope:
> 
> 1) I've read the IPR. Prior to this disclosure I was interested in
> developing|deploying|shipping  an implementation of this
> specification. Now I am not.
> 
> 2) I think you could go so far as to say. Based on this IPR I would no
> longer feel comfortable making an open-source implementation of this
> spec available.
> 
> 3) Or on the other  side: I've reviewed this new IPR and I believe I
> could implement|ship|deploy|whatever this specification.
> 
> Or if you don't like giving out as much information as 1-3:
> 
> 4) I've reviewed the new IPr and I recommend that we not advance this
> standard
> 
> 5) I've reviewed the IPR and I do recommend we advance.
> 
> Obviously, people may weigh statements of the form 1-3 with more value
> than 4-5. However it's really hard to get many organizations to say
> something in the 1-3 range.
> 
> Other valid things to say in such a context include:
> 
> 6) We've successfully obtained any licenses we believe that we need in
> order to implement this specification given the IPR.
> 
> 7) We attempted to obtain the licenses we needed in order to implement
> given this IPR but were unsuccessful.
> 
> believe all the above statements are acceptable. In particular, none of
> them comment on the validity of the IPR nor give legal advice about
> stuff.
> 
> I believe you could even go so far as to say  something like I believe
> that an open-source implementation of this technology is|is not
> important to whether we should standardize it. I believe we've come very
> close to that in the past. 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth