Re: [MTP3] Change Over procedure for 2M TDM links

Santhana <[email protected]> Wed, 06 Apr 2011 14:11:03 +0530
Newsgroups gmane.ietf.sigtran
Organization Htipl
Message-ID <[email protected]>
Hi David
	Thanks for your opinion. Pls check inline.

-----Original Message-----
From: David Laight [mailto:[email protected]] 
Sent: Wednesday, April 06, 2011 1:34 PM
To: [email protected]; arif khan
Cc: [email protected]
Subject: RE: [Sigtran] [MTP3] Change Over procedure for 2M TDM links

 
> Hi
> 	I was asking in MTP2 level whether 2M links can be used. Also I
> wanted the details of ChangeOver procedures like , which 
> message COO/XCO
> should be used and what is the FSN parameter size 12bits or 24bits....

I don't see a problem with putting a 12bit sequence number into
a 24bit field (much harder the other way around!).
--> I also think this way. But there is no explicit note about this in the
Spec, both in Q.703 or Q.2210.

The 2M/1.5M links from Q.703 Annex A certainly are used (or have
been used!). We've been asked whether we support them, but only
for 'tick box' filling, none of our customers has actually asked
us to support them (the difficulty is getting the timeslot data
through the tdm cross bar switch and the falcs without
generating a 'shear' midway through the tdm frame.

My suspicions are the the SIGTRAN protocols are being used
for any links that need to carry large traffic loads.
--> What u mean here? SIGTRAN protocols like M3UA, SUA have no restriction
on the DATA size/length by the very Standard, as they run over IP. Even
there can be(there is) a SG of M3UA-MTP3B(SAAL links) also.

	David

+ Santhana