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

Marshall Eubanks <tme@multicasttech.com> Thu, 12 February 2009 19:17 UTC

Return-Path: <tme@multicasttech.com>
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 2A0F53A68A9 for <ietf@core3.amsl.com>; Thu, 12 Feb 2009 11:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 3QZJEDEvgXTi for <ietf@core3.amsl.com>; Thu, 12 Feb 2009 11:17:00 -0800 (PST)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 4941C3A67AD for <ietf@ietf.org>; Thu, 12 Feb 2009 11:17:00 -0800 (PST)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 14619183; Thu, 12 Feb 2009 14:15:53 -0500
Message-Id: <A468E547-D9DF-47CF-B190-C00B934E6692@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <49945B7A.60603@piuha.net>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: IETF and open source license compatibility (Was: Re: yet another comment on draft-housley-tls-authz-extns-07.txt)
Date: Thu, 12 Feb 2009 14:17:02 -0500
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> <49945B7A.60603@piuha.net>
X-Mailer: Apple Mail (2.930.3)
Cc: Harald Alvestrand <harald@alvestrand.no>, ietf@ietf.org, Simon Josefsson <simon@josefsson.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 19:17:01 -0000

Dear Jari et al.;

On Feb 12, 2009, at 12:25 PM, Jari Arkko wrote:

> 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?
>

I am not a lawyer, but I don't believe that the IETF has no legal  
existence and thus cannot sue. Any "IETF" suits would have to come  
from the Trust. If there are issues, the Trust can solve them by  
warranting that they will not sue under given conditions, as is being  
done with the Trust Legal Provisions.

Marshall

> Jari
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf