AVSTR — Full profile issue

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.