IETF Logo Mail Archive

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

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Sat, 15 February 2014 01:37 UTC

Return-Path: <keith.drage@alcatel-lucent.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 1CAF81A0012 for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 17:37:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 U86Sk248c0UD for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 17:37:06 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 1720E1A0017 for <dispatch@ietf.org>; Fri, 14 Feb 2014 17:37:04 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s1F1awwW002947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 14 Feb 2014 19:36:59 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s1F1aurw004031 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 15 Feb 2014 02:36:56 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Sat, 15 Feb 2014 02:36:56 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Jiri Kuthan <jiri@iptel.org>, Harvind Samra <harvind@rangenetworks.com>, Ivo Sedlacek <ivo.sedlacek@ericsson.com>
Thread-Topic: [dispatch] SIP and GSM/UMTS with OpenBTS
Thread-Index: AQHPIj0OkF9riHfhQ0Se4gDBfVRQX5qmz3RggAAosQCAAAyAAIAAASOQgAA3AICAAALFAIAAAFCAgAAAZICAAAdQgIAALnKAgAZ4SwCAAJlyIIAAPqkAgAASvbD///eJAIAAMB4ggAFh0ACAAXHr6IABHNuAgAAqBACAADBv4IAAD6iAgAI35xA=
Date: Sat, 15 Feb 2014 01:36:54 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B132EE5@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <040E1A40-BC55-4CFC-834A-FC958DEFDE25@rangenetworks.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> <CACy T-3mAJX4uPDcXDz7j6xOAA+OSDoRguQ51EvZk9=LTG8KzJQ@mail.gmail.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-luce! nt.com> <52FCF23D.7070608@iptel.org>
In-Reply-To: <52FCF23D.7070608@iptel.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/Ow9BqFa48v7wBbUrIIe00080NRs
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: Sat, 15 Feb 2014 01:37:09 -0000

No.

But to persuade people to work on anything, you need to persuade them that there is something there in terms of a market. I'd hardly regard this as something to be treated as an academic exercise.

But I would still indicate there is insufficient information around here on what is being attempted. Rather than having a draft with a set of use cases and requirements, we are having to try and get it elaborated on the mailing list.

Keith 

> -----Original Message-----
> From: Jiri Kuthan [mailto:jiri@iptel.org] 
> Sent: 13 February 2014 16:27
> To: DRAGE, Keith (Keith); Harvind Samra; Ivo Sedlacek
> Cc: dispatch@ietf.org
> Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS
> 
> On 2/13/14 3:34 PM, DRAGE, Keith (Keith) wrote:
> > Jumping in here, they are relevant in as much as there is 
> no point in IETF working on this if there is no known market for it.
> 
> Hi Keith,
> 
> are you suggesting that IETF processes shall only allow work 
> on technologies for which there is a known market?
> 
> I'm glad this was not the case in the past, otherwise I would 
> not be able to send a single email. At least I don't have 
> memory of IETF business case criteria for the SNMP protocol. 
> If that shall change in the future, I would like to know what 
> is the specific IETF criteria for market existence. Can you 
> elaborate what these are supposed to be?
> 
> -jiri
> 
> p.s. one more question here: I understand your point that I'm 
> eligible to read emails to this WG mailing list that carry 
> confidentiality notice on the grounds of group memership. 
> What I don't understand is whether I'm also permitted (in 
> departure from the notice) to forward such an email to some 
> other email address than that of the working group.
> 
> 
> > Usually those type of projects are published only on April 1st.
> > So all Ivo is asking is for you to justify that it is worth 
> other people working on this as well as yourselves.
> > Perhaps if you identified the spectrum you believe is 
> available for use in the the countries identified, that would 
> be useful.
> > regards
> > Keith Drage
>

v2.23.0 | Report a Bug | By Email