IETF Logo Mail Archive

Re: IETF Last Call for two IPR WG Dcouments

Simon Josefsson <simon@josefsson.org> Sun, 30 March 2008 09:15 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B1BD28C1B9; Sun, 30 Mar 2008 02:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.515
X-Spam-Level:
X-Spam-Status: No, score=-100.515 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.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 2ZaA3gqXcv6Q; Sun, 30 Mar 2008 02:15:50 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0782D3A6A5E; Sun, 30 Mar 2008 02:15:50 -0700 (PDT)
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 266333A6804 for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 02:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 VvjDMMHL9s-R for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 02:15:46 -0700 (PDT)
Received: from yxa.extundo.com (yxa.extundo.com [83.241.177.38]) by core3.amsl.com (Postfix) with ESMTP id 9972C3A6A5E for <ietf@ietf.org>; Sun, 30 Mar 2008 02:15:45 -0700 (PDT)
Received: from mocca.josefsson.org (yxa.extundo.com [83.241.177.38]) (authenticated bits=0) by yxa.extundo.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id m2U9Fblv025884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 30 Mar 2008 11:15:38 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: IETF Last Call for two IPR WG Dcouments
In-Reply-To: <47EE921B.8060509@gmail.com> (Brian E. Carpenter's message of "Sun, 30 Mar 2008 08:01:47 +1300")
References: <2B752728-CE81-40B5-8E66-230D5E504D4F@thingmagic.com> <BB56240F3A190F469C52A57138047A032BCAC0@xmb-rtp-211.amer.cisco.com> <87r6dtopy9.fsf@mocca.josefsson.org> <47EE921B.8060509@gmail.com>
User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (gnu/linux)
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:080330:jmh@joelhalpern.com::lihZww7oAURjcUQa:318b
X-Hashcash: 1:22:080330:ietf@ietf.org::P2T6visKwmWL7M6Q:6Aar
X-Hashcash: 1:22:080330:brian.e.carpenter@gmail.com::z5FS5YC20Qv1XOmA:3XqA
X-Hashcash: 1:22:080330:margaret@thingmagic.com::aLKLWeEKHEdQDShv:Uvjj
Date: Sun, 30 Mar 2008 11:15:37 +0200
Message-ID: <877ifkfu86.fsf@mocca.josefsson.org>
MIME-Version: 1.0
X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on yxa.extundo.com
X-Virus-Status: Clean
Cc: Margaret Wasserman <margaret@thingmagic.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, 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-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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Brian E Carpenter <brian.e.carpenter@gmail.com> writes:

> Simon,
>
> On 2008-03-29 22:10, Simon Josefsson wrote:
> ...
>> this?  However, if a license meet the requirements of OSD/FSD/DFSG, 
>
> I don't believe it is appropriate for an IETF BCP to contain
> an open-ended dependency on whatever future requirements three
> other organizations might publish. That's why it seems
> necessary and sufficient that the BCP sets out the goals.

If the trust uses a software license for code that doesn't meet the
requirements in, say, the DFSG, would you consider that a failure?  If
that happens, Debian cannot include such code.

Using the NPOSL3.0 as the software license, which I read Ray's message
to imply was being considered, would be one way to prevent Debian from
using the code.

I would agree that the references should be for a specific version of
the documents, if that is your point.

/Simon
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email