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

Mary Barnes <mary.ietf.barnes@gmail.com> Wed, 05 February 2014 23:00 UTC

Return-Path: <mary.ietf.barnes@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 64DAE1A026A for <dispatch@ietfa.amsl.com>; Wed, 5 Feb 2014 15:00:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 j1GC6XjhIE0r for <dispatch@ietfa.amsl.com>; Wed, 5 Feb 2014 15:00:12 -0800 (PST)
Received: from mail-yk0-x229.google.com (mail-yk0-x229.google.com [IPv6:2607:f8b0:4002:c07::229]) by ietfa.amsl.com (Postfix) with ESMTP id 5647B1A016B for <dispatch@ietf.org>; Wed, 5 Feb 2014 15:00:12 -0800 (PST)
Received: by mail-yk0-f169.google.com with SMTP id q9so2856650ykb.0 for <dispatch@ietf.org>; Wed, 05 Feb 2014 15:00:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BmpsUgf43py6v4xHWHgaQPrS8v+dFXQx50AFKNvOXB0=; b=Ka0FHr8j4ilIDVzg0aXBJ2rmWl7XmXa5d99eXKpgHs/XDUXwe+Rl3bcF9W/EqmQpPL mkl83zjKtK3UDbiOSnKn6SgjUK5JichqTeGm6OWU/ELE2qn6mt7cT0jLS7e05Mivq1YH bHyjLDPOnJiFH83uM6Zvh0+BOZ0VYlYKVcOyEeKZ9/ycjUvI/sRrAc1qEIMNUTT+5/BU O32jViyVgbr6TKVR5tCHZ+BzSKHnbsY7RK4zQ5784dhrldEYYp+85IhFN6M6xEVdZb+3 AygQT0vPax+eNiyqPta2Y7T/S2bHs3IhWWE/gytuU7zMXDKLDLRu60jON2TGtPoLuo+s STpA==
MIME-Version: 1.0
X-Received: by 10.236.131.19 with SMTP id l19mr3844076yhi.0.1391641211458; Wed, 05 Feb 2014 15:00:11 -0800 (PST)
Received: by 10.170.46.143 with HTTP; Wed, 5 Feb 2014 15:00:11 -0800 (PST)
In-Reply-To: <00C069FD01E0324C9FFCADF539701DB3BBF23E22@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>
Date: Wed, 05 Feb 2014 17:00:11 -0600
Message-ID: <CAHBDyN5-O3pNury3RUNzstGHO8NCq6pV3ewHt_Yrxjd1k-if5Q@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Michael Hammer <michael.hammer@yaanatech.com>
Content-Type: multipart/alternative; boundary="20cf3010e96d1058ae04f1b0b8a3"
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:00:15 -0000

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 <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
>
>