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

Kurtis Heimerl <kheimerl@cs.berkeley.edu> Fri, 14 February 2014 05:28 UTC

Return-Path: <munncha@gmail.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 3A3201A00B9 for <dispatch@ietfa.amsl.com>; Thu, 13 Feb 2014 21:28:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 w1HKFJRW7bGs for <dispatch@ietfa.amsl.com>; Thu, 13 Feb 2014 21:28:07 -0800 (PST)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) by ietfa.amsl.com (Postfix) with ESMTP id E34021A00EE for <dispatch@ietf.org>; Thu, 13 Feb 2014 21:28:06 -0800 (PST)
Received: by mail-lb0-f176.google.com with SMTP id w7so8826666lbi.7 for <dispatch@ietf.org>; Thu, 13 Feb 2014 21:28:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=FXZpa5IItO7DGeyALdTW7AJ8qRlcUXZBs8sPxZFGolo=; b=VUawfajo32ibw+okyqjfmfZfCPEfCseUg2ruJE/Ix6V33ZDJU0KJ0O5YeQhpglrUWe 5zughijoULnRMTGIw7Y66ONy5fyEtNIMLoy1sBIxr6CXpK7OlbfPDnZChsXc5brwgCpI rlln9YH02x/ALonFws2RCJODzxL7PXYclxlHdKiI9RNLqyZMyj3a5ucYVPtg0B3YbNFw +QJr8hqIaRn7mnmREVTu8c9myiS/dm/PLWqrxH1sL3U//E1cGXsOgNUS4OKvdxQLbuKs mCYeDyjvo22FArURheYuQWKkLOd5yDAmXtyc3kIVrKcQd37iFxXJfMrqAOq3tJcKtCqb Qtog==
X-Received: by 10.112.137.65 with SMTP id qg1mr3535386lbb.7.1392355684883; Thu, 13 Feb 2014 21:28:04 -0800 (PST)
MIME-Version: 1.0
Sender: munncha@gmail.com
Received: by 10.112.42.170 with HTTP; Thu, 13 Feb 2014 21:27:24 -0800 (PST)
In-Reply-To: <201402132328.s1DNS0U64926205@shell01.TheWorld.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> <949EF20990823C4C85C18D59AA11AD8B12F7CE@FR712WXCHMBA11.zeu.alcatel-lucent.com> <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> <00b801cf28d0$3c39c000$b4ad4000$@schmid.xxx> <201402132328.s1DNS0U64926205@shell01.TheWorld.com>
From: Kurtis Heimerl <kheimerl@cs.berkeley.edu>
Date: Fri, 14 Feb 2014 14:27:24 +0900
X-Google-Sender-Auth: -IOyaiGa1M-8UZMBrhMR4wJRdSE
Message-ID: <CACyT-3=RKqvhGB-WLmWH0tGHCTEzH=Ej22sa+U-3vGN4AbTndg@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary="089e0116047effa17604f25711cd"
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/FLVu0AigjpnBGvvKvajhP6nJElQ
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: Fri, 14 Feb 2014 05:28:09 -0000

OpenBTS is an instance of an Um->SIP gateway. After this implementation,
we've become aware that a broader view of the relative correctness of our
design would be valuable...  and that's why this thread exists. We'd like
the IETF to help standardize this gateway model and make sure that the
decisions that were made are reasonable, scalable, and intelligent.

At least that's my perception on why we're here. Jim may have another.


On Fri, Feb 14, 2014 at 8:28 AM, Dale R. Worley <worley@ariadne.com> wrote:

> > From: "Ralph A. Schmid, dk5ras" <ralph@schmid.xxx>
>
> (Is there a reason you insert so many blank lines?)
>
> > So imagine a village, a few hundred people living there, most of
> > them owning mobile phones for communication when they travel to the
> > town for work or for trading goods - but at home those phones are
> > useless.
>
> > So somebody is able to spent a few thousand dollars, puts an antenna
> > onto some tree, flips the switch, and a few hundred phones can (and
> > do) log on.
>
> > Now more and more of those low-cost networks grow up, and people
> > want to connect them. Internet is available in some places, cheap to
> > buy and install WiFi-links are established, the whole thing evolves,
> > some simple structure grows.
>
> This story makes sense to me.  The question seems to be how to
> interwork the GSM radio call-control protocol with SIP, so that a set
> of these base stations can operate as an integrated system.  You'd
> want some sort of SIP registrar/proxy to operate as an ITSP, and all
> of the base stations make SIP connections with it.
>
> The next step is for someone to start designing this use of SIP.  No
> doubt a lot of interesting questions will arise, and you may need to
> design some SIP extensions.  But until you've got the design started
> and can discuss the design decisions, you're not in a position to talk
> about what SIP extensions are needed.
>
> Dale
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>