IETF Logo Mail Archive

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

Ivo Sedlacek <ivo.sedlacek@ericsson.com> Thu, 13 February 2014 15:00 UTC

Return-Path: <ivo.sedlacek@ericsson.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D7C31A02B5 for <dispatch@ietfa.amsl.com>; Thu, 13 Feb 2014 07:00:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level:
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3KHN_hFHh-ta for <dispatch@ietfa.amsl.com>; Thu, 13 Feb 2014 07:00:05 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id AA5D11A02B7 for <dispatch@ietf.org>; Thu, 13 Feb 2014 07:00:04 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-44-52fcddf20ddb
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 60.8D.23809.2FDDCF25; Thu, 13 Feb 2014 16:00:02 +0100 (CET)
Received: from ESESSMB301.ericsson.se ([169.254.1.164]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.02.0387.000; Thu, 13 Feb 2014 16:00:02 +0100
From: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
To: Jim Forster <jim.forster@rangenetworks.com>
Thread-Topic: [dispatch] SIP and GSM/UMTS with OpenBTS
Thread-Index: AQHPIj0OkF9riHfhQ0Se4gDBfVRQX5qmz3RggAAosQCAAAyAAIAAASOQgAA3AICAAALFAIAAAFCAgAAAZICAAAdQgIAALnKAgAZ4SwCAAJlyIIAAT20AgAAEZwCAAAXeAIAAJYiAgAFsZwCAAWBU1IABLnGAgAAby4CAAANfkA==
Date: Thu, 13 Feb 2014 15:00:02 +0000
Message-ID: <39B5E4D390E9BD4890E2B31079006101126623BB@ESESSMB301.ericsson.se>
References: <040E1A40-BC55-4CFC-834A-FC958DEFDE25@rangenetworks.com> <949EF20990823C4C85C18D59AA11AD8B12A6DE@FR712WXCHMBA11.zeu.alcatel-lucent.com> <60884D2D-1CC8-4A21-97BE-2ACCB49C351D@rangenetworks.com> <7723B448-642F-4138-89DD-379ACC7FA593@rangenetworks.com> <E1FE4C082A89A246A11D7F32A95A17826DFCD495@US70UWXCHMBA02.zam.alcatel-lucent.com> <F5DA260C-32C9-4D92-9169-2026983BFC47@gmail.com> <E1FE4C082A89A246A11D7F32A95A17826DFCD852@US70UWXCHMBA02.zam.alcatel-lucent.com> <77E6DEC0-BCE1-4607-B52C-A4B6761A4B17@gmail.com> <00C069FD01E0324C9FFCADF539701DB3BBF23E22@sc9-ex2k10mb1.corp.yaanatech.com> <CAHBDyN5-O3pNury3RUNzstGHO8NCq6pV3ewHt_Yrxjd1k-if5Q@mail.gmail.com> <948FB37B-F2D4-4462-8B29-D03FDF65215F@rangenetworks.com> <93B4EA30-0734-439E-A129-B3B91B077720@rangenetworks.com> <949EF20990823C4C85C18D59AA11AD8B12F6C3@FR712WXCHMBA11.zeu.alcatel-lucent.com> <2B05935E-EB65-4B36-ABD3-09DE9921F8A7@westhawk.co.uk> <949EF20990823C4C85C18D59AA11AD8B12F7CE@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CACy T-3mAJX4uPDcXDz7j6xOAA+OSDoRguQ51EvZk9=LTG8KzJQ@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B12FA06@FR712WXCHMBA11.zeu.alcatel-lucent.com> <DE4C1B56-0D67-4210-9FFA-EC0BC866E081@westhawk.co.uk> <201402121601.s1CG1q0W4835781@shell01.TheWorld.com> <39B5E4D390E9BD4890E2B3107900610112662068@ESESSMB301.ericsson.se> <676E4A52-E702-43BE-9245-5CD558D69497@rangenetworks.com>
In-Reply-To: <676E4A52-E702-43BE-9245-5CD558D69497@rangenetworks.com>
Accept-Language: en-US, cs-CZ
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.150]
Content-Type: multipart/alternative; boundary="_000_39B5E4D390E9BD4890E2B31079006101126623BBESESSMB301erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM+Jvje6nu3+CDE5Ps7BYOmkBq8WD84fY LNa9P8biwOyxZMlPJo8zJ9M9Lk7bzxTAHMVlk5Kak1mWWqRvl8CV8envf8aCzakV9yZnNTBu iupi5OSQEDCR2Pq/jxXCFpO4cG89WxcjF4eQwCFGiS+t71khnCWMEouvv2QCqWIT0JOYuOUI UIKDQ0RAX2J1qwFImFnAR2LVrqvMILawgKnEyqktYENFBMwkJk2bxQxh72KU2PoCrJ5FQFVi 3dzP7CA2r4CvxJ6L/9khdjVxS1xvuQHWwCngKvHxSzfYXkYBWYmrf3oZIZaJS9x6Mp8J4moB iSV7zjND2KISLx//g/pGSWLF9ktQ9fkSd/d9gVomKHFy5hOWCYyis5CMmoWkbBaSMoi4jsSC 3Z/YIGxtiWULXzPD2GcOPGZCFl/AyL6KkT03MTMnvdxoEyMwyg5u+a26g/HOOZFDjNIcLEri vB/eOgcJCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYLT3kZ/43OLjtuz97VtFmnMvmi2qY50s FxQz4fjRhy5bFKPvHgmX+bvLpPsH95RLd8+LC/w1vfcneXpp3Cx19ditdyJ7Umwm7jlYm1y4 8Na3Td4/ky+4XE43eVQUNNFxv10Tx3e986y60yRU383j3Tehcr7envr+D/1xaV/ZJyp57zZZ ZLM/1UOJpTgj0VCLuag4EQBhJ/36gAIAAA==
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 15:00:10 -0000

Hello Jin and Samra,

@Jin:

> > E.g. can you please clarify whether you indent to specify a solution for:
> >a) carriers with license to use the licensed GSM bands?
>
> Yes.
>
> > b) individuals/corporates without license to use the licensed GSM bands?
>
> No.

OK, thanks for clarification.

> > Or do you believe that some existing requirements are unnecessary for deployments in carrier networks?
>
> Evidence indicates entities operating legally are willing to use this approach.  I don't know the definition of a carrier,
> or if that's relevant in this forum.   You probably see other evidence indicating a different conclusion.

Can you please point me to such evidence indicating "entities operating legally are willing to use this approach"?

Can you please indicate which existing requirements defined for the existing 3GPP solution you believe are not necessary in your solution, when deployed by an operator with a license to use the licensed GSM bands? If no such unnecessary requirement is identified, your solution will end up with the same complexity as the existing 3GPP solution.

You stated "But more typically carriers with spectrum licenses are looking for an economical way to get into rural areas.".  Can you please provide any numbers or other justification proving that your proposal is more economical than the existing 3GPP solution which is already developed, tested, mass produced and mass deployed and thus benefits from economies of scale?

Note that there is no preclusion in the existing 3GPP solution to provide one node encompassing BSC, MSC, HSS, SM-SC, ... so if that was considered useful, it could have been done with the existing 3GPP solution too.


@Samra:

> I have to ask...why are the questions regarding frequency licensing and economics relevant?  This is a discussion regrading augmenting SIP.

The point is to identify whether there is a relevant business case for the solution augmenting SIP. If there is none, why to spend meeting time and effort to standardize the solution?

Kind regards

Ivo Sedlacek

v2.23.0 | Report a Bug | By Email