Re: [Seamoby] CT Requirements Comments from IESG

"James Kempf" <kempf@docomolabs-usa.com> Thu, 11 July 2002 16:27 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 MAA23931 for <seamoby-archive@odin.ietf.org>; Thu, 11 Jul 2002 12:27:04 -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 MAA23287; Thu, 11 Jul 2002 12:24:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23260 for <seamoby@optimus.ietf.org>; Thu, 11 Jul 2002 12:24:03 -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 MAA23749 for <seamoby@ietf.org>; Thu, 11 Jul 2002 12:23:09 -0400 (EDT)
Message-ID: <00ba01c228f7$22b3b130$4f6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: Gary Kenward <gkenward@nortelnetworks.com>, seamoby@ietf.org
References: <9FBD322B7824D511B36900508BF93C9C01AA4C03@zcard031.ca.nortel.com>
Subject: Re: [Seamoby] CT Requirements Comments from IESG
Date: Thu, 11 Jul 2002 09:22:22 -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

> 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