CORBA34 — Interplay of Contexts allowed in NegotiateSession messages too ill-defined

PROBLEM:
The BiDir GIOP document allows all of the contexts that can be found in a GIOP query or response message to be also allowed in a NegotiateSession message. However, the interplay among these contexts is undefined. An example is the use in NegotiateSession messages of both CodeSet negotiation and BiDir connection setup. What can be used in what order is not defined.

RECOMMENDATION:
Only bi-directional GIOP and firewall contexts may be used in a NegotiateSession message in this version of GIOP. The contexts are the following:

· BI_DIR_GIOP_OFFER
· BI_DIR_GIOP_CHALLENGE
· BI_DIR_GIOP_RESPONSE
· BI_DIR_GIOP_ACCEPT
· FIREWALL_PATH
· FIREWALL_PATH_RESP

Further contexts may be added to new versions of the BiDir GIOP spec as their interplay with the existing set and the order of their use is carefully analyzed and documented. This effectively limits the scope of the problem to the bidir protocol and use by the firewall. The order and stage of processing the above contexts is discussed in another Firewall issue.

Deferred

This proposal was generated automatically by request of the Task Force Chair Adam Mitz.