Re: [Seamoby] CT Requirements Comments from IESG

"James Kempf" <kempf@docomolabs-usa.com> Thu, 11 July 2002 20:06 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 QAA03805 for <seamoby-archive@odin.ietf.org>; Thu, 11 Jul 2002 16:06:53 -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 QAA13649; Thu, 11 Jul 2002 16:06:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA13620 for <seamoby@optimus.ietf.org>; Thu, 11 Jul 2002 16:06:06 -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 QAA03709 for <seamoby@ietf.org>; Thu, 11 Jul 2002 16:05:12 -0400 (EDT)
Message-ID: <02ff01c22916$26e0c800$4f6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: Gary Kenward <gkenward@nortelnetworks.com>, seamoby@ietf.org
References: <9FBD322B7824D511B36900508BF93C9C01AA4C0C@zcard031.ca.nortel.com>
Subject: Re: [Seamoby] CT Requirements Comments from IESG
Date: Thu, 11 Jul 2002 13:04:23 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
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

Gary,

All we need to do is agree on some wording that is precise enough for the IESG. I like your wording. Can you please
substitute "bit order and bit values" for "meaning" in the requirement? Unless there is any objection from the WG.

            jak

----- Original Message -----
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>; <seamoby@ietf.org>
Sent: Thursday, July 11, 2002 12:47 PM
Subject: RE: [Seamoby] CT Requirements Comments from IESG


> You call it fidelity, I call it data integrity.
> I've seen "data integrity" used in publications
> (no, I cannot quote references).
>
> What we need is a term that everyone, including the
> IESG, can agree upon.
>
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: July 11, 2002 12:22
> > To: Kenward, Gary [WDLN2:AN10:EXCH]; seamoby@ietf.org
> > Subject: Re: [Seamoby] CT Requirements Comments from IESG
> >
> >
> > > 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.
> > >
> >
> > So this requirement is talking about transmission fidelity? I
> > sure would not have guessed that from reading it. I thought it
> > intended to talk about usability.
> >
> > I would suggest that the wording you have above is really a
> > lot more precise that what is currently in the spec.
> >
> > Any other comments? Could we substitute Gary's wording above
> > for "meaning" in the current requirement.
> >
> >             jak
> >
> >
>


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