[Tools-discuss] Comments on draft-ietf-tools-draft-submission-08.txt
Matthew Elvey <matthew@elvey.com> Wed, 11 May 2005 08:36 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DVmi2-0004ck-4F; Wed, 11 May 2005 04:36:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DVcEj-0004n3-Sf for tools-discuss@megatron.ietf.org; Tue, 10 May 2005 17:25:54 -0400
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 RAA22810 for <tools-discuss@ietf.org>; Tue, 10 May 2005 17:25:51 -0400 (EDT)
Received: from out1.smtp.messagingengine.com ([66.111.4.25]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DVcU3-0000jD-V4 for tools-discuss@ietf.org; Tue, 10 May 2005 17:41:48 -0400
Received: from frontend2.messagingengine.com (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 30949C8D83B for <tools-discuss@ietf.org>; Tue, 10 May 2005 17:25:46 -0400 (EDT)
X-Sasl-enc: jZ3jvsPRndM6s8bzbX66HYppChc5YmMktKbxS3B7be3s 1115760338
Received: from [192.168.2.98] (adsl-67-123-76-21.dsl.snfc21.pacbell.net [67.123.76.21]) by frontend2.messagingengine.com (Postfix) with ESMTP id BAF6C57034F; Tue, 10 May 2005 17:25:38 -0400 (EDT)
Message-ID: <428126DA.20207@elvey.com>
Date: Tue, 10 May 2005 14:25:46 -0700
From: Matthew Elvey <matthew@elvey.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: tools-discuss@ietf.org
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -8.0 (--------)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 11 May 2005 04:36:48 -0400
Subject: [Tools-discuss] Comments on draft-ietf-tools-draft-submission-08.txt
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tools-discuss>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org
Sorry for the late comments, but it seems another round is in process anyway...apologies for any duplicates. Having given this a couple reads, most of my concerns were addressed. Compression is IMO a silly feature, but its implementation is optional, so that's OK. (And I wonder if HTTP 1.1 doesn't support compressed POSTs.) I still wonder if anyone has done a survey (formal or anecdotal guesstimate) to determine what format drafts are created in (i.e. source format) these days. Even though the RFC Editors reportedly* don't use nroff/troff any more, it seems quite popular, and justifiably preferred** by some users who've tried both. I suppose they can continue to submit drafts the old way, if they're just a vocal small minority. *http://www1.ietf.org/mail-archive/web/tools-discuss/current/msg00280.html **http://www1.ietf.org/mail-archive/web/tools-discuss/current/msg00301.html Does the draft take into account that it is probably much easier for the Secretariat to convert a document from one format to another (especially given appropriate instructions or better yet standard procedure regarding use of existing tools) than it is to compare two documents to confirm that they are not substantially different? Or am I mistaken? Should one of the validation steps be approval (a good score from) an anti-spam system such as SpamAssassin? I guess this can be a feature added later if it turns out it's needed. I'd bet it will be. -- Matthew _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss
- [Tools-discuss] Comments on draft-ietf-tools-draf… Matthew Elvey
- Re: [Tools-discuss] Comments on draft-ietf-tools-… Brian E Carpenter
- Re: [Tools-discuss] Comments on draft-ietf-tools-… Alex Rousskov
- Re: [Tools-discuss] Comments on draft-ietf-tools-… Bill Fenner
- Re: [Tools-discuss] Comments on draft-ietf-tools-… Henrik Levkowetz