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

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Sat, 15 February 2014 01:37 UTC

Return-Path: <keith.drage@alcatel-lucent.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 8E5251A0015 for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 17:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] 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 GYBJe4hw1NwY for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 17:37:03 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id D59A01A0012 for <dispatch@ietf.org>; Fri, 14 Feb 2014 17:37:02 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s1F1awAC002946 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 14 Feb 2014 19:36:59 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s1F1auco004034 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 15 Feb 2014 02:36:56 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Sat, 15 Feb 2014 02:36:56 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Thread-Topic: [dispatch] SIP and GSM/UMTS with OpenBTS
Thread-Index: AQHPKPi9kF9riHfhQ0Se4gDBfVRQX5q1h4VA
Date: Sat, 15 Feb 2014 01:36:55 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B132EEA@FR712WXCHMBA11.zeu.alcatel-lucent.com>
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> <949EF20990823C4C85C18D59AA11AD8B12FA06@FR712WXCHMBA11.zeu.alcatel-lucent.com> <DE4C1B56-0D67-4210-9FFA-EC0BC866E081@westhawk.co.uk> <201402121601.s1CG1q0W4835781@shell01.TheWorld.com> <39B5E4D390E9BD4890E2B3107900610112662068@ESESSMB301.ericsson.se> <017BBEA0-CDBE-453D-9E98-77F470BC9181@rangenetworks.com> <949EF20990823C4C85C18D59AA11AD8B1319E6@FR712WXCHMBA11.zeu.alcatel-lucent.com> <00361BF0-F6B9-48DD-80A6-CECD0A7C0A3B@westhawk.co.uk> <949EF20990823C4C85C18D59AA11AD8B131BEF@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAHBDyN6RVnk4PyUuf1BA1b4JB9SGC44KFDsBip_XPqRRX3CG-Q@mail.gmail.com>
In-Reply-To: <CAHBDyN6RVnk4PyUuf1BA1b4JB9SGC44KFDsBip_XPqRRX3CG-Q@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: multipart/alternative; boundary="_000_949EF20990823C4C85C18D59AA11AD8B132EEAFR712WXCHMBA11zeu_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/GlMSuwMbVE6TCAlhZlzEPcbS3zk
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: Sat, 15 Feb 2014 01:37:07 -0000

As regards membership of 3GPP and GSMA.

What I was suggesting is that 3GPP would be used. This allows you to get access to more operators and regulators than you would have in IETF, and more specifically the correct representatives of the operators and regulators.

GSMA will follow automatically if you get the operators interest.

Membership of 3GPP for small organisations (annual) is not necessarily that much more expensive that IETF (meeting fees). GSMA membership is not needed, and would be very expensive.

Keith

________________________________
From: Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
Sent: 13 February 2014 20:18
To: DRAGE, Keith (Keith)
Cc: Tim Panton new; dispatch@ietf.org
Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS




On Thu, Feb 13, 2014 at 9:28 AM, DRAGE, Keith (Keith) <keith.drage@alcatel-lucent.com<mailto:keith.drage@alcatel-lucent.com>> wrote:
Ericsson is not the only vendor that sees a market for small cells, but the expectation is that the products are built to the completed 3GPP standards will be deployed in licensed spectrum by owners of that spectrum, although the boxes may well be owned by 3rd parties.

These deployments already exist.

I see Jim has now identified that this proposal is for licensed GSM operators in licensed GSM space.

Personally, I would suggest if you believe the operators should be picking this up, you take it to 3GPP where the operators are actually present. That is the only way you will see it taken up by GSMA, which you will need to obtain interoperator agreements to use this (e.g. roaming, shared networks). 3GPP them works with IETF on any SIP extensions needed.
[MB] One big problem with this proposal is that you must be a member of 3GPP/GSMA to make contributions and to participate in meetings.

And, I think having to first do the work in 3GPP and then bring it to IETF would introduce a tremendous delay for something that's already been implemented/deployed.  While they are proposing to reuse elements and protocols that are part of an IMS network, the core issue they have is with interworking SIP with the radio layer protocols.  Certainly, one could implement all the protocols that IMS uses and then use the 3GPP based specs and proprietary headers to interwork with SIP in the Internet, but that would be terribly inefficient.
[/MB]

I would only see IETF having any direct part in this if the proposal was only to use unlicensed spectrum by enterprises rather than licensed operators, which Jim has negated.

regards

Keith

________________________________
From: Tim Panton new [mailto:thp@westhawk.co.uk<mailto:thp@westhawk.co.uk>]
Sent: 13 February 2014 14:50
To: DRAGE, Keith (Keith)
Cc: Harvind Samra; Ivo Sedlacek; dispatch@ietf.org<mailto:dispatch@ietf.org>

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


On 13 Feb 2014, at 14:34, DRAGE, Keith (Keith) <keith.drage@alcatel-lucent.com<mailto:keith.drage@alcatel-lucent.com>> wrote:

Jumping in here, they are relevant in as much as there is no point in IETF working on this if there is no known market for it.

Usually those type of projects are published only on April 1st.

So all Ivo is asking is for you to justify that it is worth other people working on this as well as yourselves.

Perhaps if you identified the spectrum you believe is available for use in the the countries identified, that would be useful.

regards

Keith Drage

Ivo's employer seems to see a market for small cells, but looks to tie them to existing operator IMS's through
internet connections "owned by themselves or a partner".
http://www.telecomlead.com/enterprise-networking/mwc-2014-ericsson-announce-small-cell-service-20233/
Perhaps that's an April fools joke too (I can't see any avian carriers mentioned though)?

It isn't up to the IETF to crown specific solutions. That's the market's job.

T.




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