Re: [Seamoby] Moving forward with paging

Behcet Sarikaya <behcet.sarikaya@alcatel.com> Wed, 06 February 2002 21:52 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 QAA03599 for <seamoby-archive@odin.ietf.org>; Wed, 6 Feb 2002 16:52:42 -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 QAA28434; Wed, 6 Feb 2002 16:39:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA28406 for <seamoby@optimus.ietf.org>; Wed, 6 Feb 2002 16:39:27 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03174 for <seamoby@ietf.org>; Wed, 6 Feb 2002 16:39:22 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80]) by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id PAA29606; Wed, 6 Feb 2002 15:38:55 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1]) by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g16LcsG28774; Wed, 6 Feb 2002 15:38:55 -0600 (CST)
Message-ID: <3C61A260.8060404@alcatel.com>
Date: Wed, 06 Feb 2002 15:38:40 -0600
From: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
Organization: Alcatel USA
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Pat R. Calhoun" <pcalhoun@bstormnetworks.com>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] Moving forward with paging
References: <DC6C13921CCAFB49BCB8461164A3F4E38D24D9@EXCHSRV.stormventures.com>
Content-Type: multipart/alternative; boundary="------------080303090600010908040200"
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


Pat R. Calhoun wrote:

>  
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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-----
>
Dear all,
  Based on the technical evaluation of all the drafts I posted in a 
previous mail on this thread, I propose draft-guri as the starting 
point. This draft uses all the entities of the requirements architecture 
and it does not make any assumptions on the mobility protocol mapping. 
This means the text from other drafts (security from draft-ohba, 
time-slot based paging from draft-sarikaya, mipv6 mappings from 
draft-renker and draft-koodli) can be easily incorporated. Along with 
its own goodies of the triggers, draft-guri would make a perfect 
starting point.
  My 2 euro cents.

-- 
Behcet