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

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 14 February 2014 18:53 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 4F7241A02D0 for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 10:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 S4O1A64U_nXh for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 10:53:13 -0800 (PST)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id ACB561A0368 for <dispatch@ietf.org>; Fri, 14 Feb 2014 10:53:11 -0800 (PST)
Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta14.westchester.pa.mail.comcast.net with comcast id SDAt1n00316LCl05EJt9mr; Fri, 14 Feb 2014 18:53:09 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta06.westchester.pa.mail.comcast.net with comcast id SJt91n00V3ZTu2S3SJt9Fy; Fri, 14 Feb 2014 18:53:09 +0000
Message-ID: <52FE6615.5010100@alum.mit.edu>
Date: Fri, 14 Feb 2014 13:53:09 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dispatch@ietf.org
References: <040E1A40-BC55-4CFC-834A-FC958DEFDE25@rangenetworks.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> <CACyT-3=RKqvhGB-WLmWH0tGHCTEzH=Ej22sa+U-3vGN4AbTndg@mail.gmail.com>
In-Reply-To: <CACyT-3=RKqvhGB-WLmWH0tGHCTEzH=Ej22sa+U-3vGN4AbTndg@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1392403989; bh=+lOQovcvt04/aCYp75QLH3ndBAllkQgNrEi463sCr+k=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=C3w8577lJKI8Mn5rAJ73Mng395SIn/4Le2eS+nNTTxDdtzzQLvu7+jbZwEJxBg8ur MeMHhMm7ummdfENTS7Kaw+JlhPVzoizQ/vUXk+iVJEtYQN88hM08Tbr9HdM6aF6sqX 5ntgXuprEx55L1mvgIOOAZMFnFQmpd8C1AfsfGbXwSju+hHKuoCfiltDUHiEFEWW/x OQ/eLA7zpZYJfaPPJZzn3yMykoNgs8IZaNP4XVRLzdoYEkLDtH9guzdafd6fpZA1J8 8DKTxFwSWCS4fmLh7r3cDshPFgzBOqCXumNgn98pqLO187S+Dcs2zytnwmXTYT3aSg d7O97LG6kXmUw==
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/nV7DcoVBMQYYLChb52bR4KYoPko
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 18:53:15 -0000

On 2/14/14 12:27 AM, Kurtis Heimerl wrote:
> 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.

I have a *little*, old, knowledge of IMS at the sip layer, and almost no 
understanding of the remainder of 3gpp. I'm trying to make sense of this 
discussion.

IIUC, you have (or plan) a box that talk to 3gpp-compatible UEs over the 
radio link. This box is sufficient so that the phones connected to it 
can talk to one another. And your goal is to put a SIP interface on the 
box so that:
1) several of your boxes can interconnect and establish calls
    between themselves using SIP over the internet
2) so that these boxes can call other E.164 numbers using SIP
    over the internet.

Do I have the right idea? Are both (1) and (2) goals?

	Thanks,
	Paul

> 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
> <mailto: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 <mailto:dispatch@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dispatch
>
>
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>