IETF Logo Mail Archive

Re: [Seamoby] CT Requirements Comments from IESG

Vijay Devarapalli <vijayd@iprg.nokia.com> Tue, 09 July 2002 20:08 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15517 for <seamoby-archive@odin.ietf.org>; Tue, 9 Jul 2002 16:08:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA04428; Tue, 9 Jul 2002 16:01:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA04399 for <seamoby@optimus.ietf.org>; Tue, 9 Jul 2002 16:01:40 -0400 (EDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15337 for <seamoby@ietf.org>; Tue, 9 Jul 2002 16:00:44 -0400 (EDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id NAA04136; Tue, 9 Jul 2002 13:00:59 -0700 (PDT)
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g69K0x414931; Tue, 9 Jul 2002 13:00:59 -0700
X-mProtect: <200207092000> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.94, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdGItpus; Tue, 09 Jul 2002 13:00:57 PDT
Message-ID: <3D2B40F9.4F9699CF@iprg.nokia.com>
Date: Tue, 09 Jul 2002 13:00:57 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] CT Requirements Comments from IESG
References: <011501c2276d$28cd0ac0$4f6015ac@T23KEMPF>
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-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

hi Jim,

James Kempf wrote:

> 2) The requirements say nothing about context which must be modified on the new router in order to be useful. An example is ROHC
> context when the mobile obtains a new care of address. How would the CT protocol handle this?

the context transfer protocol should not worry about this at all.
it is specific to each feature. for ROHC, the IP addresses have
to be changed. for IPsec Security Associations, the SPIs maybe
need to be changed in addition to the IP addresses.

regards
Vijay

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

v2.38.3 | Report a Bug | By Email | System Status