Re: [OAUTH-WG] IPR on OAuth bearer

Sam Hartman <hartmans-ietf@mit.edu> Wed, 09 May 2012 21:45 UTC

From: Sam Hartman <hartmans-ietf@mit.edu>
To: Michael Thomas <mike@mtcc.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>
Date: Wed, 09 May 2012 17:45:39 -0400
In-Reply-To: <4FAAD43C.501@mtcc.com> (Michael Thomas's message of "Wed, 09 May 2012 13:31:56 -0700")
Message-ID: <tslbolxgha4.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] IPR on OAuth bearer
Precedence: list

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-WG] IPR on OAuth bearer Hannes Tschofenig
Re: [OAUTH-WG] IPR on OAuth bearer Eran Hammer
Re: [OAUTH-WG] IPR on OAuth bearer Hannes Tschofenig
Re: [OAUTH-WG] IPR on OAuth bearer Eran Hammer
Re: [OAUTH-WG] IPR on OAuth bearer Michael Thomas
Re: [OAUTH-WG] IPR on OAuth bearer Hannes Tschofenig
Re: [OAUTH-WG] IPR on OAuth bearer Eran Hammer
Re: [OAUTH-WG] IPR on OAuth bearer Eran Hammer
Re: [OAUTH-WG] IPR on OAuth bearer Michael Thomas
Re: [OAUTH-WG] IPR on OAuth bearer Stephen Farrell
Re: [OAUTH-WG] IPR on OAuth bearer Eran Hammer
Re: [OAUTH-WG] IPR on OAuth bearer Hannes Tschofenig
Re: [OAUTH-WG] IPR on OAuth bearer Michael Thomas
Re: [OAUTH-WG] IPR on OAuth bearer Stephen Farrell
Re: [OAUTH-WG] IPR on OAuth bearer Sam Hartman
Re: [OAUTH-WG] IPR on OAuth bearer William Mills
Re: [OAUTH-WG] IPR on OAuth bearer Eliot Lear
Re: [OAUTH-WG] IPR on OAuth bearer Dick Hardt