Re: ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem

John C Klensin <john-ietf@jck.com> Fri, 30 January 2009 00:30 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E81C28C23E; Thu, 29 Jan 2009 16:30:17 -0800 (PST)
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 53D8E28C1F5; Thu, 29 Jan 2009 16:30:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level:
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 r2R7zJfrXZ+R; Thu, 29 Jan 2009 16:30:15 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 52D9B28C1F0; Thu, 29 Jan 2009 16:30:15 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1LShGX-000Njz-Gg; Thu, 29 Jan 2009 19:29:49 -0500
Date: Thu, 29 Jan 2009 19:29:48 -0500
From: John C Klensin <john-ietf@jck.com>
To: Dean Anderson <dean@av8.com>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem
Message-ID: <1A93F4183A36C97B095A96A7@PST.JCK.COM>
In-Reply-To: <Pine.LNX.4.44.0901291620470.485-100000@citation2.av8.net>
References: <Pine.LNX.4.44.0901291620470.485-100000@citation2.av8.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: trustees@ietf.org, Bob Braden <braden@ISI.EDU>, 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

--On Thursday, January 29, 2009 16:26 -0500 Dean Anderson
<dean@av8.com> wrote:

>...
> You comment explains exactly the problems with RFC5378.  This
> is why we, Glassey, myself, others advocated for having the
> contributor hold the copyright, as is done in other standards
> groups, like the ITU, The Open Group, ANSI, etc

Dean, while I prefer the "Contributor holds copyright and gives
the standards body the rights it needs" model that you appear to
be advocating for the IETF, you might want to do a little
fact-checking on the other standards groups you use as examples
(and perhaps more generally).   In almost all ANSI SDOs, the
rule is that one applies for membership and, as part of that
application, agrees to treat done anything done for the
Standards group, developed in its context, or otherwise
contributed to it, as a work for hire for that standards group.
When the contribution has already been published in another
context, those same bodies usually, although I think not always,
require explicit copyright transfers to the SDO.   Those
mechanisms are about as far from "contributor holds the
copyright" as it is possible to get, IMO.

ITU's rules are a little different, but the effect is much the
same.  And neither ITU nor most ANSI SDOs list authors for
standards -- they are always considered collective,
consensus-developed, works with, at most, an editor (usually
listed as part of the listing of the committee members or as an
indication of staff support, not as front page matter or as a
normal part of a citation to the document).

    john

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