regarding TSL authorization
Anders Juel Jensen <andersjjensen@gmail.com> Sun, 08 February 2009 20:57 UTC
Return-Path: <andersjjensen@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDCE03A6825 for <ietf@core3.amsl.com>; Sun, 8 Feb 2009 12:57:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aORto5XMCi3H for <ietf@core3.amsl.com>; Sun, 8 Feb 2009 12:57:53 -0800 (PST)
Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by core3.amsl.com (Postfix) with ESMTP id 115D33A6806 for <ietf@ietf.org>; Sun, 8 Feb 2009 12:57:52 -0800 (PST)
Received: by ewy14 with SMTP id 14so2239332ewy.13 for <ietf@ietf.org>; Sun, 08 Feb 2009 12:57:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:mime-version:content-type:content-transfer-encoding :content-disposition:message-id; bh=PY3SjNgpHvM3QYylbPO+UexxccAXYGP9XQVx8G9dCfg=; b=WlP7DRBDhLHatXuOv9xQP+CdoGpGB9DtEnDlwnRDXKH6ll3iRP72kkq2eOj8YGGbnC SB5nQdiN/lPMAkvmosgUOs5vjoKnqDo1rhkeRUCrBsGpJUVtVG1i/i47ocBgc8fsBmTr Jzv8eY/zWcvIM2gT1YSlLfvjb+gSnYVuB5CyU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; b=MCX0xa6zYYLuRzAoPTIis3K2bwzDdg45udRIqLfCTk0ALd5Z3jl8FxQf9qe2R2HZTx jZ7bbEDU7CIsczxxR2FyvLb2InRkvZfB1hJeibtkvZZTqrxMyHgaBvTtjKKcDBKHjFoH 73Ul76kWOI64FAKzZZZULNbAemJVm/ox2RFC0=
Received: by 10.210.65.15 with SMTP id n15mr3263916eba.186.1234126675764; Sun, 08 Feb 2009 12:57:55 -0800 (PST)
Received: from ?192.168.1.6? (3e6b3a9e.rev.stofanet.dk [62.107.58.158]) by mx.google.com with ESMTPS id 7sm3379483eyg.37.2009.02.08.12.57.54 (version=SSLv3 cipher=RC4-MD5); Sun, 08 Feb 2009 12:57:54 -0800 (PST)
From: Anders Juel Jensen <andersjjensen@gmail.com>
To: ietf@ietf.org
Subject: regarding TSL authorization
Date: Sun, 08 Feb 2009 22:01:55 +0100
User-Agent: KMail/1.9.10
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200902082201.55619.andersjjensen@gmail.com>
X-Mailman-Approved-At: Mon, 09 Feb 2009 14:30:37 -0800
Cc: campaigns@fsf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Feb 2009 22:18:12 -0000
It has come to my attention, that the patent encumbered method known as "TSL authorization" is again being considered for inclusion. I must object to this, as RedPhone has only granted a royalty-free license for developers, but not for end users. This naturally makes TSL authorization unsuitable for inclusion in an official standard, as this would effectively make it a proprietary standard for end users. There are currently two viable options: A) Don't include it, and use another method that can solve the same problem. B) Obtain a royalty-free license for ALL users from RedPhone. Yours sincerely: Anders Juel Jensen, Denmark.
- regarding TSL authorization Anders Juel Jensen