IETF Logo Mail Archive

Re: [Seamoby] DoCoMo Implementation Issues with CTP

Rajeev Koodli <rajeev@iprg.nokia.com> Fri, 20 February 2004 19:25 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 OAA08040 for <seamoby-archive@odin.ietf.org>; Fri, 20 Feb 2004 14:25:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuGH0-0007Zd-7i for seamoby-archive@odin.ietf.org; Fri, 20 Feb 2004 14:25:18 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KJPI2W029107 for seamoby-archive@odin.ietf.org; Fri, 20 Feb 2004 14:25:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuGH0-0007ZO-4R for seamoby-web-archive@optimus.ietf.org; Fri, 20 Feb 2004 14:25:18 -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 OAA08027 for <seamoby-web-archive@ietf.org>; Fri, 20 Feb 2004 14:25:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuGGx-00028z-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 14:25:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuGGH-00024z-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 14:24:33 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AuGFj-0001yj-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 14:23:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuGFl-0007Np-LR; Fri, 20 Feb 2004 14:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuGEv-0007Je-Ux for seamoby@optimus.ietf.org; Fri, 20 Feb 2004 14:23:09 -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 OAA07757 for <seamoby@ietf.org>; Fri, 20 Feb 2004 14:23:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuGEt-0001sJ-00 for seamoby@ietf.org; Fri, 20 Feb 2004 14:23:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuGDw-0001kG-00 for seamoby@ietf.org; Fri, 20 Feb 2004 14:22:08 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AuGD3-0001a5-00 for seamoby@ietf.org; Fri, 20 Feb 2004 14:21:14 -0500
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i1KJKeP24444; Fri, 20 Feb 2004 11:20:40 -0800
X-mProtect: <200402201920> 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 smtpdJMt0y6; Fri, 20 Feb 2004 11:20:37 PST
Message-ID: <40365DFB.1EF60B38@iprg.nokia.com>
Date: Fri, 20 Feb 2004 11:20:27 -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: Raghu <dendukuri@docomolabs-usa.com>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] DoCoMo Implementation Issues with CTP
References: <059c01c3f5a4$63e9e360$936015ac@dclkempt40> <40341585.127EE1A7@iprg.nokia.com> <023601c3f744$49c01df0$1c6015ac@dcldendukuri> <40355C74.22D0A058@iprg.nokia.com> <024601c3f750$0902ab00$1c6015ac@dcldendukuri> <40356445.C6D3270@iprg.nokia.com> <02
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

Raghu wrote:

> > Why is it necessary to know PAR's IP when the contexts
> > are already there ?
> For two reasons,
> 1. To avoid picking up of any Stale contexts due to frequent moving of MN.
>

I cannot readily figure out how PAR's IP helps here..


> 2. Security.
>

If the token matches, the MN must have had an SA
with PAR.

-Rajeev


>
> regards,
> Raghu


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

v2.23.0 | Report a Bug | By Email