RE: FWIW: draft-housley-tls-authz-extns-07.txt to Proposed Standard

+1

If the bar for allowing technology to move forward in the IETF is that
it must not only be unencumbered itself, but _any_ use of it must also
be unencumbered, then we may as well all go home, after rescinding TCP,
IP, HTTP, and anything else we have done in the past - these are all
used to do some things that are themselves encumbered. Welcome to the
real world.

If the technology in the document to be standardized is unencumbered,
then the fact that _some_ uses of that technology may run into
encumbered territory is irrelevant, except to those who hate patents in
general.

Regards, 
Chuck 
------------- 
Chuck Powers, 
Motorola, Inc 
phone: 512-427-7261
mobile: 512-576-0008

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On 
> Behalf Of Brian E Carpenter
> Sent: Monday, February 09, 2009 7:51 PM
> To: ietf@ietf.org
> Subject: FWIW: draft-housley-tls-authz-extns-07.txt to 
> Proposed Standard
> 
> FWIW (and it would be good if other actual
> IETF participants care to indicate +1 if they agree):
> 
> The actual words in RedPhone's current disclosure:
> 
> "RedPhone Security hereby asserts that the techniques for
> sending and receiving authorizations defined in TLS Authorizations
> Extensions (version draft-housley-tls-authz-extns-07.txt) do not
> infringe upon RedPhone Security's intellectual property 
> rights (IPR)..."
> 
> Now, there's been some discussion of whether some use cases for
> the protocol will nevertheless lead implementors to infringe, but
> that (plus the question of whether the offered license conditions
> in that case are in fact acceptable) is frankly irrelevant. The
> draft on the table is in itself unencumbered by RedPhone Security,
> and that's all that matters as far as the IETF's IPR rules go.
> 
> There may be other reasons not to advance this document; not being
> a security person, I have no opinion about that. But as far as this
> particular IPR issue is concerned, IMHO it's good to go.
> 
>     Brian
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 