IETF Logo Mail Archive

Re: [Seamoby] DoCoMo Implementation Issues with CTP

"Raghu" <dendukuri@docomolabs-usa.com> Fri, 20 February 2004 18:13 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04852 for <seamoby-archive@odin.ietf.org>; Fri, 20 Feb 2004 13:13:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuF95-0008KD-PW for seamoby-archive@odin.ietf.org; Fri, 20 Feb 2004 13:13:03 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KID3Zm031995 for seamoby-archive@odin.ietf.org; Fri, 20 Feb 2004 13:13:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuF95-0008Jy-Kx for seamoby-web-archive@optimus.ietf.org; Fri, 20 Feb 2004 13:13:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04821 for <seamoby-web-archive@ietf.org>; Fri, 20 Feb 2004 13:12:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuF93-0004qx-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 13:13:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuF85-0004mr-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 13:12:01 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AuF77-0004jC-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 13:11:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuF78-0008AI-IP; Fri, 20 Feb 2004 13:11:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuF6C-00089W-55 for seamoby@optimus.ietf.org; Fri, 20 Feb 2004 13:10:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04741 for <seamoby@ietf.org>; Fri, 20 Feb 2004 13:09:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuF6A-0004g4-00 for seamoby@ietf.org; Fri, 20 Feb 2004 13:10:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuF5A-0004cS-00 for seamoby@ietf.org; Fri, 20 Feb 2004 13:09:01 -0500
Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx with esmtp (Exim 4.12) id 1AuF4G-0004YX-00 for seamoby@ietf.org; Fri, 20 Feb 2004 13:08:05 -0500
Message-ID: <02be01c3f7dc$4d7fc1f0$1c6015ac@dcldendukuri>
From: Raghu <dendukuri@docomolabs-usa.com>
To: Soliman Hesham <H.Soliman@flarion.com>, seamoby@ietf.org
References: <F4410B91C6CC314F9582B1A8E91DC9281BE722@ftmail2000>
Subject: Re: [Seamoby] DoCoMo Implementation Issues with CTP
Date: Fri, 20 Feb 2004 10:06:46 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>  > 
>  > I am expecting nothing to break in CTP when MN
>  > moves from v6 to v4 only AR. 
>  > Can you please provide some examples that break.
> 
> => How do you expect the 2 ARs to talk to each other
> if they don't have a common IP version? If they do
> then sure CTP will work but nothing else will, like: 
> - connectivity (existing connections) of the MN using its v6 address? 
> - Mobile IPv6 signalling ? 
> This is one of the motivations for the dual stack MIP
> work that we discussed on MIP6 and v6ops list some time
> ago.
> 
I meant v6 networks always understand v4 too.
I didnot mean from v6 only to v4 only networks.

regards,
Raghu


_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby

v2.23.0 | Report a Bug | By Email