Copyrighted RFC Code
Simon Josefsson <simon@josefsson.org> Wed, 17 January 2007 13:26 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H7AoY-0004O8-Aj; Wed, 17 Jan 2007 08:26:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H7AoW-0004Nx-Qu for ipr-wg@ietf.org; Wed, 17 Jan 2007 08:26:52 -0500
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H7AoS-00053r-OT for ipr-wg@ietf.org; Wed, 17 Jan 2007 08:26:52 -0500
Received: from localhost.localdomain (yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id l0HDQRgv018092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jan 2007 14:26:27 +0100
From: Simon Josefsson <simon@josefsson.org>
To: "Contreras, Jorge" <Jorge.Contreras@wilmerhale.com>
References: <20070117123855.GA14142@nic.fr> <50E312B117033946BA23AA102C8134C67FFEA4@SDCPEXCCL2MX.wilmerhale.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:070117:bortzmeyer@nic.fr::t39st4lEzAOjr8dE:0fwY
X-Hashcash: 1:22:070117:jorge.contreras@wilmerhale.com::qVglwTvfoiORWmHv:4hV6
X-Hashcash: 1:22:070117:ipr-wg@ietf.org::WGb70VCYuOc/QEBm:0ADp3
Date: Wed, 17 Jan 2007 14:26:27 +0100
In-Reply-To: <50E312B117033946BA23AA102C8134C67FFEA4@SDCPEXCCL2MX.wilmerhale.com> (Jorge Contreras's message of "Wed\, 17 Jan 2007 07\:53\:18 -0500")
Message-ID: <87ejptg4xo.fsf_-_@latte.josefsson.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.92 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Status: No, score=-0.3 required=4.0 tests=AWL,BAYES_50, FORGED_RCVD_HELO autolearn=ham version=3.1.1
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on yxa-iv
X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on yxa.extundo.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: IPR WG <ipr-wg@ietf.org>
Subject: Copyrighted RFC Code
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>
Errors-To: ipr-wg-bounces@ietf.org
"Contreras, Jorge" <Jorge.Contreras@wilmerhale.com> writes: >> I did not specially mention the patent issue. Even if there is no >> patent, I cannot use at will software written by someone else unless >> there is a *specific* authorization to do so. This is this >> authorization that we miss. >> > 3.3.a.E gives this authorization, but excluding patents. There seems to be disagreement about that. Is there support for updating BCP 78 to clarify the above? The current text (the parenthesis) appears to be permissive about the _purpose_ of the rights granted, but does not modify _whom_ is given those rights. Scott Bradner's draft-bradner-rfc-extracts-00 confirm that interpretation, as does the FSF and debian-legal's interpretations, if I remember correctly. In other words, change: (E) to extract, copy, publish, display, distribute, modify and incorporate into other works, for any purpose (and not limited to use within the IETF Standards Process) any executable code or code fragments that are included in any IETF Document (such as MIB and PIB modules), ... into: (E) to extract, copy, publish, display, distribute, modify and incorporate into other works, for any purpose (and not limited to use within the IETF Standards Process) and by anyone ------------- (including third parties) any executable code or code ------------------------- fragments that are included in any IETF Document (such as MIB and PIB modules), ... I underlined the modified part. This modification would improve the copyright-aspect of this problem until the other work that this WG is doing is finished. Timing is an issue here, since new rules in this area cannot apply retroactively (as far as I understand). Until this is fixed in BCP 78, each document that contain code would need additional text to give the necessary rights to third parties. /Simon _______________________________________________ Ipr-wg mailing list Ipr-wg@ietf.org https://www1.ietf.org/mailman/listinfo/ipr-wg
- Re: IETF Trust FAQ Brian E Carpenter
- Re: IETF Trust FAQ Simon Josefsson
- Re: IETF Trust FAQ Simon Josefsson
- Re: IETF Trust FAQ Brian E Carpenter
- Re: IETF Trust FAQ todd glassey
- Re: IETF Trust FAQ Simon Josefsson
- Re: IETF Trust FAQ Harald Alvestrand
- RE: IETF Trust FAQ Lawrence Rosen
- RE: IETF Trust FAQ Contreras, Jorge
- Re: IETF Trust FAQ todd glassey
- Re: IETF Trust FAQ todd glassey
- RE: IETF Trust FAQ Contreras, Jorge
- RE: IETF Trust FAQ Lawrence Rosen
- Patent Licenses for Code in RFCs? Contreras, Jorge
- Re: IETF Trust FAQ Steven M. Bellovin
- RE: IETF Trust FAQ Lawrence Rosen
- Re: IETF Trust FAQ Harald Alvestrand
- Re: IETF Trust FAQ Stephane Bortzmeyer
- RE: IETF Trust FAQ Lawrence Rosen
- ADMIN: One topic per subject line (Re: IETF Trust… Harald Alvestrand
- Patent licenses (was: IETF Trust FAQ) Frank Ellermann
- Patented RFC Code Contreras, Jorge
- Re: Patented RFC Code Stephane Bortzmeyer
- RE: Patented RFC Code Contreras, Jorge
- Re: Patent Licenses for Code in RFCs? Brian E Carpenter
- Copyrighted RFC Code Simon Josefsson
- Re: IETF Trust FAQ Brian E Carpenter
- Granting rights that you do not have Simon Josefsson
- Purpose of this WG [Re: IETF Trust FAQ] Brian E Carpenter
- Re: Patented RFC Code John C Klensin
- Re: Patented RFC Code todd glassey
- Re: Copyrighted RFC Code Harald Alvestrand
- RE: Patented RFC Code Lawrence Rosen
- Re: Patented RFC Code Harald Alvestrand
- IETF Patent policy (was RE: IETF Trust FAQ) Ted Hardie
- RE: IETF Patent policy (was RE: IETF Trust FAQ) Lawrence Rosen
- RE: IETF Patent policy (was RE: IETF Trust FAQ) Ted Hardie
- RE: IETF Patent policy (was RE: IETF Trust FAQ) John C Klensin
- Re: IETF Patent policy (was RE: IETF Trust FAQ) Mukundan R
- Re: Patented RFC Code Frank Ellermann
- Re: Patented RFC Code Steven M. Bellovin
- Re: Patented RFC Code Scott O. Bradner
- Re: Patented RFC Code Frank Ellermann
- Re: Patented RFC Code Frank Ellermann
- Re: Patented RFC Code Simon Josefsson
- Re: Patented RFC Code Harald Alvestrand
- Re: Patented RFC Code Scott O. Bradner
- Re: IETF Patent policy (was RE: IETF Trust FAQ) todd glassey
- Re: Patented RFC Code Frank Ellermann
- Case study: SHA2 (was: Re: Patented RFC Code) Simon Josefsson
- Re: Case study: SHA2 Harald Alvestrand
- RE: Case study: SHA2 Lawrence Rosen
- Re: Case study: SHA2 Frank Ellermann
- Re: Case study: SHA2 Steven M. Bellovin
- RE: Case study: SHA2 (was: Re: Patented RFC Code) Barr Hibbs
- Re: Case study: SHA2 Simon Josefsson
- Re: Case study: SHA2 Steven M. Bellovin
- Re: Case study: SHA2 Frank Ellermann