[Seamoby] RE: Removing CT Requirements
"Gary Kenward" <gkenward@nortelnetworks.com> Fri, 04 January 2002 18:46 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 NAA10855 for <seamoby-archive@odin.ietf.org>; Fri, 4 Jan 2002 13:46:02 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA02644; Fri, 4 Jan 2002 13:34:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA02613 for <seamoby@ns.ietf.org>; Fri, 4 Jan 2002 13:34:18 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10448 for <seamoby@ietf.org>; Fri, 4 Jan 2002 13:34:15 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57]) by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g04IXhE05585; Fri, 4 Jan 2002 13:33:44 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7]) by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g04IXfA29728; Fri, 4 Jan 2002 13:33:42 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <CJV75RF5>; Fri, 4 Jan 2002 13:32:04 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA473D@zcard031.ca.nortel.com>
From: Gary Kenward <gkenward@nortelnetworks.com>
To: 'James Kempf' <kempf@docomolabs-usa.com>, George Tsirtsis <G.Tsirtsis@flarion.com>
Cc: seamoby@ietf.org
Date: Fri, 04 Jan 2002 13:03:54 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1954A.2C7554D0"
Subject: [Seamoby] RE: Removing CT Requirements
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
I would like to know from George if he believes 5.5.2 is irrelevant, or simply ambiguously worded. I believe (and I suspect that George may concur) that error protection for the context is required (consider the possible impact of attempting to install or use erroneous context at an AR), and that it is important to clearly identify that requirement (particularly given that there are no transport requirements in the id). Gary > -----Original Message----- > From: James Kempf [mailto:kempf@docomolabs-usa.com] > Sent: January 4, 2002 12:31 > To: Kenward, Gary [WDLN2:AN10:EXCH]; George Tsirtsis > Cc: seamoby@ietf.org > Subject: Removing CT Requirements > > > It seems to me like George is making a specific request as part of the > WG last call that the following > requirements be removed from the document: > > 4.12 The context information to be transferred MUST be > available at the > AR performing the transfer, prior to the initiation of a > given phase of > the context transfer. > 4.13 The context transfer solution WILL NOT verify the context > information prior to transfer. > 4.15 The context transfer solution MAY include methods for > interworking > with non-IETF mobility solutions. > 5.5.2 A context update MUST preserve the integrity, and thus the > meaning, of the context at each receiving AR." > > > based on their being impossible to interpret meaningfully in an > implementation and deployment context or to their being obvious. > > Rather than spend another week exchanging email on this > topic, I'd like > to ask the WG at this time if there > is anyone else who feels that one or several of these requirements > should be removed before we send this document to the IESG? > > jak > >
- [Seamoby] RE: Removing CT Requirements Gary Kenward
- [Seamoby] RE: Removing CT Requirements George Tsirtsis
- RE: [Seamoby] RE: Removing CT Requirements Nakhjiri Madjid-MNAKHJI1
- RE: [Seamoby] RE: Removing CT Requirements Gary Kenward