Re: Lift M3UA improvements into SUA
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
Ilie, Ilie Glib wrote: (Thu, 09 Nov 2006 19:36:00) > Hello folks, > > SUA RFC lacks a lot of details, especially if compared with M3UA RFC. > Many statements from M3UA RFC do apply to SUA as well. For instance, > explanations of n+k redundancy, SE and DE modes, and many more. > > Is there any intention to lift those improvements made in M3UAbis into > the SUA spec? I do not consider them improvements. SUA is a different beast and has a number of procedures and mechanism that differ from M3UA. This first set of common procedure changes where shoe-horned into SUA before it went to WGLC and were removed because they caused unique problems for SUA. If you are interested, look (way) back at the discussions leading up to WGLC for SUA. > > As far as understand there is no standardization body except for IETF > that accepted SUA, is there? Yes, ETSI and 3GPP really dropped the ball, but there was not a whole lot of funding at the time and M3UA was crammed out the door first. Since then ITU-T has specified TI-SCCP (transport independent SCCP) which runs directly over SCTP and is the formal standard replacement for SUA outside of IETF. 3GPP uses White Book SCCP over M3UA as well as MAP directly over GTP tunnels (over NS and IP or FR). > > Is that the actual reason that SUA does not evolve to an open protocol > that provide for interoperability? I think that "real" SCCP over M3UA or TI-SCCP (basically "real" SCCP directly over SCTP) are more workable that SUA in that they avoid SCCP issues by reusing time-tested SCCP. It's too bad because SUA goes way farther to address problems with ITU point code exhaustion because of its ability to distribute messages between SG and ASP based on global title and a richer IPSP model. Just my 2 cents. --brian > > Thank you in advance > > -- > Ilie > > _______________________________________________ > Sigtran mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/sigtran -- Brian F. G. Bidulock [email protected] http://www.openss7.org/