IETF Logo Mail Archive

Re: IETF and open source license compatibility (Was: Re: yet another comment on draft-housley-tls-authz-extns-07.txt)

Jari Arkko <jari.arkko@piuha.net> Thu, 12 February 2009 17:26 UTC

Return-Path: <jari.arkko@piuha.net>
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 7CBBD3A6AE5 for <ietf@core3.amsl.com>; Thu, 12 Feb 2009 09:26:28 -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 uUUsG0-EX3Xi for <ietf@core3.amsl.com>; Thu, 12 Feb 2009 09:26:27 -0800 (PST)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 907503A69F9 for <ietf@ietf.org>; Thu, 12 Feb 2009 09:26:27 -0800 (PST)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 4249019870C; Thu, 12 Feb 2009 19:26:32 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id DDF151986EE; Thu, 12 Feb 2009 19:26:31 +0200 (EET)
Message-ID: <49945B7A.60603@piuha.net>
Date: Thu, 12 Feb 2009 19:25:14 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>, Margaret Wasserman <mrw@lilacglade.org>, Simon Josefsson <simon@josefsson.org>
Subject: Re: IETF and open source license compatibility (Was: Re: yet another comment on draft-housley-tls-authz-extns-07.txt)
References: <87bpt9ou7d.fsf@mocca.josefsson.org> <C5B8BAE5.30347%stewe@stewe.org> <87k57vlwfu.fsf@mocca.josefsson.org> <49941899.5010506@piuha.net> <alpine.LSU.2.00.0902121243481.4546@hermes-2.csi.cam.ac.uk> <499447D1.6060600@alvestrand.no>
In-Reply-To: <499447D1.6060600@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
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 17:26:28 -0000

Harald, Margaret, and Simon,

Harald wrote
> actually that's intended to be permitted by RFC 5377 section 4.2:

and Margaret wrote:

> However, I don't think that anyone actually believes that the IETF 
> will track down people who copy RFC text into comments and sue them or 
> attempt to get injunctions against them.
>
> (2) Even if the IETF did try to sue you for copying sections of RFC 
> text into your source code comments, they'd almost certainly lose

So it seems that we actually do have at least some ability to deal with 
comment-style use of RFCs fragments in free software. Simon, do you see 
any residual issues that we need to solve, or were your concerns in 
areas other than comments?

Jari

v2.37.1 | Report a Bug | By Email | System Status