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

Tom Taylor <tom.taylor.stds@gmail.com> Fri, 14 February 2014 13:50 UTC

Return-Path: <tom.taylor.stds@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 28B961A0256 for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 05:50:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 Jx2SEUoGePVL for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 05:50:57 -0800 (PST)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 6F6291A0255 for <dispatch@ietf.org>; Fri, 14 Feb 2014 05:50:57 -0800 (PST)
Received: by mail-ob0-f176.google.com with SMTP id gq1so13772007obb.7 for <dispatch@ietf.org>; Fri, 14 Feb 2014 05:50:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=5uOxpK930RW824zCEf7xdZdUARA7nHvCgku9LIndfmo=; b=p6ygjon88NsdQlUEQkN2W+5NT53TN0PMLZJgFtKB+qpzPD1r/ohWKgnobpR4R3lNFY EeJQrlGakUyF/KecL+9DfaGX7ZU22ljLZ72YBN/N7oVFrB0oshRVR3o/7rXmUa+Wgsl4 avKrNfUHXQ/zAAdrzoxgnPwR3yQot5VZYkoZr6KI4GEBbFD7Aaswh0lxiJ3kI/sh3ZjQ kORGhG0kOhNmb9CPBv2hgNKI3EBJLrdnqDHrDfsU9PVGUlLsl+3836cJKIPBGAYOz8Wz iDDNi7RFh9tipSC9zmyQp027KiWn9ObYaOdwfAP1D2DF2aQd47uEoyk+6SHzyGZO37E/ bJaA==
X-Received: by 10.60.173.147 with SMTP id bk19mr6691292oec.46.1392385855830; Fri, 14 Feb 2014 05:50:55 -0800 (PST)
Received: from [192.168.0.101] ([207.112.119.16]) by mx.google.com with ESMTPSA id b2sm36651277oed.7.2014.02.14.05.50.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 14 Feb 2014 05:50:55 -0800 (PST)
Message-ID: <52FE1F3F.3020505@gmail.com>
Date: Fri, 14 Feb 2014 08:50:55 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Belling, Thomas (NSN - DE/Munich)" <thomas.belling@nsn.com>, "dispatch@ietf.org" <dispatch@ietf.org>
References: <040E1A40-BC55-4CFC-834A-FC958DEFDE25@rangenetworks.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-lucent.com> < 52FCF23D.7070608@iptel.org> <39B5E4D390E9BD4890E2B3107900610112662679@ESESSMB301.ericsson.se> <0A527A1E-0789-41D8-902B-A1B12F03E69C@westhawk.co.uk> <39B5E4D390E9BD4890E2B3107900610112662CD1@ESESSMB301.ericsson.se> <52FE0800.2080408@gmail.com> <BDBE1A97E84675488F72A48C23811F3515E4BC1F@DEMUMBX001.nsn-intra.net>
In-Reply-To: <BDBE1A97E84675488F72A48C23811F3515E4BC1F@DEMUMBX001.nsn-intra.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/fdcnhEcVCjSjr_yqW65ZoTcnppg
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 13:50:59 -0000

If the WG runs into a dead end for lack of expertise, so be it. 
Otherwise, this is the IETF, an open forum, and interesting technical 
problems are surely always welcome.

Tom Taylor

On 14/02/2014 8:13 AM, Belling, Thomas (NSN - DE/Munich) wrote:
> Dear Tom,
>
> your proposal for technical work seems to be that you want to describe interworking between 3GPP radio protocols and SIP?
>
> Would IETF or 3GPP be a more appropriate organization for that?
> IETF owns SIP but lacks expertise for the radio protocols.
> 3GPP knows their own protocols, and also has a certain SIP expertise by now.
> 3GPP also has experience with regulatory issues and interference problems that have been mentioned, and works based on operator requirements (that are your target customers based on your last explanations?). My conclusion thus is that 3GPP appears to be the more appropriate forum for such discussions.
>
> By the way, there is already a comparable 3GPP spec, TS 29.292, although it was written for a more specific IMS related use case.
>
> BR, Thomas
>
>
> ----------------------------------
> Dr. Thomas Belling
> 3GPP Standardisation
> NSN
>
>
...,