Re: IETF and open source license compatibility

Simon Josefsson <simon@josefsson.org> Thu, 12 February 2009 21:03 UTC

Return-Path: <simon@josefsson.org>
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 487DD28C280 for <ietf@core3.amsl.com>; Thu, 12 Feb 2009 13:03:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.488
X-Spam-Level:
X-Spam-Status: No, score=-1.488 tagged_above=-999 required=5 tests=[AWL=1.111, 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 HJ6+0SlKiUFV for <ietf@core3.amsl.com>; Thu, 12 Feb 2009 13:03:38 -0800 (PST)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id 7198F3A67D6 for <ietf@ietf.org>; Thu, 12 Feb 2009 13:03:38 -0800 (PST)
Received: from c80-216-29-127.bredband.comhem.se ([80.216.29.127] helo=mocca.josefsson.org) by yxa-v.extundo.com with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from <simon@josefsson.org>) id 1LXiii-0005fC-IY; Thu, 12 Feb 2009 22:03:40 +0100
From: Simon Josefsson <simon@josefsson.org>
To: Wes Hardaker <wjhns1@hardakers.net>
Subject: Re: IETF and open source license compatibility
References: <87bpt9ou7d.fsf@mocca.josefsson.org> <C5B8BAE5.30347%stewe@stewe.org> <87k57vlwfu.fsf@mocca.josefsson.org> <49941899.5010506@piuha.net> <sd4oyzcrh3.fsf@wes.hardakers.net>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090212:jari.arkko@piuha.net::B/7IKY5EhC5YZFor:1XeD
X-Hashcash: 1:22:090212:ietf@ietf.org::94DOB5Om+nferZIY:1PUB
X-Hashcash: 1:22:090212:wjhns1@hardakers.net::zPrffBp6FyclXrF3:ALPp
Date: Thu, 12 Feb 2009 22:03:39 +0100
In-Reply-To: <sd4oyzcrh3.fsf@wes.hardakers.net> (Wes Hardaker's message of "Thu, 12 Feb 2009 12:47:36 -0800")
Message-ID: <877i3vjrkk.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.90 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: ietf@ietf.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: Thu, 12 Feb 2009 21:03:39 -0000

Wes Hardaker <wjhns1@hardakers.net> writes:

> So, I couldn't find a statement that says automatic sublicenses will be
> given out for code related items.  It only says that the policies for
> creating those sublicenses ***will*** be guided by 5377 (which says
> about the right thing: you can modify code extracts).  IE, is it
> actually possible to use code from RFCs beyond 5378?  I think each
> company/organization/author would need to personally ask the IETF trust
> for a sublicense?

The IETF Trust sub-license third parties rights to code components in
(new) IETF documents under the BSD license, see section 4 of:

http://trustee.ietf.org/docs/IETF-Trust-License-Policy.pdf

/Simon