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

"Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com> Wed, 27 October 2004 23:17 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 TAA26672 for <forces-protocol-web-archive@ietf.org>; Wed, 27 Oct 2004 19:17:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMxH8-0001vF-30 for forces-protocol-web-archive@ietf.org; Wed, 27 Oct 2004 19:32:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMwxH-0003Xa-6Y; Wed, 27 Oct 2004 19:11:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMwwu-0003QK-8U for forces-protocol@megatron.ietf.org; Wed, 27 Oct 2004 19:11:24 -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 TAA26299 for <forces-protocol@ietf.org>; Wed, 27 Oct 2004 19:11:20 -0400 (EDT)
Received: from fmr12.intel.com ([134.134.136.15] helo=orsfmr001.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMxAq-0001no-Sf for forces-protocol@ietf.org; Wed, 27 Oct 2004 19:25:49 -0400
Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7]) by orsfmr001.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 i9RNBUM2025677; Wed, 27 Oct 2004 23:11:30 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 i9RN42bn001971; Wed, 27 Oct 2004 23:04:05 GMT
Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56]) by orsmsxvs041.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004102716104519542 ; Wed, 27 Oct 2004 16:10:45 -0700
Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 27 Oct 2004 16:10:45 -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: Wed, 27 Oct 2004 16:10:44 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E030E6FA5@orsmsx408>
Thread-Topic: [Forces-protocol] RE: 01-8
Thread-Index: AcS68JQwwSDTGN83Sx+L38GyHSBRGABh6rDA
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: <avri@psg.com>
X-OriginalArrivalTime: 27 Oct 2004 23:10:45.0946 (UTC) FILETIME=[3087E1A0:01C4BC7A]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: quoted-printable
Cc: ram.gopal@nokia.com, Ligang Dong <donglg@mail.hzic.edu.cn>, forces-protocol@ietf.org, Jamal Hadi Salim <hadi@znyx.com>, "Wang, Weiming" <wmwang@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.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: quoted-printable

Avri,

Sorry to bother you via email, but since I wont be coming for the IETF, 
I thought this might be the best way. My reply below..

-----Original Message-----
From: avri@psg.com [mailto:avri@psg.com] 

> This is fine for now but I would prefer the Authors Addresses being a
> separate section rather than part of the Appendix cause that is how I
> have seen it in most RFCs including All the ForCES RFCs.

the problem with what is currently possible is that it came before the 
references when the regular authors section came after.

[HK] This can be easily fixed in the final text, I think

i would probably have to hack at xml2rfc to make it work.  but i still 
think it is against the rules proper - even if you got away with it on 
the requirements.

[HK] I don't think we got away with anything in the Requirements, I wish
we had :-)
If you look at any of the ForCES RFCs (below) that we have so far, the
Authors Addresses are listed as a separate section, not as part of
Appendix. That's my only requirement, I would like to see this as some
section, not in the Appendix. And I agree that this section should be
after the references.


http://www.ietf.org/rfc/rfc3746.txt, http://www.ietf.org/rfc/rfc3549.txt


Thanks
Hormuzd




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