Re: Transfers of copyright versus licensing

Simon Josefsson <jas@extundo.com> Fri, 11 March 2005 22:57 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15555 for <ipr-wg-web-archive@ietf.org>; Fri, 11 Mar 2005 17:57:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9t7u-0007Jv-Dh for ipr-wg-web-archive@ietf.org; Fri, 11 Mar 2005 18:01:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9t3l-0001Y2-A6; Fri, 11 Mar 2005 17:56:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9t3j-0001XY-Uw for ipr-wg@megatron.ietf.org; Fri, 11 Mar 2005 17:56:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15484 for <ipr-wg@ietf.org>; Fri, 11 Mar 2005 17:56:35 -0500 (EST)
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9t6i-0007Cl-Aj for ipr-wg@ietf.org; Fri, 11 Mar 2005 17:59:49 -0500
Received: from latte.josefsson.org (c494102a.s-bi.bostream.se [217.215.27.65]) (authenticated bits=0) by yxa.extundo.com (8.13.3/8.13.3/Debian-6) with ESMTP id j2BMuUPS020142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 11 Mar 2005 23:56:31 +0100
From: Simon Josefsson <jas@extundo.com>
To: Brian E Carpenter <brc@zurich.ibm.com>
References: <744054F86C2018BDEF80D603@as-s2n.ietf62.ietf.org> <1110490891.10971.208.camel@unknown.hamachi.org> <4232076F.4070307@zurich.ibm.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
Blog: http://www.livejournal.com/users/jas4711/
X-Hashcash: 1:21:050311:brc@zurich.ibm.com::ObOMnh/RJGGHsL37:5SUg
X-Hashcash: 1:21:050311:ipr-wg@ietf.org::X8mRm0jXNJA7dpW9:6Rtz
Date: Fri, 11 Mar 2005 23:56:13 +0100
In-Reply-To: <4232076F.4070307@zurich.ibm.com> (Brian E. Carpenter's message of "Fri, 11 Mar 2005 22:02:39 +0100")
Message-ID: <ilu64zxdc6q.fsf@latte.josefsson.org>
User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Status: No, score=0.1 required=5.0 tests=FORGED_RCVD_HELO autolearn=failed version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on yxa-iv
X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on yxa.extundo.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: ipr-wg@ietf.org
Subject: Re: Transfers of copyright versus licensing
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
Sender: ipr-wg-bounces@ietf.org
Errors-To: ipr-wg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d

Brian E Carpenter <brc@zurich.ibm.com> writes:

> Bill Sommerfeld wrote:
>> I've seen indications (in the context of an open source project) that
>> joint copyright ownership might be legally possible.
>> In other words, both the contributor *and* the recipient would
>> retain full
>> rights to do whatever they wanted with the text.
>
> Scenario: I write a spec. The IETF puts the ISOC copyright on it.
> I invert a couple of bytes in my version and republish.
> Interoperability, anybody?

What exactly is your point?

Are you saying that simply because an author invert a few bytes in
their document and publish it somewhere (!= IETF, I presume), there
will be interoperability issues?

I'd like to hold implementors of IETF protocols to a higher standard
than becoming confused over something like that.

Non-IETF or non-technical people (which DO read RFCs) may be confused,
but fortunately they rarely implement the protocols, so I believe the
practical protocol-interoperability issues, when RFCs are freely
modifiable, is likely zero.

Remember that there is nothing the IETF can do to prevent the
possibility that non-IETF-members become confused -- everyone can
author a document and entitle it "RFC 2822".  Make it look credible,
and you will fool someone.

Looking forwards to the IPR meeting minutes,
Simon

_______________________________________________
Ipr-wg mailing list
Ipr-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/ipr-wg