[Forces-protocol] Re: draft update....

avri@acm.org Sat, 23 October 2004 02:07 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23948 for <forces-protocol-web-archive@ietf.org>; Fri, 22 Oct 2004 22:07:44 -0400 (EDT)
Received: from megatron.ietf.org ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLBWm-0003Aa-6R for forces-protocol-web-archive@ietf.org; Fri, 22 Oct 2004 22:21:08 -0400
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLBEe-00015q-Cp; Fri, 22 Oct 2004 22:02:24 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLBBM-0007xp-RD for forces-protocol@megatron.ietf.org; Fri, 22 Oct 2004 21:59:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22080 for <forces-protocol@ietf.org>; Fri, 22 Oct 2004 21:59:00 -0400 (EDT)
From: avri@acm.org
Received: from tla.crepundia.net ([] helo=report.tla-group.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLBOI-00031o-2A for forces-protocol@ietf.org; Fri, 22 Oct 2004 22:12:23 -0400
Received: from [] (report.tla-group.com []) by report.tla-group.com (8.12.4/8.12.4) with ESMTP id i9N1Ybep028222; Sat, 23 Oct 2004 03:34:38 +0200
In-Reply-To: <468F3FDA28AA87429AD807992E22D07E0257920E@orsmsx408>
References: <468F3FDA28AA87429AD807992E22D07E0257920E@orsmsx408>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1810BAF0-2497-11D9-9DB1-000393CC2112@acm.org>
Content-Transfer-Encoding: 7bit
Date: Fri, 22 Oct 2004 21:58:54 -0400
To: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
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>
Subject: [Forces-protocol] Re: draft update....
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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit


ok,  i just integrated Weiming's xml in.  the problem was it had a 
bunch of syntactic problems.  i think xml2rfc is a lot stricter then 


i will integrate your further changes in later - in a few hours.

please - everyone - let me know which changes belong in.  please flag 
the messages with changes that are supposed to go in.  the constant 
messages with 2 copies each is blowing my mind - or at least my 
concentration.  i need some definite clues.


On 22 okt 2004, at 21.38, Khosravi, Hormuzd M wrote:

> <section-6-update.txt>

Forces-protocol mailing list