Re: [Seamoby] DoCoMo Implementation Issues with CTP

"James Kempf" <kempf@docomolabs-usa.com> Fri, 20 February 2004 17:48 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 MAA03658 for <seamoby-archive@odin.ietf.org>; Fri, 20 Feb 2004 12:48: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 1AuEku-0005ws-5r for seamoby-archive@odin.ietf.org; Fri, 20 Feb 2004 12:48:04 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KHm40b022860 for seamoby-archive@odin.ietf.org; Fri, 20 Feb 2004 12:48:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuEku-0005wC-1O for seamoby-web-archive@optimus.ietf.org; Fri, 20 Feb 2004 12:48: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 MAA03579 for <seamoby-web-archive@ietf.org>; Fri, 20 Feb 2004 12:47:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuEks-00037H-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 12:48:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuEju-0002zw-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 12:47:02 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AuEiv-0002tn-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 12:46:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuEiw-0005cA-Ru; Fri, 20 Feb 2004 12:46:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuEiB-0005YM-Ca for seamoby@optimus.ietf.org; Fri, 20 Feb 2004 12:45:15 -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 MAA03437 for <seamoby@ietf.org>; Fri, 20 Feb 2004 12:45:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuEi9-0002nT-00 for seamoby@ietf.org; Fri, 20 Feb 2004 12:45:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuEhC-0002d9-00 for seamoby@ietf.org; Fri, 20 Feb 2004 12:44:15 -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 1AuEfq-0002No-00 for seamoby@ietf.org; Fri, 20 Feb 2004 12:42:51 -0500
Message-ID: <04cb01c3f7d9$074433e0$936015ac@dclkempt40>
From: James Kempf <kempf@docomolabs-usa.com>
To: Soliman Hesham <H.Soliman@flarion.com>, Raghu <dendukuri@docomolabs-usa.com>, seamoby@ietf.org
References: <F4410B91C6CC314F9582B1A8E91DC9281BE721@ftmail2000>
Subject: Re: [Seamoby] DoCoMo Implementation Issues with CTP
Date: Fri, 20 Feb 2004 09:43:19 -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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>  > > Well, CTAR includes MN's IP(v4,v6) addresses. So does
>  > > PCTD. So, nAR can still match the contexts. Since the token
>  > > does not include PAR's address, verification can still be
>  > > done.
>  > >
>  > I think I didnot make my point clear.
>  > MN is claiming that it came from one pAR IP Address(IPV6),
>  > but the nAR has a PCTD that says pAR IP is different(IPv4),
>  > How can nAR verify the Token without matching the pAR IP ?
>
> => 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 ?
>

I believe there is no requirement for CTP between IP versions. It might be
possible, depending on the context type, but I don't think it should be
required in general.

Perhaps the draft should specifically forbid this?

            jak


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