IETF Logo Mail Archive

[Tools-team] Re: Language review of draft-ietf-tools-draft-submission-08; Section 8.4, WG ID

Henrik Levkowetz <henrik@levkowetz.com> Mon, 18 April 2005 23:17 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNfUE-00011a-S3; Mon, 18 Apr 2005 19:17:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNf95-0005Np-4P for tools-team@megatron.ietf.org; Mon, 18 Apr 2005 18:55:11 -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 SAA21213 for <tools-team@ietf.org>; Mon, 18 Apr 2005 18:55:07 -0400 (EDT)
Received: from pne-smtpout1-sn2.hy.skanova.net ([81.228.8.83]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNfJt-0008DF-Mp for tools-team@ietf.org; Mon, 18 Apr 2005 19:06:26 -0400
Received: from shiraz.levkowetz.com (213.64.173.70) by pne-smtpout1-sn2.hy.skanova.net (7.1.026.7) id 41E3216700D5F502; Tue, 19 Apr 2005 00:54:46 +0200
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.50) id 1DNf8d-0002EF-Em; Tue, 19 Apr 2005 00:54:44 +0200
Message-ID: <42643AB2.2040708@levkowetz.com>
Date: Tue, 19 Apr 2005 00:54:42 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alex Rousskov <rousskov@measurement-factory.com>
References: <4264102D.4030306@levkowetz.com> <opspf9ejowiz3etf0c9082f7@pail.measurement-factory.com>
In-Reply-To: <opspf9ejowiz3etf0c9082f7@pail.measurement-factory.com>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/mixed; boundary="------------050703050808030903070802"
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e4bc10b12db1e5294e2417a6f69c34ce
X-Mailman-Approved-At: Mon, 18 Apr 2005 19:17:00 -0400
Cc: IETF TOOLS <tools-team@ietf.org>
Subject: [Tools-team] Re: Language review of draft-ietf-tools-draft-submission-08; Section 8.4, WG ID
X-BeenThere: tools-team@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "The purpose of the TOOLS team is to provide IETF feedback and guidance during the development of software tools to support various parts of IETF activities." <tools-team.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tools-team>, <mailto:tools-team-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tools-team>
List-Post: <mailto:tools-team@ietf.org>
List-Help: <mailto:tools-team-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tools-team>, <mailto:tools-team-request@ietf.org?subject=subscribe>
Sender: tools-team-bounces@ietf.org
Errors-To: tools-team-bounces@ietf.org

Hi Alex,

On 2005-04-19 12:43 am Alex Rousskov said the following:
[...]
> Yes, the second example and the "Enhancement Stage" comment are both
> stale. They do not make sense with the current WGN draft definition.
> Let's remove them:
> 
>     WG ID: Working Group identifier.  WG ID value is empty for drafts
>        that are not WG-named drafts.  For example, "sieve" in
>        "draft-ietf-sieve-vacation-07" is a WG ID.
> 
> You can add a comment saying that the extraction is purely ID-syntax based
> and does not use a list of known IETF working groups, teams, and similar
> structures.

Ok, I used your text.  I didn't add the last comment you suggested, as
I'm afraid that it will be necessary to use a list of working groups, for
the few cases of WG names which have an embedded dash ( '-' ) ...

Enclosed are new xml and text files, and the diff at 
  http://ietf.levkowetz.com/drafts/tools/draft-submission/
has also been updated.

	Henrik





_______________________________________________
Tools-team mailing list
Tools-team@ietf.org
https://www1.ietf.org/mailman/listinfo/tools-team

v2.23.0 | Report a Bug | By Email