Re: [Seamoby] Paging Triggers
"James Kempf" <kempf@docomolabs-usa.com> Mon, 17 December 2001 21:23 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 QAA18716 for <seamoby-archive@odin.ietf.org>; Mon, 17 Dec 2001 16:23:31 -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 QAA19240; Mon, 17 Dec 2001 16:11:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA19213 for <seamoby@ns.ietf.org>; Mon, 17 Dec 2001 16:11:42 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18387 for <seamoby@ietf.org>; Mon, 17 Dec 2001 16:11:37 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126]) by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBHLBAJ17777; Mon, 17 Dec 2001 13:11:10 -0800 (PST)
Message-ID: <01f001c1873f$20248c00$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
Cc: seamoby@ietf.org
References: <DC6C13921CCAFB49BCB8461164A3F4E38D216B@EXCHSRV.stormventures.com> <3C1BDB8B.4020101@alcatel.com> <005c01c18723$97c74a70$7e6015ac@T23KEMPF> <3C1E5AC1.2FE98AD1@alcatel.com>
Subject: Re: [Seamoby] Paging Triggers
Date: Mon, 17 Dec 2001 13:09:33 -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
Behcet, > I am afraid your comments on paging triggers could be misunderstood as if > Seamoby WG chairs are against defining paging triggers. > You know what Raj Patil (MIP WG) said in a recent mail: > >L2 triggers will not be discussed in the MIP WG meeting at SLC. While we > >do > >realize the importance of L2 triggers in enabling low-latency (MIPv4) > >and fast > >handoff (MIPv6), it is still undetermined as to in what WG or area of > >the IETF > >to do work related to this. > which I interpret as saying that MIP WG is supportive of trigger work. > If you are against I have a feeling that you have to make your case why > you are for defining triggers for low latency and fast handoff and not for > paging. > As Raj says for MIP and handover triggers, I believe the L2 triggers for paging work has some promise and is worthy of further investigation. However, we need to define the right context within IETF for the work. Hopefully, we will get this straightened out shortly. jak _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] WG Last Call: draft-ietf-seamoby-ct-req… Pat R. Calhoun
- Re: [Seamoby] Paging Protocol Assessment Presenta… Behcet Sarikaya
- Re: [Seamoby] Paging Protocol Assessment Presenta… James Kempf
- Re: [Seamoby] Paging Protocol Assessment Presenta… Behcet Sarikaya
- Re: [Seamoby] Paging Protocol Assessment Presenta… James Kempf
- Re: [Seamoby] Paging Triggers Behcet Sarikaya
- Re: [Seamoby] Paging Triggers James Kempf