Re: [Bridge-mib] FW: MIB copyright statement

"C. M. Heard" <heard@pobox.com> Wed, 30 July 2003 17:24 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09280 for <bridge-archive@odin.ietf.org>; Wed, 30 Jul 2003 13:24:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hufq-0002ho-8f for bridge-archive@odin.ietf.org; Wed, 30 Jul 2003 13:23:39 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6UHNcLG010396 for bridge-archive@odin.ietf.org; Wed, 30 Jul 2003 13:23:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hufE-0002dm-Vo; Wed, 30 Jul 2003 13:23:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hueG-0002cg-Ow for bridge-mib@optimus.ietf.org; Wed, 30 Jul 2003 13:22:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09215 for <bridge-mib@ietf.org>; Wed, 30 Jul 2003 13:21:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hueE-0001yi-00 for bridge-mib@ietf.org; Wed, 30 Jul 2003 13:21:58 -0400
Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19hueD-0001yf-00 for bridge-mib@ietf.org; Wed, 30 Jul 2003 13:21:57 -0400
Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h6UHLqn04493; Wed, 30 Jul 2003 10:21:52 -0700
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Wed, 30 Jul 2003 10:21:50 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: bridge-mib@ietf.org
cc: stds-802-1@ieee.org
Subject: Re: [Bridge-mib] FW: MIB copyright statement
In-Reply-To: <Pine.LNX.4.10.10307300058320.13196-100000@shell4.bayarea.net>
Message-ID: <Pine.LNX.4.10.10307300940300.20274-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Id: <bridge-mib.ietf.org>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=subscribe>

On Wed, 30 Jul 2003, C. M. Heard wrote:
> On Wed, 30 Jul 2003, Scott Bradner wrote:
> > if the IETF is republishing the material it must have a
> > non-exclusive grant of copyright to do so so the ISOC copyright
> > is correct - if the IEEE is not granting that non-exclusive
> > right then the RFC can not be published
> 
> Well, it's not obvious that a grant of copyright, as opposed to
> permission to use the material, is required for republication.
> 
> But even if ISOC does get a non-exclusive grant of copyright, the
> point still stands that the standard abbreviated MIB copyright
> notice would be misleading since it mentions ISOC only, and not
> the IEEE, which in this case is the principal copyright holder.

Another point to be noted is that extraction of a MIB module from
an RFC (or an Internet-Draft) amounts to creation of a derivative
work.  The IEEE can grant permission for the IETF to republish the
MIB module in an informational RFC without necessarily granting
permission for the MIB module to be extracted;  that permission
needs to be granted separately.  Here is an extract from Section
5.2 (entitled "Derivative Works Limitation") of
draft-ietf-ipr-submission-rights-06.txt:

   If the Contributor desires to eliminate the IETF's right to make
   modifications and derivative works of an Contribution (other than
   translations), one of the two the following notices may be included
   in the Status of memo section of an Internet-Draft and included in a
   published RFC:

   a. "This document may not be modified, and derivative works of it may
      not be created, except to publish it as a RFC and to translate it
      into languages other than English."

   b. "This document may not be modified, and derivative works of it may
      not be created."

   In the cases of MIB or PIB modules and in other cases where the
   Contribution includes material that is meant to be extracted in order
   to be used, the following should be appended to statement 5.2 (a) or
   5.2 (b):

      "other than to extract section XX as-is for separate use."

   Notice 5.2(a) is used if the Contributor intends for the Contribution
   to be published as a RFC.  Notice 5.2(b) is used along with the
   Publication Limitation in Section 5.3 when the Contributor does not
   intend for the Contribution to be published as a RFC.

Again, it seems to me that the IEEE (as owner of the rights to the
MIB module) should be able to determine (a) whether it wants to
allow extraction of the MIB module and if so (b) what copyright
notice and restrictions on use apply.  That's not actually what
draft-ietf-ipr-submission-rights-06.txt says, though.  Since that
document is now in Last Call, I shall comment asking to ask that
this apparent omission be rectified.

//cmh


_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib