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

Tim Panton new <thp@westhawk.co.uk> Wed, 12 February 2014 16:45 UTC

Return-Path: <thp@westhawk.co.uk>
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 D29521A0459 for <dispatch@ietfa.amsl.com>; Wed, 12 Feb 2014 08:45:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 iWJkW0Fa_Cgk for <dispatch@ietfa.amsl.com>; Wed, 12 Feb 2014 08:45:48 -0800 (PST)
Received: from smtp001.apm-internet.net (smtp001-out.apm-internet.net [85.119.248.222]) by ietfa.amsl.com (Postfix) with ESMTP id D95A81A02A7 for <dispatch@ietf.org>; Wed, 12 Feb 2014 08:45:47 -0800 (PST)
Received: (qmail 72940 invoked from network); 12 Feb 2014 16:45:46 -0000
X-AV-Scan: clean
X-APM-Authkey: 83769 12507
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp001.apm-internet.net with SMTP; 12 Feb 2014 16:45:46 -0000
Received: from zimbra003.verygoodemail.com (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id 00D3F18A0189; Wed, 12 Feb 2014 16:45:46 +0000 (GMT)
Received: from limit.westhawk.co.uk (limit.westhawk.co.uk [192.67.4.33]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id BD97C18A00F6; Wed, 12 Feb 2014 16:45:45 +0000 (GMT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Tim Panton new <thp@westhawk.co.uk>
In-Reply-To: <201402121601.s1CG1q0W4835781@shell01.TheWorld.com>
Date: Wed, 12 Feb 2014 16:45:34 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D0418E0-A6D0-43BC-A5DC-1D8AD1D93E75@westhawk.co.uk>
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>
To: "Dale R. Worley" <worley@ariadne.com>
X-Mailer: Apple Mail (2.1827)
Cc: dispatch@ietf.org
Subject: Re: [dispatch] [SPAM] Re: 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: Wed, 12 Feb 2014 16:45:51 -0000

On 12 Feb 2014, at 16:01, Dale R. Worley <worley@ariadne.com> wrote:

>> From: Tim Panton new <thp@westhawk.co.uk>
> 
>> Here is an interesting presentation by Kurtis that will give you
>> some feel for what these systems do:
>> 
>> https://www.usenix.org/conference/nsdi13/technical-sessions/presentation/heimurl
> 
> Though he's incorrect that the first cellular network was in 1991, it
> was in 1979.  1991 is the first GSM cellular network.
> 
>> It isn't directly related to the standardisation effort but is a
>> great background info.
> 
> It's interesting work, but I don't see its connection with SIP at all.

As I said it isn't related to the standardisation, but rather to give some background
to the usage.

> 
> My assumption is that you're asking, "How do we mate the GSM
> over-the-air protocol with SIP for backhaul?", that is, how do we
> disconnect the cellular system from IMS and all that.  But if your
> goal is to deploy base stations commercially, you're going to need the
> call accounting infrastructure of IMS.


That's assuming a currently popular billing model. If all your customers were (for example) on an
all-you-can-eat tariff then you might not need IMS. Likewise if you only had 1000 customers, the
standard IMS solution is overkill. If you don't need roaming, then you may not want the full IMS stack.

So to take Kurtis's example there might be significant value in a phone service that allowed users to:
1) call within network (that's a potential 20 mile radius even for a single cell)
2) make emergency calls
3) receive external calls
4) all bound to a specific sim
5) sms to the world

- That could be associated with a small monthly fee to cover the infrastructure costs. 

Sure they'd like the full LTE experience - but (a - wifi probably does that better (b - LTE is too expensive.


The point is these systems don't attempt to replace existing services - they are generally put into
places and scenarios where the IMS 3gpp model doesn't work (for one reason or another). This is evidenced
by the fact that these places _aren't_ served yet.

I'm hoping we'll standardise the SIP interface towards the ITSP, either in the form of a set of recommendations
and possibly a new header field or two.
I'd also like see a standard (SIP? SCTP? SNMP?) interface between cells to help with handoff etc.

The point of standardisation is to allow many vendors to interoperate and ITSPs to offer service,
but not to restrict the use-case so much that
it exactly replicates something we _know_ isn't practical for these environments.

Tim.




> 
> Dale