|
Hi All, I have some doubts on Extended NxDS0 CAS mode setup. I
have listed them below. a. Does the
packet latency specified for Basic NxDS0 holds good for Extended NxDS0 mode
with CAS. Because, when we say CAS, are we not trunk-specific. b. When ever we
need CAS, the TDM interface should be in multi frame mode. It can be 16 frames
or 24 frames based on E1 or T1 interface. But if we configure for 1 ms packet
latency then we are required to send data for each 8 frames as payload. But CAS
retrieval aligns to SF number of frames (16 or 24). Does this mean, do we need to
send previously stored CAS state. c. My second
doubt is on two pseudowires. One for CAS and one for data. How does the user
see this. For example, Does single configuration to enable two pseudowires is
required or separate configuration for two pseudowires is recommended. In the
later case, though they are configured in sequence for CAS pseudowire and data
pseudowire, do we need to enable them at same time. Can signaling PW become
active first and data PW after some time. Regards, Mahesh
|
_______________________________________________ pwe3 mailing list pwe3 at ietf.org https://www.ietf.org/mailman/listinfo/pwe3