Subject: RE: [Megaco] stream

From: "Tom-PT Taylor"<[email-masked]>
Date: Thu, 11 Apr 2002 22:55:20 -0400

Oh, well, should have read this one first :-}

-----Original Message-----
From: Y Hu [mailto:[email-masked]]
Sent: Thursday, April 11, 2002 9:47 PM
To: [email-masked]
Subject: [Megaco] stream

Hi,

Sorry, the previous message was pasted and posted
incompletely. Let me try again:

The spec says there are max 2 terminations in a
point-to-point connection context. In a multiplexing
termination context (such as H223), should there be
another termination for the mux in the context? 

         Context 1
    ------------------------
    | T1 ---- MUX ----- T2 |
    ------------------------

[PTT]
Yes.  But multiplexing is a property of a termination, not a context.
Introducing a multiplex creates asymmetry: the termination(s) feeding into
the multiplex are hidden from the other terminations in the context.  The
"centre" of the context, where the bridging is done, lies between the MUX
and the terminations that do not feed into it (are not listed in the
Multiplex Descriptor).

If the T1 and T2 are connected by a stream #1. When
the T1 is moved out of C1, should the stream #1 be
deleted or should the stream #1 still stay within the
C1?

[PTT]
I assume you mean in the above diagram.  If you mean in general, then a
stream is present in a context until no terminations support that stream.
In the above diagram, if T1 feeds into the multiplex, then the stream it
supports is visible only to the multiplex.  It is a different stream 1 that
runs between the multiplex and the other terminations in the context.

If both the T1 and T2 are moved out of C1, should the
C1 be destroyed automatically or should the C1 be
waiting until the MUX termination is requested to be
deleted by the MGC?

[PTT]
Again assuming that T1 is the termination listed in the Multiplex
Descriptor, it would be an error to move it out before modifying the MUX
termination to remove it from the Multiplex Descriptor.  (We may need to
define a suitable error code.)  Assuming that condition is met, the context
continues to exist until the MUX termination is deleted.  The MUX
termination would be a bit strange, with no supporting terminations to
provide any media, but I think  this is the logical approach.

Thank you.

At 04:21 PM 11/04/2002 -0700, you wrote:
There are two questions:

1. If a MGC issues a move request, should the MGC
issue the stream inactive command first before moving
a termination or a single MOVE request does both?

2. If in a peer connection mode, both terminations are
moved out the context, should the stream still stay
the context until an explicitly delete command or
should the stream automatically deleted is there is no
terminations connected?

Thank you.

__________________________________________________

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco

_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco