Re: Multiple Streams and mutiplex terminations

Hello Javi,

Please see my comments below.

Regards, Christian

..snip..
>
>> [CNG] Below is an example of the use of two properties TEI and SAPI 
>> (I haven't proposed a descriptor could be LocalControl). By assigning 
>> the numbers to different termination it indicates which sub-flows go 
>> where. i.e. the HDLCPW1 termination has flows with TEI=1,3,9 but not 6.
>>
>> ISDNTerm/BA17
>> StreamID=1(TEI=[1,6],SAPI=16)\
>>                               \
>> ISDNTerm/BA18                  \       HDLCPW1
>> StreamID=1(TEI=[3],SAPI=16) ---*----- StreamID=1 (TEI=[1,3,9],SAPI=16)
>>                                /
>> ISDNTerm/BA19                 /
>> StreamID=1(TEI=[9],SAPI=16)  /
>>
>
> [Javi] Ok. But there is tow problems:
>
> a) "ISDNTern/BA17/[TEI 6]" would be transported on HDLCPW2. How would 
> you model the context?. I think the next option is not possible:
>
>
> ISDNTerm/BA17
> StreamID=1(TEI=[1,6],SAPI=16)\
>                               \   ---- HDLCPW1
> ISDNTerm/BA18                  \ / StreamID=1 (TEI=[1,3,9],SAPI=16)
> StreamID=1(TEI=[3],SAPI=16) ----*
>                                / \
> ISDNTerm/BA19                 /   ----HDLCPW2
> StreamID=1(TEI=[9],SAPI=16)  /         StreamID=1 (TEI=[6], SAPI=16)
>
>
[CNG] Why do you think its not possible? I can't see the issue. By using 
the TEI=[6] parameter all you're saying is "only transport frames 
related to TEI=[6] in this stream".

> b) "ISDNTerm/BA17/[TEI 1]" may be transported on HDLCPW1 but 
> ""ISDNTerm/BA18/[TEI 1]" may be transported on HDLCPW2. How would you 
> model this?. You would need to indicate the termination name in the 
> properties:
>
> ISDNTerm/BA17
> StreamID=1(TEI=[1,6],SAPI=16)\
>                               \   ---- HDLCPW1
> ISDNTerm/BA18                  \ / StreamID=1 
> (TEI=[1-ISDNTerm/BA17,9-ISDNTerm/BA19],SAPI=16)
> StreamID=1(TEI=[1],SAPI=16) ----*
>                                / \
> ISDNTerm/BA19                 /   ----HDLCPW2
> StreamID=1(TEI=[9],SAPI=16)  /         StreamID=1 
> (TEI=[6-ISDNTerm/BA17,1-ISDNTerm/BA18],SAPI=16)
>
[CNG] I suspected we'd end up at this case. It sounds like you're trying 
to turn a single Context into an entire router to get around the fact 
that you can't have a single physical termination in multiple contexts. 
Have a look at H.248.64 to see how we handled that for an IP router. How 
many more Terminations do you envisage in a Context?

You could add TerminationID to the TEI parameter, but if you're having 
lots of Termination it may quickly become complicated.
>
>
> [CNG] Yes, so why do you propose a single Termination? Why not add the 
> interfaces via multiple Terminations to the Context?
>
> [Javi] Yes. Indeed, this woud be my solution to the problem: Create an 
> ephemeral termination for each flow, including flows of HDLCPWs:
>
> ISDNTerm/BA17/D/SAPI16,TEI1 --- * --- HDLCPW1/BA17/D/SAPI16,TEI1
>
> ISDNTerm/BA17/D/SAPI16,TEI6 --- * --- HDLCPW2/BA17/D/SAPI16,TEI6
>
> ISDNTerm/BA18/D/SAPI16,TEI1 --- * --- HDLCPW2/BA18/D/SAPI16,TEI1
>
> ISDNTerm/BA19/D/SAPI16,TEI9 --- * --- HDLCPW1/BA19/D/SAPI16,TEI9
>
>
> I think this is possible.
[CNG] A ephemeral Termination for an ISDN termination? These are 
typically physical terminations.

>
>
> Thanks,
>
> Javi
>