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

Simon Josefsson <simon@josefsson.org> Sun, 11 January 2009 21:13 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 64BDD3A68CC; Sun, 11 Jan 2009 13:13:38 -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 528CE3A68CC for <ietf@core3.amsl.com>; Sun, 11 Jan 2009 13:13:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.592
X-Spam-Level:
X-Spam-Status: No, score=-2.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 T+tdv+dXC4kJ for <ietf@core3.amsl.com>; Sun, 11 Jan 2009 13:13:36 -0800 (PST)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id 597EC3A67B6 for <ietf@ietf.org>; Sun, 11 Jan 2009 13:13:35 -0800 (PST)
Received: from c80-216-27-189.bredband.comhem.se ([80.216.27.189] helo=mocca.josefsson.org) by yxa-v.extundo.com with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from <simon@josefsson.org>) id 1LM7cQ-00048F-PI; Sun, 11 Jan 2009 22:13:15 +0100
From: Simon Josefsson <simon@josefsson.org>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your reviewand comments on a proposed Work-Around to the Pre-5378 Problem
References: <FB8A848E-E415-4CDE-9E3F-5C74A5614F18@cisco.com> <49678B2A.8000100@dcrocker.net> <20090109181503.GP24908@verdi> <6E372F257B0C42E7AB9B7DA6231FF4E4@LROSENTOSHIBA> <p06240800c58d5466241b@[10.227.48.131]> <DBAA71AA401E5398212B1E03@PST.jck.com> <4967CAA1.9020608@gmail.com> <B2385D8E5F5BA599A174BD43@PST.jck.com> <4967E348.7050300@joelhalpern.com> <87d4evgu35.fsf@mocca.josefsson.org> <20090110191055.GB31579@mit.edu> <87bpudkhfh.fsf@mocca.josefsson.org> <496A1038.4020807@joelhalpern.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090111:jmh@joelhalpern.com::tcM6lpscX4uMWS0g:1KGa
X-Hashcash: 1:22:090111:ietf@ietf.org::iveroj/gNpT3RHh3:Y28m
Date: Sun, 11 Jan 2009 22:13:13 +0100
In-Reply-To: <496A1038.4020807@joelhalpern.com> (Joel M. Halpern's message of "Sun, 11 Jan 2009 10:28:56 -0500")
Message-ID: <871vv9k0ly.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Cc: 'IETF Discussion' <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

"Joel M. Halpern" <jmh@joelhalpern.com> writes:

> Let's be quite clear here.
> Your stated requirement for doing this was that authors had to be able
> to take and modify any text from anywhere in an RFC.

No, that's a different issue.  Being able (as RFC author) to include
code not written by IETF contributors is different from being able to
modify text in an RFC (as RFC reader).

> The Working Group concluded that while that was reasonable relative to
> code (and we tried to give the open source community that ability
> relative to code), that such a wide grant was not reasonable relative
> to the text content of RFC.

Alas.

> (Among other concerns, such changes would include modification of
> normative text and text carefully worked out by working groups to get
> the meanings right.  If the WG got it wrong, the IETF is the place to
> fix it, not comments in code somewhere.)

I obviously disagree.  Users of free software need the ability to fix
the source code and modify the documentation that goes along with it.
The issue should of course be brought up within the IETF too, but it
does not serve the IETF's goal of running a "smooth Internet" to make it
harder for people to fix software that runs the Internet.

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