Re: [Seamoby] DoCoMo Implementation Issues with CTP

Rajeev Koodli <rajeev@iprg.nokia.com> Fri, 20 February 2004 18:00 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 NAA04287 for <seamoby-archive@odin.ietf.org>; Fri, 20 Feb 2004 13:00:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuEwW-0007YO-JA for seamoby-archive@odin.ietf.org; Fri, 20 Feb 2004 13:00:04 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KI04mO029027 for seamoby-archive@odin.ietf.org; Fri, 20 Feb 2004 13:00:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuEwU-0007Xw-HA for seamoby-web-archive@optimus.ietf.org; Fri, 20 Feb 2004 13:00:02 -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 MAA04199 for <seamoby-web-archive@ietf.org>; Fri, 20 Feb 2004 12:59:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuEwS-0003uI-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 13:00:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuEvT-0003om-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 12:59:00 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AuEuV-0003kx-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 12:57:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuEuW-0007Q1-LQ; Fri, 20 Feb 2004 12:58:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuEta-0007Lv-HH for seamoby@optimus.ietf.org; Fri, 20 Feb 2004 12:57:02 -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 MAA04085 for <seamoby@ietf.org>; Fri, 20 Feb 2004 12:56:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuEtY-0003he-00 for seamoby@ietf.org; Fri, 20 Feb 2004 12:57:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuEsa-0003et-00 for seamoby@ietf.org; Fri, 20 Feb 2004 12:56:01 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AuErk-0003aU-00 for seamoby@ietf.org; Fri, 20 Feb 2004 12:55:08 -0500
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i1KHsZf23153; Fri, 20 Feb 2004 09:54:35 -0800
X-mProtect: <200402201754> Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpd61DAUq; Fri, 20 Feb 2004 09:54:33 PST
Message-ID: <403649CF.146A6BFB@iprg.nokia.com>
Date: Fri, 20 Feb 2004 09:54:23 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Soliman Hesham <H.Soliman@flarion.com>
CC: Raghu <dendukuri@docomolabs-usa.com>, seamoby@ietf.org
Subject: Re: [Seamoby] DoCoMo Implementation Issues with CTP
References: <F4410B91C6CC314F9582B1A8E91DC9281BE721@ftmail2000>
Content-Type: text/plain; charset="us-ascii"
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.3 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Hesham,

Soliman Hesham wrote:

> => Just out of curiosity, why do you expect the protocol
> to function in this scenario? If I understand you correctly
> the MN is moving from a v6 AR to a v4 only one. Even if
> CT worked in this scenario, many other things will break.
> Is there a requirement for CT to work here ?
>

The issue is separation of MN's contexts (belonging to
both IPv4 and IPv6 addresses) and the IP addresses used
in the Src, Dst fields in CTP messages. The assumption is
that routers know what IP version to use for transporting
the CTP messages. But that version (i.e., v4) does not necessarily
indicate whether the AR is dual-stacked or not to support
the contexts themselves. If an AR receives contexts it does
not support for whatever reason, it discards them.

Hope this clarifies.

-Rajeev


>
> Hesham
>
>  >
>  > > >
>  > > > > Is the confusion in whether `V' bits also refer to
>  > > > > PAR and NAR addresses ? If so, we should clarify that they
>  > > > > refer to MN's IP addresses only, and that the router address
>  > > > > must be either IPv4 or IPv6 but not both.
>  > > > >
>  > > > This description in the draft may clarify things, but how to
>  > > > identify the IP version AR in CT messages.
>  > > > I guess another V flag for AR might simply things.
>  > > >
>  > >
>  > > Perhaps this is not necessary. (See above)
>  > >
>  > I mean,
>  > In CTAR Message there is pAR IP,
>  > how can nAR know that there is IPv4 or IPv6 address of pAR,
>  > if the V flag is only for MN IP version.
>  >
>  >
>  > regards,
>  > Raghu
>  >
>  > _______________________________________________
>  > Seamoby mailing list
>  > Seamoby@ietf.org
>  > https://www1.ietf.org/mailman/listinfo/seamoby
>  >
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby


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