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

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 14 February 2014 07:02 UTC

Return-Path: <christer.holmberg@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 C173E1A012D for <dispatch@ietfa.amsl.com>; Thu, 13 Feb 2014 23:02:30 -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 M84_z3qM9AKt for <dispatch@ietfa.amsl.com>; Thu, 13 Feb 2014 23:02:28 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 466BC1A00E3 for <dispatch@ietf.org>; Thu, 13 Feb 2014 23:02:27 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-30-52fdbf815abd
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id C1.DD.23809.18FBDF25; Fri, 14 Feb 2014 08:02:25 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.02.0387.000; Fri, 14 Feb 2014 08:02:24 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Kurtis Heimerl <kheimerl@cs.berkeley.edu>, "Dale R. Worley" <worley@ariadne.com>
Thread-Topic: [dispatch] SIP and GSM/UMTS with OpenBTS
Thread-Index: AQHPIj0OkF9riHfhQ0Se4gDBfVRQX5qmz3RggAAosQCAAAyAAIAAASOQgAAmPICAAALFAIAAAFCAgAAAZICAAAdQgIAALnMAgAZ4WICAAOAQAIAACMEAgAAEaACAAAXeAIAAJYeAgAFsZwCAAXEU6IABHbKAgAAqBACAACCygIAADx+AgACZBYqAAFFnAIAAKpNQ
Date: Fri, 14 Feb 2014 07:02:24 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D172166@ESESSMB209.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> <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>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D172166ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDLMWRmVeSWpSXmKPExsUyM+JvjW7j/r9BBk/vC1ksnbSA1WLmkkcs Fi9PlDkwe0ze/5XZY8LJ8+weS5b8ZApgjuKySUnNySxLLdK3S+DKWDr3HFvB6rCK55PFGhif enUxcnJICJhInH0zgQnCFpO4cG89WxcjF4eQwCFGiW0bTzJDOIsZJWYt+svaxcjBwSZgIdH9 TxukQUQgTKLj7ksWEJtZQFvi//V1jCC2sICpxMqpLawQNWYSk6bNApsjInCJUeJUw3+wIhYB VYnJb/ezg8zkFfCV2NybAhIWEtjOI9H8ORTE5hQIlLjVsAxsPiPQcd9PrWGC2CUucevJfKij BSSW7DnPDGGLSrx8/I8VwlaS+LHhEtRt+RJNc5eCreUVEJQ4OfMJywRG0VlIRs1CUjYLSRlE XEdiwe5PbLOg3ly28DUzjH3mwGMmZPEFjOyrGNlzEzNz0suNNjECY+zglt+qOxjvnBM5xCjN waIkzvvhrXOQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBkY+dQ0VDn/tf6/rTjuFf1vW0H6h q1X4xb1HZyYWRweqf2Vayq2TP8OUe1Gjqu6DWQz2hw3OtHquUpy0IeqXbdQB9QBPj5K+2wIi 6v+jV27e6t1g4jUvOiXT5EqHFPtHxQdh+U41G48c0n6xZqnkZdEVa5YtPK+U3bL+2MUbZy9u VNRd7Cgav0OJpTgj0VCLuag4EQCsQ5QafwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/mfnU2H_jjHZLPiysvItOPyaKQN4
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 07:02:31 -0000

Hi,

Simple mapping between two protocols is one thing. IETF has done that in the past, e.g. between ISUP and SIP.

However, my understanding is that you want more than that. You are looking at an architecture (or, you want to define one), and you want to define the SIP procedures etc within that architecture to achieve certain things. Or, am I wrong?

Regards,

Christer

From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Kurtis Heimerl
Sent: 14. helmikuuta 2014 7:27
To: Dale R. Worley
Cc: dispatch@ietf.org
Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS

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<mailto:worley@ariadne.com>> wrote:
> From: "Ralph A. Schmid, dk5ras" <ralph@schmid.xxx<mailto: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