Re: [Mobopts] FW: I-D ACTION:draft-schuetz-tcpm-tcp-rlci-00.txt

Soohong Daniel Park <soohong.park@samsung.com> Thu, 08 June 2006 06:22 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoDuy-00048b-6q; Thu, 08 Jun 2006 02:22:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoDux-00048O-17 for mobopts@irtf.org; Thu, 08 Jun 2006 02:22:55 -0400
Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FoDut-0003Ul-Mh for mobopts@irtf.org; Thu, 08 Jun 2006 02:22:54 -0400
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0J0J00JZU31RUI@mailout2.samsung.com> for mobopts@irtf.org; Thu, 08 Jun 2006 15:22:39 +0900 (KST)
Received: from daniellaptop ([168.219.198.109]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0J0J00CMP31RBL@mmp1.samsung.com> for mobopts@irtf.org; Thu, 08 Jun 2006 15:22:39 +0900 (KST)
Date: Thu, 08 Jun 2006 15:22:46 +0900
From: Soohong Daniel Park <soohong.park@samsung.com>
Subject: Re: [Mobopts] FW: I-D ACTION:draft-schuetz-tcpm-tcp-rlci-00.txt
To: Simon Schuetz <Simon.Schuetz@netlab.nec.de>, tcpm@ietf.org, tsvwg@ietf.org, mobopts@irtf.org
Message-id: <019e01c68ac3$f5694310$6dc6dba8@daniellaptop>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <6D28EBC684A4D94096217AD2FE4008737529AB@venus.office>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc:
X-BeenThere: mobopts@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Mobility Optimizations <mobopts.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@irtf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@irtf.org>
List-Help: <mailto:mobopts-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@irtf.org?subject=subscribe>
Errors-To: mobopts-bounces@irtf.org

Hi Simon, 

I am very much interested in this issue. Also I had a couple
of times for relevant discussion within MobOpts in terms
of MIP option for connectivity-change indication. Now, I
am trying to revise it based on recent feedbacks from IETF.
http://www.watersprings.org/pub/id/draft-daniel-mip-link-characteristic-02.txt

Anyway, one concern occurs in my mind regarding TCP
option for connectivity-change indication. In case host
changes its point of attachment (typically called handover), 
TCP operations will happen after all IP/MIP operation
are completed. It seems a bit serious than MIP option 
from the service disruption. By enabling simple interface 
between MIP and Trnasport laer (TCP), indication included
in MIP option can be used for TCP module. In case we do
not consider handover (for example: wireless interference,
etc), TCP option seems a bit useful than MIP approach.
I am not sure MIP option can be applied for the case above.

Regards.

Daniel (Soohong Daniel Park)
Mobile Convergence Laboratory, SAMSUNG Electronics.

_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts