RE: [Seamoby] RE: Removing CT Requirements

[Nakhjiri Madjid-MNAKHJI1 <[e-mail]>]

Without getting into details (we had debated some of this a lot), I don't
want to remove them.
You can work on rewording it, but removing it, make CT much more complex.
 
Madjid

-----Original Message-----
From: George Tsirtsis [mailto:[e-mail]]
Sent: Monday, January 07, 2002 4:41 AM
To: 'Gary Kenward'; 'James Kempf'; George Tsirtsis
Cc: [e-mail]
Subject: [Seamoby] RE: Removing CT Requirements


yes I could say this is ambiguous and unnecessary since I can clearly claim
that error rates provided by almost all links today are good enough....
 
George

-----Original Message-----
From: Gary Kenward [mailto:[e-mail]]
Sent: Friday, January 04, 2002 6:04 PM
To: 'James Kempf'; George Tsirtsis
Cc: [e-mail]
Subject: RE: Removing CT Requirements



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:[e-mail]
<mailto:[e-mail]> ] 
> Sent: January 4, 2002 12:31 
> To: Kenward, Gary [WDLN2:AN10:EXCH]; George Tsirtsis 
> Cc: [e-mail] 
> 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 
> 
>