-
Key: CORBA34-23
-
Legacy Issue Number: 6285
-
Status: closed
-
Source: Syracuse University ( Polar Humenn)
-
Summary:
Here is a small proposal for GIOP 1.4 with Firewall and Bidirectional. We
would get rid of all the weird nasty service contexts and make it
simplistic. The FireWall messages are only allowed before any other GIOP
messages. BiDir messages can happen at any time according to their
protocol.What do you think? Asside from some problems I see with BiDir
offer/challenge/response correlation, it is essentially equivalent to the
solution proposed in the adopted spec.module GIOP {
{ Request, Reply, CancelRequest, LocateRequest, LocateReply, CloseConnection, MessageError, Fragment, // GIOP 1.1 addition // GIOP 1.4 additions FirewallPathRequest, // 8 FirewallPathRepsonse, // 9 BiDirOffer, // 10 BiDirChallenge, // 11 BiDirResponse // 12 }
enum MsgType_1_4;
// Firewall Traversal GIOP 1.4
struct FirewallSpec
{ boolean is_intelligent; IOP::TaggedComponentSeq endpoints; };
typedef sequence<FirewallSpec> FirewallPath;struct FirewallPathRequestHeader
{ unsigned long host_index; FirewallPath path; };
// No body follows.enum FirewallPathResponseStatusType
{ NO_EXCEPTION, SYSTEM_EXCEPTION };
struct FirewallPathResponseHeader
{ FirewallPathResponseStatusType status; boolean connection_complete; };
// Marshalled body immediately follows// Bidirectional GIOP 1.4
// To keep this file uncomplicated we can introduce the
// headers and put the marshalled bodies in a separate BiDir module
// Due due some issue about the challege/response protocol for this,
// there may be a need of an offer_id to correlate them.struct BiDirOfferHeader
{ unsigned long offer_id; };
// Marshalled body immediately follows.
struct BiDirChallengeHeader { unsigned long offer_id; };
// Marshalled body immediately follows.struct BiDirResponseHeader
{ unsigned long offer_id; };
// Marshalled body immediately follows.
}; -
Reported: CORBA 3.0.2 — Thu, 2 Oct 2003 04:00 GMT
-
Disposition: Deferred — CORBA 3.4
-
Disposition Summary:
Deferred
This proposal was generated automatically by request of the Task Force Chair Adam Mitz.
-
Updated: Wed, 1 Feb 2023 21:59 GMT
CORBA34 — Change new GIOP Negotiate Session Message to Firewall Specific
- Key: CORBA34-23
- OMG Task Force: CORBA 3.4 RTF