IETF Logo Mail Archive

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

James Winterbottom <a.james.winterbottom@gmail.com> Wed, 05 February 2014 22:21 UTC

Return-Path: <a.james.winterbottom@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 7DA2A1A0209 for <dispatch@ietfa.amsl.com>; Wed, 5 Feb 2014 14:21:48 -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 KZhysaEvcDn4 for <dispatch@ietfa.amsl.com>; Wed, 5 Feb 2014 14:21:41 -0800 (PST)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id B64631A012F for <dispatch@ietf.org>; Wed, 5 Feb 2014 14:21:41 -0800 (PST)
Received: by mail-pb0-f48.google.com with SMTP id rr13so938265pbb.21 for <dispatch@ietf.org>; Wed, 05 Feb 2014 14:21:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=LiyYtYBP+XbbpZjs2dATXqufE56r6NGgktw03kguNEM=; b=fSW2rTpo66+ptDMxeXiQQI/TbO8j59GIlK7nLynoZLSbRug4LI9vHEpbYi4SuzI9Ms u0u/4uh9B4fqEgEEKkHvTqHuvJPnGnn/Qn3UzpJKp6BzQE2Q8idDKXM5bVLCVlludMmy 83KTPXfC79Z+F23aubt0+8OUQHizeALu3mDkMpCVYqNPxUJ13aMMkm66Izl9k3IKEgH9 Dvov6c/VZD6YmaOhDl7o2Pb+Ow4cxtWeCmpZVMgm9+1jza2b1LL4oSSHSYZmCLZ9PME5 KyaPAaF3P9qY1FA+Kxp5YXwFh5D/rTX+JiNLJr20o5uyLvKzw0FwxUqsvsFdNqBGcVTQ P2Pw==
X-Received: by 10.68.133.229 with SMTP id pf5mr5868256pbb.115.1391638900965; Wed, 05 Feb 2014 14:21:40 -0800 (PST)
Received: from [192.168.1.7] (124-149-100-27.dyn.iinet.net.au. [124.149.100.27]) by mx.google.com with ESMTPSA id eb5sm205369020pad.22.2014.02.05.14.21.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Feb 2014 14:21:40 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_D1B2A9D1-1042-4126-A429-39EB12785746"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: James Winterbottom <a.james.winterbottom@gmail.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17826DFCD495@US70UWXCHMBA02.zam.alcatel-lucent.com>
Date: Thu, 06 Feb 2014 09:21:35 +1100
Message-Id: <F5DA260C-32C9-4D92-9169-2026983BFC47@gmail.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>
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1827)
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 22:21:49 -0000

DIAMETER is used to carry signalling information through out IMS.


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

> 
>  
> [Raju] WebRTC is NOT a signaling protocol!! Neither Diameter is!! WebRTC only deals with bearer representation (via SDP) and transport while diameter is an “authentication, authorization, and accounting“ protocol and not suitable for signaling. That’s pretty much leaves us with, whether we like it or not, SIP. Trying to come up with another protocol (and architecture) is like reinventing the SIP/IMS-wheel in another form, which may not please the same folks who don’t like IMS/SIP.
> We can surely debate on chatty nature of SIP, which I really don’t think that chatty. SIP does many things like routing, signaling NAT traversal facilitation, topology hiding, SDP transport etc.  I believe, the SDP is the one which makes it look “chatty”, rest of them are headers just like HTTP headers (they are even designed after HTTP/SMTP).
> Btw, though it is not signaling, WebRTC is far from simple!! Basically, “it’s the devil you know vs. the angel you don’t now!”!! J
>

v2.23.0 | Report a Bug | By Email