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

Michael Hammer <michael.hammer@yaanatech.com> Wed, 05 February 2014 23:19 UTC

Return-Path: <michael.hammer@yaanatech.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 051771A02B5 for <dispatch@ietfa.amsl.com>; Wed, 5 Feb 2014 15:19:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level:
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, 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 5S6dc8gPBGMv for <dispatch@ietfa.amsl.com>; Wed, 5 Feb 2014 15:19:38 -0800 (PST)
Received: from email1.corp.yaanatech.com (webmail10.yaanatech.com [63.128.177.10]) by ietfa.amsl.com (Postfix) with ESMTP id 33E5D1A021F for <dispatch@ietf.org>; Wed, 5 Feb 2014 15:19:38 -0800 (PST)
Received: from SC9-EX2K10MB1.corp.yaanatech.com ([fe80::149d:c2e1:8065:2a47]) by ex2k10hub1.corp.yaanatech.com ([::1]) with mapi id 14.03.0123.003; Wed, 5 Feb 2014 15:19:37 -0800
From: Michael Hammer <michael.hammer@yaanatech.com>
To: "mary.ietf.barnes@gmail.com" <mary.ietf.barnes@gmail.com>
Thread-Topic: [dispatch] SIP and GSM/UMTS with OpenBTS
Thread-Index: AQHPIj0OkF9riHfhQ0Se4gDBfVRQX5qmz3RggAAosQCAAAyAAIAAASOQgAC9HICAAALFAIAAAFCA//96B5CAAI2tgP//fihg
Date: Wed, 05 Feb 2014 23:19:35 +0000
Message-ID: <00C069FD01E0324C9FFCADF539701DB3BBF23F45@sc9-ex2k10mb1.corp.yaanatech.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>
In-Reply-To: <CAHBDyN5-O3pNury3RUNzstGHO8NCq6pV3ewHt_Yrxjd1k-if5Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.17.100.48]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_0140_01CF229E.D2A6FD10"
MIME-Version: 1.0
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: Wed, 05 Feb 2014 23:19:42 -0000

Mary,

 

What I was hoping to avoid was full-blown tutorials on 3GPP and IMS.

As well as discussion about what parts of 3GPP are signaling versus
something else.

 

Distinguishing what the impacts of OpenBTS on SIP are versus what is in use
for 3GPP 

could clarify if we would be doing the same thing but with redundant
headers, for example, would be useful.

 

Just didn't want to lose sight of the touchstone (how does this impact SIP).

 

Michael Hammer

Principal Engineer

 <mailto:michael.hammer@yaanatech.com> michael.hammer@yaanatech.com

Mobile: +1 408-202-9291

500 Yosemite Drive Suite 120

Milpitas, CA 95035 USA

 

From: Mary Barnes [mailto:mary.ietf.barnes@gmail.com] 
Sent: Wednesday, February 05, 2014 6:00 PM
To: Michael Hammer
Cc: a.james.winterbottom@gmail.com; Raju.Makaraju@alcatel-lucent.com;
dispatch@ietf.org
Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS

 

I don't necessarily think 3GPP is out of scope in that I think it's very
important that if IETF decides that we will be documenting or even defining
protocol elements to support OpenBTS, it needs to be clear why 3GPP Call
control/SIP specifications aren't being used. 

 

In offline in discussions with the proponents, it's my understanding that
OpenBTS is being used in very specific environments where there is no full
MSC deployments (i.e., remote locations that have no deployed IMS networks).
The intent isn't to replicate a full IMS system, but rather to provide basic
connectivity to the Internet and use SIP in a non-IMS context to complete
the calls.   So, I think more detail about this context would be very
helpful.  

 

I think it would really help if there were some diagrams showing what IMS
protocols are being used.  My understanding is that current implementations
have various ways in which they are interworking the Radio Layer Call
Control messages to SIP messages.  I think the motivation is to improve
interop by defining a consistent "mapping" if you will.  It's not clear to
me how exactly registration is being handled - perhaps mapping some of the
Radio Layer mobility management messages.   My understanding is that there
can be no change to the existing messages from the cell phone to the BTS for
obvious reasons, so all the interworking needs to happen in the BTS.  

 

Regards,

Mary. 

 

On Wed, Feb 5, 2014 at 4:34 PM, Michael Hammer
<michael.hammer@yaanatech.com> wrote:

Could we take debates about 3GPP off-line?

Seems to be getting off-topic.

 

Michael Hammer

Principal Engineer

michael.hammer@yaanatech.com

Mobile: +1 408-202-9291

500 Yosemite Drive Suite 120

Milpitas, CA 95035 USA

 

From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of James
Winterbottom
Sent: Wednesday, February 05, 2014 5:33 PM
To: Makaraju, Maridi Raju (Raju)
Cc: dispatch@ietf.org
Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS

 

Check out SLh.

Check out SLg

 

On 6 Feb 2014, at 9:31 am, Makaraju, Maridi Raju (Raju)
<Raju.Makaraju@alcatel-lucent.com> wrote:

 

 

DIAMETER is used to carry signalling information through out IMS.

[Raju] Which interface? and what kind of signaling? To the best of my
knowledge, diameter is only used for "authentication, authorization, and
accounting". The Rx diameter interface used between P-CSCF and PCRF is not
really call processing related signaling but rather used for "authorization"
of the media flow.

 

-Raju

 


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