[Seamoby] CT Requirements Comments from IESG

"James Kempf" <kempf@docomolabs-usa.com> Tue, 09 July 2002 17:31 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 NAA04526 for <seamoby-archive@odin.ietf.org>; Tue, 9 Jul 2002 13:31:09 -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 NAA23375; Tue, 9 Jul 2002 13:23:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA23350 for <seamoby@optimus.ietf.org>; Tue, 9 Jul 2002 13:23:47 -0400 (EDT)
Received: from fridge.docomolabs-usa.com (fwuser@key1.docomolabs-usa.com [216.98.102.225]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04369 for <seamoby@ietf.org>; Tue, 9 Jul 2002 13:22:55 -0400 (EDT)
Message-ID: <011501c2276d$28cd0ac0$4f6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: seamoby@ietf.org
Date: Tue, 09 Jul 2002 10:22:10 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] CT Requirements Comments from IESG
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

I have finally managed to get a couple of technical comments out of the IESG on the CT requirements. More are coming but I think it
might be worthwhile to start discussing these.

1) The requirements say nothing about the maintenance of dynamic context. Something must be said, is this out of scope or what? Gary
tells me that supporting dynamic context was rejected by the working group, but it seems like we cannot punt on at least saying
something about this issue.

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?

I've asked Gary to lead a discussion on these two issues, please send comments to the list.

            jak


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