Issue 2455:  Issue for Firewall RTF - HTTP tunnelling. (firewall-rtf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: The submission makes no mention of HTTP tunnelling. There are many
          firewalls which filter HTTP, FTP and email related traffic. Is the
          omission based on the assumption that such firewalls will comprise
          a CORBA conformant GIOP proxy on a well-known IIOP port? The Bi-
          directional GIOP specification suggests not (section 5-1,
          paragraph 2).
 
          Is tunnelling regarded as an implementation matter? If so there
          will be important issues such as relaxing GIOP/HTTP mapping and
          security which the specification should clarify.
 

Resolution: 
Revised Text: 
Actions taken:
February 17, 1999: received issue
Discussion: 

End of Annotations:=====
From: A.Hashmi@man0506.wins.icl.co.uk
X400-Received: by mta bath.mail.pipex.net in
/PRMD=pipex/ADMD=pipex/C=gb/;
               Relayed; Wed, 17 Feb 1999 09:47:49 +0000
X400-Received: by /PRMD=icl/ADMD=gold 400/C=GB/; converted (ia5-text);
Relayed;
               Wed, 17 Feb 1999 09:50:59 +0000
Date: Wed, 17 Feb 1999 09:50:59 +0000
X400-Originator: A.Hashmi@man0506.wins.icl.co.uk
X400-Recipients: non-disclosure:;
X400-MTS-Identifier: [/PRMD=icl/ADMD=gold 400/C=GB/;man0506
0000032700004457]
Original-Encoded-Information-Types: ia5-text
X400-Content-Type: P2-1984 (2)
Content-Identifier: 4457
Alternate-Recipient: Allowed
To: issues@omg.org
Subject: Issue for Firewall RTF



         Issue for Firewall RTF - HTTP tunnelling.

         The submission makes no mention of HTTP tunnelling. There are
many
         firewalls which filter HTTP, FTP and email related
traffic. Is the
         omission based on the assumption that such firewalls will
comprise
         a CORBA conformant GIOP proxy on a well-known IIOP port? The
Bi-
         directional GIOP specification suggests not (section 5-1,
         paragraph 2).

         Is tunnelling regarded as an implementation matter? If so
there
         will be important issues such as relaxing GIOP/HTTP mapping
and
         security which the specification should clarify.

         Assad Hashmi
---------------------------------------------------
         PeerLogic UK               Tel     : (+44) 161 223 1301 Ext
2760  
         Wenlock Way                Fax     : (+44) 161 223 0482
    
         West Gorton                Email   : a.hashmi@peerlogic.com
    
         Manchester M12 5DR         Web site: www.peerlogic.com
    
         ----------------------------------------------------------------

Date: Mon, 29 Nov 1999 17:47:13 +0000
From: Owen Rees <owen_rees@hp.com>
To: mchapman@iona.com, firewall-rtf@omg.org
Subject: RE: Round 1
Message-ID: <3299795410.943897633@ews-proj-2.hpl.hp.com>
In-Reply-To: <001701bf3a6e$650b0da0$4d01020a@leo.dublin.iona.ie>
Originator-Info: login-id=ore; server=ticb.hpl.hp.com
X-Mailer: Mulberry (Win32) [1.4.3, s/n P005-300802-001]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Type: text/plain; charset=us-ascii
X-UIDL: b~X!!Z8fd96@"!!78Ud9

--On 29 November 1999, 13:34 +0000 Martin Chapman <mchapman@iona.com>
wrote:

> Issue 2455: Issue for Firewall RTF - HTTP tunnelling. (firewall-rtf)
> 
> Click here for this issue's archive. 
> Nature: Uncategorized Issue 
> Severity: 
> Summary: The submission makes no mention of HTTP tunnelling. 
> Resolution: HTTP tunelling was explictly excluded in the RFP and
> hance is
> not covered. The issue is out of scope.
> Revised Text: 
> Actions taken: Closed without action.
> February 17, 1999: received issue 
> 

Agreed.

Regards,
Owen Rees <owen_rees@hp.com>
Hewlett Packard Laboratories, Bristol, UK
tel: +44 117 312 9439 fax: +44 117 312 9285