RE: [Seamoby] CT Requirements Comments from IESG

"Gary Kenward" <gkenward@nortelnetworks.com> Thu, 11 July 2002 14:39 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 KAA19323 for <seamoby-archive@odin.ietf.org>; Thu, 11 Jul 2002 10:39:39 -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 KAA11624; Thu, 11 Jul 2002 10:35:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11600 for <seamoby@optimus.ietf.org>; Thu, 11 Jul 2002 10:35:01 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19205 for <seamoby@ietf.org>; Thu, 11 Jul 2002 10:34:07 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7]) by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g6BEY7H14264; Thu, 11 Jul 2002 10:34:07 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <NYVCCSB0>; Thu, 11 Jul 2002 10:34:07 -0400
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4C03@zcard031.ca.nortel.com>
From: Gary Kenward <gkenward@nortelnetworks.com>
To: 'James Kempf' <kempf@docomolabs-usa.com>, seamoby@ietf.org
Subject: RE: [Seamoby] CT Requirements Comments from IESG
Date: Thu, 11 Jul 2002 10:34:04 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C228E7.799DF86C"
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 understand your intentions James, but as a requirement,
preserving "intended usability" does not make any sense to
me. How does on test that a solution is in conformance to 
this requirement? 

Just to be clear, I don't believe that "preserving meaning"
is a real requirement either. It is also not testable.

I am not just arguing semantics here, if we are going to 
revise these requirements, let's make sure that they are
real requirements.

Perhaps the actual answer is to state exactly what was intended
originally: that the bit order and bit values have to arrive exactly
as they were transmitted.

gary

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: July 10, 2002 18:12
> To: Kenward, Gary [WDLN2:AN10:EXCH]; seamoby@ietf.org
> Subject: Re: [Seamoby] CT Requirements Comments from IESG
> 
> 
> It's not the same definition
> 
> I suggest:
> 
> 5.5.2 A context update MUST preserve the integrity, and thus the
>       intended useability, of the context at each receiving AR.
> 
>             jak
> 
> 
> 
> ----- Original Message ----- 
> From: "Gary Kenward" <gkenward@nortelnetworks.com>
> To: "'James Kempf'" <kempf@docomolabs-usa.com>; <seamoby@ietf.org>
> Sent: Wednesday, July 10, 2002 11:31 AM
> Subject: RE: [Seamoby] CT Requirements Comments from IESG
> 
> 
> > A word is often defined as 4 bytes, or 32 bits :-) in many
> > computational architectures and programming languages.
> > 
> > Neither here nor there, really. I'll wait for further
> > suggestions/comments on the working of 5.5.2 from the wg.
> > 
> > Gary
> > 
> > > -----Original Message-----
> > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > Sent: July 10, 2002 14:12
> > > To: Kenward, Gary [WDLN2:AN10:EXCH]; seamoby@ietf.org
> > > Subject: Re: [Seamoby] CT Requirements Comments from IESG
> > > 
> > > 
> > > "Word" or "phrase", from the definition you cite, typically 
> > > applies to natural language. I have not heard anyone use that
> > > terminology for machine readable information, even in 
> > > programming languages.
> > > 
> > >             jak
> > > 
> > > ----- Original Message -----
> > > From: "Gary Kenward" <gkenward@nortelnetworks.com>
> > > To: "'James Kempf'" <kempf@docomolabs-usa.com>; <seamoby@ietf.org>
> > > Sent: Wednesday, July 10, 2002 9:58 AM
> > > Subject: RE: [Seamoby] CT Requirements Comments from IESG
> > > 
> > > 
> > 
> > *snip*
> > 
> > > 
> > 
> 
>