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

worley@ariadne.com (Dale R. Worley) Thu, 06 February 2014 19:21 UTC

Return-Path: <worley@shell01.TheWorld.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 E36631A0469 for <dispatch@ietfa.amsl.com>; Thu, 6 Feb 2014 11:21:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.254
X-Spam-Level:
X-Spam-Status: No, score=-1.254 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=no
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 gWPVeSBwg4Ge for <dispatch@ietfa.amsl.com>; Thu, 6 Feb 2014 11:21:27 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id A47751A045A for <dispatch@ietf.org>; Thu, 6 Feb 2014 11:21:27 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s16JKGfl012342; Thu, 6 Feb 2014 14:20:18 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s16JF2av4389550; Thu, 6 Feb 2014 14:15:02 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s16JEva54399000; Thu, 6 Feb 2014 14:14:57 -0500 (EST)
Date: Thu, 06 Feb 2014 14:14:57 -0500
Message-Id: <201402061914.s16JEva54399000@shell01.TheWorld.com>
From: worley@ariadne.com
Sender: worley@ariadne.com
To: Jim Forster <jim.forster@rangenetworks.com>
In-reply-to: <040E1A40-BC55-4CFC-834A-FC958DEFDE25@rangenetworks.com> (jim.forster@rangenetworks.com)
References: <040E1A40-BC55-4CFC-834A-FC958DEFDE25@rangenetworks.com>
Cc: 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: Thu, 06 Feb 2014 19:21:29 -0000

It's certainly an interesting project.

It looks to me like you're looking for support in regard to which SIP
standards the user agent should support.  The best practices of
implementing SIP user agents, as it were.  If you are making an
organized project of this, I can see the value of clearly documenting
it.

> Use of SIP Re-invite for hand-over when a mobile phone moves from
> one BTS to a neighbor

In practice, I would expect INVITE-with-Replaces to be used for
handovers.  But I suspect that you haven't designed how to do
handovers yet.  That's going to be an interesting problem...

Dale