Re: Hybrid TMLs

This is one of the reasons why there needs to be a mandatory to implement TML.
I am inclined to observe that
Given the existence of at least one common TML, it is permitted for 
the CE to simply use a TML that is common across all FEs.
A CE which has support for multiple TMLs, and which can manage the 
selection and management issues of using such (including, if used, 
multicast) is free to choose to use multiple TMLs to speak to 
different FEs in the NE.

I.e. a single TML works, but we have no reason to prohibit multiple 
TMLs, if someone builds a CE that can do it.

Yours,
Joel Halpern

At 11:23 AM 10/3/2006, Wang,Weiming wrote:
>Hi,
>
>When I'm considering the TML service primitive, I come upon a 
>question on the TML instances.
>
>Considering a case with one CE and multiple FEs,  it is possible FEs 
>may use different TML media for ForCES protocol transportation. This 
>actually implies the CE have to support more than one TML instances, 
>or the CE TML must be an all in one TML, with different TML media 
>supported by one TML layer.
>
>There are several questions here:
>1. Shall our charter support different TML media in one ForCES NE?
>2. If yes, then what scheme shall we adopt, multiple TML instances 
>or allowing a hybrid TML? Or, do we have other alternatives? I just 
>can see questions for either of the schemes.
>
>Thanks a lot for any thoughts.
>
>Weiming