CORBA35 — GIOP version 2.0 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.