Re: [dispatch] SIP and GSM/UMTS with OpenBTS

I believe it was someone from rangenetworks that said:

"OpenBTS diverges from these standards by immediately gatewaying the call to SIP.  Each GSM or UMTS phone can then appear on the Internet as a SIP endpoint. "

If you meant something else, then perhaps...

But in any case, the questions I asked about requirements apply to any protocol. The key parts of 3GPP TS 22.228 were written before SIP was identified as a protocol to support the requirements. amd H.323 was still in the frame.

regards

Keith Drage

________________________________
From: Harvind Samra [mailto:harvind@rangenetworks.com]
Sent: 05 February 2014 19:01
To: Jim Forster
Cc: DRAGE, Keith (Keith); dispatch@ietf.org
Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS

I've run into very few mobile folks who think IMS was a good idea.  One of the chief reasons is that SIP, upon which IMS was developed, is a verbose/chatty protocol that occupies way too much bandwidth.

Some of the alternatives may be webRTC, DIAMETER...

On Feb 5, 2014, at 10:16 AM, Jim Forster <jim.forster@rangenetworks.com<mailto:jim.forster@rangenetworks.com>> wrote:

A good question for you to answer would be as to which of the requirements of 3GPP TS 22.228 you would support and which you would not support.

http://www.3gpp.org/DynaReport/22228.htm

Wow, that would be quite a job!  Well, I guess it should be looked at.

These requirements led to the development of IMS as it is now, and the IMS architecture is as it is because of those requirements.

Yes, but it starts out with the title:

Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1

Offhand, I don't immediately see the need to have such a thing as an "Internet Protocol (IP) multimedia core network subsystem". OK, certainly a large community (3GPP) does, which is fine and I use that stuff all the time on my phone and so am happy/grateful that it works, but does the rest of the Internet community accept those requirements for other things? What's the boundary for those requirements?  Are they a part of some RTAI or other IETF spec?  I think lots of interesting multimedia activity and specs happen without conformance to those particular requirements.  I'll readily admit to a lot of ignorance and naiveté, but it doesn't seem SIP or WebRTC aspires to support those requirements.  To some degree, OpenBTS is just trying to connect a bunch of nice phones with an OK air interface, to the Internet architecture, which another large set of people seem to like.

OK, I'll duck while the missiles fly overhead :-)
.
 How much are you trying to design something new, versus integrating a P-CSCF and a BTS economically in the same box, which network virtualisation will ultimately do?

Umm, I don't  know what a P-CSCF is, so I'll have to look into it, or please help me/us.

 -- Jim

_______________________________________________
dispatch mailing list
dispatch@ietf.org<mailto:dispatch@ietf.org>
https://www.ietf.org/mailman/listinfo/dispatch

Harvind Samra
Founder, CTO
Range Networks
San Francisco, CA
____________________________________________

Cellular networks made simple and affordable.
http://www.rangenetworks.com<http://www.rangenetworks.com/>
____________________________________________