IETF Logo Mail Archive

Re: [Seamoby] DoCoMo Implementation Issues with CTP

"Raghu" <dendukuri@docomolabs-usa.com> Fri, 20 February 2004 19:19 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 OAA07626 for <seamoby-archive@odin.ietf.org>; Fri, 20 Feb 2004 14:19:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuGB1-0006hI-Ia for seamoby-archive@odin.ietf.org; Fri, 20 Feb 2004 14:19:07 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KJJ7p4025738 for seamoby-archive@odin.ietf.org; Fri, 20 Feb 2004 14:19:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuGB1-0006h3-E7 for seamoby-web-archive@optimus.ietf.org; Fri, 20 Feb 2004 14:19:07 -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 OAA07606 for <seamoby-web-archive@ietf.org>; Fri, 20 Feb 2004 14:19:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuGAy-0001RU-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 14:19:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuGA5-0001Ov-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 14:18:10 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AuG9u-0001M6-00 for seamoby-web-archive@ietf.org; Fri, 20 Feb 2004 14:17:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuG9w-0006XA-LC; Fri, 20 Feb 2004 14:18:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuG97-0006O4-Vv for seamoby@optimus.ietf.org; Fri, 20 Feb 2004 14:17:10 -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 OAA07552 for <seamoby@ietf.org>; Fri, 20 Feb 2004 14:17:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuG95-0001Kd-00 for seamoby@ietf.org; Fri, 20 Feb 2004 14:17:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuG8G-0001Hq-00 for seamoby@ietf.org; Fri, 20 Feb 2004 14:16:16 -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 1AuG7W-0001EG-00 for seamoby@ietf.org; Fri, 20 Feb 2004 14:15:30 -0500
Message-ID: <02ea01c3f7e5$b9ce6ab0$1c6015ac@dcldendukuri>
From: Raghu <dendukuri@docomolabs-usa.com>
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Cc: seamoby@ietf.org
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 <40365AEA.7EA35957@iprg.nokia.com>
Subject: Re: [Seamoby] DoCoMo Implementation Issues with CTP
Date: Fri, 20 Feb 2004 11:14:13 -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

> 
> Raghu wrote:
> 
> > > (Also, note that you could not match contexts using PAR's IP
> > > address since that could yield many contexts corresponding to
> > > multiple MNs.)
> > >
> > I was also under impression that both (PAR IP & MN IP)
> > from CTAR & PCTD must match before verifying the token.
> > Otherwise how can nAR determine from
> > which pAR a MN is comming from ?
> >
> 
> 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.
2. Security. 

regards,
Raghu


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

v2.23.0 | Report a Bug | By Email