ietf
[Top] [All Lists]

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

2009-02-10 10:41:18
Brian E Carpenter <brian(_dot_)e(_dot_)carpenter(_at_)gmail(_dot_)com> writes:

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.

I disagree.  The IETF policies around patents mention "use" as well as
"implementation".  Thus, a license that permit "implementation" but not
permitting "use" should generate similar scrutiny and discussion.  It
poses the same problem for actual users.

I strongly disagree with a notion that just because someone grants a
patent license for "implementation" that the IETF community has to
consider the patent situation around the technology as irrelevant.  Use
of technology goes beyond "implementation".  This is acknowledged in the
IETF policy documents.  Compare, e.g., RFC 3979 and in particular the
definition of the term "Covers".

I also disagree with the claim that the draft is unencumbered.  I don't
follow how you reach that conclusion from the patent disclaimer.  You
quoted only one paragraph out of several, and the other paragraphs are
the ones that encumber use of the protocol.  It may be your
interpretation that the draft is unencumbered, but everyone get the same
opportunity to make their own interpretation.  As implementer of the
technology, and having consulted with legal aid, I have made another
interpretation.

/Simon
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf