Re: [Seamoby] Defining Paging Area

"James Kempf" <kempf@docomolabs-usa.com> Tue, 18 December 2001 18:02 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 NAA23049 for <seamoby-archive@odin.ietf.org>; Tue, 18 Dec 2001 13:02:32 -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 MAA01160; Tue, 18 Dec 2001 12:48:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA01131 for <seamoby@optimus.ietf.org>; Tue, 18 Dec 2001 12:48:15 -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 MAA22849 for <seamoby@ietf.org>; Tue, 18 Dec 2001 12:48:11 -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 fBIHl9825088; Tue, 18 Dec 2001 09:47:09 -0800 (PST)
Message-ID: <00af01c187eb$cac66af0$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: Kar Ann Chew <k.chew@eim.surrey.ac.uk>, seamoby@ietf.org
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk>
Subject: Re: [Seamoby] Defining Paging Area
Date: Tue, 18 Dec 2001 09:45:32 -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

Kar Ann,

This is an entirely open question at this point. There is one draft out
there on the issue (draft-mutaf-dpac-00.txt),
but this just one approach, others are possible.

One of the major advantages of IP paging over strictly L2 paging is the
ability to do dynamic paging area configuration.
At some point, it might be useful to look into a protocol for dynamic
paging area configuration, but, for now,
I think it is more important that we get a paging protocol defined. Of
course, any paging area configuration protocol would
need to be independent of the policy used to configure the paging area.

            jak


----- Original Message -----
From: "Kar Ann Chew" <k.chew@eim.surrey.ac.uk>
To: <seamoby@ietf.org>
Sent: Tuesday, December 18, 2001 8:01 AM
Subject: [Seamoby] Defining Paging Area


>
> Hi,
> A simple question - How should Paging Areas be defined in IP network?
>
> Most of the paging proposals mention how to detect change of PA, and
> procedure of updating related entities, but not on how a PA is
defined?.
>
> Anyone, any pointers/advice on how to make paging area definition?  Or
we
> can simply leave is to cell planning people?
>
> Cheers,
> Karann
> ++++++++++++++++++++++++++++++++++++++++++
> Karann Chew
> Mobile Communications Research Group
> Centre for Communication Systems Research
> University of Surrey, Guildford
> Surrey GU2 7XH, United Kingdom
> Tel: +44 (0) 1483-876001
> Fax: +44 (0) 1483-876011
> ++++++++++++++++++++++++++++++++++++++++++
>
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
>


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