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

Haruki Izumikawa <izumikawa@kddilabs.jp> Sat, 10 May 2008 15:44 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 [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E07CE3A6825; Sat, 10 May 2008 08:44:48 -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 CB5543A6825 for <sipping@core3.amsl.com>; Sat, 10 May 2008 08:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 aeCUMaKqkBSx for <sipping@core3.amsl.com>; Sat, 10 May 2008 08:44:46 -0700 (PDT)
Received: from mandala.kddilabs.jp (unknown [IPv6:2001:200:601:12:230:48ff:fe22:3a84]) by core3.amsl.com (Postfix) with ESMTP id 0DCE43A65A5 for <sipping@ietf.org>; Sat, 10 May 2008 08:44:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mandala.kddilabs.jp (Postfix) with ESMTP id 80F78EC95C; Sat, 10 May 2008 04:43:01 +0900 (JST)
Received: from wcg.radio.kddilabs.jp (wcg.radio.kddilabs.jp [172.19.84.3]) by mandala.kddilabs.jp (Postfix) with ESMTP id AF1C6EC971; Sat, 10 May 2008 04:43:00 +0900 (JST)
Received: from [127.0.0.1] (c012.vpn.kddilabs.jp [172.19.87.12]) by wcg.radio.kddilabs.jp (Postfix) with ESMTP id 416BE160047; Sat, 10 May 2008 04:42:52 +0900 (JST)
Message-ID: <4824A93F.8040204@kddilabs.jp>
Date: Sat, 10 May 2008 04:42:55 +0900
From: Haruki Izumikawa <izumikawa@kddilabs.jp>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Ashutosh Dutta <adutta@research.telcordia.com>
References: <4819667D.9060600@kddilabs.jp> <481F1407.1020400@research.telcordia.com> <4824287D.1080304@kddilabs.jp> <48247433.9030601@research.telcordia.com>
In-Reply-To: <48247433.9030601@research.telcordia.com>
X-Virus-Scanned: by amavisd-new
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

Thanks, Ashutosh.
I understood what's been going on with the discussion of SIP mobility. 
It seems that SIP mobility was not needed so much at that time. But now, 
SIP mobility have been actively studied and developed recently as you 
commented. In addition, all-IP NW environments would be just around the 
corner and SIP mobility will become more important technology to support 
flexibly mobile users. So, I also think that it's time to restart some 
discussion regarding SIP-based terminal mobility here.

Best wishes,

Haruki


Ashutosh Dutta wrote:
> Dear Haruki,
>             If I remember correctly, the conclusion of the BAR BOF was 
> to discuss some of these issues in the SIPPING working group that got 
> formed around the same time.
> 
>     Thereafter, during 51st IETF in July 2001, we had submitted few 
> drafts with respect to SIP-based terminal mobility (requirement 
> document, terminal-mobility solution documents). During the discussion 
> in SIPPING WG, folks within WG thought it was to early to discuss the 
> SIP-based mobility stuff at that time. These old drafts can still be 
> found at the same archive along with other reference materials 
> (http://www.argreenhouse.com/SIP-mobile/Reference.html). However, some 
> of these documents are little outdated now. Subsequently, over the years 
> there have been a lot of useful work with respect to SIP-based mobility 
> (e.g., session mobility, terminal mobility) that are published in many 
> conferences/magazines/journals.
> 
> While there is already a draft under RFC queue to support  SIP-based 
> session mobility, it would be good to see some discussion to support 
> SIP-based terminal mobility in the SIPPING WG.
> 
> Regards
> Ashutosh
> 
> 
> 
> Haruki Izumikawa wrote:
>> Hi all,
>>
>> Will someone tell me the conclusion of the past discussion concerning 
>> SIP mobility. I have read the "SIP-Mobile Minutes" in 50th IETF and 
>> understood the outline of the discussion. But, I cannot find the 
>> conclusion of the meeting. So, I would be happy especially to hear the 
>> conclusion.
>>
>> Regards,
>>
>> Haruki
>>
>>
>>
>> Ashutosh Dutta wrote:
>>> 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
>>>>
>>>>
>>>
>>
> 

-- 
Haruki Izumikawa
KDDI R&D Laboratories
_______________________________________________
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