Issue 7168: GIOP version 2.0 issue (firewall-traversal-ftf) Source: (Ms. Rebecca Bergersen, becky(at)bergersen.org) Nature: Uncategorized Issue Severity: Summary: The following paragraph raises an interesting issue. If we follow this to the letter - since it says that the new version of GIOP is not backward compatible with the earlier versions of GIOP, it implicitly appears to make this new GIOP version a new "major" version of GIOP. Clearly we need to figure out a way to avoid doing this, since creating GIOP version 2.0 in this way raises all sorts of other issues. From the second paragraph on page 1-30 of the Firewall Final Adopted Spec (ptc/04-04-01): This document supercedes the previously adopted CORBA firewall specification. In addition, the changes to bi-directional GIOP, specified in Chapter 15, supercede the adopted specification for bi-directional GIOP. These specifications are not backwards compatible with the previous specifications and they are intended to make it possible to create a functional protocol for the interoperation of ORBs and firewalls. Resolution: Revised Text: Actions taken: March 19, 2004: received issue Discussion: End of Annotations:===== ubject: Firewall spec issue Date: Fri, 19 Mar 2004 17:35:27 -0500 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Firewall spec issue Thread-Index: AcQOAsyk6g7gvG6uSqe4SG5ajmjQ5A== From: "Bergersen, Rebecca" To: The following paragraph raises an interesting issue. If we follow this to the letter - since it says that the new version of GIOP is not backward compatible with the earlier versions of GIOP, it implicitly appears to make this new GIOP version a new "major" version of GIOP. Clearly we need to figure out a way to avoid doing this, since creating GIOP version 2.0 in this way raises all sorts of other issues. From the page 1-30 of the Firewall Final Adopted Spec (ptc/04-04-01): This document supercedes the previously adopted CORBA firewall specification. In addition, the changes to bi-directional GIOP, specified in Chapter 15, supercede the adopted specification for bi-directional GIOP. These specifications are not backwards compatible with the previous specifications and they are intended to make it possible Subject: FW: Firewall spec issue (small revision) Date: Fri, 19 Mar 2004 17:40:09 -0500 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Firewall spec issue Thread-Index: AcQOAsyk6g7gvG6uSqe4SG5ajmjQ5AAAD1sg From: "Bergersen, Rebecca" To: Cc: "Bergersen, Rebecca" Sorry, Juergen - I hit send too early through some combination of control/alt keys. I meant the issue to be stated with the additional text in blue, below. --Rebecca -----Original Message----- From: Bergersen, Rebecca Sent: Friday, March 19, 2004 5:35 PM To: 'juergen@omg.org' Subject: Firewall spec issue The following paragraph raises an interesting issue. If we follow this to the letter - since it says that the new version of GIOP is not backward compatible with the earlier versions of GIOP, it implicitly appears to make this new GIOP version a new "major" version of GIOP. Clearly we need to figure out a way to avoid doing this, since creating GIOP version 2.0 in this way raises all sorts of other issues. From the second paragraph on page 1-30 of the Firewall Final Adopted Spec (ptc/04-04-01): This document supercedes the previously adopted CORBA firewall specification. In addition, the changes to bi-directional GIOP, specified in Chapter 15, supercede the adopted specification for bi-directional GIOP. These specifications are not backwards compatible with the previous specifications and they are intended to make it possible to create a functional protocol for the interoperation of ORBs and firewalls. Date: Mon, 29 Mar 2004 18:12:56 -0500 From: Jishnu Mukerji Organization: Hewlett-Packard SGBU/MSO User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en To: firewall-traversal-ftf@omg.org Subject: Proposed resolution for issue 7168 Here is the proposed resolution for issue 7168. Once I have the resolution for 7167 taken care of I will post a modified version of both Chapters 15 and the CSIv2 Chapter as supporting material for the vote on these issues. Expect all this to happen by Wednesday. Jishnu. ____________________________________________________________________________ _ Issue 7168: GIOP version 2.0 issue (firewall-traversal-ftf) /Click //here for this issue's archive./ *Source:* IONA (Ms. Rebecca Bergersen, rebecca.bergersen@iona.com ) *Nature:* Uncategorized Issue *Severity:* *Summary:* The following paragraph raises an interesting issue. If we follow this to the letter - since it says that the new version of GIOP is not backward compatible with the earlier versions of GIOP, it implicitly appears to make this new GIOP version a new "major" version of GIOP. Clearly we need to figure out a way to avoid doing this, since creating GIOP version 2.0 in this way raises all sorts of other issues. From the second paragraph on page 1-30 of the Firewall Final Adopted Spec (ptc/04-04-01): This document supersedes the previously adopted CORBA firewall specification. In addition, the changes to bi-directional GIOP, specified in Chapter 15, supersede the adopted specification for bi-directional GIOP. These specifications are not backwards compatible with the previous specifications and they are intended to make it possible to create a functional protocol for the interoperation of ORBs and firewalls. *Resolution:* Restore the original sections 15.8 and 15.9 and constrain them to apply to GIOP versions 1.2 and 1.3 only. The new sections apply to all post 1.3 versions of GIOP. Make the necessary editorial adjustments to get these sections to fit together. *Revised Text:* The following changes to be made to the published adopted Firewall Traversal specification version of CORBA Core Chapter 15: 1. Restore the original section 15.8 from formal CORBA Core 3.0 Chapter 15 as Section 15.8. 1.a. Change the title of the section to "Bi-directional GIOP in GIOP 1.2 and 1.3" 1.b. Insert the following paragraph as the first paragraph of this section: "This section and its subsections contains the specification for Bi-Directional GIOP, IIOP and Policy as it applies to GIOP and IIOP versions 1.2 and 1.3" 2. Restore the original section 15.9 from formal CORBA Core 3.0 Chapter 15 as Section Section 15.8.2. Note that this causes the Section 15.8 in the published adopted specification to become Section 15.9 "Bi-directional GIOP". 3. Remove the first four paragraphs of Section 15.9 "Bi-directional GIOP". These are simply a repeat of what appears as the 2nd through 5th para of section 15.8. 4. Insert the following paragraph as the first para of Section 15.9 "Bi-directional GIOP": "This section contains the specification of Bi-directional GIOP, IIOP and associated Policies for GIOP and IIOP minor version 1.4 and later." 5. In the first sentence of the last para of section 15.9 replace the word "outlines" by the word "specifies". 6. Insert the following as the first two sentences of the last paragraph of section 15.9: "Based on the experience gained with GIOP 1.2 and 1.3 certain weaknesses were discovered in the specification of Bi-Directional GIOP. The specification of GIOP in this section addresses those shortcoming." 7. Change Section 15.10 "Bi-directional GIOP policy" to Section 15.9.5 "Bi-directional GIOP policy". 8. Remove all sentences except the last sentence of the first paragraph of this section 15.9.5 "Bi-directional GIOP policy". They are just a repeat of the sentences that appear in section 15.8.2. 10. In sections 15.10.1 and 15.10.3 in the IDL replace all occurrences of the line: #if MAX_GIOP_MINOR_VERSION > 5 by #if MAX_GIOP_MINOR_VERSION > 3 *Actions taken:* March 19, 2004: received issue Date: Tue, 30 Mar 2004 18:09:29 -0500 From: Jishnu Mukerji Organization: Hewlett-Packard SGBU/MSO User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en To: firewall-traversal-ftf@omg.org Subject: Re: Proposed resolution for issue 7168 Updated resolution. I missed an item stating that the offending paragraph in section 1.8 (the last para). ___________________________________________________________________________ Issue 7168: GIOP version 2.0 issue (firewall-traversal-ftf) /Click //here for this issue's archive./ *Source:* IONA (Ms. Rebecca Bergersen, rebecca.bergersen@iona.com ) *Nature:* Uncategorized Issue *Severity:* *Summary:* The following paragraph raises an interesting issue. If we follow this to the letter - since it says that the new version of GIOP is not backward compatible with the earlier versions of GIOP, it implicitly appears to make this new GIOP version a new "major" version of GIOP. Clearly we need to figure out a way to avoid doing this, since creating GIOP version 2.0 in this way raises all sorts of other issues. From the second paragraph on page 1-30 of the Firewall Final Adopted Spec (ptc/04-04-01): This document supersedes the previously adopted CORBA firewall specification. In addition, the changes to bi-directional GIOP, specified in Chapter 15, supersede the adopted specification for bi-directional GIOP. These specifications are not backwards compatible with the previous specifications and they are intended to make it possible to create a functional protocol for the interoperation of ORBs and firewalls. *Resolution:* Restore the original sections 15.8 and 15.9 and constrain them to apply to GIOP versions 1.2 and 1.3 only. The new sections apply to all post 1.3 versions of GIOP. Make the necessary editorial adjustments to get these sections to fit together. Make the new version of BiDir GIOP be the optionally required one for GIOP version 1.4 and later while the old version would continue to be the one that applies to GIOP 1.2 and 1.3. *Revised Text:* The following changes to be made to the published adopted Firewall Traversal specification version of CORBA Core Chapter 15: 1. Restore the original section 15.8 from formal CORBA Core 3.0 Chapter 15 as Section 15.8. 1.a. Change the title of the section to "Bi-directional GIOP in GIOP 1.2 and 1.3" 1.b. Insert the following paragraph as the first paragraph of this section: "This section and its subsections contains the specification for Bi-Directional GIOP, IIOP and Policy as it applies to GIOP and IIOP versions 1.2 and 1.3" 2. Restore the original section 15.9 from formal CORBA Core 3.0 Chapter 15 as Section Section 15.8.2. Note that this causes the Section 15.8 in the published adopted specification to become Section 15.9 "Bi-directional GIOP". 3. Remove the first four paragraphs of Section 15.9 "Bi-directional GIOP". These are simply a repeat of what appears as the 2nd through 5th para of section 15.8. 4. Insert the following paragraph as the first para of Section 15.9 "Bi-directional GIOP": "This section contains the specification of Bi-directional GIOP, IIOP and associated Policies for GIOP and IIOP minor version 1.4 and later." 5. In the first sentence of the last para of section 15.9 replace the word "outlines" by the word "specifies". 6. Insert the following as the first two sentences of the last paragraph of section 15.9: "Based on the experience gained with GIOP 1.2 and 1.3 certain weaknesses were discovered in the specification of Bi-Directional GIOP. The specification of GIOP in this section addresses those shortcoming." 7. Change Section 15.10 "Bi-directional GIOP policy" to Section 15.9.5 "Bi-directional GIOP policy". 8. Remove all sentences except the last sentence of the first paragraph of this section 15.9.5 "Bi-directional GIOP policy". They are just a repeat of the sentences that appear in section 15.8.2. 10. In sections 15.10.1 and 15.10.3 in the IDL replace all occurrences of the line: #if MAX_GIOP_MINOR_VERSION > 5 by #if MAX_GIOP_MINOR_VERSION > 3 *Actions taken:* March 19, 2004: received issue 11. Remove the last paragraph of section 1.8 of ptc/04-01-01. ___________________________________________________________________________________ Jishnu. -- Jishnu Mukerji Senior Systems Architect 1001 Frontier Road, Suite 300 Technology Office Bridgewater NJ 08807, USA Management Software Organization Tel: +1 908 243 8924 Hewlett-Packard Company Fax: +1 908 243 8850 mailto: jishnu@hp.com