Re: Multiple Streams and mutiplex terminations

Javi Muñoz <[email protected]> Fri, 18 Nov 2011 11:28:46 +0100
Newsgroups gmane.ietf.megaco
Message-ID <[email protected]>
Heloo Christian,

I agree, I'll use that name.

Thank you very much for everything.

Regards,

Javi


El 16/11/2011 1:57, Christian Groves escribió:
> Hello Javi,
>
> I was suggesting some more like: EphISDNTerm/BA17/D/SAPI16/TEI23 for 
> the ephemeral terminations. That way if you want to clear all 
> ephemeral termination you can simply issue: Subtract(EphISDNTerm/*). 
> Otherwise you'll end up with a very convoluted way to do this as you'd 
> have to do multiple groups.
>
> Regards, Christian
>
> On 16/11/2011 10:52 AM, Javi wrote:
>> Hello Christian,
>>
>> You're right.
>>
>> I think it's better the next names:
>>
>> * Physical termination:     ISDNTerm/BA17/D
>>
>> * Ephemeral terminations: ISDNTerm/BA17/Eph/D/SAPI16/TEI23
>>
>>
>> Do you see any problem now?
>>
>> Regards,
>>
>> Javi
>>
>>
>> El 15/11/2011 23:16, Christian Groves escribió:
>>> Hello Javi,
>>>
>>> H.248 allows wildcarding at different levels of a TerminationID. So 
>>> you could use a subtract like below. However its not unambigious, 
>>> would ../D/* still match ISDNTerm/*/D? As I've mentioned previously 
>>> I think its good practise to separate ephemeral and physical 
>>> terminations at the highest level in the heirarchy. 3GPP do this in 
>>> their naming scheme, ie. see TS 29.232 etc.
>>>
>>> Regards, Christian
>>>
>>> On 15/11/2011 9:14 PM, Javi Muñoz wrote:
>>>> Hello Christian,
>>>>>
>>>>> I think you may need a different top level for the Physical and 
>>>>> Ephemeral terminations to avoid any unwanted protocol problems..
>>>>> i.e. What would happen if you do a Subtract(ISDN/Term/*)? The MG 
>>>>> would try to subtract Termination in the NULL context which is not 
>>>>> allowed.
>>>>
>>>> May we use  Subtract(ISDNTerm/*/D/*)  ?
>>>>
>>>> Regards,
>>>>
>>>> Javi
>>>>
>>>>>
>>>>> Regards, Christian
>>>>>
>>>>> On 14/11/2011 8:57 PM, Javi Muñoz wrote:
>>>>>> Hello Christian,
>>>>>>>>>> ISDNTerm/BA17/D [null context]
>>>>>>>>>>
>>>>>>>>>> ISDNTerm/BA17/D/SAPI16-TEI1 --- * --- HDLCPW1/BA17/D/SAPI16-TEI1
>>>>>>>>>>
>>>>>>>>>> ISDNTerm/BA17/D/SAPI16-TEI6 --- * --- HDLCPW2/BA17/D/SAPI16-TEI6
>>>>>>> [CNG] I think there is only ever one physical termination. There 
>>>>>>> can be empheral terminations to describe the connection 
>>>>>>> topology. Something like the above would be possible 
>>>>>>
>>>>>> I agree.
>>>>>>
>>>>>>> although you would need to work on your naming conventions to 
>>>>>>> ensure they are valid.
>>>>>>
>>>>>> I think this naming convention is valid:
>>>>>>
>>>>>> * Physical termination:     ISDNTerm/BA17/D
>>>>>>
>>>>>> * Ephemeral terminations: ISDNTerm/BA17/D/SAPI16/TEI23
>>>>>>
>>>>>>
>>>>>> Do you think it has any problem?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Javi
>>>>>> _______________________________________________
>>>>>> Megaco mailing list
>>>>>> [email protected]
>>>>>> https://www.ietf.org/mailman/listinfo/megaco
>>>>>>
>>>>> _______________________________________________
>>>>> Megaco mailing list
>>>>> [email protected]
>>>>> https://www.ietf.org/mailman/listinfo/megaco
>>>>>
>>>>
>>>>
>>>
>>
>>
>