Re: [Forces-protocol] RE: 01-8

avri@psg.com Mon, 25 October 2004 06:58 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 CAA24700 for <forces-protocol-web-archive@ietf.org>; Mon, 25 Oct 2004 02:58:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLz1p-0007Ft-R3 for forces-protocol-web-archive@ietf.org; Mon, 25 Oct 2004 03:12:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLylh-0005Ta-EV; Mon, 25 Oct 2004 02:55:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLylR-0005Ql-7k for forces-protocol@megatron.ietf.org; Mon, 25 Oct 2004 02:55:33 -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 CAA24569 for <forces-protocol@ietf.org>; Mon, 25 Oct 2004 02:55:31 -0400 (EDT)
From: avri@psg.com
Received: from tla.crepundia.net ([194.71.127.149] helo=report.tla-group.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLyyo-0007D6-Vs for forces-protocol@ietf.org; Mon, 25 Oct 2004 03:09:24 -0400
Received: from [127.0.0.1] (report.tla-group.com [194.71.127.149]) by report.tla-group.com (8.12.4/8.12.4) with ESMTP id i9P6Upep001011; Mon, 25 Oct 2004 08:30:52 +0200
In-Reply-To: <022701c4ba5e$17fc2830$845c21d2@Necom.hzic.edu.cn>
References: <468F3FDA28AA87429AD807992E22D07E02579220@orsmsx408> <B5625BE5-2650-11D9-9DB1-000393CC2112@psg.com> <022701c4ba5e$17fc2830$845c21d2@Necom.hzic.edu.cn>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DA4A69B8-2652-11D9-9DB1-000393CC2112@psg.com>
Content-Transfer-Encoding: 7bit
Subject: Re: [Forces-protocol] RE: 01-8
Date: Mon, 25 Oct 2004 02:55:27 -0400
To: "Wang,Weiming" <wmwang@mail.hzic.edu.cn>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>, ram.gopal@nokia.com, forces-protocol@ietf.org, Jamal Hadi Salim <hadi@znyx.com>, Ligang Dong <donglg@mail.hzic.edu.cn>, Robert Haas <rha@zurich.ibm.com>
X-BeenThere: forces-protocol@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: forces-protocol <forces-protocol.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/forces-protocol>
List-Post: <mailto:forces-protocol@ietf.org>
List-Help: <mailto:forces-protocol-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=subscribe>
Sender: forces-protocol-bounces@ietf.org
Errors-To: forces-protocol-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

On 25 okt 2004, at 02.44, Wang,Weiming wrote:

> I know xml2rfc does not support direct author address listing. I 
> suggest you may
> just use a normal section to currently add it. Later when you have 
> much time,
> you can add the xml2rfc style address listing. does it help?

it would still be a separate section, e.g. an appendix.  i cannot 
figure out a way to put the names in the normal author's section 
without also putting them in the header.

as i said, i figure the id editor will let it pass, so we can have the 
header fight some other time.

it is still my hope that the WG chairs will pick editors and put an put 
an end to the question.


_______________________________________________
Forces-protocol mailing list
Forces-protocol@ietf.org
https://www1.ietf.org/mailman/listinfo/forces-protocol