Re: [Seamoby] Paging Protocol Decision Description

"James Kempf" <kempf@docomolabs-usa.com> Thu, 17 January 2002 17:54 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 MAA28290 for <seamoby-archive@odin.ietf.org>; Thu, 17 Jan 2002 12:54:59 -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 MAA14945; Thu, 17 Jan 2002 12:43:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA14913 for <seamoby@ns.ietf.org>; Thu, 17 Jan 2002 12:43:53 -0500 (EST)
Received: from fridge.docomo-usa.com (fridge.docomo-usa.com [216.98.102.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27899 for <seamoby@ietf.org>; Thu, 17 Jan 2002 12:43:51 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126]) by fridge.docomo-usa.com (8.11.3/8.11.3) with SMTP id g0HHhJe28351; Thu, 17 Jan 2002 09:43:19 -0800 (PST)
Message-ID: <00cc01c19f7e$3a410580$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: "Pat R. Calhoun" <pcalhoun@bstormnetworks.com>, 'Behcet Sarikaya' <behcet.sarikaya@alcatel.com>
Cc: seamoby@ietf.org
References: <DC6C13921CCAFB49BCB8461164A3F4E38D234E@EXCHSRV.stormventures.com>
Subject: Re: [Seamoby] Paging Protocol Decision Description
Date: Thu, 17 Jan 2002 09:41:43 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
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

Pat,

> To be honest, I don't see how this numbering scheme came into play.
> It is the first time that I've ever heard of it within the IETF. If I
> would have known that the evaluation team was doing this, I would
> have stopped it.
>  
> The reason for the evaluation is to find the candidate protocol that
> most closely matches the requirements, which the WG agreed upon. This
> would ensure that there is less work involved in getting the protocol
> up to par.
>  
> That was the process (and the same process has been used in many
> other WGs)
>  

It was just something I cooked up to allow the evaluation team
to quickly summarize the comparison between the different
protocols on individual requirements. It was never intended
to be used as an absolute measure of quality. I need to
put some text into the draft to this effect. 

You can rest assured, that I will *never* use something like
this again, and we should probably inform other WGs
that they shouldn't either! The danger of misinterpretation
is too great.

            jak



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