Subject: RE: draft-ietf-opes-protocol-reqs-01

From: <[email-masked]>
Date: Fri, 21 Jun 2002 09:35:00 -0400

Hi Andre,

> IMO each callout request and response (which may each consist of 
> multiple OCP messages) should only contain a single 
> application message, 
> but I am not sure that this is what you meant. What are your concerns 
> for sending multiple application messages within the same OCP message?

My only concern with sending multiple application messages in the same OCP message is that, by holding up the first application message at the OPES intermediary end waiting to fill up the OCP message before sending the OCP message to the callout server, arent we unnecessarily increasing the latency for the application message. By sending only 1 application message in each OCP message, the latency is reduced at the cost of a greater overhead.

> Right, "Service Completion" is a good description of an event 
> that could 
> trigger a "premature termination" of a callout transaction. I'll 
> rephrase the corresponding section in the draft to reflect 
> this and give 
> a better description of the termination process.

That sounds great!

Thanks,
-Srini