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:51 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 44B3B28C1A8 for <tls@core3.amsl.com>; Fri, 18 Sep 2009 07:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.555
X-Spam-Level:
X-Spam-Status: No, score=-2.555 tagged_above=-999 required=5 tests=[AWL=0.043, 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 8eyW6vaC29gb for <tls@core3.amsl.com>; Fri, 18 Sep 2009 07:51:21 -0700 (PDT)
Received: from web45502.mail.sp1.yahoo.com (web45502.mail.sp1.yahoo.com [68.180.197.62]) by core3.amsl.com (Postfix) with SMTP id D2D4B3A67AD for <tls@ietf.org>; Fri, 18 Sep 2009 07:51:20 -0700 (PDT)
Received: (qmail 31192 invoked by uid 60001); 18 Sep 2009 14:52:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1253285535; bh=+JwzqlW++NqkbZ6D3vhhvYZfEd2zRfSgOCFprN+dKtE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=4B+Jog1IY4l0E4HnKplBLT+5huHJMTPYsWUIKDu3y4Zb/ZHg07bs+4w5+jGR37Y9FziGO6UhG0w6sAPjhkpdzfJsVtryVK4mKlIP8rmQo7EmiPN0fwyat8iEo17L18aIA4cGYxbk0od6Zh7t4f8Max3FHvtUyeUlMr3PaORiRDE=
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=1Jar3/lC5NB9eXkhMWGigCRjoks+9wc4L9fhcxqmpuNTBQhglgmmcTUnafon8CvxTwWNCgJBDDQOLgRdW6CPeYplmpbseFelQW34eePIl/aZNEvdfwW4VqSc9hudBlyY4mOd/6i0l2cQtPtIC4POqvXtvai+ksSm9PfAUIDIBJ0=;
Message-ID: <447049.29825.qm@web45502.mail.sp1.yahoo.com>
X-YMail-OSG: 8jErUw8VM1kL7_eiswZTrGprcQMa_ij_BpZeoKDtUWGUD0b72X99NkL6
Received: from [68.106.217.192] by web45502.mail.sp1.yahoo.com via HTTP; Fri, 18 Sep 2009 07:52:14 PDT
X-Mailer: YahooMailRC/157.18 YahooMailWebService/0.7.347.2
References: <Pine.LNX.4.44.0907201436360.16218-100000@citation2.av8.net> <026364d64021d6cef8b930cf16df1221.squirrel@www.trepanning.net>
Date: Fri, 18 Sep 2009 07:52:14 -0700
From: Erick O <ericko0@yahoo.com>
To: Dan Harkins <dharkins@lounge.org>, Dean Anderson <dean@av8.com>
In-Reply-To: <026364d64021d6cef8b930cf16df1221.squirrel@www.trepanning.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-94601468-1253285534=:29825"
Cc: tls@ietf.org, ietf@ietf.org, rms@gnu.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:51:23 -0000





________________________________
From: Dan Harkins <dharkins@lounge.org>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org; rms@gnu.org; tls@ietf.org
Sent: Monday, July 20, 2009 1:24:44 PM
Subject: Re: [TLS] Last Call: draft-ietf-tls-extractor (Keying Material Exporters for Transport Layer Security (TLS)) to Proposed Standard


  Certicom's IPR statement dated 13 October 2008 lists some patents
that "may be necessary and essential to implementations of..." the
TLS extractor draft "when used with either: " RFC4492, RFC5289
or draft-rescorla-tls-suiteb. Check it out:

http://www.certicom.com/images/pdfs/certicom%20-ipr-contribution-to-ietfsept08.pdf

  Don't use it with RFC4492, RFC5289 or draft-rescorla-tls-suiteb and
then the IPR statement does not apply. If it's possible to use the TLS
extractor draft in a way that the IPR statement doesn't apply then I
don't think you can say "the TLS Extractor draft is patent-encumbered".

  I support free software* and I have no problem with this draft being
advanced as a Proposed Standard.

  regards,

  Dan.

* http://www.lounge.org/siv_for_openssl.tgz is a free version of RFC5297
  for OpenSSL, and check out the "authsae" project on Source Forge.

On Mon, July 20, 2009 12:15 pm, Dean Anderson wrote:
> I am against this standard because of its patent encumbrances and
> non-free licencing terms.  The working group did not get any clear
> answers on what particular patents this draft may infringe, but a patent
> holder (Certicom) did assert an IPR disclosure (1004) listing many
> patents.  We have no alternative but to accept the Certicom disclosure
> statements as meaning that the TLS Extractor draft is patent-encumbered
> without a universal, free defensive license.
>
> The statement by https://datatrackerietf.org/ipr/1004/ referring to
> http://www.certicom.com/images/pdfs/certicom%20-ipr-contribution-to-ietfsept08.pdf
> which states:
>
>  "Certicom will, upon request, provide a nonexclusive, royalty free
> patent license, to manufacturers to permit end users (including both
> client and server sides), to use the patents in schedule A when
> implementing any of these protocols, including those requiring third
> party certificates provided the certificate is obtained from a licensed
> Certificate Authority (CA). This license does not cover the issuing of
> certificates by a Certification Authority (CA)."
>
> That is not a free license, since Certicom must respond to the "request"
> before any license is granted. After the IETF finally approves the
> necessary standards, Certicom is free to stop approving the requests.
>
> I ask others who support free software to join me in opposing this
> document by sending a message stating opposition to the IETF@IETF.ORG
> mailing list.  IETF participation is open to the public, and anyone may
> voice their view on IETF standards.  It is also substantive to oppose a
> document because of its patent status, and in fact, any topic that is
> considered during or related to the IETF process is substantive.
>
>         --Dean
>
>
> On Mon, 20 Jul 2009, The IESG wrote:
>
>> The IESG has received a request from the Transport Layer Security WG
>> (tls) to consider the following document:
>>
>> - 'Keying Material Exporters for Transport Layer Security (TLS) '
>>    <draft-ietf-tls-extractor-06.txt> as a Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action.  Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2009-08-10. Exceptionally,
>> comments may be sent to iesg@ietf.org instead. In either case, please
>> retain the beginning of the Subject line to allow automated sorting.
>>
>> The file can be obtained via
>> http://www.ietf.org/internet-drafts/draft-ietf-tls-extractor-06.txt
>>
>>
>> IESG discussion can be tracked via
>> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16821&rfc_flag=0
>>
>> _______________________________________________
>> TLS mailing list
>> TLS@ietf.org
>> https://www.ietf.org/mailman/listinfo/tls
>>
>>
>
> --
> Av8 Internet  Prepared to pay a premium for better service?
> www.av8.net        faster, more reliable, better service
> 617 344 9000
>
>
>
>
>
>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>


_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls