Re: [Seamoby] Defining Paging Area
Pars MUTAF <pars.mutaf@inrialpes.fr> Wed, 19 December 2001 11:09 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 GAA26888 for <seamoby-archive@odin.ietf.org>; Wed, 19 Dec 2001 06:09:17 -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 FAA08434; Wed, 19 Dec 2001 05:53:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA08403 for <seamoby@optimus.ietf.org>; Wed, 19 Dec 2001 05:53:12 -0500 (EST)
Received: from ebene.inrialpes.fr (ebene.inrialpes.fr [194.199.18.70]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26718 for <seamoby@ietf.org>; Wed, 19 Dec 2001 05:53:07 -0500 (EST)
Received: from inrialpes.fr (lalena.inrialpes.fr [194.199.24.114]) by ebene.inrialpes.fr (8.11.6/8.11.6) with ESMTP id fBJAqtP03947; Wed, 19 Dec 2001 11:52:56 +0100 (MET)
Message-ID: <3C2071E4.7D29DC85@inrialpes.fr>
Date: Wed, 19 Dec 2001 11:54:28 +0100
From: Pars MUTAF <pars.mutaf@inrialpes.fr>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
CC: Kar Ann Chew <k.chew@eim.surrey.ac.uk>, seamoby@ietf.org
Subject: Re: [Seamoby] Defining Paging Area
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk> <3C1FE3D5.5D9061EA@alcatel.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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
Hello, Behcet Sarikaya wrote: > > What Pars and Claude talk about as PAs I think is a cell level or L1 > concept. I am having difficulty in understanding their theory. Hopefully they > will further develop it using L2 or L3 ideas so that we can grasp the theory > of dynamic paging areas. Only thereafter some standardization can be thought > of. Thank you for your comments (but I assume that your "L1" statement was a joke). A clarification: DPAC configures L3 paging areas. Seems like there is an ambiguity in the current version of the DPAC text. In fact, we should have chosen the term "IP subnet" instead of "cell". We were thinking about "L3 cells" . An L3 cell comprises one or more L2 cells. An L3 cell is nothing but an IP subnet. I'll change the text and adopt the same terminology (i.e. IP subnet) as RFC3132 (IP paging problem statement). Regards, pars _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] Defining Paging Area Kar Ann Chew
- Re: [Seamoby] Defining Paging Area Pars MUTAF
- RE: [Seamoby] Defining Paging Area Andrew T. Campbell
- Re: [Seamoby] Defining Paging Area Marco Liebsch
- Re: [Seamoby] Defining Paging Area Karann Chew
- Re: [Seamoby] Defining Paging Area James Kempf
- Re: [Seamoby] Defining Paging Area Behcet Sarikaya
- Re: [Seamoby] Defining Paging Area Pars MUTAF
- Re: [Seamoby] Defining Paging Area Pars MUTAF
- Re: [Seamoby] Defining Paging Area James Kempf
- Re: [Seamoby] Defining Paging Area Claude Castelluccia
- Re: [Seamoby] Defining Paging Area Claude Castelluccia
- Re: [Seamoby] Defining Paging Area James Kempf