|
Posted by Michelot on April 1, 2006, 9:17 am
If you were Registered and logged in, you could reply and use other advanced thread options
Bonjour Albert,
Albert Manfredi a =E9crit :
> http://www.metroethernetforum.org/PDFs/WhitePapers/Introduction-to-CESoE.=
pdf
> states requirements but not how they're going to be met.
There are other documents more practical.
The Y.1413 (03/2004) recommendation from ITU-T explains how to transmit
TDM signals through MPLS networks not done for that.
RFC3985 dicuss how to emulate TDM services over packet switched
networks.
> It seems to me
> that if the Ethernet underlying service is much faster than the TDM
Even with rapid spanning tree, SDH with GFP will remain always faster
than Ethernet. The TDM signals are not only PDH or n x 16 kbit/s, but
also SDH and OTN.
> In the extreme, you could use GPS at the
> source and at the destination, to regenerate clock. That would be a true
> isochronous system (same clock through the net).
You're right, it is one of the four solutions explained in figure
10-2/Y.1413. You can have a same reference clock (e.g. GPS) at the
interworking function between the asynchronous network and TDM
synchronous network. And, by this way, to have a hierarchically
distributed and precise timing between the both TDM domains separated
by an asynchronous network.
> If the Ethernet is fast
> enough compared to what you're sending over it
Ok
> ...the slack could be used
> just like those stuffed bytes (whatever they're called) in SONET/SDH.
You want to define another SDH. And this case could be 10Gbase-W, with
SDH framing.
Best regards,
Michelot
|