Issue 2053:  Full profile issue (avstreams-rtf)
Source:  (, )
Nature:  Revision
Severity:  Critical
Summary: Summary: Probably the most serious problem for the specification is in the
 ‘full profile’. The model erroneously constrains the FlowProducer
 to always perform the transport connect() call while the FlowConsumer
 is the party which always calls transport listen(). Tying the
 connect()/listen() roles to the producer/consumer roles creates a
 problem with firewalls. With a firewall, the connection must always
 be accepted on the firewall machine. This is impossible, however
 if the FlowProducer is behind the firewall since there is no listen()
 operation in the FlowProducer IDL. There is a possible resolution to
 this problem which would be backward compatible for implementations
 which use the old IDL.
 

Resolution: 
Revised Text: 
Actions taken:
October 7, 1998: received issue
Discussion: 

End of Annotations:=====
Return-Path: <www>
Date: Wed, 7 Oct 1998 09:17:43 -0400
From: www
To: juergen@omg.org, web-incoming@omg.org
Subject: WWW Form output

Name: Damian McGrath
Company: IONA Technologies
Email: dmcgrath@iona.com
Notification: No
Specification: Control and  Management of Audio/Video Streams
Section: 2
Formal #: 98-07-12
Version: 1to always perform the transport connect() call while the
FlowConsumer
is the party which always calls transport listen(). Tying the
connect()/listen() roles to the producer/consumer roles creates a
problem with firewalls. With a firewall, the connection must always
be accepted on the firewall machine. This is impossible, however
if the FlowProducer is behind the firewall since there is no listen()
operation in the FlowProducer IDLto always perform the transport
connect() call while the FlowConsumer
is the party which always calls transport listen(). Tying the
connect()/listen() roles to the producer/consumer roles creates a
problem with firewalls. With a firewall, the connection must always
be accepted on the firewall machine. This is impossible, however
if the FlowProducer is behind the firewall since there is no listen()
operation in the FlowProducer IDL. There is a possible resolution to
this problem which would be backward compatible for implementations
which use the old IDL.



submit: Submit Issue Report

. There is a possible resolution to
this problem which would be backward compatible for implementations
which use the old IDL.



submit: Submit Issue Report

.0
Revision_Date: 
Page: 
Nature: Revision
Severity: Critical
full_desc: Probably the most serious problem for the specification is
in the
full profile


Return-Path: <www>
Date: Wed, 7 Oct 1998 09:17:43 -0400
From: www
To: juergen@omg.org, web-incoming@omg.org
Subject: WWW Form output

Name: Damian McGrath
Company: IONA Technologies
Email: dmcgrath@iona.com
Notification: No
Specification: Control and  Management of Audio/Video Streams
Section: 2
Formal #: 98-07-12
Version: 1.0
Revision_Date: 
Page: 
Nature: Revision
Severity: Critical
full_desc: Probably the most serious problem for the specification is
in the
full profil