Re: [Sipping] Request for Open discussion about SIP mobility

Ashutosh Dutta <adutta@research.telcordia.com> Mon, 05 May 2008 14:05 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B20A83A6B65; Mon, 5 May 2008 07:05:01 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E63003A68D5 for <sipping@core3.amsl.com>; Mon, 5 May 2008 07:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gZPibzylSsmN for <sipping@core3.amsl.com>; Mon, 5 May 2008 07:04:58 -0700 (PDT)
Received: from flower.research.telcordia.com (flower.research.telcordia.com [128.96.41.5]) by core3.amsl.com (Postfix) with ESMTP id 63B303A69DB for <sipping@ietf.org>; Mon, 5 May 2008 07:04:58 -0700 (PDT)
Received: from [128.96.58.190] (vpntnlA190.research.telcordia.com [128.96.58.190]) by flower.research.telcordia.com (8.14.2/8.14.2) with ESMTP id m45E540a003903; Mon, 5 May 2008 10:05:04 -0400 (EDT)
Message-ID: <481F1407.1020400@research.telcordia.com>
Date: Mon, 05 May 2008 10:04:55 -0400
From: Ashutosh Dutta <adutta@research.telcordia.com>
User-Agent: Thunderbird 1.5.0.14 (Windows/20071210)
MIME-Version: 1.0
To: Haruki Izumikawa <izumikawa@kddilabs.jp>
References: <4819667D.9060600@kddilabs.jp>
In-Reply-To: <4819667D.9060600@kddilabs.jp>
Cc: sipping@ietf.org
Subject: Re: [Sipping] Request for Open discussion about SIP mobility
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

Haruki,
        Thanks for bringing this discussion up again. Few years back we 
did create a mailing list and web page to add some of the references 
with respect to SIP-based mobility work. This reference list is not 
up-to-date by any means and needs to be updated as people have done more 
work on this recently.

Here is the pointer to the archive that has some relevant materials. I 
can update this list with more recent papers in this area.

http://www.argreenhouse.com/SIP-mobile/

Regards
Ashutosh


Haruki Izumikawa wrote:
> Hello folks,
> 
> I'd like to have an open discussion about SIP-based mobility in this ML.
> Mobility managements using SIP have been actively studied and developed
> worldwide since "Mobility Support Using SIP" (by Elin and Henning) was
> published. SIP-based mobility would have strong advantages such as its
> great affinity for an application as well as flexibility, i.e., terminal
> mobility can be optimally supported independent from underlying network.
> On the other hand, despite many advantages, it is not used for
> large-scale commercial yet. In addition, the discussion about SIP-based
> mobility in IETF seems to be undynamic.
> These days, a multimode terminal is getting popular. Each access
> networks, e.g., cellular and WLAN, have different characteristics in
> terms of throughput or delay. In such a heterogeneous network, SIP
> becomes more useful tool for mobility management because of its
> flexibility. The quality of a multimedia service can be adaptively
> changed in accordance with a nature of an access networks even after
> changing an access network. I think it is time to resume discussing
> about SIP-based mobility. For your information, I have submitted I-D
> regarding seamless session handoff by SIP-based bicasting.
> http://www.ietf.org/internet-drafts/draft-izumikawa-sipping-sipbicast-01.txt
> I would be happy to hear frank opinions of SIP specialists.
> 
> Best regards,
> 
> Haruki
> 
> 
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP