Re: [Cfrg] I-D Action:draft-kiyomoto-kcipher2-02.txt

David McGrew <mcgrew@cisco.com> Fri, 22 April 2011 13:28 UTC

Return-Path: <mcgrew@cisco.com>
X-Original-To: cfrg@ietfc.amsl.com
Delivered-To: cfrg@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 1BC2BE071D for <cfrg@ietfc.amsl.com>; Fri, 22 Apr 2011 06:28:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.599
X-Spam-Level:
X-Spam-Status: No, score=-109.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4xEsrkWC2vfO for <cfrg@ietfc.amsl.com>; Fri, 22 Apr 2011 06:28:06 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfc.amsl.com (Postfix) with ESMTP id 91BD3E06CC for <cfrg@irtf.org>; Fri, 22 Apr 2011 06:28:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=3347; q=dns/txt; s=iport; t=1303478886; x=1304688486; h=cc:message-id:from:to:in-reply-to: content-transfer-encoding:mime-version:subject:date: references; bh=p9ZtaPXbtdX6SfCMHgdIOnWYDYEvf1aLyI7cPI2d2pU=; b=i9v8WSxTtrlFZwVfyNqdnYrndETnmQhXmKGri2Jkm4lFh+8UJpyFILcN buWIeHat8p4omzjSDDJjMYUVx6znTet+ieNCN3F8IbKHLQQOK5zX6j3kp Q8f9PHGu3OapyaYR0RwqxHBjgz5kt1orcrTSsR+KIQDBWyBr7uev7TXPG o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMeBsU2rRDoJ/2dsb2JhbAClXneIcJ11nF+FdgSFdIg5hAc
X-IronPort-AV: E=Sophos;i="4.64,253,1301875200"; d="scan'208";a="342728766"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-2.cisco.com with ESMTP; 22 Apr 2011 13:28:05 +0000
Received: from [10.32.254.210] ([10.32.254.210]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p3MDS53S004243; Fri, 22 Apr 2011 13:28:05 GMT
Message-Id: <000DAA29-1B5D-478C-B460-025014924431@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: "Wook Shin" <wookshin@kddilabs.jp>
In-Reply-To: <op.vucavstipzjggh@ohpato-t61.sec.kddilabs.jp>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 22 Apr 2011 06:28:04 -0700
References: <20110413010001.17531.11616.idtracker@ietfc.amsl.com> <op.vtur72zepzjggh@ohpato-t61.sec.kddilabs.jp> <4DAFE257.4080602@Strombergson.com> <op.vucavstipzjggh@ohpato-t61.sec.kddilabs.jp>
X-Mailer: Apple Mail (2.936)
Cc: "cfrg@irtf.org" <cfrg@irtf.org>
Subject: Re: [Cfrg] I-D Action:draft-kiyomoto-kcipher2-02.txt
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Apr 2011 13:28:08 -0000

Hi Wook,

On Apr 22, 2011, at 5:41 AM, Wook Shin wrote:

> Hello all,
>
> Now I am revising the draft reflecting the comments that I got from
> Joachim, Jim and Uri. (Thank you for the precious comments!)
> I think I would be able to have the next version of the draft on
> Tuesday next week.
>
> I have a question regarding the copyright issue though. By the IETF
> policy, is there a way of giving rights only to non-commercial uses?
> My company is preparing the IPR disclosure and just want to know
> what kind of options they could have.

right to what, exactly?  If you mean rights to "code components", that  
is, snippets of source code that appear in the draft, then the answer  
is yes, if you choose a license statement for the draft that forbids  
derivative works.  From the Trust Legal Provisions, http://trustee.ietf.org/license-info/ 
, "unless one of the legends contained in Section 6.c.i or 6.c.ii is  
included in an IETF Document containing Code Components, such Code  
Components are also licensed to each person who wishes to receive such  
a license on the terms of the “Simplified BSD License", as described  
below."  Section 6.c.i says : "If a Contributor chooses to limit the  
right to make modifications and derivative works of an IETF  
Contribution, then one of the notices in clause (i) or (ii) below must  
be included. Note that an IETF Contribution with such a notice cannot  
become a Standards Track document or, in most cases, a working group  
document."  But note that the current draft includes the statement  
"Code Components extracted from this document must include Simplified  
BSD License text as described in Section 4.e of the Trust Legal  
Provisions and are provided without warranty as described in the  
Simplified BSD License", so that code components in that draft can be  
used under those terms.

If by rights you mean IPR, that is, the right to use a patent, there  
are many options open to your company.  See http://www.ietf.org/ipr/  
for the details and examples of IPR statements made by other  
companies.  Please also note that, if you are aware of patents that  
are essential to the implementation of the draft, you have an  
obligation to the IETF to disclose them.

The above is the IETF policy.  I would like to add a personal note: I  
encourage your employer to consider an IPR statement that allows for  
royalty-free use, and which does not require every implementer to have  
to hire a lawyer, which would be the case if the IPR statement  
requires that some legal paperwork needs to be done.  Here is an  
example of a royalty-free, lawyer-free IPR statement, chosen at  
random: https://datatracker.ietf.org/ipr/752/.  Experience has shown  
that crypto algorithms that require royalties from implementers see  
very low adoption, and are typically rejected by working groups that  
are developing standards.  Even a royalty-free license that requires  
some legal paperwork inhibits adoption, especially in open source  
projects.

David

>
> Best regards,
>
> Wook
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg