[Seamoby] Moving forward with paging

"Pat R. Calhoun" <pcalhoun@bstormnetworks.com> Fri, 01 February 2002 18:32 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 NAA06944 for <seamoby-archive@odin.ietf.org>; Fri, 1 Feb 2002 13:32: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 NAA01635; Fri, 1 Feb 2002 13:13: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 NAA01607 for <seamoby@optimus.ietf.org>; Fri, 1 Feb 2002 13:13:53 -0500 (EST)
Received: from EXCHSRV.stormventures.com ([65.107.25.226]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06407 for <seamoby@ietf.org>; Fri, 1 Feb 2002 13:13:49 -0500 (EST)
Received: by EXCHSRV.stormventures.com with Internet Mail Service (5.5.2653.19) id <1B7WAVVF>; Fri, 1 Feb 2002 10:13:22 -0800
Message-ID: <DC6C13921CCAFB49BCB8461164A3F4E38D24D9@EXCHSRV.stormventures.com>
From: "Pat R. Calhoun" <pcalhoun@bstormnetworks.com>
To: seamoby@ietf.org
Date: Fri, 01 Feb 2002 10:13:20 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1AB4C.21697C70"
Subject: [Seamoby] Moving forward with paging
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

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

All,

As many of you know, last week we asked the WG for their comments on
how to proceed with the paging work.  A summary of the comments that
came in is:

       Start from a known protocol - 5
       Reopen selection phase - 3  
       Design team to start from scratch - 2  
       Drop the work altogether - 1  

Many did not give opinions obviously, and these numbers are not to be
viewed as a "vote" (our AD reminds us that rough consensus is not
voting).  But considering the 5 and 3, there is at least a preference
for starting with a candidate, rather 
than from scratch.

So the issue that needs to be resolved is which protocol should be
used, since the protocol assessment wasn't conclusive, the chairs had
picked one based on the findings of the assessment team. However,
since an (admitedly useless) numbering rating scheme was used in the
assessment, it was hard to really determine which protocol should be
used.

After discussing the matter ourselves, and with our AD, Allison, we
decided to revise the paging assessment draft and remove the useless
numerical ratings. This means that each draft must now be assessed
using just technical merit. Further, a new section has been added to
the document stating the chairs' basis (including charter
reasons) for viewing the Renker draft as the starting point most
likely to get us to the requirements and to a IETF-quality
protocol...

So we are calling a WG last call on the assessment document
(draft-ietf-seamoby-paging-protocol-assessment-01.txt). We encourage
folks to provide their *technical* comments on the draft should they
believe that the findings of the assessment team are incorrect. We do
ask the WG members to kindly refrain from posting any process related
comments, since it detracts us from achieving our milestones. Once
the WG last call is complete, we will collect the comments that have
WG concensus and make any necessary changes to the draft. The WG last
call ends February 25th.

The end result is that the WG will get to decide which document is to
be used as the *starting point*.

Thanks for your patience,

PatC & jak

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPFrawTN1fXKoxmisEQIaWQCfYIis0Nsd52Q0Xv7wA77/RWn4J9IAn0t2
FoREK4Kavht9sSs7VjZIhLlV
=EmAk
-----END PGP SIGNATURE-----