Re: Sigtran Digest, Vol 46, Issue 5

Tolga,

In the numerous deployments that we are doing with M3UA, we are seeing that operators are not going away from STPs for the reasons that you specified below and others (security, ease of GT management, ease of migration from current SS7 architecture to SIGTRAN based architecture).

Regards,
Lincoln

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Asveren, Tolga
Sent: Tuesday, February 26, 2008 1:48 PM
To: LI Xinyan; [email protected]
Cc: [email protected]; [email protected]
Subject: Re: [Sigtran] Sigtran Digest, Vol 46, Issue 5

Bryan, Li,

Just summarizing my personal thoughts on this issue:

1) I think using SNMM messages as described, e.g. sending DUPU from ASP to SG, is conceptually against the philosophy of M3UA protocol (It is not an oversight).

2) IMHO, STP type nodes make sense even in IP domain for reasons like security, ease of management etc... I would be interested to hear what operators think about this as they are the ones which actually deploy and use the systems.

3) I am not sure the difficulty arising from configuring sub-PC RKs is significant. Again, would like to hear operator's opinion.

4) It makes sense to me to base something like M3UA SG-SG/M3PA on SSNM (AFAIR -it really has been a long time-, last version was using SSNM).

Thanks,
Tolga



> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On 
> Behalf Of LI Xinyan
> Sent: Monday, February 25, 2008 9:29 PM
> To: [email protected]
> Cc: [email protected]; [email protected]
> Subject: Re: [Sigtran] Sigtran Digest, Vol 46, Issue 5
> 
> Hello, Brain
> 
> I don't agree with you.
> 
> brain wrote:                              (2008225 16:30)
> >Be very clear: when you are using the ASP/SG configuration, the SG is 
> >simply backhauling its local MTP/MTP-User interface to the ASP.
> 
> [lxy]
> You are the author of M2UA? M2UA is a complete backhauling protocol.
> But M3UA has more wide use than M2UA, it can apply to backhauling 
> scenario, and also STP like scenario.
> That is why M3UA is recommended in 3GPP not M2UA, We wish we can 
> extend M3UA in order to apply SIGTRAN more widely in Mobile Network.
> Not say"SG-SG", even for "SG-ASP", current M3UA has shortcoming in 
> SSNM handling.
> M2UA can inherit the management of SS7, but M3UA cann't. So this part 
> of M3UA should be strengthened.
> 
> I totoally agree with Tolga's opinion.
> "
> >BTW, it is a pitty/shame we couldn't evaluate M3UA SG-SG/M3PA ideas
> properly in this WG,
> >as this seems to me exactly what people out there are looking for 
> >(and
> possibly would allow them
> >to use a single protocol throughout their networks, rather than a
> M3UA/M2PA hybrid).
> 
> >Thanks,
> >Tolga
> "
> 
> What's more, M3UA with flexible RK is an advantage. Operator can 
> select different granularity RK in various scenarios.
> But you cann't suppose all use RK with SI, to split PC based RK out.
> 
> 
> Regards
> Li Xinyan
> 
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:[email protected]]
> Sent: 2008225 16:30
> To: LI Xinyan
> Cc: [email protected]; [email protected]
> Subject: Re: Sigtran Digest, Vol 46, Issue 5
> 
> Li,
> 
> Why refuse to use the facility that was specifically placed in the RFC 
> to provide for independent user parts?
> 
> That facility is the DPC/SI RK.  If you refuse to use it, do not 
> expect to benefit from the fuctionality it provides.  Too hard and too complex:
> not!  M3UA is the "interface" between MTP and an MTP-User.  It is not 
> even a stack: it is a shim.  SS7 stacks do this all day long.
> 
> Sending SG messages in the wrong direction from an ASP is simply not 
> an option.  DUPU and SCON corresponds to MTP-STATUS, DUNA to MTP-PAUSE 
> and DAVA MTP-RESUME.  These primitives go from MTP to MTP-User; *not* 
> *visa* *versa*.
> If an MTP User wishes to attach to or withdraw from the MTP/MTP-User 
> interface and an MTP-SAP it uses an implementation dependent local 
> binding and unbinding function.  For M3UA this is the ASP TM 
> procedures and messages.  ASP Active/Ack attaches to the MTP-SAP 
> (PC/SI) and ASP Inactive/Ack detaches from the MTP-SAP.  Local to the 
> SS7 stack *at* *the* *SG*, an MTP-User detaching from the MTP-SAP 
> results in UPU(unavailable) being sent for the corresponding MTP-SAP.  
> That's how SS7 works.  That's how M3UA works.
> 
> Be very clear: when you are using the ASP/SG configuration, the SG is 
> simply backhauling its local MTP/MTP-User interface to the ASP.
> 
> --brian
> 
> --
> Brian F. G. Bidulock
> [email protected]
> http://www.openss7.org/
> _______________________________________________
> Sigtran mailing list
> [email protected]
> http://www.ietf.org/mailman/listinfo/sigtran
_______________________________________________
Sigtran mailing list
[email protected]
http://www.ietf.org/mailman/listinfo/sigtran