Issue 2056:  Description of connect() and request_connection(), stop(), start(), and de (avstreams-rtf)
Source:  (, )
Nature:  Clarification
Severity:  Minor
Summary: Summary: In the description of the connect() and request_connection(), stop(),
 start() and destroy(), for point-to-point streams there is a bias
 towards always viewing the StreamEndPoint_A as the ‘initiator’ and
 StreamEndPoint_B as the ‘responder’. In fact the B party can equally
 be used as an initiator and an A party as the responder. This point
 needs to be emphasised by the text.
 
 

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

End of Annotations:=====
Return-Path: <www>
Date: Wed, 7 Oct 1998 09:22:19 -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: 1be used as an initiator and an A party as the
responder. This point
needs to be emphasised by the text.




submit: Submit Issue Report

.0
Revision_Date: 
Page: 
Nature: Clarification
Severity: Minor
full_desc: In the description of the connect() and
request_connection(), stop(),
start()StreamEndPoint_B as the responder and destroy(), for point-to-point streams there is a bias
towards always viewing the StreamEndPoint_A as the initiato