Re: Coupling RFC copying conditions with the existence of the IETF

Sam Hartman <hartmans-ietf@mit.edu> Mon, 07 March 2005 16:40 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 LAA06016 for <ipr-wg-web-archive@ietf.org>; Mon, 7 Mar 2005 11:40:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8LJv-00088s-5G for ipr-wg-web-archive@ietf.org; Mon, 07 Mar 2005 11:43:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D8LFg-0000GD-5Q; Mon, 07 Mar 2005 11:38:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D8LFe-0000G8-OG for ipr-wg@megatron.ietf.org; Mon, 07 Mar 2005 11:38:38 -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 LAA05868 for <ipr-wg@ietf.org>; Mon, 7 Mar 2005 11:38:36 -0500 (EST)
Received: from wireless-130-129-135-158.ietf62.ietf.org ([130.129.135.158] helo=cz.mit.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8LHs-00085c-DQ for ipr-wg@ietf.org; Mon, 07 Mar 2005 11:40:56 -0500
Received: by cz.mit.edu (Postfix, from userid 8042) id 3EAD6E0063; Mon, 7 Mar 2005 11:30:03 -0500 (EST)
To: Brian E Carpenter <brc@zurich.ibm.com>
References: <iluy8dir7p5.fsf@latte.josefsson.org> <20050221021306.897F122ADB7@newdev.harvard.edu> <iluoeeeqq5z.fsf_-_@latte.josefsson.org> <421D8709.4030806@twcny.rr.com> <421F2A8F.5050405@zurich.ibm.com>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Mon, 07 Mar 2005 11:30:03 -0500
In-Reply-To: <421F2A8F.5050405@zurich.ibm.com> (Brian E. Carpenter's message of "Fri, 25 Feb 2005 14:39:27 +0100")
Message-ID: <tslu0nns9kk.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: ipr-wg@ietf.org
Subject: Re: Coupling RFC copying conditions with the existence of the IETF
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: e5ba305d0e64821bf3d8bc5d3bb07228

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

    Brian> Personal opinion: I find much more confusion in these
    Brian> comments than in the draft. I don't see any grounds to
    Brian> believe that it's in the IETF's best interests, or in
    Brian> technology users' best interests, for technical
    Brian> specifications to be "free documents" in the sense used
    Brian> below. Technical specifications are used to achieve
    Brian> interoperability; in the Internet we strive for global
    Brian> interoperability.  So *preventing* 3rd party modifications
    Brian> to specifications is essential to their value as freely
    Brian> available open interoperability standards.


Several of us have argued that making standards not freely modifiable
does not actually reduce the chances that such standards will be
modified.  Instead it will mean that when the standards are modified,
they are not clearly documented.

Clear documentation improves global interoperability.  Unless you or
someone else can show that making our standards not freely modifiable
actually reduces modification then I think global interoperability is
best served by freely modifiable standards.

--Sam


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