RE: [Seamoby] Moving forward with paging
john.loughney@nokia.com Mon, 04 February 2002 05: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 AAA06135 for <seamoby-archive@odin.ietf.org>; Mon, 4 Feb 2002 00:32:24 -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 AAA27085; Mon, 4 Feb 2002 00:10:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA27060 for <seamoby@optimus.ietf.org>; Mon, 4 Feb 2002 00:10:27 -0500 (EST)
Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05906 for <seamoby@ietf.org>; Mon, 4 Feb 2002 00:10:23 -0500 (EST)
From: john.loughney@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x3.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g145Ahi27554 for <seamoby@ietf.org>; Mon, 4 Feb 2002 07:10:43 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T58dc6362c7ac158f21081@esvir01nok.ntc.nokia.com>; Mon, 4 Feb 2002 07:10:22 +0200
Received: from esebe004.NOE.Nokia.com ([172.21.138.44]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779); Mon, 4 Feb 2002 07:09:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1AD3A.2A711358"
Subject: RE: [Seamoby] Moving forward with paging
Date: Mon, 04 Feb 2002 07:09:47 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D9549@esebe004.NOE.Nokia.com>
Thread-Topic: [Seamoby] Moving forward with paging
Thread-Index: AcGrTER6ZZ16ch1TSTeTw9ZlR7u0GQB7WT8Q
To: pcalhoun@bstormnetworks.com, seamoby@ietf.org
X-OriginalArrivalTime: 04 Feb 2002 05:09:47.0977 (UTC) FILETIME=[2ABC3390:01C1AD3A]
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
Hi Pat, Sorry for my late comments, I completely forgot to reply to the mail. My suggest was to be quite similar to what you proposed: Use the Renker draft as a starting point, nearly a sort of 'framework' to get the work going. Next, areas where the Renker document were deficient should be noted, and areas where the other candidates were strong be noted as well. From this, a conference call could be held to discuss the next steps in paging could be held. Most likely, the authors of the other documents could help move the new work group document forward. best regards, John -----Original Message----- From: ext Pat R. Calhoun [mailto:pcalhoun@bstormnetworks.com] Sent: 01 February, 2002 20:13 To: seamoby@ietf.org Subject: [Seamoby] Moving forward with paging -----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-----
- [Seamoby] Moving forward with paging Pat R. Calhoun
- RE: [Seamoby] Moving forward with paging john.loughney
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Yoshihiro Ohba
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- Re: [Seamoby] Moving forward with paging Yoshihiro Ohba
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging -resendiā¦ Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging rene.purnadi