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

"Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com> Mon, 25 October 2004 07:18 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 DAA26083 for <forces-protocol-web-archive@ietf.org>; Mon, 25 Oct 2004 03:18:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLzLM-0007cI-Du for forces-protocol-web-archive@ietf.org; Mon, 25 Oct 2004 03:32:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLz6s-0006xF-FR; Mon, 25 Oct 2004 03:17:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLz3K-0006go-GB for forces-protocol@megatron.ietf.org; Mon, 25 Oct 2004 03:14:02 -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 DAA25720 for <forces-protocol@ietf.org>; Mon, 25 Oct 2004 03:14:00 -0400 (EDT)
Received: from fmr06.intel.com ([134.134.136.7] helo=caduceus.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLzGj-0007W2-69 for forces-protocol@ietf.org; Mon, 25 Oct 2004 03:27:53 -0400
Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7]) by caduceus.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-outer.mc,v 1.15 2004/01/30 18:16:28 root Exp $) with ESMTP id i9P7D9r8001640; Mon, 25 Oct 2004 07:13:09 GMT
Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by talaria.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-inner.mc,v 1.11 2004/07/29 22:51:53 root Exp $) with SMTP id i9P76wJU020747; Mon, 25 Oct 2004 07:06:58 GMT
Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs041.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004102500132906339 ; Mon, 25 Oct 2004 00:13:29 -0700
Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 25 Oct 2004 00:13:30 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Forces-protocol] RE: 01-8
Date: Mon, 25 Oct 2004 00:13:19 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E02579227@orsmsx408>
Thread-Topic: [Forces-protocol] RE: 01-8
Thread-Index: AcS6X6G0ZllXic/2THWzkoeFafBnIgAASC7Q
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: <avri@psg.com>, "Wang,Weiming" <wmwang@mail.hzic.edu.cn>
X-OriginalArrivalTime: 25 Oct 2004 07:13:30.0235 (UTC) FILETIME=[215A64B0:01C4BA62]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
Cc: Jamal Hadi Salim <hadi@znyx.com>, ram.gopal@nokia.com, Robert Haas <rha@zurich.ibm.com>, Ligang Dong <donglg@mail.hzic.edu.cn>, forces-protocol@ietf.org
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.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable

Avri,

Just to clarify my position one final time, I believe you are the editor
of this draft and I did not intent to start any fight again. I was
thinking of the Requirements RFC when I asked you to add our addresses.
If it is easy enough, we should just do this in the final generated text
file...the header should list your name as editor and the small text
paragraph with our names (authors) as it was before (01-7) and we should
have all our addresses at the end. That's all.

IMHO, this will have no issues with the id or rfc editor,

Hormuzd

-----Original Message-----
From: avri@psg.com [mailto:avri@psg.com] 
Sent: Sunday, October 24, 2004 11:55 PM
To: Wang,Weiming
Cc: Ligang Dong; forces-protocol@ietf.org; Robert Haas; Jamal Hadi
Salim; Khosravi, Hormuzd M; ram.gopal@nokia.com
Subject: Re: [Forces-protocol] RE: 01-8


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