Re: [TLS] Last Call: draft-ietf-tls-extractor (Keying Material Exporters for Transport Layer Security (TLS)) to Proposed Standard

Erick O <ericko0@yahoo.com> Fri, 18 September 2009 14:40 UTC

Return-Path: <ericko0@yahoo.com>
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 595A53A6820 for <tls@core3.amsl.com>; Fri, 18 Sep 2009 07:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level:
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 zPz37HrC9Tt9 for <tls@core3.amsl.com>; Fri, 18 Sep 2009 07:40:58 -0700 (PDT)
Received: from web45508.mail.sp1.yahoo.com (web45508.mail.sp1.yahoo.com [68.180.197.116]) by core3.amsl.com (Postfix) with SMTP id 2FCD03A67AD for <tls@ietf.org>; Fri, 18 Sep 2009 07:40:58 -0700 (PDT)
Received: (qmail 47342 invoked by uid 60001); 18 Sep 2009 14:41:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1253284912; bh=4q527537ON8+gqPBUOWaq8Qn1F3Dx1KROi8l3S2OOcI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=r1BfW9PdlqMVxAaBaT3jZexS4eegWDvvpL+N9I328SiKvn0tXVL8KPpWO+P6rlHh4Lr5GjTz3m5V/bZNnUwF9TY//H3ZLOvnGU0aEHTW+xddaTSdH+1bLTj8cz0Gdw0RcyHbbjCmECpOIfvtnP9CqqUgvjAwq+iNeCdoWqfuBZ4=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=2YGwFr7N7rRlpm4cKV/TriP1qwQsO4YjBQOD0LvJ4WS9gZMr3XLDrwH53y9nSmv42EPeihs/3pYkZw7+Mii8uTBrZCKdL/T7G6amLVv7msIobHfjTziVeWImOXkDiCM9YF6Hpfcpk6LdUPtTgLngF99ln/9AA8TOAEEV5sGpM4w=;
Message-ID: <760813.34822.qm@web45508.mail.sp1.yahoo.com>
X-YMail-OSG: tC8KsDwVM1mAtMYp54i0s3EBtHQ8NGaWeHHGmyepkAzC7LaBljlZlf58o3i60kXrNmxLyNhV84U8j42NGDnOQSzhXqBWT_m9p2iooHFpiaq6jF41FgRkxGXdVvTrLEGtBsJr6B4DSV.AHC2IFqNVMvwTGVcc106KP0kysLHJqczinLORnJpDblbAvb_HirTkVM3IQ.khM.54Y9GvSXi5kwg-
Received: from [68.106.217.192] by web45508.mail.sp1.yahoo.com via HTTP; Fri, 18 Sep 2009 07:41:52 PDT
X-Mailer: YahooMailRC/157.18 YahooMailWebService/0.7.347.2
References: <026364d64021d6cef8b930cf16df1221.squirrel@www.trepanning.net> <Pine.LNX.4.44.0907201645020.16218-100000@citation2.av8.net> <20090721195028.GQ1020@Sun.COM> <E1MTkBi-0007Gi-5e@fencepost.gnu.org> <20090722223622.GP1020@Sun.COM> <E1MU9jO-0007UF-Sl@fencepost.gnu.org>
Date: Fri, 18 Sep 2009 07:41:52 -0700
From: Erick O <ericko0@yahoo.com>
To: rms@gnu.org, Nicolas Williams <Nicolas.Williams@sun.com>
In-Reply-To: <E1MU9jO-0007UF-Sl@fencepost.gnu.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1838977118-1253284912=:34822"
Cc: ietf-honest@lists.iadl.org, tls@ietf.org, ietf@ietf.org
Subject: Re: [TLS] Last Call: draft-ietf-tls-extractor (Keying Material Exporters for Transport Layer Security (TLS)) to Proposed Standard
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Sep 2009 14:40:59 -0000





________________________________
From: Richard Stallman <rms@gnu.org>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: tls@ietf.org; ietf-honest@lists.iadl.org; ietf@ietf.org
Sent: Thursday, July 23, 2009 6:37:54 PM
Subject: Re: [TLS] Last Call: draft-ietf-tls-extractor (Keying Material Exporters for Transport Layer Security (TLS)) to Proposed Standard

    The operative word here is uncertainty.  A patent-holder creates
    uncertainty.  How should an SDO respond?  I'm not sure.  I'm only sure
    that I don't like getting DoSed, either into dropping a standard or into
    not implementing it for fear of infringing.

That's the nature of software patents: each one denies people the
freedom to write and run certain kinds of software.  This is why we
must abolish software patents.

Until we succeed in doing that, we can resist in certain ways.  One of
them is to refuse to establish standards that encourage their use.

Generally speaking, standards are useful, because they enable people
to converge what they are doing.  But that ceases to be true when the
use of the standard is patented.  It is better to have no standard
than have a standard that invites people into danger.
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls