Good point, Chris. I added a clarifying sentence to the draft explaining that diverging state information is to be dealt with specifially to a particular domain, e.g., by replication or dispute handling. Heiko ----- Heiko Ludwig, Dr. rer. pol. IBM TJ Watson Research Center, PO Box 704, Yorktown, NY, 10598 hludwig@us.ibm.com, tel. +1 914 784 7160, mob. +1 646 675 8469 http://www.research.ibm.com/people/h/hludwig/ Christopher Dabrowski <christopher.dabrowski@nist.gov> Sent by: owner-graap-wg@ggf.org 08/03/2005 12:14 PM To graap-wg@gridforum.org cc Subject [graap-wg] Comment on section 9, first paragraph, All, An additional comment on Section 9, first paragraph #2 (WORD version of document dated July 13) states: "2 Call Back. As with the simple client-server scenario, the initiator invokes the AgreementFactory to create a responder-side Agreement. As additional input to the createAgreement call, the initiator passes the address of an initiator-side Agreement representing the offer he is making. As a result, both parties have an Agreement representing the same accepted agreement relationship between them, to allow symmetric messaging for monitoring and management." Is it clear what is meant by "symmetric messaging for monitoring and management"? (Also appears in #4) Points of clarification -- does this imply that there are two copies of the agreement, one for the client and one for the server? If so, must messages be exchanged to ensure these copies are consistent? I raised this earlier and it may have been addressed. Sincerely, Chris Dabrowski Christopher Dabrowski National Institute of Standards and Technology 100 Bureau Drive, Stop 8970 Gaithersburg, MD 20899-8970 Phone: +1 301 975-3249 FAX: +1 301 948-6213 cdabrowski@nist.gov