Re: Experimental makes sense for tls-authz
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Experimental makes sense for tls-authz



"Joel M. Halpern" <jmh at joelhalpern.com> writes:

> We have published encumbered experimental and informational
> documents on many occasions.  I can see no reason not to do so in
> this case.

The reasons are the same as they have always been. Making a mistake in
the past is no reason to continue making that same mistake.

Software idea patents place control over *every* independent
implementation of an idea in the hands of *one* entity, who then gets
to dictate whatever terms they like. This is unjust, and is a
practical hindrance on every software developer since it adds to the
minefield of ideas that they must avoid using when designing their
code.

Even developers who are not intending to use ideas encumbered by a
particular patent can independently arrive at some specific method
described in that patent, and inadvertantly violate the patent
rules. In such cases the violation will not be discovered for some
unknown amount of time. The burden on software developers thus mounts
with every patent on a software idea.

To allow a technology, encumbered by any known patent holder's
monopoly, as a proposed standard (even experimental or informational
or any other status) is to give legitimacy to this system that
directly harms development of all software, and especially harms the
goal of interoperability that is part of the purpose of a standards
process.

Please explicitly reject technologies from any part of the standards
process that are encumbered by software idea patents. I encourage the
IETF to start by rejecting 'draft-housley-tls-authz-extns'.

-- 
 \               "Holy bouncing boiler-plated fits, Batman!"  -- Robin |
  `\                                                                   |
_o__)                                                                  |
Ben Finney


_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf





rg with esmtp (Exim 4.43) id 1Ildtt-0002q6-VX
	for ietf at ietf.org; Sat, 27 Oct 2007 01:07:57 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ildtj-0000fC-Jl
	for ietf at ietf.org; Sat, 27 Oct 2007 01:07:53 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1IldtN-0006DF-Fg
	for ietf at ietf.org; Sat, 27 Oct 2007 05:07:25 +0000
Received: from eth595.vic.adsl.internode.on.net ([150.101.214.82])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <ietf at ietf.org>; Sat, 27 Oct 2007 05:07:25 +0000
Received: from ben+ietf by eth595.vic.adsl.internode.on.net with local (Gmexim
	0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <ietf at ietf.org>; Sat, 27 Oct 2007 05:07:25 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf at ietf.org
From: Ben Finney <ben+ietf at benfinney.id.au>
Date: Sat, 27 Oct 2007 15:07:15 +1000
Lines: 39
Message-ID: <87y7dpgn7g.fsf at benfinney.id.au>
References: <003e01c817fa$b09cfb80$6801a8c0 at oemcomputer>
	<20071026191611.C65F27E13 at bender.tigertech.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet at ger.gmane.org
X-Gmane-NNTP-Posting-Host: eth595.vic.adsl.internode.on.net
X-Public-Key-ID: 0xBD41714B
X-Public-Key-Fingerprint: 9CFE 12B0 791A 4267 887F  520C B7AC 2E51 BD41 714B
X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-gpg.asc
X-Post-From: Ben Finney <ben+ietf at benfinney.id.au>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)
Cancel-Lock: sha1:S1uGfIPzzUwh507IYKIZgQKpDx8=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: Re: Experimental makes sense for tls-authz
X-BeenThere: ietf at ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf at ietf.org>
List-Help: <mailto:ietf-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=subscribe>
Errors-To: ietf-bounces at ietf.org

"Joel M. Halpern" <jmh at joelhalpern.com> writes:

> We have published encumbered experimental and informational
> documents on many occasions.  I can see no reason not to do so in
> this case.

The reasons are the same as they have always been. Making a mistake in
the past is no reason to continue making that same mistake.

Software idea patents place control over *every* independent
implementation of an idea in the hands of *one* entity, who then gets
to dictate whatever terms they like. This is unjust, and is a
practical hindrance on every software developer since it adds to the
minefield of ideas that they must avoid using when designing their
code.

Even developers who are not intending to use ideas encumbered by a
particular patent can independently arrive at some specific method
described in that patent, and inadvertantly violate the patent
rules. In such cases the violation will not be discovered for some
unknown amount of time. The burden on software developers thus mounts
with every patent on a software idea.

To allow a technology, encumbered by any known patent holder's
monopoly, as a proposed standard (even experimental or informational
or any other status) is to give legitimacy to this system that
directly harms development of all software, and especially harms the
goal of interoperability that is part of the purpose of a standards
process.

Please explicitly reject technologies from any part of the standards
process that are encumbered by software idea patents. I encourage the
IETF to start by rejecting 'draft-housley-tls-authz-extns'.

-- 
 \               "Holy bouncing boiler-plated fits, Batman!"  -- Robin |
  `\                                                                   |
_o__)                                                                  |
Ben Finney


_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf






Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.